[jboss-jira] [JBoss JIRA] Commented: (JBAS-7798) Naming deployers should get module name from NamedModule attached to DeploymentUnit

[Brian Stansberry (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBAS-7798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12521233#action_12521233 ] 

Brian Stansberry commented on JBAS-7798:
----------------------------------------

Sounds reasonable. Note my comment on method names in http://community.jboss.org/wiki/VDFInformer though.

> 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