Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

4
  • Thanks! That will involve additional installation procedures each time we install the application, writing an instruction etc. But if we don't find some other way and this is the only option - we'll have to do that... Commented Nov 10, 2011 at 10:00
  • Also, take a look at this document: Alternate JPA Providers in WebSphere Application Server. Looks like you should be able to use hibernate by specifying the provider in persistence.xml and by embedding the required jars in your application. See my edit on the answer. Commented Nov 10, 2011 at 10:13
  • Xavi, we did specify provider... but it just resulted in The server cannot create an EntityManagerFactory factory for the xxx persistent unit from the org.hibernate.ejb.HibernatePersistence provider in jar:file:/C:/IBM/WebSphere/wp_profile/installedApps/XXX/xxx-ear.ear/xxx-ejb.jar!/ module. It could be a separate issue of course... Commented Nov 10, 2011 at 10:30
  • Thanks!!! I just couldn't think that the solution would be so strange... I would actually prefer to rename persistence xml rather than making it WebSphere aware Commented Nov 10, 2011 at 10:59