On 19 Oct 2008, at 01:05, Jay Balunas wrote: > I wanted to provide a status on the testing of Seam 2.1.0.GA on AS > 5 CR2. I believe these issues are a mixture of Seam and AS 5 > issues. Please review and let me know what you think. > > I have a couple of examples and seam-gen testing to complete. I > will also be doing a spot check on windows, and with jdk5. > > Thanks, > Jay > > So far I have tested only with JDK6 on Fedora 8. I can provide > additional details for most of these if needed. > > * Blog example > - When I deploy the blog example I get the exception below. > - "Caused by: org.hibernate.cache.NoCachingEnabledException: Second- > level cache is not enabled for usage > [hibernate.cache.use_second_level_cache | > hibernate.cache.use_query_cache]" > - Made several changes that I reviewed with Pete, Norman. > - Still getting this issue with these changes. > - Waiting to hear from Stan on this. > - Should this be a JBAS or JBSEAM jira? Report this in JBSEAM for now, I will investigate.

> > > * GroovyBooking example > - JBSEAM-3579 > - Getting the sql error below. Jozef also saw this with Seam > 2.0.3.CR2 on AS 5 CR2 > - Caused by: java.sql.SQLException: Violation of unique constraint > SYS_PK_49: duplicate value(s) for column(s) $$ > - during import.sql import Are you sure you have a clean data dir?

> > > * JPA/Hiberante example are showing a ZipException on jboss-seam- > ui.jar > - Entered JBAS-6107 > - Original issue JBAS-6076 > - Ales said that this should be fixed in trunk > > * Wicket undeploy exceptions > - When undeploying the wicket example I see the following exceptions: > - I will enter a jira - although I am not sure if this is Seam or > AS related? > Caused by: java.io.IOException: Child not found jboss-seam-wicket- > booking.ear/lib/wicket.jar/org/apache/wicket/Application.properties > for FileHandler@21707409[path context=file:/jboss/projects/seam/ > 2.1.0.GA/jboss-5.0.0.CR2/server/default/deploy/ real=file:/jboss/ > projects/seam/2.1.0.GA/jboss-5.0.0.CR2/server/default/deploy/] > at org.jboss.virtual.VFS.findChild(VFS.java:211) > at > org > .jboss > .virtual > .plugins > .vfs > .VirtualFileURLConnection > .resolveCachedVirtualFile(VirtualFileURLConnection.java:122) > at > org > .jboss > .virtual > .plugins > .vfs > .VirtualFileURLConnection > .getVirtualFile(VirtualFileURLConnection.java:144) > at > org > .jboss > .virtual > .plugins > .vfs > .VirtualFileURLConnection > .getLastModified(VirtualFileURLConnection.java:89) > ... 4 more Please report in JBAS, with instructions to reproduce. Assign to Ales I think. > * Spring example deployment exception > - See spring_deploy_error.txt for listing > - Persistence.xml is using "RESOURCE_LOCAL" and not define any data > source > - this works fine on other jboss versions. Report in JBSEAM, assign to Mike Youngstrom > * SeamSpace example > - I believe two separate issues found > - 1) If you click on "create user" or "create role" twice you get > the following exception: > - IllegalStateException: begin method invoked from a long-running > conversation, try using @Begin(join=true) on method: createRole > - 2) When adjusting security settings either on images, or users/ > roles the tables are empty > - The application still functions as it should so this is > probably an issue with view not the data > > * itext example > - When you attempt to access the example you see a 404 not found > page. > - This may be fixed by the changes that Pete did for AS 5 - > JBSEAM-3575 > - This may also be related to hotdeploy changes in Seam - need to > wait for new tag to test > - See the attached itext_error.txt for output. Just try AS5 trunk, Ales upgraded to the seam-int which contains the fix. > * Can't deploy 2 Seam Applications > - javax.management.InstanceAlreadyExistsException: > jboss.j2ee:jar=jboss-seam.jar,service=EJB3 already registered. > - See full stack trace in 2_seam_app.txt > - I believe we have seen this, but I was not able to find the jira Stan assigned this to Carlo > > > Minor or Known issues: > ---------------------- > > * EntityManagerFactory Issue with AS 5 CR1 effects several examples > - dvdstore, contactlist, quartz, others... > - Followed workaround here > - http://www.jboss.com/index.html?module=bb&op=viewtopic&t=142385&a... > - Also needed to add the following to the persistence.xml > -<property name="hibernate.transaction.manager_lookup_class" > value="org.hibernate.transaction.JBossTransactionManagerLookup"/> > - I believe this is a side effect of the workaround

> * "Welcome to Seam null" shows in nearly every example when > deployed. I have also seen "Welcome to Seam 5.0.0.CR2" in cases. > - Adrian fixed this for AS 5 GA > > * Excessive logging for every request of seam - JBSEAM-3575 entered > 14:51:54,551 INFO [Initialization] Installing components... > 14:51:54,551 INFO [Initialization] done redeploying > 14:51:55,293 INFO [Initialization] redeploying > - Pete fixed this in AS 5 trunk and should be in AS 5 GA

> > > * Paths/links in the booking examples popup details are out of date. > - Will report but this is minor > > <2_seam_app.txt><itext_error.txt><wicket_undeploy_errortxt> _______________________________________________ seam-dev mailing list seam-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/seam-dev

On 19 Oct 2008, at 11:20, Pete Muir wrote: > > On 19 Oct 2008, at 01:05, Jay Balunas wrote: > >> I wanted to provide a status on the testing of Seam 2.1.0.GA on AS >> 5 CR2. I believe these issues are a mixture of Seam and AS 5 >> issues. Please review and let me know what you think. >> >> I have a couple of examples and seam-gen testing to complete. I >> will also be doing a spot check on windows, and with jdk5. >> >> Thanks, >> Jay >> >> So far I have tested only with JDK6 on Fedora 8. I can provide >> additional details for most of these if needed. >> >> * Blog example >> - When I deploy the blog example I get the exception below. >> - "Caused by: org.hibernate.cache.NoCachingEnabledException: >> Second-level cache is not enabled for usage >> [hibernate.cache.use_second_level_cache | >> hibernate.cache.use_query_cache]" >> - Made several changes that I reviewed with Pete, Norman. >> - Still getting this issue with these changes. >> - Waiting to hear from Stan on this. >> - Should this be a JBAS or JBSEAM jira? > > Report this in JBSEAM for now, I will investigate. I would not expect the blog example to work in general, as it deploys JBoss Cache 1.x whilst you need to use JBoss Cache 2.x with JBoss 5. Norman, can you take a look adding a JBoss 5 target to the blog example? In general, add those examples known not working on JBoss 5 to the release notes.

I removed the use of the query cache from seamdiscs.

> > >> >> >> * GroovyBooking example >> - JBSEAM-3579 >> - Getting the sql error below. Jozef also saw this with Seam >> 2.0.3.CR2 on AS 5 CR2 >> - Caused by: java.sql.SQLException: Violation of unique constraint >> SYS_PK_49: duplicate value(s) for column(s) $$ >> - during import.sql import > > Are you sure you have a clean data dir? Ok, this occurs because EJB3 is now deploying JPA for WARs (persistence.xml in WEB-INF/classes/persistence.xml), so that Hibernate gets started twice, and so import.sql is run twice. ALR, is it correct that PUs get deployed from inside a war for EJB3? Other EE5 containers don't do this. > > >> >> >> * JPA/Hiberante example are showing a ZipException on jboss-seam- >> ui.jar >> - Entered JBAS-6107 >> - Original issue JBAS-6076 >> - Ales said that this should be fixed in trunk >> >> * Wicket undeploy exceptions >> - When undeploying the wicket example I see the following >> exceptions: >> - I will enter a jira - although I am not sure if this is Seam or >> AS related? >> Caused by: java.io.IOException: Child not found jboss-seam-wicket- >> booking.ear/lib/wicket.jar/org/apache/wicket/ >> Application.properties for FileHandler@21707409[path context=file:/ >> jboss/projects/seam/2.1.0.GA/jboss-5.0.0.CR2/server/default/ >> deploy/ real=file:/jboss/projects/seam/2.1.0.GA/jboss-5.0.0.CR2/ >> server/default/deploy/] >> at org.jboss.virtual.VFS.findChild(VFS.java:211) >> at >> org. >> jboss. >> virtual. >> plugins. >> vfs. >> VirtualFileURLConnection. >> resolveCachedVirtualFile(VirtualFileURLConnection.java:122) >> at >> org. >> jboss. >> virtual. >> plugins. >> vfs. >> VirtualFileURLConnection. >> getVirtualFile(VirtualFileURLConnection.java:144) >> at >> org. >> jboss. >> virtual. >> plugins. >> vfs. >> VirtualFileURLConnection. >> getLastModified(VirtualFileURLConnection.java:89) >> ... 4 more > > Please report in JBAS, with instructions to reproduce. Assign to > Ales I think. > >> * Spring example deployment exception >> - See spring_deploy_error.txt for listing >> - Persistence.xml is using "RESOURCE_LOCAL" and not define any >> data source >> - this works fine on other jboss versions. > > Report in JBSEAM, assign to Mike Youngstrom > >> * SeamSpace example >> - I believe two separate issues found >> - 1) If you click on "create user" or "create role" twice you get >> the following exception: >> - IllegalStateException: begin method invoked from a long-running >> conversation, try using @Begin(join=true) on method: createRole >> - 2) When adjusting security settings either on images, or users/ >> roles the tables are empty >> - The application still functions as it should so this is >> probably an issue with view not the data >> >> * itext example >> - When you attempt to access the example you see a 404 not found >> page. >> - This may be fixed by the changes that Pete did for AS 5 - >> JBSEAM-3575 >> - This may also be related to hotdeploy changes in Seam - need to >> wait for new tag to test >> - See the attached itext_error.txt for output. > > Just try AS5 trunk, Ales upgraded to the seam-int which contains > the fix. > >> * Can't deploy 2 Seam Applications >> - javax.management.InstanceAlreadyExistsException: >> jboss.j2ee:jar=jboss-seam.jar,service=EJB3 already registered. >> - See full stack trace in 2_seam_app.txt >> - I believe we have seen this, but I was not able to find the jira > > Stan assigned this to Carlo > >> >> >> Minor or Known issues: >> ---------------------- >> >> * EntityManagerFactory Issue with AS 5 CR1 effects several examples >> - dvdstore, contactlist, quartz, others... >> - Followed workaround here >> - http://www.jboss.com/index.html?module=bb&op=viewtopic&t=142385&a... >> - Also needed to add the following to the persistence.xml >> -<property name="hibernate.transaction.manager_lookup_class" >> value="org.hibernate.transaction.JBossTransactionManagerLookup"/> >> - I believe this is a side effect of the workaround This one is a major PITA.... https://jira.jboss.org/jira/browse/JBAS-6093 >> * "Welcome to Seam null" shows in nearly every example when >> deployed. I have also seen "Welcome to Seam 5.0.0.CR2" in cases. >> - Adrian fixed this for AS 5 GA >> >> * Excessive logging for every request of seam - JBSEAM-3575 entered >> 14:51:54,551 INFO [Initialization] Installing components... >> 14:51:54,551 INFO [Initialization] done redeploying >> 14:51:55,293 INFO [Initialization] redeploying >> - Pete fixed this in AS 5 trunk and should be in AS 5 GA It's in AS5 trunk now. >> >> >> * Paths/links in the booking examples popup details are out of date. >> - Will report but this is minor >> >> <2_seam_app.txt><itext_error.txt><wicket_undeploy_errortxt> > > _______________________________________________ > seam-dev mailing list > seam-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/seam-dev

> Ok, this occurs because EJB3 is now deploying JPA for WARs > (persistence.xml in WEB-INF/classes/persistence.xml), so that

> Hibernate gets started twice, and so import.sql is run twice. ALR, is > it correct that PUs get deployed from inside a war for EJB3? Other EE5 > containers don't do this. Yes, @see comments in: http://anonsvn.jboss.org/repos/jbossas/trunk/ejb3/src/main/org/jboss/ejb3...

>> Ok, this occurs because EJB3 is now deploying JPA for WARs >> (persistence.xml in WEB-INF/classes/persistence.xml), so that Missing META-INF?

>> Hibernate gets started twice, and so import.sql is run twice. ALR, >> is it correct that PUs get deployed from inside a war for EJB3? >> Other EE5 containers don't do this. > Yes, @see comments in: > http://anonsvn.jboss.org/repos/jbossas/trunk/ejb3/src/main/org/jboss/ejb3... It's actually the WarStructure that understands it. ;-) - http://anonsvn.jboss.org/repos/jbossas/trunk/server/src/main/org/jboss/we...

It's actually the WarStructure that understands it. ;-) - http://anonsvn.jboss.org/repos/jbossas/trunk/server/src/main/org/jboss/we... Ok, then we're going need different components.xml for JBoss 4.2 and JBoss 5. https://jira.jboss.org/jira/browse/JBSEAM-3579 Yes, in fact with any Java EE 5 container, we should make it a policy in the examples to assume that the container is taking care of the persistence unit rather than Seam. Seam should only step in when the container isn't willing or able (such as with JBoss AS 4.2).

Just as a side note, it would be really cool if we could have a way to configure the persistence in Seam such that Seam will look for the JNDI name and if that fails, it falls back to having Seam bootstrap the PU. This is a matter of putting both in place and letting Seam pick. <persistence:managed-persistence-context name="entityManager" auto-create="true" persistence-unit-jndi-name="java:/appNamePU" entity-manager-factory="#{entityManagerFactoryUsedIfNecessary}"/> <persistence:entity-manager-factory name="entityManagerFactoryUsedIfNecessary" persistence-unit-name="appNamePU" persistence-unit-jndi-name="java:/appNamePU"/> This is not vetted yet, but by adding the persistence-unit-jndi-name to the entity manager factory, it could disable Seam bootstrapping if the JNDI lookup returns a hit. Then, the managed persistence context goes through similar logic when it is being created. -Dan -- Dan Allen Software consultant | Author of Seam in Action http://mojavelinux.com http://mojavelinux.com/seaminaction NOTE: While I make a strong effort to keep up with my email on a daily basis, personal or other work matters can sometimes keep me away from my email. If you contact me, but don't hear back for more than a week, it is very likely that I am excessively backlogged or the message was caught in the spam filters. Please don't hesitate to resend a message if you feel that it did not reach my attention.

> Yes, in fact with any Java EE 5 container, we should make it a > policy in the examples to assume that the container is taking care > of the persistence unit rather than Seam. Seam should only step in > when the container isn't willing or able (such as with JBoss AS 4.2). What? This isn't something that is mandated by the EE5 spec so how does this work? Looking up the EMF over JNDI only works in JBoss. The problem here isn't about EMF lookup, it's about whether the container deploys the PU or not (JBoss 4.2 doesn't for a war, whilst JBoss 5 does). That's not true. If defined as persistence-unit-ref in web.xml (I know, silly requirement) a Java EE container will load the persistence unit and make it available in JNDI for that application.

5.3.1 of JPA spec: "Within a Java EE environment, an entity manager factory may be injected using the Persistence-Unit annotation or obtained through JNDI lookup." JBoss 4 did not support this. Hibernate on JBoss AS just happens to support putting it in JNDI defined in a vendor properties (w/o the resource reference).

Can you add that to the issue then :-) We should do this in any EE example that deploys to anything but JBoss and uses SMPCs (none AFAIK).

Can you add that to the issue then :-) We should do this in any EE example that deploys to anything but JBoss and uses SMPCs (none AFAIK). https://jira.jboss.org/jira/browse/JBSEAM-3612 Jay, should we add this to the JBoss AS 5 page just as a roadmap item (not necessarily a bug) -Dan -- Dan Allen Software consultant | Author of Seam in Action http://mojavelinux.com http://mojavelinux.com/seaminaction NOTE: While I make a strong effort to keep up with my email on a daily basis, personal or other work matters can sometimes keep me away from my email. If you contact me, but don't hear back for more than a week, it is very likely that I am excessively backlogged or the message was caught in the spam filters. Please don't hesitate to resend a message if you feel that it did not reach my attention.