[jboss-jira] [JBoss JIRA] (WFLY-3292) EE Resource Definition Code Rework
Eduardo Martins (JIRA)
issues at jboss.org
Mon Apr 28 09:52:34 EDT 2014
[ https://issues.jboss.org/browse/WFLY-3292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12964109#comment-12964109 ]
Eduardo Martins commented on WFLY-3292:
---------------------------------------
[~jesper.pedersen] [~jmesnil] [~ctomc] [~swd847] I guess all of you have been involved with EE resource definitions before, thus I invite you all to have a look to changes in your code.
> EE Resource Definition Code Rework
> ----------------------------------
>
> Key: WFLY-3292
> URL: https://issues.jboss.org/browse/WFLY-3292
> Project: WildFly
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: EE, JCA, JMS, Mail, Naming
> Reporter: Eduardo Martins
> Assignee: Eduardo Martins
>
> This enhancement task provides a refresh/cleanup of all code related with EE resource definitions (as defined by EE.5.18).
> A major goal is to sync the logic that works out the deployment of all resource definitions (datasource, connection factory, administered objects, mail session, jms destination and jms connection factory), introducing specific abstract processors for both descriptors and annotations. These processors should continue to use the same functionality under the hood, i.e. feed BindingConfigurations to the same collections as any resource, but may allow in the future an easy split of deployment phase to install the related bindings, which should help the logic of dependent services.
> Another goal is to fix or provide missing functionality, such as support for <connection-factory /> and <administired-object />.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list