Uploaded image for project: 'Application Server 3  4  5 and 6'
  1. Application Server 3 4 5 and 6
  2. JBAS-4444

The invoker-proxy-binding in the base container configuration is ignored on sub-configurations.

    XMLWordPrintable

    Details

    • Workaround Description:
      Hide

      Explicitly define the invoker-proxy-binding-name in the overriding configuration.

      Show
      Explicitly define the invoker-proxy-binding-name in the overriding configuration.

      Description

      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";

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  dimitris Dimitris Andreadis
                  Reporter:
                  dimitris Dimitris Andreadis
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  0 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: