You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "David Jencks (JIRA)" <de...@geronimo.apache.org> on 2005/03/13 17:36:52 UTC
[jira] Closed: (GERONIMO-606) gbeans in an application plan have no module component in their name
[ http://issues.apache.org/jira/browse/GERONIMO-606?page=history ]
David Jencks closed GERONIMO-606:
---------------------------------
Resolution: Fixed
Fix Version: 1.0-M4
Fixed in rev 157340, added J2EEModule=null to gbean names from application plan.
> gbeans in an application plan have no module component in their name
> --------------------------------------------------------------------
>
> Key: GERONIMO-606
> URL: http://issues.apache.org/jira/browse/GERONIMO-606
> Project: Geronimo
> Type: Bug
> Components: deployment
> Versions: 1.0-M3
> Reporter: David Jencks
> Assignee: David Jencks
> Fix For: 1.0-M4
>
> If you have gbeans in an application plan their names have no component "J2EEModule=foo". Furthermore, references specifying only the name component will look for a gbean with a "null=null" component instead of J2EEModule=foo. I think this is because the ear-level j2eeContext has no module component, since there isn't really a module.
> What should the "module" component be for a gbean that is in an application but no module? Should we name them
> J2EEApplication=appname,J2EEModule=null
> whereas a gbean in a gbean plan gets
> J2EEApplication=null,J2EEModule=moduleName?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira