Hi, I saw the recent post about testing Seam 2.x on the (upcoming) JBoss AS7 and wanted to ask about Hibernate 4.0 support. Currently in AS7, we inject the Hibernate (4.0) module dependencies into application deployments, if we scan certain (@PersistenceUnit @PersistenceContext or their equivalent deployment descriptor) ) annotations or a persistence.xml. Any idea if Seam 2.x applications will also work with Hibernate 4.0? Thanks, Scott _______________________________________________ seam-dev mailing list seam-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/seam-dev

> I had to switch over this persistence unit to being container-managed, which is the better thing anyway. I was only using a Seam-managed PU to get around an AS6 issue, and that particular issue doesn't exist with AS7. Which AS6 issue is this?

Hi, I saw the recent post about testing Seam 2.x on the (upcoming) JBoss AS7 and wanted to ask about Hibernate 4.0 support. Currently in AS7, we inject the Hibernate (4.0) module dependencies into application deployments, if we scan certain (@PersistenceUnit @PersistenceContext or their equivalent deployment descriptor) ) annotations or a persistence.xml. Any idea if Seam 2.x applications will also work with Hibernate 4.0? Thanks, Scott _______________________________________________ seam-dev mailing list seam-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/seam-dev

-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk3uhTkACgkQU4HO8G8hNxWvqgCfWrpFOPpq1Fzpxv0iPatFVATL C4YAnj/7etw0MTHMw5ndKyFTuEjs+cz7 =z+ND -----END PGP SIGNATURE-----

> > I guess that it is not good. How will AS7 solves deploying old EJB3 > application? > > I am new in JBoss AS 7 world, and right now I am trying to deploy some > old applications. For instance I saw this warning: > > 21:37:17,430 WARN [org.jboss.as.server.deployment.module] (MSC service > thread 1-2) META-INF directory > /content/jboss-seam-jpa.war/WEB-INF/classes/META-INF ignored as it is > not a valid location for META-INF > > Why the location is not valid? > It should be in war/META-INF, not war/WEB-INF/classes/META-INF.

On Wednesday 08 June 2011 04:12 AM, Stuart Douglas wrote: > >> >> I guess that it is not good. How will AS7 solves deploying old EJB3 >> application? >> >> I am new in JBoss AS 7 world, and right now I am trying to deploy some >> old applications. For instance I saw this warning: >> >> 21:37:17,430 WARN [org.jboss.as.server.deployment.module] (MSC service >> thread 1-2) META-INF directory >> /content/jboss-seam-jpa.war/WEB-INF/classes/META-INF ignored as it is >> not a valid location for META-INF >> >> Why the location is not valid? >> > > It should be in war/META-INF, not war/WEB-INF/classes/META-INF. > Note that the WARN is a bit misleading because (only) the JPA spec allows the persistence.xml file to be in .war/WEB-INF/classes/META-INF (section 8.2 of JPA spec). That file infact will be picked up by AS7. It's just warning that the rest of the metadata should come from .war/META-INF. The .war/WEB-INF/classes/META-INF location is just for JPA persistence.xml -Jaikiran _______________________________________________ seam-dev mailing list seam-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/seam-dev

> > Note that the WARN is a bit misleading because (only) the JPA spec > allows the persistence.xml file to be in .war/WEB-INF/classes/META-INF > (section 8.2 of JPA spec). That file infact will be picked up by AS7. > It's just warning that the rest of the metadata should come from > .war/META-INF. The .war/WEB-INF/classes/META-INF location is just for > JPA persistence.xml I'd say the code should be smarter and not throw a WARN if only persistence.xml is in. That's the legal place to put a persistence.xml in a WAR.

On Wednesday 08 June 2011 01:09 PM, Emmanuel Bernard wrote: > > I'd say the code should be smarter and not throw a WARN if only persistence.xml is in. That's the legal place to put a persistence.xml in a WAR. Agreed. I'm looking at changing that WARN as we speak.

Hi, I saw the recent post about testing Seam 2.x on the (upcoming) JBoss AS7 and wanted to ask about Hibernate 4.0 support. Currently in AS7, we inject the Hibernate (4.0) module dependencies into application deployments, if we scan certain (@PersistenceUnit @PersistenceContext or their equivalent deployment descriptor) ) annotations or a persistence.xml. Any idea if Seam 2.x applications will also work with Hibernate 4.0? Thanks, Scott _______________________________________________ seam-dev mailing list seam-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/seam-dev

> I found a backward compatibility issue while deploying jboss-seam-jpa > example. > > org.hibernate.cache.HashtableCacheProvider was moved to > org.hibernate.cache.internal.HashtableCacheProvider > > So this will force Seam application to bundle old hibernate libraries > version 3. Or simply change this property in persistence.xml.

OK, I of course commented out that property, but what should be recommended replacement example? Could you point me to doc/web page? On Wed, 2011-06-08 at 13:24 +0200, Emmanuel Bernard wrote: > On 8 juin 2011, at 12:27, Ales Justin wrote: > >>> I found a backward compatibility issue while deploying jboss-seam-jpa >>> example. >>> >>> org.hibernate.cache.HashtableCacheProvider was moved to >>> org.hibernate.cache.internal.HashtableCacheProvider >>> >>> So this will force Seam application to bundle old hibernate libraries >>> version 3. >> >> Or simply change this property in persistence.xml. > > We should move away from these. Especially in an example people are meant to study, we should not recommend using HashtableCacheProvider. > Best would be to show Infinispan (even in local mode). > _______________________________________________ > seam-dev mailing list > seam-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/seam-dev