You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just as it can be useful to package (embed) a resource adapter and an application together, it could also be useful to be able to allow resource adapters to create what would normally be application defined resources like @ConnectionFactoryDefinition and @ConnectionFactoryDefinitions. This would allow the creation of a self-contained ear that could be deployed to any jakarta ee compliant app server w/o having to deal with server config.
The text was updated successfully, but these errors were encountered:
frowe
changed the title
Support for resource adapter defined resources like ConnectionFactory
Support for application defined resources of connectors like ConnectionFactory
Dec 11, 2021
frowe
changed the title
Support for application defined resources of connectors like ConnectionFactory
Support for creating connector spec resources like ConnectionFactory in Resource Adapters
Dec 13, 2021
If we did this, I could see putting them on the resource adapter's ManagedConnectionFactory implementation class alongside where it declares the @ConnectionDefinition annotation, in which case interfaceName as well as resourceAdapter attributes could be made optional,
Just as it can be useful to package (embed) a resource adapter and an application together, it could also be useful to be able to allow resource adapters to create what would normally be application defined resources like @ConnectionFactoryDefinition and @ConnectionFactoryDefinitions. This would allow the creation of a self-contained ear that could be deployed to any jakarta ee compliant app server w/o having to deal with server config.
The text was updated successfully, but these errors were encountered: