When selecting deployment isolation/call-by-value, the installer sets the values for the ear-deployer.xml and ejb-deployer.xml, but leaves the CallByValue setting false in naming.sar/META-INF/jboss-service.xml.

This guarantees ClassCastExceptions in what seems like the most common case:

1) A.ear makes a call to a remote service in B.ear
2) A.ear and B.ear are deployed into the same container

The ClassCastException is inescapable because the interface to B now lives in two separate classloaders (A's and B's) but the one registered in JNDI is always going to be B's.

I suspect most people turn on deployment isolation for the same reason our team does. We have a fairly large number of services, each as a separate ear, that get deployed to different servers in production. For development, we deploy all these services into a single container for convenience.

Deployment isolation/call-by-value works fine, but *only* if we also manually turn on CallByValue in the naming.sar. Why doesn't the installer set this value too?

Thanks,
Jeff Schnitzer