[jboss-jira] [JBoss JIRA] Closed: (JBAS-4444) The invoker-proxy-binding in the base container configuration is ignored on sub-configurations.

[Dimitris Andreadis (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBAS-4444?page=all ]

Dimitris Andreadis closed JBAS-4444.
------------------------------------

    Resolution: Done

Fixed.

> The invoker-proxy-binding in the base container configuration is ignored on sub-configurations.
> -----------------------------------------------------------------------------------------------
>
>                 Key: JBAS-4444
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4444
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: EJB2
>    Affects Versions: JBossAS-4.2.0.GA, JBossAS-4.0.5.GA
>            Reporter: Dimitris Andreadis
>         Assigned To: Dimitris Andreadis
>             Fix For:  JBossAS-5.0.0.Beta3, JBossAS-4.2.1.CR1
>
>
> 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";

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira