This content has been marked as final. Show 1 reply
represents the public API for our JCA implementation. Hence it is important that we only expose what we will support over time.
The package will mostly consist of interfaces - as the implementation details should be hidden from the caller.
I think for now that only the
should remain in the package - without any methods defined. Just to define our top-level interface.
E.g. RealConnectionManager should be moved to the implementation package - it currently also creates a dependency on the implementation JAR, which an API JAR can't have. Its all or nothing ;)
Its better to start with the data structures in the implementation and move them out to the API if there are use-cases for it.
A good rule of thumb is to ask:
* Do I want users to call this method ?
* Do I want to expose this attribute as a bean property ?