[
https://jira.jboss.org/jira/browse/JBAS-7798?page=com.atlassian.jira.plug...
]
Carlo de Wolf resolved JBAS-7798.
---------------------------------
Resolution: Rejected
I'm going to stick with the informer pattern. If we go to explicit metadata it needs
more than just NamedModule. You could argue that the deployer is therefore still unaware
of the means to obtaining the information. By sticking to this setup we can always switch
the means from analyzing existing metadata to consuming new metadata on a higher level.
http://community.jboss.org/wiki/VDFInformer
Naming deployers should get module name from NamedModule attached to
DeploymentUnit
-----------------------------------------------------------------------------------
Key: JBAS-7798
URL:
https://jira.jboss.org/jira/browse/JBAS-7798
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: Deployers
Reporter: Brian Stansberry
Assignee: Carlo de Wolf
Fix For: JBossAS-6.0.0.M3
See discussion thread linked from parent issue.
The ModuleNameDeployer created for the JBAS-7644 work attaches the metadata object that
implements the NamedModule interface to the DU under key NamedModule.class. The naming
deployers should get this attachment to find the module name, rather than using
NamingJavaEEModuleInformer.getModulePath().
Note that my JBAS-7644 work actually hacked NamingJavaEEModuleInformer.getModulePath() to
have it get the NamedModule attachment rather than returning a path. That was to allow the
deployer to get integrated and tested in hudson pending completion of this subtask.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira