Agree with Websphere - everything seemed a little (or a lot) harder than it needed to be.
Try putting the complete persistence.xml file from the release back in. That is how I have it running. Not to mention that one of the people on the websphere forums thought that when the application was actually loaded and running that it would be using hibernate. So if none of the hibernate values are there, maybe it reverts to openJPA. Its a long shot but give it a try. Put this back in the build, update the app through the admin console, then restart. Good luck. | <?xml version="1.0" encoding="UTF-8"?> | <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="bookingDatabase" transaction-type="RESOURCE_LOCAL"> | <provider>org.hibernate.ejb.HibernatePersistence</provider> | <jta-data-source>DefaultDatasource</jta-data-source> | <properties> | <!-- From WAS 6.1.0.9, the embedded DB is switched to the same Derby DB in Glassfish --> | <property name="hibernate.dialect" value="GlassfishDerbyDialect"/> | <property name="hibernate.hbm2ddl.auto" value="create-drop"/> | <property name="hibernate.show_sql" value="true"/> | <property name="hibernate.cache.provider_class" value="org.hibernate.cache.HashtableCacheProvider"/> | <property name="hibernate.transaction.manager_lookup_class" value="org.hibernate.transaction.WebSphereExtendedJTATransactionLookup"/> | </properties> | </persistence-unit> | </persistence> | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4128130#4128130 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4128130 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
