JBoss/Hibernate/InstantClient/RAC

Hi,
First, I have no experience with RAC. I have RAC on two machines with one storage and want to use with load balancing and TAF. On next machine I have JBoss AS where I connect to Oracle via Hibernate whith thin client. All connection data I have in hibernate.cfg.xml file, where I point one database form RAC. I don't have full client on JBoss' host. Is it correct configuration? I saw, when full client is installed in tnsname.ora one sid points two hosts.
Thanx, Jacek

Here is stack trace: LocalManagedConnectionFactory.createManagedConnection crashes at line 160.
We believe that the problem is in hotdeployment: JBoss does not manage to undeploy the application and connections and that is why hotdeployment fails when Hibernate asks for a connection from JBoss connection manager. I use jTDS driver, but problems occur with MS JDBC Driver too.
09:15:50,995 WARN [JBossManagedConnectionPool] Throwable while attempting to get a new connection:
org.jboss.resource.JBossResourceException: Could not create connection; - nested throwable: (java.lang.RuntimeException: No message resource found for message property prop.servertype)
at org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.createManagedConnection(LocalManagedConnectionFactory.java:160)
at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.createConnectionEventListener(InternalManagedConnectionPool.java:477)
at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.getConnection(InternalManagedConnectionPool.java:213)
at org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BasePool.getConnection(JBossManagedConnectionPool.java:496)
at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(BaseConnectionManager2.java:425)
at org.jboss.resource.connectionmanager.TxConnectionManager.getManagedConnection(TxConnectionManager.java:318)
at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:477)
at org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseConnectionManager2.java:814)
at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:122)
at net.sf.hibernate.connection.DatasourceConnectionProvider.getConnection(DatasourceConnectionProvider.java:56)
at net.sf.hibernate.cfg.SettingsFactory.buildSettings(SettingsFactory.java:72)

Similar Messages

  • JBoss Can't find Oracle Driver

    Hello, everyone,
    I'm hoping someone can help me.
    I've created a small web service. I have one method which returns something very straight forward, and it works fine.
    I have then progressed this to try to return some data from an Oracle table.
    However, when I try to do this, I get an error back saying that the Oracle Driver can not be found.
    I am using JBoss, and am running this in Eclipse's Web Service Explorer.
    The things I have tried to solve the issue are:
    - Ensuring the Oracle driver is located in Windows>Preferences>General>Data Management>Connectivity>Driver Definitions
    - Placing the Oracle driver jar in as many lib folders in my JBoss directory on my C drive as possible (I may have missed some out).
    I am not sure what else to try. Please can someone help me or point me in the right direction?
    Any help would be hugely appreciated.
    Thank you very much in advance.
    Robin
    My stacktrace is as follows:
    [code]
    java.lang.ClassNotFoundException: oracle.jdbc.OracleDriver from BaseClassLoader@1652e61{VFSClassLoaderPolicy@1c7eb33{name=vfsfile:/C:/Jboss/jboss-5.0.0.GA/server/default/conf/jboss-service.xml domain=ClassLoaderDomain@9fe84e{name=DefaultDomain parentPolicy=BEFORE parent=org.jboss.system.NoAnnotationURLClassLoader@a97b0b} roots=[MemoryContextHandler@2254409[path= context=vfsmemory://4shc4f-nlo6vf-hjk3qb83-1-hjk3qewj-6 real=vfsmemory://4shc4f-nlo6vf-hjk3qb83-1-hjk3qewj-6], DelegatingHandler@6903079[path=antlr.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/antlr.jar], DelegatingHandler@22387624[path=autonumber-plugin.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/autonumber-plugin.jar], DelegatingHandler@22963857[path=bcel.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/bcel.jar], DelegatingHandler@10479206[path=bsf.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/bsf.jar], DelegatingHandler@30371681[path=bsh.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/bsh.jar], DelegatingHandler@26839239[path=commons-collections.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/commons-collections.jar], DelegatingHandler@14875150[path=commons-httpclient.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/commons-httpclient.jar], DelegatingHandler@26137220[path=commons-logging.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/commons-logging.jar], DelegatingHandler@27193209[path=dtdparser121.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/dtdparser121.jar], DelegatingHandler@24916054[path=edb-jdbc14.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/edb-jdbc14.jar], DelegatingHandler@4824957[path=ejb3-persistence.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ejb3-persistence.jar], DelegatingHandler@25551189[path=el-api.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/el-api.jar], DelegatingHandler@9229531[path=hibernate-annotations.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/hibernate-annotations.jar], DelegatingHandler@32148925[path=hibernate-commons-annotations.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/hibernate-commons-annotations.jar], DelegatingHandler@33522601[path=hibernate-core.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/hibernate-core.jar], DelegatingHandler@1899900[path=hibernate-entitymanager.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/hibernate-entitymanager.jar], DelegatingHandler@21354482[path=hibernate-jmx.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/hibernate-jmx.jar], DelegatingHandler@6588912[path=hibernate-validator.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/hibernate-validator.jar], DelegatingHandler@10229202[path=hsqldb-plugin.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/hsqldb-plugin.jar], DelegatingHandler@22852149[path=hsqldb.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/hsqldb.jar], DelegatingHandler@12046052[path=ibatis-2.3.4.726.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ibatis-2.3.4.726.jar], DelegatingHandler@24115680[path=jaxen.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jaxen.jar], DelegatingHandler@8259012[path=jboss-bindingservice.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-bindingservice.jar], DelegatingHandler@28085047[path=jboss-common-jdbc-wrapper.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-common-jdbc-wrapper.jar], DelegatingHandler@15191255[path=jboss-current-invocation-aspects.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-current-invocation-aspects.jar], DelegatingHandler@3753755[path=jboss-ejb3-cache.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-ejb3-cache.jar], DelegatingHandler@7028679[path=jboss-ejb3-common.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-ejb3-common.jar], DelegatingHandler@19417347[path=jboss-ejb3-core.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-ejb3-core.jar], DelegatingHandler@30502607[path=jboss-ejb3-deployers.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-ejb3-deployers.jar], DelegatingHandler@12704779[path=jboss-ejb3-ext-api-impl.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-ejb3-ext-api-impl.jar], DelegatingHandler@22379127[path=jboss-ejb3-ext-api.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-ejb3-ext-api.jar], DelegatingHandler@14371981[path=jboss-ejb3-interceptors.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-ejb3-interceptors.jar], DelegatingHandler@25089808[path=jboss-ejb3-metadata.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-ejb3-metadata.jar], DelegatingHandler@5868125[path=jboss-ejb3-proxy-clustered.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-ejb3-proxy-clustered.jar], DelegatingHandler@9114403[path=jboss-ejb3-proxy.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-ejb3-proxy.jar], DelegatingHandler@9795777[path=jboss-ejb3-security.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-ejb3-security.jar], DelegatingHandler@19590177[path=jboss-ejb3-transactions.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-ejb3-transactions.jar], DelegatingHandler@16028187[path=jboss-ha-client.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-ha-client.jar], DelegatingHandler@10766816[path=jboss-ha-server-api.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-ha-server-api.jar], DelegatingHandler@32391332[path=jboss-ha-server-cache-jbc.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-ha-server-cache-jbc.jar], DelegatingHandler@14017136[path=jboss-ha-server-cache-spi.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-ha-server-cache-spi.jar], DelegatingHandler@345667[path=jboss-hibernate.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-hibernate.jar], DelegatingHandler@4725080[path=jboss-iiop.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-iiop.jar], DelegatingHandler@24635060[path=jboss-integration.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-integration.jar], DelegatingHandler@13327669[path=jboss-jaspi-api.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-jaspi-api.jar], DelegatingHandler@22302276[path=jboss-javaee.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-javaee.jar], DelegatingHandler@31347466[path=jboss-jca.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-jca.jar], DelegatingHandler@18733404[path=jboss-jmx-remoting.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-jmx-remoting.jar], DelegatingHandler@11086506[path=jboss-jpa-deployers.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-jpa-deployers.jar], DelegatingHandler@3152885[path=jboss-jsr77.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-jsr77.jar], DelegatingHandler@8104009[path=jboss-jsr88.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-jsr88.jar], DelegatingHandler@6656120[path=jboss-management.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-management.jar], DelegatingHandler@32490450[path=jboss-messaging-int.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-messaging-int.jar], DelegatingHandler@2167036[path=jboss-messaging.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-messaging.jar], DelegatingHandler@14820075[path=jboss-metadata.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-metadata.jar], DelegatingHandler@6467398[path=jboss-monitoring.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-monitoring.jar], DelegatingHandler@14768745[path=jboss-profileservice.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-profileservice.jar], DelegatingHandler@16166715[path=jboss-remoting-aspects.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-remoting-aspects.jar], DelegatingHandler@23747954[path=jboss-remoting.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-remoting.jar], DelegatingHandler@1902564[path=jboss-security-aspects.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-security-aspects.jar], DelegatingHandler@32586504[path=jboss-security-spi.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-security-spi.jar], DelegatingHandler@5935979[path=jboss-serialization.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-serialization.jar], DelegatingHandler@8687994[path=jboss-srp.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-srp.jar], DelegatingHandler@23794987[path=jboss-sunxacml.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-sunxacml.jar], DelegatingHandler@20627169[path=jboss-transaction-aspects.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-transaction-aspects.jar], DelegatingHandler@30003582[path=jboss-xacml.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss-xacml.jar], DelegatingHandler@14199075[path=jboss.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jboss.jar], DelegatingHandler@4740342[path=jbossas-remoting.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jbossas-remoting.jar], DelegatingHandler@12716179[path=jbossha.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jbossha.jar], DelegatingHandler@12653911[path=jbossjta-integration.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jbossjta-integration.jar], DelegatingHandler@6300663[path=jbossjta.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jbossjta.jar], DelegatingHandler@31019059[path=jbosssx-server.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jbosssx-server.jar], DelegatingHandler@2115134[path=jbosssx.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jbosssx.jar], DelegatingHandler@14919969[path=jbossts-common.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jbossts-common.jar], DelegatingHandler@7651652[path=jbossws-common.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jbossws-common.jar], DelegatingHandler@20739678[path=jbossws-framework.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jbossws-framework.jar], DelegatingHandler@8331318[path=jbossws-native-jaxrpc.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jbossws-native-jaxrpc.jar], DelegatingHandler@1823783[path=jbossws-native-jaxws-ext.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jbossws-native-jaxws-ext.jar], DelegatingHandler@17125267[path=jbossws-native-jaxws.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jbossws-native-jaxws.jar], DelegatingHandler@28000914[path=jbossws-native-saaj.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jbossws-native-saaj.jar], DelegatingHandler@10464309[path=jbossws-spi.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jbossws-spi.jar], DelegatingHandler@14869110[path=jmx-adaptor-plugin.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jmx-adaptor-plugin.jar], DelegatingHandler@25281771[path=jnpserver.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jnpserver.jar], DelegatingHandler@10968735[path=joesnmp.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/joesnmp.jar], DelegatingHandler@3486913[path=jsp-api.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/jsp-api.jar], DelegatingHandler@18513535[path=log4j-snmp-appender.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/log4j-snmp-appender.jar], DelegatingHandler@6749397[path=log4j.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/log4j.jar], DelegatingHandler@23142099[path=mail-plugin.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/mail-plugin.jar], DelegatingHandler@19847791[path=mail.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/mail.jar], DelegatingHandler@17226797[path=properties-plugin.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/properties-plugin.jar], DelegatingHandler@23150623[path=quartz.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/quartz.jar], DelegatingHandler@28882952[path=scheduler-plugin-example.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/scheduler-plugin-example.jar], DelegatingHandler@3816987[path=scheduler-plugin.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/scheduler-plugin.jar], DelegatingHandler@29594642[path=servlet-api.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/servlet-api.jar], DelegatingHandler@19811980[path=slf4j-api.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/slf4j-api.jar], DelegatingHandler@19335035[path=slf4j-jboss-logging.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/slf4j-jboss-logging.jar]] delegates=null exported=[, org.hibernate.loader.collection, org.jboss.deployers.spi.management.deploy, org.jboss.remoting.transporter, org.jboss.ejb3.proxy.clustered.objectfactory.session.stateful, com.arjuna.ats.txoj.semaphore, org.jboss.varia.property, com.arjuna.common.util.propertyservice, com.arjuna.common.util.logging, org.jboss.jms.server.messagecounter, org.jboss.ejb3.proxy.invocation, org.jboss.remoting.invocation, org.jboss.remoting.samples.transporter.proxy, javax.persistence, org.hibernate.engine.loading, org.jboss.security.xacml.sunxacml.combine, org.jboss.jms.client.remoting, com.arjuna.ats.internal.txoj.recovery, org.jboss.remoting.samples.transporter.serialization.server, javax.xml.registry.infomodel, org.jboss.resource.adapter.jdbc.remote, org.jboss.resource.spi.timer, org.jboss.ha.cachemanager, org.jboss.web.tomcat.service.session.distributedcache.spi, org.jboss.ejb3.timerservice, org.jboss.wsf.test, org.jboss.ejb3.cluster.metadata, org.jboss.metadata.annotation.creator.client, org.jboss.resource.statistic.formatter, com.arjuna.ats.internal.jta.transaction.arjunacore, org.jboss.ejb3.proxy.handler.stateless, com.edb.util, org.jboss.security.mapping.providers.principal, org.jboss.hibernate.deployers.metadata, org.jboss.wsf.common.management, org.jboss.resource.metadata, javax.enterprise.deploy.spi, com.ibatis.common.logging.log4j, org.apache.log4j.lf5, org.jboss.remoting.detection.jndi, org.jboss.security.integration, com.arjuna.common.internal.util.logging.simpleLog, org.jboss.jms.server.remoting, org.jboss.ejb3.metadata, org.hibernate.cache.access, META-INF.maven.org.jboss.cluster.jboss-ha-server-api, org.jboss.remoting.samples.transporter.basic, org.apache.bsf.util, org.jboss.ejb3.proxy.handler.session.service, org.hibernate.intercept.cglib, org.jboss.remoting.transport.sslrmi, org.hibernate.proxy, org.apache.bcel.verifier.exc, org.jboss.remoting.stream, org.apache.log4j.varia, org.hibernate.cache, org.jboss.jmx.adaptor.rmi, org.jboss.security.auth.container.config, org.jboss.ejb3.timerservice.jboss, org.hibernate.usertype, javax.security.auth.message.module, org.jboss.management.j2ee.statistics, org.jboss.remoting, org.jboss.serial.util, org.jboss.security.acl.config, com.ibatis.sqlmap.engine.mapping.sql.dynamic.elements, org.jboss.resource.adapter.jdbc.vendor, META-INF.maven.org.jboss.ws.native.jbossws-native-saaj, org.jboss.resource.adapter.jdbc, org.hibernate.ejb.event, org.jboss.metadata.validation.chain.ejb.jboss, com.arjuna.ats.jta.utils, javax.servlet, org.jboss.monitor.alerts, org.hibernate.annotations, org.jboss.jms.wireformat, com.arjuna.ats.internal.arjuna.objectstore.jdbc, antlr.debug.misc, org.jboss.security.xacml.jaxb, org.jboss.ejb3.deployers, com.edb.ds, org.hibernate.hql.ast.exec, com.ibatis.common.jdbc, org.jboss.metadata.process.processor, org.jboss.wsf.spi.util, org.hibernate.context, org.jboss.remoting.samples.detection.multicast, org.jboss.jmx.connector.invoker, javax.enterprise.deploy.model, org.jboss.web.tomcat.service.session.distributedcache.impl.jbc, xmdesc, org.jboss.ejb3.interceptors.container, org.jboss.ejb3.proxy.objectfactory.session, org.jboss.remoting.transport.web, org.hibernate.id.enhanced, javax.enterprise.deploy.shared, org.jboss.metadata.common.jboss, org.jboss.ejb3.enc, org.jboss.ejb3.proxy.factory, org.jboss.remoting.samples.callback.statistics, com.arjuna.ats.jta.xa, org.jboss.proxy.ejb.handle, org.jboss.ejb3.proxy.clustered.factory.session.stateful, org.jboss.metadata.serviceref, javax.mail.event, org.apache.bsf.engines.xslt, org.jaxen.pattern, org.jboss.ha.client.loadbalance, org.apache.log4j.lf5.viewer, org.jboss.ejb.plugins.cmp.jdbc, org.jboss.metadata.annotation.finder, org.jboss.jms.server.security, org.jboss.aspects.currentinvocation, org.jboss.wsf.framework.serviceref, org.jboss.web.tomcat.service.session.distributedcache.impl, org.jboss.ejb3.dependency, com.arjuna.ats.jbossatx.jta, org.jboss.iiop.jacorb, org.apache.bcel.generic, org.slf4j.helpers, org.quartz.plugins.xml, com.arjuna.ats.txoj.lockstore, com.edb.core.v2, org.jboss.ejb3.proxy.objectstore, com.sun.mail.handlers, com.ibatis.sqlmap.engine.transaction.user, org.jboss.remoting.serialization.impl.java, org.jboss.metadata.jpa.spec, com.edb.core.v3, org.hibernate.intercept.javassist, org.jboss.injection.lang.reflect, org.jboss.ejb3.protocol.jarjar, org.jboss.remoting.transport.servlet, com.arjuna.ats.internal.jta.xa, com.edb.fastpath, org.jboss.ha.client.loadbalance.aop, org.hibernate.stat, javax.xml.ws, org.jboss.invocation.iiop, com.arjuna.ats.tsmx.mbeans, com.ibatis.sqlmap.engine.impl, org.jboss.varia.autonumber, org.jboss.deployers.spi.management, org.quartz.simpl, com.edb.largeobject, org.jboss.security.plugins.acl, org.jboss.deployment.services, org.jboss.profileservice.management, org.quartz.jobs, javax.xml.rpc.handler.soap, org.hibernate.impl, com.arjuna.ats.internal.arjuna.gandiva.nameservice, org.hibernate.event.def, org.jboss.remoting.samples.multiplex, org.hibernate.persister, org.hibernate.ejb.transaction, org.hibernate.validator.resources, org.jboss.ejb3.proxy.clustered.handler.session.stateful, org.jboss.remoting.marshal.serializable, org.jboss.remoting.samples.transporter.complex.server, org.jboss.security.mapping.providers, org.jboss.wsf.framework.management.recording, org.jboss.messaging.core.impl.jchannelfactory, org.jnp.interfaces, org.jboss.verifier, javax.xml.rpc, org.apache.commons.httpclient.methods, org.opennms.protocols.snmp.asn1, org.jboss.ejb3.interceptors.currentinvocation, org.hibernate.tool.instrument.cglib, org.jboss.client, org.hibernate.annotations.common.reflection.java, bsh.util.lib, com.edb.translation, org.jboss.remoting.samples.transporter.multiple.client, org.jboss.ha.hasessionstate.server, org.jboss.security.xacml.interfaces, com.ibatis.sqlmap.engine.transaction.jdbc, org.jboss.iiop.test, org.quartz.core, org.jboss.ejb.plugins.cmp.jdbc2.schema, org.jboss.ejb3.interceptors.proxy, META-INF.maven.org.jboss.jpa.jboss-jpa-deployers, com.arjuna.ats.txoj.logging, com.arjuna.ats.internal.arjuna.template, org.jboss.metadata.ejb.spec, org.hibernate.type, com.arjuna.ats.arjuna.gandiva.inventory, javax.xml.ws.http, com.arjuna.ats.jbossatx.logging, org.jboss.verifier.strategy, org.apache.commons.httpclient.protocol, com.ibatis.sqlmap.engine.mapping.sql.raw, org.jboss.remoting.samples.transporter.custom.server, org.apache.bsf.util.event.adapters, org.apache.log4j.lf5.viewer.images, org.apache.commons.collections.set, org.hibernate.loader, org.jboss.jms.delegate, org.jboss.services.binding, org.hibernate.engine, org.quartz.spi, META-INF.maven.org.jboss.ws.jbossws-common, org.jboss.security.propertyeditor, org.jboss.ha.framework.server.util, META-INF.maven.org.jboss.security.jboss-sunxacml, org.jboss.mail, org.jboss.remoting.detection.util, org.jboss.ejb, org.jboss.wsf.spi.metadata.j2ee.serviceref, com.arjuna.ats.jdbc, org.jboss.ha.jndi.spi, org.hsqldb.jdbc, org.jboss.serial.objectmetamodel, com.arjuna.ats.internal.jta.transaction.arjunacore.subordinate.jca, META-INF.maven.org.hibernate.hibernate-core, javax.mail.util, org.apache.log4j.nt, org.jboss.security.srp, com.arjuna.ats.internal.txoj.semaphore, com.arjuna.common.internal.util.propertyservice.plugins.io, com.arjuna.ats.internal.jbossatx.jta.jca, org.jboss.security.xacml.locators, org.hibernate.tuple, org.jboss.remoting.transport.rmi, org.hibernate.annotations.common.reflection, org.jboss.web, bsh.reflect, org.hibernate.classic, org.hibernate.ejb.connection, org.jboss.security.xacml.util, org.jboss.security.ssl, org.jboss.ejb3.mdb, javax.transaction.xa, org.hsqldb, org.apache.bsf.engines.netrexx, com.arjuna.ats.jta.common, org.hibernate.jdbc.util, javax.security.auth.message.config, com.ibatis.sqlmap.engine.cache.oscache, com.wutka.dtd, org.jboss.jms.server.connectormanager, org.jboss.wsf.spi.transport, org.jboss.metadata.process.processor.ejb.jboss, org.omg.stub.javax.ejb, org.jboss.jpa.tx, org.hibernate.loader.entity, org.jboss.remoting.samples.oneway, org.jboss.messaging.core.impl.clusterconnection, org.jboss.wsf.spi.deployment, org.jboss.ejb3.interceptors.direct, antlr.collections.impl, org.apache.log4j.or, org.hibernate, javax.xml.rpc.soap, com.ibatis.sqlmap.engine.mapping.result, com.ibatis.common.logging.nologging, com.arjuna.ats.internal.tsmx.agent.exceptions, org.jboss.ha.jndi, org.hsqldb.sample, org.hibernate.bytecode.util, org.hsqldb.lib, com.arjuna.ats.txoj.exceptions, org.jboss.ejb3.metamodel, org.apache.log4j.or.jms, javax.management.remote.rmi, META-INF.maven.org.jboss.ws.native.jbossws-native-jaxws-ext, javax.interceptor, org.jboss.wsf.spi.tools.ant, security, org.jboss.resource.timer, com.arjuna.ats.tsmx.agent.exceptions, org.jboss.ejb3.proxy.objectfactory.session.stateless, com.arjuna.ats.jta.transaction, org.jboss.ejb3.metadata.plugins.loader, org.jboss.deployment.vfs, com.arjuna.ats.internal.jta.recovery.arjunacore, org.jaxen, com.ibatis.sqlmap.engine.execution, com.ibatis.sqlmap.engine.cache.memory, com.arjuna.ats.jta.resources, org.jboss.wsf.common.logging, com.arjuna.ats.arjuna.utils, org.jboss.ejb3.aop, META-INF.maven.org.jboss.ejb3.jboss-ejb3-security, org.jboss.jms.client.delegate, bsh.commands, com.arjuna.ats.tsmx.agent, org.jboss.security.xacml.sunxacml.support, org.jboss.serial.finalcontainers, com.arjuna.ats.internal.txoj.lockstore, org.jboss.resource.security, org.jboss.messaging.core.impl.tx, org.jboss.resource.connectionmanager, javax.xml.ws.addressing.soap, org.quartz.impl.calendar, com.arjuna.ats.internal.jdbc.drivers, org.jboss.deployment.dependency, org.jboss.security.identity.fed, org.jboss.ejb3.kernel, com.edb.ds.common, META-INF.maven.org.jboss.ejb3.jboss-ejb3-proxy-clustered, org.jboss.wsf.framework, com.arjuna.ats.arjuna.coordinator, org.jboss.services.binding.impl, org.jboss.invocation, javax.servlet.http, com.arjuna.common.internal.util.licence.utils, org.jboss.metadata.validation, javax.jws, org.hibernate.bytecode, org.jboss.jms.exception, org.jboss.security.mapping, org.apache.log4j.spi, org.jboss.ejb3.interceptors.lang, com.arjuna.ats.arjuna.gandiva.nameservice, org.jboss.security.xacml.sunxacml.ctx, org.jboss.ejb3.naming, org.jboss.messaging.core.impl, org.jboss.jpa.resolvers, org.jboss.remoting.samples.transporter.clustered.server, org.hsqldb.util.sqltool, org.jboss.hibernate.deployers, org.jboss.ejb.plugins.local, org.jboss.monitor, org.jboss.remoting.samples.transporter.proxy.client, org.hibernate.cache.entry, org.quartz, org.hibernate.hql, org.jboss.security.auth.spi, com.arjuna.common.util, org.hibernate.transform, org.hibernate.tuple.component, org.jboss.ejb3.cache.persistence, org.jboss.invocation.pooled.server, org.jboss.security.identitytrust.modules, org.jboss.metadata.common.spi, com.arjuna.ats.internal.jta.utils, org.jboss.security.authorization.modules, org.jboss.verifier.event, org.jboss.iiop.rmi.marshal, org.jboss.ejb3.proxy.clustered.registry, org.apache.log4j.jdbc, com.arjuna.ats.internal.jta.resources.errorhandlers, org.jboss.ejb3.proxy.clustered.familyname, org.apache.bcel.util, org.jboss.annotation.javaee, org.jboss.ejb3.metadata.annotation, org.hibernate.sql, org.jboss.messaging.util, org.jboss.ejb.plugins.cmp.jdbc.metadata, com.arjuna.common.util.propertyservice.propertycontainer, org.jboss.invocation.http.server, org.hsqldb.persist, org.jboss.remoting.transport.sslsocket, com.arjuna.ats.arjuna.state, org.jboss.ejb3.interceptors.aop, org.hibernate.lob, org.jboss.ejb3.security.helpers, org.jboss.wsf.spi.management, org.jboss.remoting.detection.multicast, org.jboss.security.authorization.modules.web, antlr.build, org.hibernate.persister.entity, com.edb.stream, org.jboss.classloading.spi, org.jboss.metadata.rar.jboss, org.jboss.jpa.injection, org.apache.bsf.engines.jacl, org.jboss.mx.remoting.event, org.jboss.ejb3.proxy.jndiregistrar, META-INF.maven.org.jboss.ejb3.jboss-ejb3-ext-api, org.jboss.jca.spi, org.jboss.remoting.samples.bisocket, org.apache.log4j.lf5.viewer.configure, org.jboss.ejb3.common.registrar.spi, org.jboss.ejb3.security.embedded.plugins, org.jboss.crypto.digest, org.jboss.naming.java, org.jboss.security.xacml.sunxacml, org.jboss.remoting.samples.transporter.complex, META-INF.maven.org.jboss.ejb3.jboss-ejb3-ext-api-impl, com.arjuna.ats.arjuna.thread, org.apache.commons.collections.map, javax.xml.rpc.holders, org.jboss.jms.server.plugin.contract, org.jboss.ejb3.interceptors.registry, org.jboss.tm.usertx.client, com.arjuna.ats.txoj, org.hibernate.cfg.search, org.jboss.remoting.transport.bisocket, org.jboss.resource.binding.remote, org.jboss.wsf.framework.transport, org.jboss.ejb3.injection, com.arjuna.ats.txoj.common, org.jboss.wsf.spi.serviceref, com.ibatis.sqlmap.client.extensions, com.ibatis.sqlmap.engine.cache.fifo, javax.security.jacc, META-INF.maven.org.jboss.ws.native.jbossws-native-jaxrpc, org.jboss.wsf.common.utils, org.jboss.jms.server.bridge, com.arjuna.ats.internal.arjuna, javax.enterprise.deploy.spi.exceptions, org.quartz.xml, org.jboss.management.j2ee, org.jboss.deployment.spi.configurations, bsh.servlet, org.jboss.aspects.tx, org.apache.commons.collections.iterators, org.jboss.serial.io, com.ibatis.sqlmap.engine.accessplan, com.edb.core.charset, org.hibernate.cfg.annotations.reflection, org.hibernate.id, org.jboss.ejb3.proxy.handler.session, org.jboss.ejb3.common.thread, com.arjuna.common, org.jboss.jpa.util, org.jboss.deployment, javax.ejb.spi, bsh.collection, org.jboss.metamodel.descriptor, org.jboss.profileservice.management.upload, org.jboss.invocation.local, META-INF.maven.org.slf4j.slf4j-api, org.jaxen.function, META-INF.maven.org.jboss.cluster.jboss-ha-client, org.jboss.security.microcontainer.beans.metadata, com.arjuna.ats.arjuna.objectstore.jdbc, org.jboss.remoting.samples.multiplex.invoker, org.jaxen.javabean, org.jboss.ejb3.tx.container, org.jboss.lang.ref, org.hsqldb.resources, org.jboss.security.xacml.sunxacml.finder.impl, org.jboss.ejb3.common.spi, com.edb, org.jboss.metadata.process.chain.ejb.jboss, org.jboss.security.xacml.sunxacml.support.finder, org.jboss.jms.server.container, org.jboss.profileservice.management.templates, org.apache.bsf.util.cf, org.quartz.utils, org.jboss.ha.framework.test, org.hibernate.validator.event, javax.security.auth.message.callback, org.jboss.ejb3.common.lang, org.hsqldb.lib.java, org.jboss.ejb3.proxy.intf, org.jboss.iiop.naming, org.jboss.security.xacml.bridge, org.jboss.remoting.samples.chat, org.jnp.server, org.hsqldb.scriptio, org.apache.commons.httpclient.methods.multipart, org.jboss.ejb3.proxy.factory.stateful, org.jboss.metadata.client.spec, org.w3c.dom, com.arjuna.ats.tsmx.common, org.jaxen.function.ext, javax.management.remote, com.arjuna.ats.internal.jbossatx.jta, org.jboss.ejb3.security.annotation, org.jnp.interfaces.java, org.jboss.ejb3.entity.hibernate, bsh, org.apache.log4j.lf5.util, org.quartz.plugins.management, org.jaxen.saxpath.helpers, org.jboss.metadata.annotation.creator.ws, org.jboss.remoting.samples.transporter.proxy.server, javax.jms, org.jboss.ejb3.util, antlr.actions.python, org.hibernate.loader.custom, stylesheets, org.jnp.client, javax.jws.soap, org.jboss.profileservice.management.upload.remoting, org.jboss.ejb3.common.string, org.hibernate.engine.query.sql, org.jboss.ejb3.metadata.spi.signature, org.jboss.metadata.validation.validator.ejb.jboss, org.jboss.ejb3.javaee, javax.resource.spi, org.hibernate.persister.collection, org.hibernate.hql.ast.tree, org.jboss.remoting.samples.simple, org.jboss.remoting.serialization, org.jboss.profileservice.management.matchers, org.jaxen.expr.iter, org.jboss.remoting.transport.servlet.web, org.jboss.ha.singleton.examples, org.jboss.ejb3.proxy.clustered.objectstore, org.jboss.ejb3.proxy.objectfactory.session.stateful, org.jboss.jms.client.plugin, org.jboss.remoting.samples.chat.utility, org.jboss.remoting.transport.sslservlet, org.jboss.security.plugins.audit, org.jboss.ejb3.proxy, org.hibernate.hql.antlr, org.jboss.security.identitytrust, org.jboss.ejb3.interceptors.annotation, org.jboss.deployment.spi.status, org.hibernate.proxy.pojo.javassist, org.jboss.remoting.loading, javax.resource.spi.work, com.arjuna.common.util.exceptions, org.jboss.security.jndi, org.apache.commons.collections.bidimap, org.jboss.ejb.plugins.lock, com.ibatis.sqlmap.engine.datasource, META-INF.maven.org.jboss.aspects.jboss-remoting-aspects, org.jboss.aspects.remoting.interceptors.invoker, org.apache.bcel.verifier.structurals, org.jboss.remoting.samples.transporter.multiple, org.quartz.helpers, org.jboss.varia.scheduler.example, com.arjuna.ats.jdbc.common, org.jboss.mx.remoting.provider.iiop, org.jboss.crypto, org.apache.bsf, com.ibatis.sqlmap.client.event, org.jboss.security.identity, org.quartz.utils.weblogic, javax.servlet.jsp.tagext, com.arjuna.ats.jbossatx, org.hibernate.jmx, org.jboss.resource.work, javax.enterprise.deploy.spi.status, org.jboss.security.identitytrust.config, org.jboss.metadata.validation.validator, org.hibernate.hql.ast, antlr, com.arjuna.ats.internal.txoj, org.jboss.resource.statistic, org.jboss.naming, org.jboss.jms.server.connectionfactory, org.jboss.remoting.detection, org.hibernate.proxy.map, org.apache.commons.collections.buffer, org.jboss.metadata.validation.chain, org.jboss.wsf.spi.binding, org.jboss.wsf.spi.invocation, com.ibatis.sqlmap.engine.mapping.sql.stat, org.jboss.remoting.security, org.hibernate.annotations.common.util, org.jboss.ejb3.timerservice.quartz, javax.xml.registry, org.jboss.jpa.remote, org.jboss.metadata.javaee.jboss, org.jaxen.jdom, org.jboss.messaging.core.contract, org.jboss.ejb3.common.registrar.plugin.mc, org.jboss.messaging.util.prioritylinkedlist, org.jboss.ejb3.proxy.factory.session.service, org.apache.bsf.engines.javascript, antlr.preprocessor, org.jboss.wsf.framework.http, org.jboss.security.jce, org.jboss.ejb.plugins.jms, org.quartz.ee.jmx.jboss.doc-files, javax.xml.rpc.server, org.jboss.ejb3.proxy.clustered.factory.session.stateless, com.sun.mail.smtp, org.jboss.metadata.web.jboss, com.edb.core.types, org.jboss.remoting.transport.multiplex, org.quartz.jobs.ee.mail, org.apache.log4j.or.sax, org.jboss.wsf.common, org.jaxen.util, org.jboss.remoting.samples.http, org.jboss.aspects.security, org.jboss.security.acl, com.arjuna.common.util.concurrency, org.hibernate.engine.transaction, com.ibatis.common.beans, org.hibernate.bytecode.cglib, org.jboss.util.stream, org.jboss.jms.server.destination, javax.enterprise.deploy.shared.factories, org.jboss.ejb3.common.proxy.spi, org.jboss.ejb3.annotation, org.jboss.corba, org.hibernate.loader.criteria, org.jboss.metadata.merge, org.jboss.ejb3.proxy.clustered.objectfactory.session.stateless, org.jboss.ejb3.proxy.clustered.jndiregistrar, com.arjuna.ats.internal.tsmx.mbeans, org.hibernate.annotations.common, org.jboss.remoting.ident, org.jboss.invocation.unified.interfaces, org.jboss.security.plugins.authorization, org.jboss.ejb.deployers, org.hsqldb.util, org.jboss.hibernate, META-INF.maven.org.jboss.security.jboss-xacml, com.ibatis.sqlmap.engine.type, org.jboss.ejb3.metadata.jpa.spec, org.jboss.ejb3.proxy.objectfactory, org.jboss.ha.framework.server.spi, org.jboss.ejb3.interceptor, org.jboss.jms.server.endpoint.advised, javax.servlet.jsp, org.jboss.mx.remoting, org.jboss.security.factories, org.jboss.resource.connectionmanager.xa, org.jboss.verifier.factory, org.jboss.ha.hasessionstate.interfaces, org.jboss.aspects.remoting.interceptors.marshall, org.hibernate.engine.query, META-INF.maven.org.jboss.ejb3.jboss-ejb3-cache, org.apache.commons.logging, org.jboss.deployment.security, org.jboss.jpa.javaee, org.jboss.iiop.rmi.marshal.strategy, org.jboss.cache.invalidation.triggers, com.arjuna.ats.internal.arjuna.objectstore, org.jboss.tm, org.jboss.security.auth, javax.resource.cci, org.jboss.management.j2ee.deployers, org.jboss.jms.server, org.jboss.security.srp.jaas, com.edb.jdbc2, com.arjuna.common.internal.util.propertyservice, com.edb.jdbc3, javax.xml.ws.spi, org.jboss.naming.interceptors, org.jboss.metadata.annotation.creator.ejb.jboss, org.jboss.security.xacml.sunxacml.cond, org.jboss.security, org.jboss.security.auth.message.config, org.apache.commons.collections.functors, org.jboss.ejb3.proxy.clustered.invocation, META-INF.maven.org.jboss.cluster.jboss-ha-server-cache-jbc, org.jboss.slf4j, org.hibernate.mapping, org.jboss.jms.server.endpoint, org.jboss.metadata.process, META-INF.services, org.quartz.impl, org.jboss.ejb3.proxy.factory.session.stateful, org.hibernate.validator.interpolator, META-INF.maven.org.jboss.ws.jbossws-framework, org.jboss.ejb3.security, org.jboss.security.auth.login, org.apache.bsf.util.type, org.apache.commons.collections.collection, org.jboss.jms.client.state, com.arjuna.ats.internal.jta.resources.arjunacore, org.jboss.remoting.samples.transporter.multiple.server, org.jboss.ejb3.common.proxy.plugins.async, org.jboss.remoting.samples.config.factories, org.hibernate.ejb.instrument, org.apache.log4j.xml, org.jboss.remoting.samples.transporter.serialization, org.hibernate.action, org.jboss.resource, org.jboss.wsf.spi.tools, org.jboss.deployment.spi.beans, org.jboss.remoting.samples.transporter.clustered.client, org.jboss.ejb3, org.jboss.metadata.annotation.creator, org.jboss.ha.framework.server.deployers, org.jboss.ejb3.proxy.factory.stateless, org.quartz.jobs.ee.jmx, org.jboss.wsf.framework.invocation, org.apache.bsf.engines.jython, org.jboss.invocation.jrmp.server, org.jboss.wsf.spi.annotation, org.jboss.ejb3.connectionmanager, org.hibernate.dialect, org.jboss.ejb3.jms, org.jboss.invocation.unified.marshall, com.ibatis.sqlmap.engine.cache.lru, org.jboss.messaging.core.jmx, javax.mail, org.jboss.wsf.spi.deployment.integration, com.edb.core, org.hibernate.bytecode.javassist, com.edb.copy, org.apache.log4j.helpers, com.arjuna.ats.jta.recovery, META-INF.maven.org.jboss.metadata.jboss-metadata, org.jboss.security.xacml.core.ext, org.jboss.proxy.generic, org.jboss.metadata.lang, com.arjuna.ats.arjuna, org.slf4j.impl, com.arjuna.ats.internal.tsmx.agent.implementations.ri, org.hsqldb.index, org.jboss.persistence, org.hibernate.connection, org.jboss.aspects.remoting, org.jboss.remoting.serialization.impl.jboss, org.jboss.web.tomcat.service.sso.spi, org.jboss.jms.server.connectionmanager, com.ibatis.sqlmap.engine.mapping.statement, com.ibatis.common.xml, org.jboss.ejb3.proxy.handler.session.stateful, org.hibernate.proxy.pojo, org.jaxen.expr, com.ibatis.sqlmap.engine.mapping.parameter, org.jboss.remoting.samples.detection.jndi.ssl, org.jboss.messaging.core.impl.message, org.jboss.security.authorization.resources, org.jboss.ejb.plugins.cmp.jdbc2, org.jboss.metadata.ejb.jboss, antlr.collections, org.jboss.security.cache, org.jboss.web.tomcat.service.sso.jbc, javax.enterprise.deploy.model.exceptions, org.hsqldb.rowio, META-INF, org.jboss.mx.remoting.tracker, org.jboss.mx.remoting.provider.rmi, com.arjuna.ats.txoj.tools, org.jboss.security.xacml.core, org.jboss.wsf.spi.metadata.webservices, org.jboss.security.authorization.util, org.quartz.ee.jmx.jboss, org.jboss.ejb3.proxy.objectfactory.session.service, org.hibernate.validator, com.arjuna.ats.internal.arjuna.coordinator, org.apache.commons.collections.keyvalue, com.ibatis.common.resources, org.jboss.security.xacml.sunxacml.attr.proxy, javax.mail.internet, com.arjuna.ats.arjuna.objectstore, org.jboss.ha.framework.interfaces, org.apache.log4j.lf5.config, org.jboss.metadata.annotation.creator.jboss, org.jboss.invocation.pooled.interfaces, javax.xml.ws.handler, org.jboss.ejb3.cache, org.jboss.metadata.ejb.jboss.proxy, com.ibatis.common.logging.jdk14, com.arjuna.ats.internal.jta.resources, org.jboss.remoting.samples.transporter.basic.client, org.quartz.ee.jta, com.ibatis.common.jdbc.exception, org.hibernate.transaction, org.jboss.security.config, com.arjuna.ats.internal.jta.utils.arjunacore, org.jboss.ejb3.proxy.factory.session, org.jboss.ejb3.proxy.clustered.handler.session.stateless, javax.security.auth.message, org.jboss.ejb3.cache.tree, com.edb.xa, org.jboss.remoting.samples.callback.acknowledgement, com.ibatis.common.jdbc.logging, org.jboss.remoting.samples.serialization, org.jboss.hibernate.jmx, com.sun.mail.iap, META-INF.maven.org.jboss.aspects.jboss-current-invocation-aspects, com.ibatis.sqlmap.engine.scope, org.jboss.ejb3.proxy.factory.session.stateless, org.jboss.jms, org.jboss.ejb3.statistics, org.apache.commons.httpclient.params, org.jboss.ejb.plugins.cmp.jdbc.keygen, com.edb.geometric, org.apache.commons.logging.impl, org.hibernate.intercept, com.arjuna.ats.internal.jdbc.recovery, org.quartz.plugins.history, org.jboss.jmx.connector.invoker.serializablepolicy, javax.ejb, org.jboss.ha.singleton, com.sun.mail.imap, org.apache.commons.collections, org.jboss.ejb.plugins.keygenerator, org.hibernate.jdbc, org.jboss.security.audit, org.jboss.wsf.spi.http, com.ibatis.sqlmap.engine.mapping.result.loader, org.jboss.managed.plugins.advice, org.hsqldb.store, org.slf4j.spi, org.jboss.wsf.spi, org.jboss.remoting.samples.transporter.complex.client, org.jboss.jms.recovery, org.jboss.iiop, com.arjuna.ats.internal.jta.transaction.arjunacore.subordinate, org.jboss.ha.jmx.examples, org.jboss.monitor.client, org.jboss.security.xacml.sunxacml.cond.cluster, org.hibernate.secure, org.jboss.metadata, org.jboss.ejb3.tx, org.jboss.security.callbacks, com.arjuna.ats.internal.arjuna.thread, org.quartz.impl.jdbcjobstore.oracle, javax.xml.ws.soap, org.jboss.ejb3.interceptors, org.jboss.wsf.spi.metadata.j2ee, javax.xml.ws.wsaddressing, org.hibernate.cfg, org.jboss.management.j2ee.cluster, org.jboss.security.client, org.jboss.security.plugins.identitytrust, org.jboss.ejb3.interceptors.metadata, org.jboss.ejb3.proxy.handler, org.hibernate.tool.instrument.javassist, org.jboss.ejb3.remoting, org.jboss.metadata.ejb.jboss.jndipolicy.spi, com.arjuna.ats.internal.jta, org.jboss.security.plugins.javaee, com.ibatis.common.logging.jakarta, org.jaxen.saxpath.base, org.jboss.remoting.network.filter, META-INF.maven.org.jboss.ejb3.jboss-ejb3-interceptors, org.apache.commons.httpclient.cookie, org.jboss.remoting.marshal, org.jboss.ejb3.resolvers, org.hibernate.cache.impl, org.jboss.proxy.compiler, org.jboss.jpa.deployment, org.jboss.serial.exception, org.jboss.invocation.unified.server, org.hibernate.id.insert, org.jboss.ejb.plugins.cmp.ejbql, org.jboss.cache.invalidation.bridges, org.jboss.remoting.transport.local, com.arjuna.common.internal.util.logging.jakarta, org.jaxen.dom, com.arjuna.ats.arjuna.gandiva, com.arjuna.ats.arjuna.tools, org.jboss.remoting.marshal.http, bsh.util, org.apache.log4j.lf5.viewer.categoryexplorer, org.jboss.ejb.plugins, org.jboss.ejb.txtimer, org.jboss.serial.references, javax.xml.rpc.handler, org.jboss.ejb3.pool, org.hibernate.hql.ast.util, org.jboss.mx.remoting.connector, org.jboss.security.auth.callback, org.jboss.metadata.annotation.creator.ejb, org.apache.commons.collections.comparators, org.jboss.ejb3.stateless, com.arjuna.ats.internal.jdbc.drivers.modifiers, org.jboss.remoting.samples.detection.jndi, com.arjuna.ats.arjuna.logging, org.jboss.ejb3.interceptors.aop.annotation, org.jboss.ejb3.annotation.impl, org.jboss.ejb3.mdb.inflow, javax.servlet.resources, org.jboss.security.authorization.modules.ejb, org.jboss.proxy, org.jboss.remoting.samples.chat.server, org.jboss.jms.jndi, org.jboss.aspects.txlock, org.jboss.remoting.transport.https, org.quartz.impl.jdbcjobstore.oracle.weblogic, org.jboss.security.xacml.sunxacml.attr, org.jboss.iiop.csiv2, org.jboss.remoting.transport.coyote.ssl, javax.el, org.jaxen.xom, META-INF.maven.org.jboss.ejb3.jboss-ejb3-metadata, com.arjuna.ats.internal.jbossatx.agent, javax.management.j2ee.statistics, META-INF.maven.org.jboss.javaee.jboss-jaspi-api, com.arjuna.ats.internal.arjuna.gandiva.inventory, org.jboss.ejb3.service, org.jboss.remoting.samples.chat.client, org.jboss.metadata.validation.validator.ejb, org.hibernate.ejb.util, org.hibernate.ejb, org.jboss.security.plugins.auth, org.hibernate.dialect.function, org.jboss.invocation.http.interfaces, com.arjuna.ats.arjuna.recovery, org.quartz.impl.jdbcjobstore, schema, org.jboss.messaging.core.impl.postoffice, org.jboss.security.authorization, org.jboss.ejb3.cache.simple, META-INF.maven.org.jboss.ejb3.jboss-ejb3-core, org.jboss.ejb3.interceptors.annotation.impl, org.jboss.monitor.services, org.jboss.profileservice.spi, org.jboss.remoting.socketfactory, org.jboss.profileservice.spi.types, org.apache.commons.collections.list, org.jboss.tm.iiop, com.arjuna.ats.arjuna.common, org.jboss.jms.server.recovery, org.hibernate.annotations.common.reflection.java.generics, antlr.actions.java, com.ibatis.sqlmap.engine.exchange, org.jboss.resource.deployment, org.jboss.annotation.ear, com.ibatis.sqlmap.engine.mapping.sql.simple, META-INF.maven.org.jboss.naming.jnpserver, org.jboss.ha.jndi.impl.jbc, org.hibernate.dialect.lock, org.jboss.remoting.transport.coyote, org.apache.commons.httpclient.auth, org.hibernate.proxy.dom4j, org.hibernate.pretty, javax.annotation, org.jboss.remoting.transport.multiplex.utility, javax.xml.ws.handler.soap, org.hibernate.util, javax.resource, org.jaxen.dom4j, org.jboss.jms.tx, org.jboss.remoting.util.socket, org.jboss.jmx.connector.invoker.client, META-INF.maven.org.jboss.slf4j.slf4j-jboss-logging, org.jboss.wsf.spi.management.recording, META-INF.maven.org.jboss.ws.native.jbossws-native-jaxws, com.arjuna.ats.internal.arjuna.state, org.jboss.jpa.deployers, org.hibernate.proxy.pojo.cglib, com.sun.mail.pop3, org.jboss.proxy.ejb, org.jboss.messaging.core.impl.memory, org.jboss.remoting.samples.transporter.custom.client, org.jboss.security.javaee, org.apache.log4j.ext, org.apache.bcel.verifier.statics, org.jboss.jms.client.container, org.jboss.metadata.rar.spec, org.slf4j, org.apache.bsf.util.event, com.arjuna.common.internal.util.logging, META-INF.maven.org.jboss.ejb3.jboss-ejb3-transactions, org.jboss.remoting.samples.transporter.serialization.client, org.jboss.serial.objectmetamodel.safecloning, org.hibernate.ejb.packaging, org.jboss.ejb3.proxy.clustered.objectfactory.session, javax.persistence.spi, bsh.classpath, com.arjuna.ats.tsmx, org.jboss.ejb.plugins.cmp.bridge, org.jboss.resource.metadata.repository, com.arjuna.ats.tsmx.logging, org.jboss.cache.invalidation, org.jboss.profileservice.aop, org.hibernate.cache.impl.bridge, org.jboss.remoting.network, org.jboss.ejb3.cache.impl, org.jboss.ejb3.naming.client.java, org.jboss.ha.jmx, org.apache.commons.httpclient.util, org.jboss.monitor.alarm, dtd, com.ibatis.sqlmap.client, com.ibatis.sqlmap.engine.mapping.sql, META-INF.maven.org.jboss.aspects.jboss-transaction-aspects, org.jboss.metadata.annotation.creator.web, org.jboss.jms.destination, org.jboss.remoting.samples.chat.exceptions, org.jboss.web.deployers, org.jboss.ejb.plugins.security, org.jboss.tm.usertx.interfaces, com.edb.ssl, org.jboss.wsf.common.handler, org.jboss.ejb3.proxy.container, com.ibatis.common.logging, javax.servlet.jsp.el, META-INF.maven.org.jboss.ws.jbossws-spi, org.jboss.remoting.marshal.encryption, org.jboss.ejb3.entity, org.jboss.security.microcontainer.beans, org.jboss.jms.server.jbosssx, org.jboss.jms.client, org.apache.log4j.jmx, org.jboss.ejb.plugins.inflow, org.jboss.ejb3.security.client, org.jboss.ha.framework.server, org.apache.log4j.config, org.jboss.profileservice.spi.repository, org.jboss.serial, org.hibernate.tuple.entity, javax.xml.ws.addressing, org.jboss.tm.usertx.server, org.jboss.resource.adapter.jdbc.jdk5, org.jboss.remoting.marshal.compress, org.jboss.security.annotation, META-INF.maven.org.jboss.ejb3.jboss-ejb3-deployers, com.arjuna.ats.internal.jta.transaction.arjunacore.jca, org.jboss.metadata.ear.jboss, org.jboss.injection, com.ibatis.sqlmap.engine.transaction.jta, com.arjuna.ats.jta.exceptions, org.jboss.jms.message, org.jboss.serial.persister, org.hibernate.hql.classic, org.jboss.remoting.util, org.quartz.jobs.ee.ejb, org.jboss.remoting.callback, org.jboss.remoting.samples.transporter.simple, org.jboss.resource.statistic.pool, com.arjuna.ats.jta.logging, com.ibatis.sqlmap.engine.transaction.external, com.ibatis.sqlmap.engine.cache, org.hibernate.criterion, javax.transaction, javax.xml.soap, org.jboss.security.xacml.core.model.context, org.jboss.remoting.marshal.rmi, org.jboss.invocation.jrmp.interfaces, org.jboss.security.jacc, org.apache.log4j, org.jboss.ejb3.proxy.clustered.objectfactory, org.hibernate.tool.instrument, org.jboss.remoting.samples.transporter.basic.server, org.jboss.ejb3.annotation.defaults, org.jboss.iiop.rmi, org.jboss.mq.server.jmx, org.jboss.metadata.ear.spec, org.jboss.security.plugins, org.jboss.ejb3.proxy.impl, org.apache.commons.collections.bag, org.apache.log4j.chainsaw, org.opennms.protocols.snmp, org.jboss.deployment.spi.factories, org.jboss.security.mapping.config, org.jboss.aspects.remoting.interceptors.transport, com.ibatis.sqlmap.engine.builder.xml, org.jboss.serial.classmetamodel, com.arjuna.ats.internal.arjuna.recovery, org.jboss.security.identity.plugins, org.apache.bsf.util.event.generator, org.apache.bcel, org.jboss.remoting.transport.http, org.jboss.tm.usertx, org.jboss.remoting.marshall.encryption, org.jboss.security.auth.message, org.hibernate.loader.hql, org.jboss.security.identity.extensions, META-INF.maven.org.jboss.ejb3.jboss-ejb3-common, javax.mail.search, org.jboss.security.auth.container.modules, org.hibernate.metadata, org.jboss.metadata.web.spec, org.jboss.deployment.spi, org.jboss.security.authorization.config, org.jboss.iiop.tm, org.jboss.ejb3.interceptors.util, org.jboss.wsf.framework.deployment, org.jboss.ejb3.asynchronous, org.hibernate.property, org.jboss.remoting.samples.stream, javax.management.j2ee, org.jboss.util, org.jboss.mx.remoting.rmi, org.jboss.deployment.remoting, org.jnp.interfaces.jnp, org.hibernate.collection, org.jboss.management.j2ee.factory, com.ibatis.common.util, org.hibernate.exception, org.jboss.wsf.spi.tools.cmd, org.jboss.naming.client.java, com.sun.mail.util, org.hibernate.param, META-INF.maven.org.jboss.ejb3.jboss-ejb3-proxy, org.jboss.metadata.rar.jboss.mcf, org.jboss.wsf.spi.invocation.integration, com.arjuna.ats.arjuna.xa, org.jboss.jms.server.plugin, org.jboss.ejb.plugins.cmp.jdbc2.keygen, org.jboss.wsf.common.servlet, javax.servlet.jsp.resources, org.jboss.security.plugins.mapping, org.jboss.hibernate.session, org.jboss.remoting.transport.sslbisocket, com.sun.mail.imap.protocol, org.jboss.ejb3.timerservice.quartz.jmx, com.edb.jdbc2.optional, META-INF.maven.org.jboss.aspects.jboss-security-aspects, org.jboss.remoting.transport, org.jboss.jpa.spi, com.arjuna.ats.internal.arjuna.utils, org.apache.bcel.classfile, org.jboss.ejb3.stateful, antlr.ASdebug, org.jboss.metadata.client.jboss, org.hibernate.tool.hbm2ddl, org.jboss.jms.referenceable, com.arjuna.ats.arjuna.exceptions, org.hibernate.loader.custom.sql, org.jboss.remoting.samples.callback, com.arjuna.ats.internal.arjuna.objectstore.jdbc.accessors, org.jboss.ws.tools.ant, org.hsqldb.types, org.jboss.iiop.codebase, META-INF.maven.org.hibernate.hibernate-jmx, org.jboss.security.xacml.factories, org.apache.bcel.verifier, com.ibatis.sqlmap.engine.transaction, org.apache.commons.httpclient, com.arjuna.ats.jdbc.logging, org.jboss.ejb.plugins.cmp.jdbc2.bridge, org.jaxen.saxpath, antlr.debug, com.arjuna.common.util.propertyservice.plugins, org.jboss.metadata.process.chain, antlr.actions.csharp, org.jboss.remoting.security.domain, org.jboss.security.xacml.sunxacml.finder, org.jboss.ejb3.proxy.remoting, org.jboss.ejb.plugins.cmp.jdbc.bridge, org.jboss.iiop.rmi.ir, org.jboss.jms.server.selector, org.jboss.ejb3.proxy.handler.stateful, org.hibernate.annotations.common.annotationfactory, org.jboss.ejb3.security.bridge, org.jboss.security.audit.config, org.jboss.remoting.transport.http.ssl, org.jboss.deployment.plugin, org.jboss.security.xacml.core.model.policy, org.apache.log4j.net, org.jboss.ejb3.tx.metadata, org.jboss.security.auth.certs, antlr.actions.cpp, org.jboss.metadata.ejb.jboss.jndipolicy.plugins, org.jboss.resource.metadata.mcf, licenses, com.ibatis.sqlmap.engine.config, org.hibernate.event, org.jboss.metadata.common.ejb, org.jaxen.function.xslt, javax.resource.spi.endpoint, javax.resource.spi.security, org.hibernate.cfg.annotations, META-INF.maven.org.jboss.cluster.jboss-ha-server-cache-spi, org.jboss.wsf.framework.management, org.jboss.ejb3.cache.grouped, org.jboss.metadata.javaee.support, org.jboss.ejb3.session, org.jboss.ejb3.proxy.handler.session.stateless, org.jboss.remoting.transport.socket, org.quartz.ee.servlet, com.arjuna.ats.jta, org.jboss.profileservice.remoting, javax.xml.rpc.encoding, javax.enterprise.deploy.spi.factories, org.jboss.security.audit.providers, javax.annotation.security, org.jboss.remoting.transport.sslmultiplex, org.jboss.varia.scheduler, com.ibatis.sqlmap.engine.mapping.sql.dynamic, org.jboss.logging, org.jboss.metadata.javaee.spec, org.jboss.jdbc, com.arjuna.ats.internal.jdbc, com.ibatis.common.io] <IMPORT-ALL>NON_EMPTY}}
    at org.jboss.classloader.spi.base.BaseClassLoader.loadClass(BaseClassLoader.java:385)
    at java.lang.ClassLoader.loadClass(Unknown Source)
    at java.lang.ClassLoader.loadClassInternal(Unknown Source)
    at java.lang.Class.forName0(Native Method)
    at java.lang.Class.forName(Unknown Source)
    at org.hibernate.util.ReflectHelper.classForName(ReflectHelper.java:123)
    at org.hibernate.connection.DriverManagerConnectionProvider.configure(DriverManagerConnectionProvider.java:84)
    at org.hibernate.connection.ConnectionProviderFactory.newConnectionProvider(ConnectionProviderFactory.java:137)
    at org.hibernate.connection.ConnectionProviderFactory.newConnectionProvider(ConnectionProviderFactory.java:79)
    at org.hibernate.cfg.SettingsFactory.createConnectionProvider(SettingsFactory.java:448)
    at org.hibernate.cfg.SettingsFactory.buildSettings(SettingsFactory.java:89)
    at org.hibernate.cfg.Configuration.buildSettings(Configuration.java:2101)
    at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1325)
    at ws.RobinWebService.getRobinTest(RobinWebService.java:71)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    at org.apache.axis.providers.java.RPCProvider.invokeMethod(RPCProvider.java:397)
    at org.apache.axis.providers.java.RPCProvider.processMessage(RPCProvider.java:186)
    at org.apache.axis.providers.java.JavaProvider.invoke(JavaProvider.java:323)
    at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
    at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
    at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
    at org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService.java:454)
    at org.apache.axis.server.AxisServer.invoke(AxisServer.java:281)
    at org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:699)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
    at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:327)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
    at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235)
    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
    at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190)
    at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92)
    at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
    at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
    at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
    at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
    at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:828)
    at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:601)
    at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
    at java.lang.Thread.run(Unknown Source)
    16:56:55,319 ERROR [STDERR] Failed to create sessionFactory object.org.hibernate.HibernateException: JDBC Driver class not found: oracle.jdbc.OracleDriver
    16:58:29,557 INFO [STDOUT] hello
    16:58:29,557 INFO [Configuration] configuring from resource: support/oracle.hibernate.cfg.xml
    16:58:29,557 INFO [Configuration] Configuration resource: support/oracle.hibernate.cfg.xml
    16:58:30,116 INFO [Configuration] Reading mappings from resource : support/Centres.hbm.xml
    16:58:30,116 INFO [HbmBinder] Mapping class: ws.Centres -> CENTRE_DETAIL
    16:58:30,116 INFO [Configuration] Reading mappings from resource : support/RobinTest.hbm.xml
    16:58:30,116 INFO [HbmBinder] Mapping class: ws.RobinTest -> ROBIN_TEST
    16:58:30,116 INFO [Configuration] Configured SessionFactory: null
    16:58:30,116 INFO [DriverManagerConnectionProvider] Using Hibernate built-in connection pool (not for production use!)
    16:58:30,116 INFO [DriverManagerConnectionProvider] Hibernate connection pool size: 1
    16:58:30,116 INFO [DriverManagerConnectionProvider] autocommit mode: false
    16:58:30,131 ERROR [DriverManagerConnectionProvider] JDBC Driver class not found: oracle.jdbc.OracleDriver
    java.lang.ClassNotFoundException: oracle.jdbc.OracleDriver from BaseClassLoader@1652e61{VFSClassLoaderPolicy@1c7eb33{name=vfsfile:/C:/Jboss/jboss-5.0.0.GA/server/default/conf/jboss-service.xml domain=ClassLoaderDomain@9fe84e{name=DefaultDomain parentPolicy=BEFORE parent=org.jboss.system.NoAnnotationURLClassLoader@a97b0b} roots=[MemoryContextHandler@2254409[path= context=vfsmemory://4shc4f-nlo6vf-hjk3qb83-1-hjk3qewj-6 real=vfsmemory://4shc4f-nlo6vf-hjk3qb83-1-hjk3qewj-6], DelegatingHandler@6903079[path=antlr.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/antlr.jar], DelegatingHandler@22387624[path=autonumber-plugin.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/autonumber-plugin.jar], DelegatingHandler@22963857[path=bcel.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/bcel.jar], DelegatingHandler@10479206[path=bsf.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/bsf.jar], DelegatingHandler@30371681[path=bsh.jar context=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/ real=file:/C:/Jboss/jboss-5.0.0.GA/common/lib/bsh.jar], DelegatingHandler@26839239[path=commons

    You have to put the path of the driver jar file on server.xml file. If you open up the server.xml file inside the config directory of the appserver instance you will find all the paths are added to <java-config java-home = tag. So place the path in this place. Then there should not be any problem getting the driver.
    Thanks

  • EJB 3 CMP not working in JBoss

    hi,
    i created a simple CMP Entity Bean with mySQL and works fine with OC4J but when delpoy to JBoss 4.0.4RC1, it doesn't work.
    What I realised is that when a JDeveloper create a CMP Entity Bean from a Table it uses @Resource annotaion while I saw all the JBoss samples using @Persistance annotation.
    I changed my CMP to use @persistence annotation and created a persistence.xml file; for somereason it is not working neither in JBoss nor does it work in OC4J.
    Now, if i continue using @Resource annotation, where can I set the datasource so that the @Resource annotation uses my datasource when I deploy it to JBoss?
    or is there any other way to get it working?
    p/s: my datasource is working fine. i created a simple slsb and used
    DataSource ds =
    (DataSource)context.lookup(
    "java:jdbc/mysqlDS");
    and it works fine both in OC4J and JBoss
    any help is appreciated.
    thanks

    Ok, i got this working in JBoss.
    1) Replaced @Resource annotation with @Peristence annotation
    @PersistenceContext(unitName="mysql")
    2) Created persistence.xml in META-INF directory
    <persistence>
    <persistence-unit name="mysql">
    <jta-data-source>java:/jdbc/mysqlDS</jta-data-source>
    <!-- <properties>
    <property name="hibernate.hbm2ddl.auto"
    value="create-drop"/>
    </properties> -->
    </persistence-unit>
    </persistence>
    that is it.
    It means that whether we create EJB 3 on toplink EJB 3 or hibernate EJB 3, we should be able to run it on any of these as long as we stick with the standard annotations. JBoss Hibernate EJB has many additional annotations.
    Now, the only thing that is not working is my Firebird DataSource in JBoss. If anyone has done it please let me know .. thanks.

  • 1xM relation working in Hibernate doesn't work in Kodo and EclipseLink

    Greetings,
    I'm migrating some applications from JBoss/Hibernate to WebLogic 10gR3 and I found lots of JPA problems. In order to simplify the context, I used a very simple one to many bidirectional relationship between 2 entities. Using the following persistence.xml file:
    <?xml version="1.0"?>
    <persistence xmlns="http://java.sun.com/xml/ns/persistence"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd"
    version="1.0">
    <persistence-unit name="ww204-jpa" transaction-type="JTA">
    <provider>org.hibernate.ejb.HibernatePersistence</provider>
    <jta-data-source>cgDataSource</jta-data-source>
    <class>fr.simplex_software.jpa.Employee</class>
    <class>fr.simplex_software.jpa.Department</class>
    <exclude-unlisted-classes>true</exclude-unlisted-classes>
    <properties>
    <property name="hibernate.hbm2ddl.auto" value="create-drop" />
    <property name="hibernate.transaction.factory_class"
    value="org.hibernate.transaction.JTATransactionFactory" />
    <property name="hibernate.transaction.manager_lookup_class"
    value="org.hibernate.transaction.WeblogicTransactionManagerLookup" />
    <property name="jta.UserTransaction" value="java:comp/UserTransaction" />
    </properties>
    </persistence-unit>
    </persistence>
    the test works correctly on WebLogic 10gR3. Now, I'm modifying the persistence.xml to read:
    <?xml version="1.0"?>
    <persistence xmlns="http://java.sun.com/xml/ns/persistence"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd"
    version="1.0">
    <persistence-unit name="ww204-jpa" transaction-type="JTA">
    <provider>org.apache.openjpa.persistence.PersistenceProviderImpl</provider>
    <jta-data-source>cgDataSource</jta-data-source>
    <class>fr.simplex_software.jpa.Employee</class>
    <class>fr.simplex_software.jpa.Department</class>
    <exclude-unlisted-classes>true</exclude-unlisted-classes>
    <properties>
    <property name="kodo.jdbc.SynchronizeMappings" value="refresh" />
    </properties>
    </persistence-unit>
    </persistence>
    The test raises the following exception:
    Exception in thread "Main Thread" java.lang.ClassCastException: fr.simplex_software.jpa.Department
         at fr.simplex_software.slsb.Facade_7ky0ac_FacadeRemoteImpl_WLSkel.invoke(Unknown Source)
         at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
         at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
         at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.security.service.SecurityManager.runAs(Unknown Source)
         at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:473)
         at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    If I modify the persistence.xml to read:
    <?xml version="1.0" encoding="UTF-8"?>
    <persistence version="1.0"
    xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd">
    <persistence-unit name="ww204-jpa" transaction-type="JTA">
    <provider>org.eclipse.persistence.jpa.PersistenceProvider </provider>
    <jta-data-source>cgDataSource</jta-data-source>
    <class>fr.simplex_software.jpa.Employee</class>
    <class>fr.simplex_software.jpa.Department</class>
    <exclude-unlisted-classes>true</exclude-unlisted-classes>
    <properties>
    <property name="eclipselink.ddl-generation" value="drop-and-create-tables" />
    <property name="eclipselink.ddl-generation.output-mode"
    value="database" />
    </properties>
    </persistence-unit>
    </persistence>
    the test raises the same exception. If I come back to the first persistence.xml file, the test works properly again. Is there something I'm doing wrong ?
    Many thanks in advance for any help.
    Nicolas

    Performing the following operations after having changed the persistence.xml file solve the problem:
    1. Undeploy the application.
    2. Run appc to re-generate stubs and copy them on the client CLASSPATH (see also How to run a Java EE client application ?
    3. Stop the server.
    4. Start the server.
    5. Re-deploy the application.
    All the above operations are purhaps not absolutely required but the whole procedure is sufficient to provide the expected result.
    Kind regards,
    Nicolas

  • EJB3/JBoss vs. JDO2/Kodo

    Hi,
    does anybody here per chance have a (convincing ;) feature comparison between
    EJB3/JBoss and JDO2/Kodo (Enterprise)? I'm not talking about support here, as that
    can be purchased for JBoss as well.
    My intuition says that Kodo is better technology and e.g. has better documentation,
    but unfortunately that's too subjective to convince anybody else (which I'd really
    like to).
    Thanks for any information,
    J__rg.

    Thank you a lot for this even longer answer! Whenever someone asks me again why we
    should go for Kodo, I'll give him a printout of this mail, just saying to him "read
    this" ;)
    Neelan Choksi schrieb:
    It is clear that Kodo 4 complies to EJB3 (although it is notproduction-ready
    currently).No implementation that supports EJB3 is production ready currently. That
    is simply because the EJB3 specification just moved into public draft 2
    weeks ago. There are still a lot of changes that are taking place in the
    EJB3 spec (simply compare the Early Draft to the Public Draft and you'll
    see how much things are changing). I am not criticizing the spec - I am
    just pointing out that the spec is at a specific point in its life cycle
    and there are a lot of really smart people including our CTO Patrick
    Linskey trying to make sure 1) it is a good specification and 2) trying to
    drive the specification forward to completion.
    That said there are a lot of O/R Mapping products that are production
    ready. I am going to limit my comments in this thread to focus on what
    Kodo, the product, does well and not go into the differences in the
    specifications.
    I would also encourage you to take a look at both specifications and
    determine which specification is right for you. Although fundamentally
    similar, I believe certain developers will feel more comfortable with JDO
    and certain developers will feel more comfortable with EJB3.
    One distinguishing characteristic about Kodo is that you can use EJB 3 and
    JDO 2 interoperably. This is a very big difference than some of the other
    products that are on the market esp. since each specification has things
    that the other specification is missing. Kodo gives you the best of both
    worlds and allows you to choose how much of each world you want to use.
    A pattern that we see emerging is that a lot of new customers are excited
    to use our JDO standard support today and get the productivity gains that
    Kodo provides today. While they wait to see if EJB3 Persistence meets
    their needs and while they wait for their companies to adopt the
    technology that EJB3 requires (JEE 5 and an app server that supports JEE
    5), they will get the benefits of a solid O/R mapping tool that is based
    on a standard. Over time, the interoperability that Kodo provides will
    allow them to migrate piecemeal to EJB3 Persistence as it matures, thereby
    managing their risk of adopting new technologies. Some of our customers
    will migrate quickly and some have no plans of migrating ever. In any
    case, Kodo provides a pathway for them.
    But I can get the JBOSS implementation of EJB3 for free, why should
    I pay
    more for Kodo when it doesn't give me more functionality or performance?Abe has highlighted a number of technical features that distinguish Kodo.
    I would encourage you to evaluate those features in a serious manner.
    Often times we see other products who claim to have a given feature that
    is in Kodo but when you actually use the feature, there are big
    differences in quality and functionality. For example, I know that a
    number of O/R mapping products claim to have a JMX management console but
    I also know that the depth of functionality that is specific to O/R
    mapping and ease of use of Kodo's Management Console was a big enough
    differentiator that clients have asked to purchase the Management Console
    standalone (FYI, to date we have not chosen to sell it standalone).
    Regarding performance, this is one of the hardest things to compare.
    We've been asked often if we have benchmarking numbers. The problem with
    benchmarks is that a benchmark can be written to say anything you really
    want. I would encourage you to benchmark for your specific application.
    When properly tuned, I have not seen Kodo lose a benchmark since we
    released Kodo 3 over a year ago. And we've seen some wins that have
    really excited us e.g., Kodo + relational database has beaten existing
    applications with object databases in performance / scalability
    comparisons.
    I also would like to highlight that a big differentiator between Kodo and
    other products is the business model each employs. SolarMetric's focus is
    selling product and occasionally selling services. As such, we do things
    like take the most common of our experiences with performance tuning and
    the most common support cases on performance / scalability and generalized
    them into a chapter on optimizations techniques in our documentation. We
    created the Management Console and Profiler to help customers resolve
    their own performance / scalability issues. Other organizations that have
    different models, e.g., solely services, are not motivated to provide this
    level of best practices documentation and / or tools because that cuts
    into their ability to provide services work.
    I'm often in the same situation like J__rg. Always defending the decision touse
    kodo (and doing so in future times) against statements like 'if we switch toEJB
    why stay with kodo if we can get everything with JBoss/Hibernate for "free" 'Ok, even the JBoss guys admit that they are a business (there are some
    recent interviews with Marc Fleury where he distinguishes between open
    source hobbyists and professional open source where the goal is to
    generate revenue). The reality is that how JBoss makes money is different
    than how SolarMetric makes money, but nonetheless JBoss has to make money
    to stay in business and to keep their investors happy just as SolarMetric
    does.
    What we've found interesting over the past few months is that many of our
    enterprise customers who need support services and indemnification
    protection have found that Kodo breaks even with open source solutions
    when analyzed over a 1-2 year span and is dramatically cheaper over a 5
    year span (simply comparing the costs of license and support between the
    two). When factoring in other things e.g., quality of support, attitude
    of support personnel, cost of training, quality of training, ease of use,
    cost / time of contributing to the open source project, cost of digging in
    the code of the open source project, Kodo has a lower Total Cost of
    Ownership (TCO).
    One final point to highlight with Kodo is that our model is not based on
    certain customers of ours subsidizing all of the rest of our customers.
    Such a model has a lot of business risk associated with it because the
    customers that are willing to pay for services are customers that are
    highly coveted. It is often dangerous to wake sleeping giants and put
    your business at risk (see
    http://www.forbes.com/home/intelligentinfrastructure/2005/06/15/jboss-ibm-linux_cz_dl_0615jboss.html).
    I guess the bottom line is that JBoss/Hibernate or other open source
    alternatives aren't free whether you look at out of pockets costs, TCO, or
    risk.
    Anyway. I'm convinced of kodo's robustnest - never had less problems whenusing
    a third party product. If you describe a feature in the manual usually itworks.
    Also the good pluggable architecture was worth its money ... it helpedeverytime
    other implementation surely would have let us down.
    Unfortunataly that are all things that you only realize, when you use it and
    they are pretty difficult to communicate to decision makers, who are aboveme ;-)
    Thank you for the compliments. I believe that the competition we've faced
    supporting standards has made us quite bit stronger than products that
    have been historically proprietary. The challenge with proprietary
    products (e.g., TopLink and Hibernate) was that once you used them, you
    have to re-write your entire data access infrastructure to switch away
    from them. Having to support standards (JDO historically and now EJB 3)
    for the past 4 years has meant that we've faced severe competition and the
    only way for us to succeed was to build superior quality products that
    have more functionality and better scalability and performance than
    anything else out there. If we didn't, our customers could simply pick up
    another of as many as 25 JDO implementations and try it out to see if
    there was something better.
    That said, the fact that our differentiators are a bit more subtle is one
    of the challenges that we face as a business. A lot of the things that
    differentiate Kodo e.g., Profiler, Management Console, Large Results Sets
    Handling, Custom Fetch Groups, Lock Groups, Query Editor, etc. are things
    that typically aren't evaluated very closely in a typical time-constrained
    evaluations, but are absolutely critical when deploying in production
    environments and when using Kodo with Agile Programming Methodologies.
    The pluggable architecture that you reference is also very important
    because many of our customers have constraints that prevent them from
    fitting into a specific box. Again when a prospect does an eval, they
    typically evaluate standard mappings and base functionality but the
    reality is that the real world often brings up issues that no matter how
    good the implementation is there will be something that isn't supported.
    In our opinion, a pluggable architecture provides a cleaner way of
    allowing customers to customize what they need rather than digging into
    someone else's source code.
    The things that we've heard from customers who have switched from other
    solutions are:
    - Kodo produces extremely clean SQL relative to other tools and
    consequently has better performance and scaling characteristics
    - Kodo's documentation and error messaging are extensive and makes
    debugging quite easy
    - Kodo's javadocs are extensive and provides a useful framework to
    customize a wide variety of things.
    - When tuning an application, Kodo provides a number of facilities and
    tools for doing so relative to any other O/R mapping tools out there.
    - Kodo's tooling is a large differentiator; in particular, the Kodo Query
    Editor, the Profiler and the Management Console are often cited as
    distinguishing features.
    Also, one additional benefit with SolarMetric is that we are independent.
    Our agenda is very clear - we are trying to create value for you such that
    we get paid. There are no hidden agendas e.g., using Kodo as a loss
    leader to sell you an object database, an application server, an entire
    stack of products, training, services, etc. We simply are trying to build
    a high quality product that meets our customers' needs that works well
    with all the other technology products out there.
    I hope between Abe's post and this post, we have helped you with arguments
    for your management.
    I'd encourage you to evaluate yourself and give us feedback.
    Also, do not hesitate to contact me directly with any specific questions
    or if you want me to review any documentation that you put together for
    your management.
    Thanks for your questions and interest. Stefan, thank you for being a
    loyal customer.
    Neelan Choksi
    SolarMetric
    [email protected]
    202-595-2064 (main)
    512-542-9707 (direct)
    Vote for Kodo JDO as the Best DB Tool or Driver (Category 2), the Best
    Java Data Access Tool (Category 7), and the Best Java Persistence
    Architecture (Category 11) in the JDJ Readers Choice Awards at
    http://jdj.sys-con.com/general/readerschoice.htm.

  • JPA with MySQL-Data-Source

    Hello Forum,
    I have a question regarding usage of a MySQL-Data-Source in combination with JPA
    on the SAP NetWeaver Application Server, Java ™ EE 5 Edition.
    I have setup a custom datasource like explained in paper:
    "Working with Database Tables, DataSources and JMS Resources"
    - registered the database driver via telnet (Using mysql-connector-java-5.0.3-bin.jar)
    - created the data-sources.xml file underneath the META-INF dir of the EAR project
    [code]
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE data-sources SYSTEM "data-sources.dtd" >
    <data-sources>
      <data-source>
        <data-source-name>titan_cruises_ds</data-source-name>
        <driver-name>mysql-connector-java-5.0.3-bin.jar</driver-name>
         <init-connections>1</init-connections>
         <max-connections>10</max-connections>
         <max-time-to-wait-connection>60</max-time-to-wait-connection>
         <expiration-control>
              <connection-lifetime>600</connection-lifetime>
              <run-cleanup-thread>60</run-cleanup-thread>
         </expiration-control>
         <sql-engine>native_sql</sql-engine>
        <jdbc-1.x>
          <driver-class-name>com.mysql.jdbc.Driver</driver-class-name>
          <url>jdbc:mysql://ourHost.internal.com:3306/practise_titan_cruises</url>
          <user-name>myUser</user-name>
          <password>myPass</password>
        </jdbc-1.x>
      </data-source>
    </data-sources>
    [/code]
    After that I manually created the persistence.xml underneath the META-INF dir of the EJB project.
    [code]
    <persistence xmlns="http://java.sun.com/xml/ns/persistence" version="1.0">
         <persistence-unit name="titan_cruises_pu">
              <jta-data-source>titan_cruises_ds</jta-data-source>
         </persistence-unit>
    </persistence>
    [/code]
    After that I created the Entity named "Cabin" and the corresponding table within the db.
    Entity code:
    [code]
    package de.collogia.beans.pojo.ship;
    import java.io.IOException;
    import java.io.Serializable;
    import javax.persistence.Column;
    import javax.persistence.Entity;
    import javax.persistence.GeneratedValue;
    import javax.persistence.Id;
    import javax.persistence.Table;
    This persisted POJO class models the cabin data.
    <p>
    In this class persistence annotations are placed on the getter methods
    of the attributes. This tells the persistence manager to access them
    via the corresponding get- and set-Methods.</p>
    (Unfortunately this does not work on NetWeaver and I had to place them
    on field level aggain...)
    @author Henning Malzahn ([email protected])
    svn-revision:         $Rev:: 670                                           $:
    svn-lasted-edited-by: $Author:: henning                                    $:
    svn-last-changed:     $Date:: 2007-02-21 21:49:51 +0100 (Wed, 21 Feb 2007) $:
    @Entity
    @Table(name = "cabin")
    public class Cabin implements Serializable {
        /** The generated serial version UID used for serialization. */
        private static final long serialVersionUID = -8522497314498903378L;
        /** The actual version number of this class used for serialization. */
        private static int actualVersion = 1;
        /** The cabin's id. */
        @Id
        @GeneratedValue
        @Column(name = "id")
        private long id;
        /** The cabin's name */
        @Column(name = "name")
        private String name;
        /** The cabin's deck level */
        @Column(name = "deck_level")
        private int deckLevel;
        /** The cabin's ship id */
        @Column(name = "ship_id")
        private int shipId;
        /** The cabin's bed count */
        @Column(name="bed_count")
        private int bedCount;
    /---- Serialization/ Deserialization methods -/
    Method that is responsible for deserialization of the object.
    @param in The <code>ObjectInputStream</code> object to read
              the data from.
    @throws IOException That may occur when reading from the
                        <code>ObjectInputStream</code> object
    @throws ClassNotFoundException That may occur when invoking the default
                                   deserialization mechanism.
        private void readObject(final java.io.ObjectInputStream in)
            throws IOException, ClassNotFoundException {
            /* Invoke default deserialization mechanism. */
            in.defaultReadObject();
            /* Read the actual version number of the class. */
            actualVersion =  in.readInt();
        } // End of readObject()
    Method that is responsible for serialization of the object.
    @param out The <code>ObjectOutputStream</code> object to write
               the data to.
    @throws IOException That may occur when writing to the
                        <code>ObjectOutputStream</code> object.
        private void writeObject(final java.io.ObjectOutputStream out)
            throws IOException {
            /* Invoke default serialization mechanism. */
            out.defaultWriteObject();
            /* Write the actual version number of the class. */
            out.writeInt(actualVersion);
        } // End of writeObject()
    /---- Defining constructors -/
    Private default constructor.
        private Cabin() {
        } // End of default constructor
    Full constructor.
    @param name The cabin's name.
    @param deckLevel The cabin's deck level.
    @param shipId The cabin's ship id.
    @param bedCount The cabin's bed count.
        public Cabin(final String name,
                     final int deckLevel,
                     final int shipId,
                     final int bedCount) {
            this.name = name;
            this.deckLevel = deckLevel;
            this.shipId = shipId;
            this.bedCount = bedCount;
        } // End of full constructor
    /---- Overridden class methods -/
    Returns a string representation of the cabin's data.
    @see java.lang.Object#toString()
        @Override
        public String toString() {
            StringBuffer strBuf = new StringBuffer();
            strBuf.append(this.name);
            strBuf.append("\n");
            strBuf.append(this.deckLevel);
            strBuf.append("\n");
            strBuf.append(this.shipId);
            strBuf.append("\n");
            strBuf.append(this.bedCount);
            return strBuf.toString();
        } // End of toString()
    /---- Defining instance methods -/
    Get method for the member "<code>id</code>".
    @return Returns the id.
        public long getId() {
            return this.id;
    Set method for the member "<code>id</code>".
    HTDODO hm: Check whether it is possible to have setId method
    using private accesss level with NetWeaver JPA-Provider!
    @param id The id to set.
        private void setId(final long id) {
            this.id = id;
    Get method for the member "<code>name</code>".
    @return Returns the name.
        public String getName() {
            return this.name;
    Set method for the member "<code>name</code>".
    @param name The name to set.
        public void setName(final String name) {
            this.name = name;
    Get method for the member "<code>deckLevel</code>".
    @return Returns the deckLevel.
        public int getDeckLevel() {
            return this.deckLevel;
    Set method for the member "<code>deckLevel</code>".
    @param deckLevel The deckLevel to set.
        public void setDeckLevel(final int deckLevel) {
            this.deckLevel = deckLevel;
    Get method for the member "<code>shipId</code>".
    @return Returns the shipId.
        public int getShipId() {
            return this.shipId;
    Set method for the member "<code>shipId</code>".
    @param shipId The shipId to set.
        public void setShipId(final int shipId) {
            this.shipId = shipId;
    Get method for the member "<code>bedCount</code>".
    @return Returns the bedCount.
        public int getBedCount() {
            return this.bedCount;
    Set method for the member "<code>bedCount</code>".
    @param bedCount The bedCount to set.
        public void setBedCount(final int bedCount) {
            this.bedCount = bedCount;
    } // End of class Cabin
    [/code]
    After that I created the TravelAgentBean, a Stateless Session Bean, implementing
    a remote interface that allows construction and persisting of new Cabin objects:
    [code]
    package de.collogia.beans.session.stateless;
    import javax.ejb.Stateless;
    import javax.persistence.EntityManager;
    import javax.persistence.PersistenceContext;
    import de.collogia.beans.pojo.ship.Cabin;
    Class that implements the <code>TravelAgentRemote</code> interface
    and defines the business methods of the TravelAgent service.
    @author Henning Malzahn ([email protected])
    svn-revision:         $Rev:: 670                                           $:
    svn-lasted-edited-by: $Author:: henning                                    $:
    svn-last-changed:     $Date:: 2007-02-21 21:49:51 +0100 (Wed, 21 Feb 2007) $:
    @Stateless
    public class TravelAgentBean implements TravelAgentRemote {
        /** The <code>Log</code> object for this class. */
    //    private static final Log LOGGER;
        /** The <code>PersistenceManager</code> object. */
        @PersistenceContext(unitName = "titan_cruises_pu")
        EntityManager em;
    /---- Static initializer -/
    //    static {
    //        LOGGER = LogFactory.getLog(TravelAgentBean.class);
    //    } // End of static initializer block
    /---- Implementing remote interface methods -/
    {@inheritDoc}
        public void createCabin(final Cabin cabin) {
            this.em.persist(cabin);
        } // End of createCabin()
    } // End of class TravelAgentBean
    [/code]
    After that I created a Controller class containing a main method that looks up the remote
    interface of the TravelAgentBena like explained in document "Accessing Enterprise JavaBeans Using JNDI
    in SAP NetWeaver Application Server, Java ™ EE 5 Edition" written by Validimir Pavlov of SAP NetWeaver
    development team.
    Unfortunately I receive an Exception after invoking the createCabin(...) method.
    On the console of the NWDS I receive:
    [code]
    javax.ejb.EJBException: Exception in getMethodReady() for stateless bean sap.com/test2Earannotation|test2Ejb.jarannotation|TravelAgentBean;
    nested exception is: com.sap.engine.services.ejb3.util.pool.PoolException: javax.ejb.EJBException: Cannot perform injection over bean instance
    Caused by: java.lang.RuntimeException: The persistence unit is inconsistent:
    The entity >>de.collogia.beans.pojo.ship.Cabin<< is mapped to the table >>cabin<<, which does not exist.
    [/code]
    But if I look at the log file located in "C:\NWAS_JAVAEE5\JP1\JC00\j2ee\cluster\server0\log\defaultTrace.0.trc"
    I see the real reason is:
    [code]
    [EXCEPTION]
    #6#1064#42000#You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax
    to use near '"cabin"' at line 1#collnx02.collogia.de:3306:null:practise_titan_cruises#select * from "cabin"#com.mysql.jdbc.exceptions.MySQLSyntaxErrorException:
    You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '"cabin"' at line 1
         at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:936)
         at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:2870)
         at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1573)
         at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:1665)
         at com.mysql.jdbc.Connection.execSQL(Connection.java:3124)
         at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:1149)
         at com.mysql.jdbc.PreparedStatement.executeQuery(PreparedStatement.java:1262)
         at com.sap.sql.jdbc.basic.BasicPreparedStatement.executeQuery(BasicPreparedStatement.java:99)
         at com.sap.sql.jdbc.direct.DirectPreparedStatement.executeQuery(DirectPreparedStatement.java:307)
         at com.sap.sql.jdbc.direct.DirectPreparedStatement.executeQuery(DirectPreparedStatement.java:264)
         at com.sap.engine.services.dbpool.wrappers.PreparedStatementWrapper.executeQuery(PreparedStatementWrapper.java:274)
    [/code]
    My goodness - what a long post - sorry for this - I hope I provided all information
    necessary to deal with the issue.
    Am I thinking in the right direction to blame attribute [code]<sql-engine>native_sql</sql-engine>[/code]
    of file data-sources.xml for the beaviour? Are there any other argument options than native_sql?
    Thanks in Advance!
    Henning Malzahn

    Hi Henning,
    > Despite the fact it's working now I have to do some
    > changes to my code currently
    > developed using JBoss/ Hibernate combination.
    > Hibernate allows you to have the
    > default no-arg constructor with private visibility -
    > any special reason for the fact that
    > only protected is allowed on NetWeaver?
    Here we strictly implemented the checks according to the requirements of the JPA specification. Technically, we could do with private constructors as well. But the JPA specifications requires the constructor to be protected to allow a JPA implementation to subclass entities if needed.
    > The entities in the project are final classes
    > so declaring a ctor protected doesn't really make
    > sense...
    For the same reason, your entities should not be final. Are we missing a check here ?
    > Also the persistence.xml parameter
    >
    hibernate.hbm2ddl.auto
    with the value of
    > create-drop is very useful while
    > developing the app - everytime you deploy the project
    > you get a fresh database.
    > Is there a comparable option for NetWeaver?
    No, unfortunately, there is no comparable option in SAP JPA (yet). We understand that there is a need for forward mapping. We would have liked to delegate this task to the JPA design time (i.e. Dali). However, we had to discover that Dali does not perform this task properly and we can't recommend using it any more.
    Consequently, there is no automatic schema generation in SAP JPA 1.0.
    >
    > Another thing is the extra TMP_SEQUENCE table which
    > isn't necessary using JBoss and
    > Hibernate - what's the reason for that?
    With Hibernate Entity Manager, the id generation strategy in use with GenerationType.AUTO depends on the database dialect. This means that depending on the database dialect, IDENTITY columns, SEQUENCES or generator tables (TableHiLo) are required. As Hibernate has the before mentioned schema generation property this fact can be hidden to the user.
    In SAP JPA, we are always using a table generator if GenerationType.AUTO is used. This allows for better portability across databases. It requires the table TMP_SEQUENCE. As we unfortunately do not have a schema generation capability, the user must create this table.
    Best regards,
    Adrian

  • GenerationType.AUTO doesn't work correctly with Kodo and MySQL

    Greetings,
    I'm migrating applications from JBoss/Hibernate to WebLogic/Kodo. The following column annotation:
    @Id
    @Column(name="CUSTOMER_ID")
    @GeneratedValue(strategy = GenerationType.AUTO)
    public long getCustomerId()
    is supposed to generate auto-increment primary key in mysql. This is what happens with Hibernate. With Kodo, this seems to be equivalent with GenerationType.TABLE as a table named openjpa_sequence_table is created, containing sequence values. So what should one do in order to be able to use true auto-increment strategy with MySQL and Kodo ?
    Many thanks in advance,
    Nicolas

    Hi Nicolas,
    By setting the generation strategy to AUTO, you're essentially letting the JPA provider choose which strategy to use. It looks like Kodo is using the TABLE strategy by default and Hibernate is using the IDENTITY strategy here. You can set the strategy to IDENTITY if you want Kodo to behave similarly to Hibernate. However, it's worth pointing out that there may be a reason for Kodo not using the IDENTITY strategy by default.
    The docs at: http://edocs.bea.com/wls/docs103/kodo/full/html/ref_guide_pc_oid.html#ref_guide_pc_oid_pkgen_autoinc
    point out the following:
    "Statements inserting into tables with auto-increment / identity columns cannot be batched. After each insert, Kodo must go back to the database to retrieve the last inserted auto-increment value to set back in the persistent object. This can have a negative impact on performance. "
    - Matt

  • Class Not Found Exception when saving in Backend?

    Hello all,
    we are using JBOSS, Hibernate, Flex 3 and BlazeDS.
    I have added a class ProjectDocument and it is configured identically to an existing class PartDocument.
    I can successfully load the class in front  end, but the save of the class leads to the following exception.
    The jar is successfully compiled, and includes both PartDocument.class and ProjectDocument.class.
    Does anyone know why BlazeDS cannot find the class?
    regards and thanks
    David
    15:28:49,062 INFO  [STDOUT] [BlazeDS]Cannot create class of type 'ProjectDocumen
    t'.
    flex.messaging.MessageException: Cannot create class of type 'ProjectDocument'.
    Type 'ProjectDocument' not found.
            at flex.messaging.util.ClassUtil.createClass(ClassUtil.java:66)
            at flex.messaging.io.AbstractProxy.getClassFromClassName(AbstractProxy.j
    ava:103)
            at flex.messaging.io.amf.Amf3Input.readScriptObject(Amf3Input.java:430)
            at flex.messaging.io.amf.Amf3Input.readObjectValue(Amf3Input.java:153)
            at flex.messaging.io.amf.Amf3Input.readObject(Amf3Input.java:132)
            at flex.messaging.io.amf.Amf3Input.readArray(Amf3Input.java:371)
            at flex.messaging.io.amf.Amf3Input.readObjectValue(Amf3Input.java:157)
            at flex.messaging.io.amf.Amf3Input.readObject(Amf3Input.java:132)
            at flex.messaging.io.amf.Amf3Input.readScriptObject(Amf3Input.java:473)
            at flex.messaging.io.amf.Amf3Input.readObjectValue(Amf3Input.java:153)
            at flex.messaging.io.amf.Amf3Input.readObject(Amf3Input.java:132)
            at flex.messaging.io.amf.Amf0Input.readObjectValue(Amf0Input.java:135)
            at flex.messaging.io.amf.Amf0Input.readArrayValue(Amf0Input.java:326)
            at flex.messaging.io.amf.Amf0Input.readObjectValue(Amf0Input.java:139)
            at flex.messaging.io.amf.Amf0Input.readObject(Amf0Input.java:95)
            at flex.messaging.io.amf.AmfMessageDeserializer.readObject(AmfMessageDes
    erializer.java:226)
            at flex.messaging.io.amf.AmfMessageDeserializer.readBody(AmfMessageDeser
    ializer.java:205)
            at flex.messaging.io.amf.AmfMessageDeserializer.readMessage(AmfMessageDe
    serializer.java:125)
            at flex.messaging.endpoints.amf.SerializationFilter.invoke(Serialization
    Filter.java:114)
            at flex.messaging.endpoints.BaseHTTPEndpoint.service(BaseHTTPEndpoint.ja
    va:278)
            at flex.messaging.MessageBrokerServlet.service(MessageBrokerServlet.java
    :322)
            at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)

    Hi all,
    we found the problem.
    To read the class in flex we used:
    registerClassAlias("ProjectDocument", ProjectDocument);
    Then BlazeDS sent as class name just ProjectDocument and not the whole string.
    So do not register classes - if you have a class coming from JAva that Flex does not recognise because it is not used in the mxml, just create a dummy variable.
    Hope this helps someone else!

  • Moving to JSF 1.2_12 causing misc problems in my app

    I have an app that was running nicely with JSF 1.2_04.p02. But when I moved to JSF 1.2_12, I started having several problems..
    (1) h:selectOneMenu was not rendering my onchange event (I was able to resolve this by fixing my classpath. See http://forums.sun.com/thread.jspa?threadID=5409440)
    (2) a4j:support does not appear to be working with h:selectOneMenu. The a4j:support action is no longer being invoked.
    (3) ui:include does not appear to be working. For example, this code
                        <div id="terminalSelectionDiv" class="divClear">
                         <ui:include src="virtualPOSTopNav.xhtml" />
                        </div>... renders as ...
                        <div id="terminalSelectionDiv" class="divClear">
                        </div>What am I missing? I was able to fix #1 by adjusting my classpath. Are #2 & #3 classpath issues as well?
    The am currently trying to use JSF-API 1.2_12, JSF-IMPL 1.2_12, Facelets 1.1.14, Richfaces 3.3.2.CR1, JBoss EL 1.0_02.CR4 (plus other misc APIs). But, as I mentioned, I did not modify my code. All I did was started trying to run my code with newer versions of JSF, Facelets and Richfaces. As I try different versions of these APIs, the problems seems to appear when I start using JSF 1.2_12 and the goes away when I revert back to an older version.
    Here's a rundown of the jar files in my classpath...
    My ear contains the following jar files...
    com.echo.myapp.web-1.0.0-SNAPSHOT.war
    com.echo.myapp.ejb-1.0.0-SNAPSHOT.jar
    com.echo.myapp.jmx-1.0.0-SNAPSHOT.sar
    My ear's APP-INF/lib directory in the ear file contains the following jar files (All jar files are in the ear's APP-INF/lib dir. No jar files are in the war file.)
    com.echo.myapp.domain-1.0.0-SNAPSHOT.jar
    com.echo.myapp.util-1.0.0-SNAPSHOT.jar
    com.echo.common.myappremoteapi-1.0.0-SNAPSHOT.jar
    com.echo.common.web-1.0.0-SNAPSHOT.jar
    commons-beanutils-1.7.0.jar
    commons-codec-1.2.jar
    commons-digester-1.8.1.jar
    commons-fileupload-1.1.1.jar
    commons-httpclient-3.1.jar
    commons-io-1.4.jar
    commons-lang-2.2.jar
    commons-logging-1.0.4.jar
    gwt-user-1.4.60.jar
    hibernate-search-3.1.0.GA.jar
    itext-2.1.2.jar
    itext-rtf-2.1.2.jar
    jboss-el-1.0_02.CR4.jar
    jboss-seam-2.2.0.GA.jar
    jboss-seam-debug-2.2.0.GA.jar
    jboss-seam-jul-2.2.0.GA.jar
    jboss-seam-pdf-2.2.0.GA.jar
    jboss-seam-remoting-2.2.0.GA.jar
    jboss-seam-ui-2.2.0.GA.jar
    jcifs-1.3.5.jar
    jcommon-1.0.9.jar
    jfreechart-1.0.9.jar
    jibx-bind-1.1.5.jar
    jibx-extras-1.1.5.jar
    jibx-run-1.1.5.jar
    jsf-api-1.2_12.jar
    jsf-facelets-1.1.14.jar
    jsf-impl-1.2_12.jar
    lucene-core-2.4.0.jar
    quartz-1.6.1-RC1.jar
    richfaces-api-3.3.2.CR1.jar
    richfaces-impl-3.3.2.CR1.jar
    richfaces-ui-3.3.2.CR1.jar
    slf4j-api-1.4.2.jar
    slf4j-log4j12-1.4.2.jar
    stax-api-1.0.1.jar
    wstx-asl-3.2.1.jar
    xpp3_min-1.1.3.4.O.jar
    xstream-1.1.3.jar
    JBOSS_HOME/lib contains...
    commons-codec.jar
    commons-httpclient.jar
    commons-logging.jar
    concurrent.jar
    getopt.jar
    jboss-common.jar
    jboss-jmx.jar
    jboss-system.jar
    jboss-xml-binding.jar
    log4j-boot.jar
    PwdSetter.jar
    JBOSS_HOME/lib/endorsed contains...
    serializer.jar
    xalan.jar
    xercesImpl.jar
    JBOSS_HOME/server/default/lib contains...
    activation.jar
    antlr.jar
    autonumber-plugin.jar
    bcel.jar
    bindingservice-plugin.jar
    bsf.jar
    bsh-deployer.jar
    bsh.jar
    cglib.jar
    classes12-10.2.0.2.0.jar
    commons-codec.jar
    commons-collections.jar
    commons-httpclient.jar
    commons-logging.jar
    dom4j.jar
    ehcache-1.6.2.jar
    ejb3-persistence.jar
    el-api.jar
    hibernate-annotations.jar
    hibernate-entitymanager.jar
    hibernate3.jar
    hsqldb-plugin.jar
    hsqldb.jar
    javassist.jar
    jaxen.jar
    jboss-cache-jdk50.jar
    jboss-common-jdbc-wrapper.jar
    jboss-ejb3x.jar
    jboss-hibernate.jar
    jboss-j2ee.jar
    jboss-jaxrpc.jar
    jboss-jaxws.jar
    jboss-jca.jar
    jboss-jsr77.jar
    jboss-jsr88.jar
    jboss-management.jar
    jboss-monitoring.jar
    jboss-remoting-int.jar
    jboss-remoting.jar
    jboss-saaj.jar
    jboss-serialization.jar
    jboss-srp.jar
    jboss-transaction.jar
    jboss-vfs.jar
    jboss.jar
    jbossjta-integration.jar
    jbossjta.jar
    jbossmq.jar
    jbosssx.jar
    jbossts-common.jar
    jbossws-common.jar
    jbossws-framework.jar
    jbossws-jboss42.jar
    jbossws-spi.jar
    jmx-adaptor-plugin.jar
    jnpserver.jar
    joesnmp.jar
    jpl-pattern.jar
    jpl-util.jar
    jsp-api.jar
    jtds-1.2.2.jar
    log4j-snmp-appender.jar
    log4j.jar
    mail-plugin.jar
    mail.jar
    properties-plugin.jar
    quartz.jar
    scheduler-plugin-example.jar
    scheduler-plugin.jar
    servlet-api.jar
    xmlentitymgr.jar
    The classpath in the manifest of my war file contains references to the following jar files...
    APP-INF/conf
    APP-INF/lib/com.echo.common.web-1.0.0-SNAPSHOT.jar
    APP-INF/lib/jsf-facelets-1.1.14.jar
    APP-INF/lib/jboss-seam-2.2.0.GA.jar
    APP-INF/lib/xstream-1.1.3.jar
    APP-INF/lib/xpp3_min-1.1.3.4.O.jar
    APP-INF/lib/jboss-el-1.0_02.CR4.jar
    APP-INF/lib/jboss-seam-ui-2.2.0.GA.jar
    APP-INF/lib/jboss-seam-2.2.0.GA.jar
    APP-INF/lib/jboss-seam-jul-2.2.0.GA.jar
    APP-INF/lib/commons-beanutils-1.7.0.jar
    APP-INF/lib/commons-lang-2.2.jar
    APP-INF/lib/jboss-seam-pdf-2.2.0.GA.jar
    APP-INF/lib/itext-2.1.2.jar
    APP-INF/lib/itext-rtf-2.1.2.jar
    APP-INF/lib/jfreechart-1.0.9.jar
    APP-INF/lib/jcommon-1.0.9.jar
    APP-INF/lib/jboss-seam-debug-2.2.0.GA.jar
    APP-INF/lib/gwt-user-1.4.60.jar
    APP-INF/lib/hibernate-search-3.1.0.GA.jar
    APP-INF/lib/commons-logging-1.0.4.jar
    APP-INF/lib/lucene-core-2.4.0.jar
    APP-INF/lib/slf4j-api-1.4.2.jar
    APP-INF/lib/com.echo.myapp.util-1.0.0-SNAPSHOT.jar
    APP-INF/lib/commons-httpclient-3.1.jar
    APP-INF/lib/commons-codec-1.2.jar
    APP-INF/lib/jcifs-1.3.5.jar
    APP-INF/lib/commons-io-1.4.jar
    APP-INF/lib/commons-fileupload-1.1.1.jar
    APP-INF/lib/richfaces-api-3.3.2.CR1.jar
    APP-INF/lib/richfaces-impl-3.3.2.CR1.jar
    APP-INF/lib/commons-digester-1.8.1.jar
    APP-INF/lib/richfaces-ui-3.3.2.CR1.jar
    APP-INF/lib/jsf-impl-1.2_12.jar
    APP-INF/lib/jsf-api-1.2_12.jar

    Which JAR's exactly have you added/replaced? And how does the WEB-INF/lib look like?
    Here's some technical background information which may be of use:
    In case of an EAR there are basically four places where classes will be looked up for classloading (they are all covered by the classpath).
    1) JRE/lib (where you installed Java SE)
    2) appserver/lib (in your case JBOSS_HOME/*).
    3) APP-INF/lib (of your EAR)
    4) WEB-INF/lib (of your WAR)
    To start, there should in fact be no duplicates of the same libs in the mentioned locations. If a duplicate is really necessary for some reasons, then ensure that the versioning is the same and/or that you understand the classloading policy. The JRE/lib and appserver/lib should be kept default all the time and in no way be changed nor duplicated in other places. The APP-INF/lib less or more denotes a shared library for all EJB's and WAR's inside the same EAR. The WEB-INF/lib should contain webapp-specific libraries only.
    It depends on the (usually limited configureable) classloading policy of your appserver in which order the mentioned classpath paths will be scanned for the classes to be loaded. Usually, when the appserver starts up and does all its in-house initialization, it will look for classes in appserver/lib and JRE/lib only. Usually, when you request your webapp which is deployed as an EAR, the WEB-INF/lib will first be scanned and then APP-INF/lib and then appserver/lib and then JRE/lib. So if you for example upgraded a lib in APP-INF/lib only while there's still an older one in WEB-INF/lib, your app will break. The appserver's classloading policy is usually only configureable to swap APP-INF/lib and WEB-INF/lib in the search order for classes.

  • Memory analyzer, how to get the to problem root/object

    Hi,
    I've viewed the live tutorial from https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f0a5d007-a35f-2a10-da9f-99245623edda.
    My case was, i Dominator Tree, all top ten classes (with 95% retained Heap) were from org.hibernate.*, and only a few of my classes (with 1% retained heap) which were from http request/respond thread.
    Deep into those top classes, it didn't seem to link to my class; however my web app (use jboss, hibernate/ejb3) was runing of memory (GC overhead limit exceed).
    I'm wondering, any other way to find the problem with help of SAP Memory analyzer?
    Thanks
    John
    Toronto

    Hi
    Check out this guide and update the thread thereafter: https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/40244428-5703-2a10-17af-9e878922f900
    Ravi

  • What's your strategy for learning Java technologies?

    Or, in other words, how do YOU acquire knowledge that is necessary for implementing Java technologies?
    After having spent one-and-a-half years developing an enterprise app, I've gained lots of knowledge about Java and some surface knowledge about its related technologies (JBoss, Hibernate, Ant, XDoclet, NetBeans and probably some others I can't think of at the moment).
    I'm now realizing that -- although the standalone prototype version of my program is growing mature -- I've still got lots to learn for refactoring it to a web platform. For example, I 've done small test projects using Servlets, but haven't done any work with JSP (or HTML for that matter) yet.
    Now, I'm sure I can learn JSP etc., but the questions I ask myself are: how long will it take?
    It's a rhetorical question of course (I don't expect an answer from you, the reader) However, it's an important issue because the months or years I spend fumbling around learning these new technologies, are time I could otherwise spend on the business logic and functionality of my program.
    So, how do you guys acquire knowledge of technologies? Official training perhaps? Or do you simply experiment until it works? Or do you rely on your company's knowledge base (e.g. someone in your company knows how it works)? Or do you get prototypes built from someone who already knows how it works?
    I�m really curious about this and would appreciate your thoughts.
    Thanks in advance,
    P

    Well, it seems like most of you simply read the
    various texts and try the vendors' examples. I'm
    surprised that no one mentioned ever having bought a
    prototype application from the onset. "bought"? What's that mean? You don't buy prototypes. You download evaluation versions, maybe.
    I try to find sample code and tweak it to see the effects. Otherwise, I start writing small sample code an build on that.
    I consider myself a reasonably competent core Java
    programmer, but I had serious difficulty configuring
    and merging its related technologies. There were so
    many disjointed pieces of instructional information
    that the additional research time really hurt our
    budget severely. Not an uncommon thing, I'm sure. There's a lot of stuff. But don't bother learning all of it. Not in detail, at least. It's a good idea to familiarize yourself with the names of packages/libraries and what they do. But only really learn what you need to learn for what you need to do. The next project you will probably need other things, so you learn them then.
    bsampieri,
    I've setup Tomcat and tried the examples--in fact, I
    normally follow tutorials for all products I hope to
    use. Problem is, the examples and tutorials never
    address my specific needs. So, I usually inch toward
    my goal by spending weeks or months in forums to
    continue where the tutorials leave off. Anything complex is going to not be there.... the trick is to identify pieces that you can pull out to build more complex apps. And the fact that JSP/servlets have the issue of being compounded by all the HTML/CSS/JS and HTTP protocol ... I don't want to say limitiations, exactly... Well, it just makes things more complex and harder to know what you need.
    Perhaps you guys are much faster and smarter than
    I...or you have a much bigger budget :)Probably not... on either account.

  • Problem with EJB3 - BlazeDS on Glassfish

    Hi, I'm new in BlazeDS. I have a problem with Flex application using BlazeDS on Glassfish. I want to call sayHello method from EJB 3 (stateful or stateless) from Flex but I can't correctly configure BlazeDS. I search in internet from two weeks for examples, but most of them is for JBoss. Can somebody show me full config for BlazeDS, Flex application (and Glassfish if it's needed).
    I should be grateful for any help.

    Lucasz, did you find out how to configure BlazeDS on GlassFish ?
    I'm having trouble also. We need to run on glassfish/netbeans/toplink, which is not quite common in the doc's/web. Even granite is very eclipse/jboss/hibernate oriented.
    I just need some good EJB3Factory available, or an example, and a way to match JNDI calls from glassfish to my blazeDS destinations.
    Any help is greatly appreciated.
    el sebastian
    upside down, from south america.

  • Why database related code not wriiten in jsp's

    hi all
    what all resons are there for which database related code
    is not written in jsp's
    one thing that i know is
    it's not a j2ee architecture to do so
    so is it the thing that doing so hits the performance issue
    thanx

    Me, I'm still trying to get my head around Java 1.5, J2EE, Tomcat, JBoss, and Oracle RAC (both programming and DBAing)... My head hurts... Badly...
    Back to the topic, though... I also agree with the previous posters...
    I agree there are exceptions to the "no JDBC in JSP rule of thumb"- I have a JSP-based generic table browser as a tool for emergency maintenance from a (presumably) hostile network, it provides read-only access and automatic password rotation. The flexibility of having it in the JSP has saved my bacon in a crisis; when travelling, I had to talk a non-programmer through applying a code fix (damn developers, using reserved words as column name...)( I had the source on my laptop...). To get a class file fixed, I would have had to get a programmer on the phone, and get the server to reload the class which in our environment at the time required an application restart... The project I work on is about 70 man-years of work, mostly Java, and we have maybe 6 or 8 JSPs that access the DB directly...
    Most of the time though, good design says that you access a particular "type" of data (table or group of tables) in the same "chunk" of code, jsp or class file. It's a lot harder to share a jsp among different invokers than it is a class file. It's also better to isolate presentation from data access.
    Imagine that you have a "USER" table, with first name, last name, username, and password. You program a "login" jsp, a user "edit" jsp and an administrator "edit" jsp. Then a security audit declares that saving an unexcrypted password in the database is insecure; you now have to change evey place that can access the password. If the user object was accessed through a single Java class file, then there would be only one place to fix. Of course, it's possible to use jsp includes to simulate class files, but that's just about as much work as creating the class file to begin with, with more problems.
    Another big advantage of keeping your data access out of JSPs is that you can write unit tests much more easily for the Java classes, using something like JUnit. You can have a set of tests for all your persisted data, which can be run anytime your data model changes. This makes it a lot harder for "side effect" bugs to creep into your code.

  • EJB QL: Passing array of enum to SELECT * WHERE a IN () clause

    Hello,
    I am trying to pass an array of enum to EJB QL as followed:
    em.createQuery("FROM OrderInfo o WHERE o.ordStatus IN (:ordStatus)")
                     .setParameter("ordStatus", ordStatsStr)Note that o.ordStatus is of type enum OrderStatus.
    I've tried to set "ordStatus" as String (i.e. 'OPEN', 'CLOSED'), as well as an array of enum but EJB QL would not parse them (perhaps for a good reason). EJB QL (I use JBoss + Hibernate) threw the following exception (or similar depending on whether I passed in an array of enum or a String):
    org.hibernate.TypeMismatchException: named parameter [ordStatus] not of expected type;
    expected = class ....OrderStatus; but was =java.lang.StringCan someone show me the way to set the IN clause with an array of enum?
    Thanks

    I suppose that your enum declaration is like
    public enum OrderStatus{
    OPEN,
    CLOSED
    The exception remarks that the valid type must be OrderStatus. I think that you must change your sentence by
    em.createQuery("FROM OrderInfo o WHERE o.ordStatus IN (:ordStatus)")
    .setParameter("ordStatus", OrderStatus.OPEN);
    On the other hand, for the array option I think that you must use setParameterList like this
    OrderStatus options[] = new OrderStatus[2];
    options[0] = OrderStatus.OPEN;
    options[1] = OrderStatus.CLOSED;
    em.createQuery("FROM OrderInfo o WHERE o.ordStatus IN (:ordStatus)")
    .setParameterList("ordStatus", options);
    I hope it helps you
    hayken.

  • Setting packetSize given in JDBCDriver.

    I am using, Java, Jboss, Hibernate, SqlServer 2008 R2, getting following exception
    WARNING [com.microsoft.sqlserver.jdbc.internals.TDS.Reader] (pool-26-thread-7) ConnectionID:4 TDS header contained invalid packet length:12590; packet size:8000
    SEVERE [com.microsoft.sqlserver.jdbc.internals.TDS.Reader] (pool-26-thread-7) ConnectionID:4 got unexpected value in TDS response at offset:7992
    ERROR [STDERR] (pool-25-thread-2) Exception in thread "pool-25-thread-2"
    ERROR [STDERR] (pool-25-thread-2) org.hibernate.TransactionException: JDBC rollback failed
    [STDERR] (pool-25-thread-2) at org.hibernate.transaction.JDBCTransaction.rollback(JDBCTransaction.java:204)
    [STDERR] (pool-25-thread-2) at com.wideplay.warp.persist.hibernate.HibernateLocalTxnInterceptor.rollbackIfNecessary(HibernateLocalTxnInterceptor.java:149)
    [STDERR] (pool-25-thread-2) at com.wideplay.warp.persist.hibernate.HibernateLocalTxnInterceptor.invoke(HibernateLocalTxnInterceptor.java:72)
    [STDERR] (pool-25-thread-2) at com.softpak.marserm.engine.library.impl.JobReportStatusUtil.updateReportStatus(Unknown Source)
    [STDERR] (pool-25-thread-2) at com.softpak.marserm.engine.library.impl.ExecutableJob.run(Unknown Source)
    [STDERR] (pool-25-thread-2) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
    [STDERR] (pool-25-thread-2) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
    [STDERR] (pool-25-thread-2) at java.lang.Thread.run(Thread.java:662)
    [STDERR] (pool-25-thread-2) Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: The connection is closed.
    [STDERR] (pool-25-thread-2) at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDriverError(SQLServerException.java:170)
    [STDERR] (pool-25-thread-2) at com.microsoft.sqlserver.jdbc.SQLServerConnection.checkClosed(SQLServerConnection.java:304)
    ERROR [STDERR] (pool-25-thread-2) at com.microsoft.sqlserver.jdbc.SQLServerConnection.rollback(SQLServerConnection.java:1655)
    ERROR [STDERR] (pool-25-thread-2) at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.jdbcRollback(BaseWrapperManagedConnection.java:697)
    ERROR [STDERR] (pool-25-thread-2) at org.jboss.resource.adapter.jdbc.WrappedConnection.rollback(WrappedConnection.java:500)
    ERROR [STDERR] (pool-25-thread-2) at org.hibernate.transaction.JDBCTransaction.rollbackAndResetAutoCommit(JDBCTransaction.java:217)
    ERROR [STDERR] (pool-25-thread-2) at org.hibernate.transaction.JDBCTransaction.rollback(JDBCTransaction.java:196)
    ERROR [STDERR] (pool-25-thread-2) ... 7 more
    I need to increase packetSize given in JDBCDriver (sqljdbc4), How can I do this?
    I tried many things including defining <packetSize>32767</packetSize> in ds.xml but no use, getting this exception now
    SEVERE [com.microsoft.sqlserver.jdbc.internals.TDS.TOKEN] (pool-27-thread-7) ConnectionID:1: FetchBufferTokenHandler: Encountered unexpected unknown token (0x30)
    SEVERE [com.microsoft.sqlserver.jdbc.internals.TDS.Reader] (pool-27-thread-7) ConnectionID:1 got unexpected value in TDS response at offset:7282
    SEVERE [com.microsoft.sqlserver.jdbc.internals.TDS.TOKEN] (pool-27-thread-7) ConnectionID:1: getNextResult: Encountered unexpected unknown token (0x30)
    SEVERE [com.microsoft.sqlserver.jdbc.internals.TDS.Reader] (pool-27-thread-7) ConnectionID:1 got unexpected value in TDS response at offset:7282
    Edited by: 1007286 on 22-May-2013 00:23

    This isn't the place to ask questions about Microsoft products. I would try to find a manual for the JDBC driver on the Microsoft website if I were you. But I'm a curious chap so I did a quick Google for "sqlserver jdbc packetsize" and turned this up as the first result:
    http://msdn.microsoft.com/en-us/library/ms378988%28v=sql.90%29.aspx
    This documentation lists the property exactly as you say. However one (old) source of information is not enough, I check more results.
    http://docs.oracle.com/cd/E13157_01/wlevs/docs30/jdbc_drivers/mssqlserver.html
    This documentation has an interesting tidbit:
    "NOTE: If SSL is enabled, the driver communicates with database protocol packets set by the server’s default packet size. Any value set by the PacketSize property is ignored. "
    I would read more documentation if I were you.

Maybe you are looking for

  • Connection b/w BW and External S/S

    Hello ALL If we need to extract data from external source system(say like Informatica,oracle,Java,etc.,)to BW system.Now what is the procedure/steps for connecting between them.(connections between Informatica,oracle,etc., & BW) I came to know that b

  • Learning Pro *C On Oracle 9i(9.2.0.1.0)... ORA_HOME/.../precomp(problem)

    Hi Everyone, I dont know whether its a right place to post my query, But its related to the Oracle database. I want to learn Pro* C, when i started refering the Getting started guide, its been instructed that i have to check various locations of the

  • Heterogeneous Connectivity to MSSQLServer2000 from Oracle 10g ver10.1.0.2.0

    Hi Gurus! I have oracle 10.1.0.2.0 (personal edition) running on WinXp Professional Edition MS-SqlServer 2000 developer edition on the same machine I have preinstalled microsoft ODBC for SQL Server .. I have configred MSSQLDSN for my sqlserver databa

  • Batch determination at creation status

    Hi Experts, I want to do batch dertemination in create status.Currently system allow me to do batch determination after release of order. How to achieve this

  • Call from Java to combine PDF and XML

    What adobe software do I need to combine PDF form template and XML data to produce PDF with XML data embedded. Also is there any samples/references available to make a call to the above from a Java program ? Any help is deeply appreciated. Thanks! Pr