[OPENEJB-1130] Stricter ClientModule classpath discovery prevents possible NameAlreadyBoundException

• Type: Improvement
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 3.1.1, 3.1.2
• Fix Version/s: 3.1.3
• Component/s: configuration, deployment
• Assignee: David Blevins
• Reporter: David Blevins
• Created: 13/Jan/10 21:47
• Updated: 19/Oct/10 03:51
• Resolved: 13/Jan/10 21:51

Description

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.