[
https://issues.apache.org/jira/browse/OPENEJB-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Gawor resolved OPENEJB-1359.
----------------------------------
Fix Version/s: 3.2
Resolution: Fixed
Committed fixes (and a simple test case) in revision 999462.
As to module/ModuleName, module's moduleId will now be set to module-name
element if specified in the DD. Otherwise, the moduleId will be set to the id
attribute if set. And if the id attribute is not set in the DD the moduleId
will be set to a name based on the jar of the module. This seems to follow the
spec except the id attribute part. We might need to review this at some point.
> Application app/AppName is Null
> -------------------------------
>
> Key: OPENEJB-1359
> URL: https://issues.apache.org/jira/browse/OPENEJB-1359
> Project: OpenEJB
> Issue Type: Bug
> Components: ejb31
> Affects Versions: (trunk/openejb3)
> Reporter: Gurkan Erdogdu
> Assignee: Jarek Gawor
> Fix For: 3.2
>
>
> App context is created in Assembler,
> Context appJndiContext = new JndiEncBuilder(appInfo.appJndiEnc,
> appInjections, null, classLoader).build(JndiEncBuilder.JndiScope.app);
> app/AppName is created in JndiEncBuilder.buildMap(JndiScope.app), with
> if(moduleUri != null){
> bindings.put("app/AppName")
> }
> But moduleUri is always null
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
