0 Replies Latest reply on Dec 14, 2003 1:39 AM by msalgado

    overriding container configuration defined in standardjboss.

    msalgado

      Hi,

      I've been successfully using the capabilities for overriding the commit option for CMP entity beans specified on in standardjboss.xml in the deployment's jboss.xml on jboss versions 3.2.1 and 3.2.2. I have tried the same approach without any success on jboss 3.2.3. However, if I change the commit option in standardjboss.xml everything works like it should. I would like the ability, though, to override commit options and other container configuration parameters on a per bean basis in 3.2.3 as in 3.2.1 and 3.2.2. This is an example of my jboss.xml

      <enterprise-beans>
      <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>

      <ejb-name>MyBean</ejb-name>
      <container-name>CMP 2.x and Cache</container-name>
      <local-jndi-name>MyBeanLocalHome</local-jndi-name>
      <method-attributes>
      <method>
      <method-name>get*</method-name>
      <read-only>true</read-only>
      </method>
      </method-attributes>
      <resource-ref>
      <res-ref-name>jdbc/oracleDB</res-ref-name>
      <jndi-name>java:/OracleDS</jndi-name>
      </resource-ref>
      </entity>
      </enterprise-beans>
      </jboss>

      All jboss versions are run on the same machine and connect to the same database, I'm using Java SDK 1.4.2.

      All help is greatly appreciated,

      Thanks,

      Manuel