+1.

Current implementation is dependent on packaging, which, while ensuring namespace-based unique values, immediately breaks all applications once JAR names change, are placed into an EAR, etc.

Bean providers must currently override default names using their own homebaked solution; I'd heavily made use of LocalBinding/RemoteBinding on every EJB just for this purpose. Pluggable policy would address this in one fell swoop.

S,
ALR

Would also make sense to determine what properties in a deployment might be interesting to a developer implementing a binding strategy, and pass this in:

String getJndiName(SomeNewEjb3DeploymentTO)

Not sure if an annotation is really useful. Makes most sense in jboss.xml or jboss-app.xml.

An entry in jboss-app.xml would also allow us to define a policy for all modules in the EAR; wouldn't require explicit definition on the part of the bean provider for each. Sounds very beneficial.

S,
ALR

http://jira.jboss.com/jira/browse/EJBTHREE-1101

I've added a default pluggable binding strategy that mirrors the legacy implementation.

Still TODO: Allow definition in jboss.xml, jboss-app.xml (optional for now).

API in org.jboss.ejb3.jndipolicy.DefaultJndiBindingPolicy

S,
ALR

Create a new artifact in projects/ejb3 so we can import one component into both 4.2 and 5.

For the xml I would to see an expression in the likes of: ${earName}/${deploymentName}/${beanName}/${interfaceType}

I don't want a requirement to create new classes when configuring xml stuff.

Alexey has added a String class name to JBossEnterpriseBeanMetaData. The DefaultJndiBindingPolicy/EjbDeploymentSummary interfaces could be part of metadata so that one can load the policy and use it in the determineJndiName() methods so that there is one method to call to obtain an ejb's jndi name.

Related to this is how the ProxyDeployer determines the remote interface binding jndi name. If I need to determine the target jndi name at reference resolution time, this needs to be set earlier.

Can this be done in JBoss 5.1.0? I would like a way to change the default naming behavior for all EJB jndi names, instead of using the LocalBinding/RemoteBinding annotation in code. Something like a external configuration done on jboss itself, not hard coded inside the applcation code.