[
https://issues.apache.org/jira/browse/OPENEJB-1130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Blevins updated OPENEJB-1130:
-----------------------------------
Summary: Stricter ClientModule classpath discovery prevents possible
NameAlreadyBoundException (was: Stricter ClientModule classpath discovery
prevents NameAlreadyBoundException)
> Stricter ClientModule classpath discovery prevents possible
> NameAlreadyBoundException
> -------------------------------------------------------------------------------------
>
> Key: OPENEJB-1130
> URL: https://issues.apache.org/jira/browse/OPENEJB-1130
> Project: OpenEJB
> Issue Type: Improvement
> Components: configuration, deployment
> Affects Versions: 3.1.1, 3.1.2
> Reporter: David Blevins
> Assignee: David Blevins
> Priority: Critical
>
> Existing openejb.deployments.classpath.require.descriptor option now supports
> 'ejb' and 'client' as possible values (also ALL or NONE as synonyms for
> 'true' and 'false'). By default in an embedded environment this is set to
> 'client' which results in potential ClientModules (any jar with a Main-Class
> as per javaee specification) being ignored unless they have a
> META-INF/application-client.xml descriptor.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
