-
Bug
-
Resolution: Done
-
Major
-
JBossAS-4.0.5.GA, JBossAS-4.2.0.GA
-
None
When overriding a container configuration, without specifying an explicit invoker-proxy-binding-name e.g.
<container-configurations>
<container-configuration extends="Standard CMP 2.x EntityBean">
<container-name>CMP 2.x and Cache</container-name>
<commit-option>A</commit-option>
</container-configuration>
</container-configurations>
Then, instead of deriving it from the base configuration invoker-proxy-binding-name (since we are extending it), it falls back to whatever is the hardcoded default, e.g. for entity beans in 4.2.x it is:
public class EntityMetaData
extends BeanMetaData
{
... public static final String DEFAULT_ENTITY_INVOKER_PROXY_BINDING =
"entity-unified-invoker";
- blocks
-
JBAS-4416 Introduce compatibility tests for interoperating with older jboss versions using the legacy rmi invokers
- Closed