Hi,
See below.
Penn wrote:
>
> Hi Richard and ole,
>
> It still doesn't work.
>
> below is the print out of the jboss.xml
>
>
> <?xml version="1.0" encoding="Cp1252"?>
>
> <jboss>
> <secure>false</secure>
> <container-configurations>
> <container-configuration
> configuration-class="org.jboss.ejb.deployment.EntityContainerConfiguration">
> <container-name>aa</container-name>
> <call-logging>false</call-logging>
>
> <container-invoker>org.jboss.ejb.plugins.jrmp13.server.JRMPContainerInvoker<
> /container-invoker>
> <instance-pool>org.jboss.ejb.plugins.EntityInstancePool</instance-pool>
> <instance-cache>org.jboss.ejb.plugins.EntityInstanceCache</instance-cache>
>
> <persistence-manager>org.jboss.ejb.plugins.BMPPersistenceManager</persistenc
> e-manager>
> <transaction-manager></transaction-manager>
> <authentication-module></authentication-module>
> <role-mapping-manager></role-mapping-manager>
> <container-invoker-conf>
> <Optimized>true</Optimized>
> </container-invoker-conf>
> <container-cache-conf>
>
> <cache-policy>org.jboss.ejb.plugins.LRUEnterpriseContextCachePolicy</cache-p
> olicy>
> <cache-policy-conf>
> <min-capacity>0</min-capacity>
> <max-capacity>0</max-capacity>
> <overager-period>0</overager-period>
> <resizer-period>0</resizer-period>
> <max-bean-age>0</max-bean-age>
> <max-cache-miss-period>0</max-cache-miss-period>
> <min-cache-miss-period>0</min-cache-miss-period>
> <cache-load-factor>0.0</cache-load-factor>
> </cache-policy-conf>
> </container-cache-conf>
> <container-pool-conf>
> <MaximumSize>100</MaximumSize>
> <MinimumSize>10</MinimumSize>
> </container-pool-conf>
> <commit-option>B</commit-option>
> </container-configuration>
> </container-configurations>
> <resource-managers />
> <enterprise-beans>
> <entity>
> <ejb-name>AuctionRoomEB</ejb-name>
> <jndi-name>JNDIAUCEBAuctionRoom</jndi-name>
> <configuration-name></configuration-name>
No configuration name specified?
You should specify the name of the
configuration you created (aa),
otherwise JBoss does not know that
your bean is using this particular
configuration.
> </entity>
> </enterprise-beans>
> </jboss>
>
> any clue ?????
It is somewhat simpler to just do
an incremental specification of
one of the existing container
configurations:
<jboss>
<container-configurations>
<container-configuration>
<container-name>Standard BMP EntityBean</container-name>
<commit-option>B</commit-option>
</container-configuration>
</container-configurations>
<enterprise-beans>
<entity>
<ejb-name>AuctionRoomEB</ejb-name>
<jndi-name>JNDIAUCEBAuctionRoom</jndi-name>
<configuration-name>Standard BMP EntityBean</configuration-name>
</entity>
</enterprise-beans>
</jboss>
This will do a (ejb jar local) change
to the standard BMP configuration as
specified in standardjboss.xml.
An advantage of this is that if a new
version of JBoss requires some new
configuration options, they will be
automagically used in your custom
container configuration.
Best Regards,
Ole Husgaard.
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
List Help?: [EMAIL PROTECTED]
