JBossDeveloper

I wonder how this all makes sense with my situation. I have my old (online) webapp which works on JBoss AS 7.0.0.Final up to JBoss AS 7.1.0.CR1 using Seam 2.2.2 and it's not kicking in Hibernate 4. Then I changed the project to Maven, now resulting in a different set of deployed libs, a slightly different jboss-deployment-structure.xml, a slightly different dir structure plus the persistence now being JTA (not RESOURCE_LOCAL as the old app) and it's still using Seam 2.2.2 but this time the app is kicking in Hibernate 4.... it doesn't make sense to me to look into Seam as the cause.

We probably could boot your app on AS 7.0.0.Final with JPA TRACE logging enabled and examine the server.log.  Some of the variables that we will look for, is which persistence provider is added to the javax.persistence.Persistence providers list.  I think it was probably the Hibernate 3 jars instead of the Hibernate 4 jars.

If we cannot solve AS7-3423 (not an AS 7.1 task), I would look for a different way to allow the Hibernate 3 jars to be added to the javax.persistence.Persistence providers list (first).  The other way, could be allowing the default (global) persistence provider module to be configured but I would prefer to take the AS7-3423 route.

Scott

Scott,

seam does that with @Install annotations

you can look at docs here:

http://docs.jboss.org/seam/latest/reference/en-US/html/annotations.html

if I remember correctly this would be the class signature for overriding the peristenceProvider

@Name("org.jboss.seam.persistence.persistenceProvider")
@Scope(ScopeType.STATELESS)
@BypassInterceptors
@Install(precedence=BUILT_IN, classDependencies={"org.hibernate.Session", "javax.persistence.EntityManager"})
public class HibernatePersistenceProvider extends PersistenceProvider{

I think this would be the proper way to override this with your own implementation, the core of the problem lies in newer version of hibernate as seam was compiled against 3.3

I was working alot on migration of seam projects to as7 and there ware many paths I tryied, latest was making fork of seam to work with h4 but I haven't touched for a while now...

Let me try to debug this on my machine as I think I have an idea how to fix this.

fixed the precedence in example

@Karsten,

Can you provide the server.log output from AS start to after application is deployed.

Scott

Anyway, looking backwards at why your old application deployed successfully on AS 7.0.0.Final versus your new app is not going to show us what you need to change in your new app to deploy on AS 7.1.

I'll look at them...

I just pulled the old webapp from my remote server, it deployed to JBAS 7.1 CR1 without any exceptions.

If your old app is working on 7.1, then my theory about why your old app worked on 7.0, is incorrect.  It must be something else that has changed. 

Hi,

I have now played with both versions of your application and now both deploy on current snapshot (build this afternoon)

The trick is that your old version (from remote server) deployed becouse it used hibernate 4 as you can see from log and not bundled hibernate 3.

If I modify your new version of app so that i comment out exclude of hibernate in jboss-deployment-structure.xml and comment out

<property name="jboss.as.jpa.providerModule" value="hibernate3-bundled" />

it deployes, but with hibernate 4 not bundled version of hibernete.

I have not tested the functionaly of app but just that it deployed ant it was accessable trough browser.

@Scott: you are right the problem is that with "hibernate3-bundled" it loads both versions of hibernate starts with one and than continues with another from main slot. this is a bug in jpa subsystem i belive...

--

tomaz

I have the old copy of the app locally and will investigate why Hibernate 4 is coming into play (probably because javax.persistence.Persistence.createEntityManagerFactory is used which only knows about Hibernate 4 but it will be good to verify). 

For others having this problem, trying the @Install workaround that Tomaz mentioned earlier might be worth trying. 

@Tomaz, yes, its because javax.persistence.Persistence.createEntityManagerFactory only knows about the Hibernate 4 jars (just verified that is the root cause in the debugger). 

I think trying to address AS7-3423 will be a good start. 

I'll respond on the Seam forum thread, I think you will need to try that @Install annotation workaround that Tomaz mentioned.

Tomaz Cerar wrote:

 

Seam 2 works with hibernate 3.3.x and validator 3.1 that is your main couse of the problems.

Bundle hibernate 3.3(jpa 1) instead 3.6(jpa 2) and it should work.

 

--

tomaz

Or you need to use latest 2.3.0-SNAPSHOT starting from 8th February as this is the point when I added JPA2 and Bean Validation into org.jboss.seam:jboss-seam-jsf2:2.3.0-SNAPSHOT artifact.