JBoss Community

Re: AS 7 Persistence Provider Problem

created by Subhra Roy in JBoss AS7 Development - View the full discussion

Thanks for pointing to the fix.

 

Actually we have a platform that can (supposed to be able to) dynamically create the EntityManagers and can switch between Hibernate / Eclipselink / Ibatis. We manage our own datasources and configure the EMs dynamically depending on the requirement. That means the same application can have more than one EMs and of different providers.

 

We can do that in Tomcat / Jetty / OSGi (Equinox with embedded Tomcat). We are trying to see if that will be possible with JBoss also.

 

I would really like if AS7 provides a way where it does not try to limit an application to a specific provider / datasource.

 

By the way if the persistence.xml is removed(renamed) AS 7 does not throw the exception and configures eclipse.jpa.provider correctly.

 

I am also stuck because AS 7 is forcing the <jta-datasource> / <non-jta-datasource> tag.

Any help there would be highly appreciated (though it is out of place in this thread) .

Reply to this message by going to Community

Start a new discussion in JBoss AS7 Development at Community