Hi Jay, Did you run it against JBossTools 3.x or JBDS 1.1 ? Any open urgent issues you know about would be nice to know since we are 2 weeks away from 3 beta1 release. /max Testing status for Seam 2.1.0.GA testing on windows XP. > > JDK 6, AS 5 CR2 > ---------------------------- > itext - good > drools - good > seam-gen ear > - amazingly slow > - part of it was ajax4jsf logging below (but not all of it - need to > get > this changed to trace). > org.ajax4jsf.io.parser.FastHtmlParser] (http-127.0.0.1-8080-1) Parser > reached state is StateManager.DOCTYPE > > JDK 5, AS 5 CR2 > --------------------------- > booking - good > excel - good > seam-gen war - failed with war deployment error. > > testsuite - 1 fail - testPayMultiple > - java.lang.AssertionError > at > > org.jboss.seam.example.seampay.test.PaymentProcessorTest.testPayMultiple(PaymentProcessorTest.java:71) > > > > > -- /max

On Tue, 21 Oct 2008 14:56:16 +0200, Jay Balunas <tech4j(a)gmail.com&gt; wrote: Hi Max, > > Jozef will be doing most of our JBDS testing. What version do you want him > to use? > We are testing/qa'ing for beta1 at the moment; you can use the nightly build updatesite at: http://download.jboss.org/jbosstools/updates/nightly/3.0.0.Beta1 or get the zips at http://download.jboss.org/jbosstools/builds/nightly/latest-3.0.0.Beta1-bu...

<http://download.jboss.org/jbosstools/builds/nightly/latest-3.0.0.Beta1-bu... or you can get JBDS 2.0.0.beta1 full install nightly build from http://reports.qa.atl.jboss.com/binaries/RHDS/nightly/latest-2.0.0.Beta1-... They all have the same Seam related functionallity. /max I should also be able to do some testing with it this morning. I have > been > focusing on AS 5 integration testing so if it would be helpful I can test > with that, and Jozef can test with JBoss 4.2.3. > > -Jay > > On Tue, Oct 21, 2008 at 2:57 AM, Max Rydahl Andersen < > max.andersen(a)redhat.com&gt; wrote: > > Hi Jay, >> >> Did you run it against JBossTools 3.x or JBDS 1.1 ? >> >> Any open urgent issues you know about would be nice to know since we are >> 2 >> weeks away from 3 beta1 release. >> >> /max >> >> >> Testing status for Seam 2.1.0.GA testing on windows XP. >> >>> >>> JDK 6, AS 5 CR2 >>> ---------------------------- >>> itext - good >>> drools - good >>> seam-gen ear >>> - amazingly slow >>> - part of it was ajax4jsf logging below (but not all of it - need to >>> get >>> this changed to trace). >>> org.ajax4jsf.io.parser.FastHtmlParser] (http-127.0.0.1-8080-1) Parser >>> reached state is StateManager.DOCTYPE >>> >>> JDK 5, AS 5 CR2 >>> --------------------------- >>> booking - good >>> excel - good >>> seam-gen war - failed with war deployment error. >>> >>> testsuite - 1 fail - testPayMultiple >>> - java.lang.AssertionError >>> at >>> >>> >>> org.jboss.seam.example.seampay.test.PaymentProcessorTest.testPayMultiple(PaymentProcessorTest.java:71) >>> >>> >>> >>> >>> >>> >> >> -- >> /max >> >> > > > -- /max

I should also be able to do some testing with it this morning. I have been focusing on AS 5 integration testing so if it would be helpful I can test with that, and Jozef can test with JBoss 4.2.3.

-Jay On Tue, Oct 21, 2008 at 2:57 AM, Max Rydahl Andersen < max.andersen(a)redhat.com&gt; wrote: > Hi Jay, > > Did you run it against JBossTools 3.x or JBDS 1.1 ? > > Any open urgent issues you know about would be nice to know since we > are 2 > weeks away from 3 beta1 release. > > /max > > > Testing status for Seam 2.1.0.GA testing on windows XP. >> >> JDK 6, AS 5 CR2 >> ---------------------------- >> itext - good >> drools - good >> seam-gen ear >> - amazingly slow >> - part of it was ajax4jsf logging below (but not all of it - need to >> get >> this changed to trace). >> org.ajax4jsf.io.parser.FastHtmlParser] (http-127.0.0.1-8080-1) Parser >> reached state is StateManager.DOCTYPE >> >> JDK 5, AS 5 CR2 >> --------------------------- >> booking - good >> excel - good >> seam-gen war - failed with war deployment error. >> >> testsuite - 1 fail - testPayMultiple >> - java.lang.AssertionError >> at >> >> org.jboss.seam.example.seampay.test.PaymentProcessorTest.testPayMultiple(PaymentProcessorTest.java:71) >> >> >> >> >> > > > -- > /max >

Testing status for Seam 2.1.0.GA <http://2.1.0.GA> testing on windows XP. JDK 6, AS 5 CR2 ---------------------------- itext - good drools - good seam-gen ear - amazingly slow - part of it was ajax4jsf logging below (but not all of it - need to get this changed to trace). org.ajax4jsf.io.parser.FastHtmlParser] (http-127.0.0.1-8080-1) Parser reached state is StateManager.DOCTYPE JDK 5, AS 5 CR2 --------------------------- booking - good excel - good seam-gen war - failed with war deployment error. testsuite - 1 fail - testPayMultiple - | java.lang.AssertionError at org.jboss.seam.example.seampay.test.PaymentProcessorTest.testPayMultiple(PaymentProcessorTest.java:71) | -- blog: http://in.relation.to/Bloggers/Jay ------------------------------------------------------------------------ _______________________________________________ seam-dev mailing list seam-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/seam-dev

I've re-applied Seam-int 5.0.0.CR4 to AS_trunk. That should take care of war deployment - I tested it yesterday on non-reverted trunk and it worked.

But I would still need jboss-seam-jpa.war example in 2.1.0.GA version. - adding Seam war example to AS testsuite As I don't think we should move Seam testing version to 2.1.1 in current AS_trunk. Unless you guys are sure you can deliver 2.1.1.GA before JBoss5.GA. Which is probably not that hard ... ;-(

Otherwise I would suggest the following config: - JBoss5.0.GA + Seam-2.1.0.GA + Seam-int_5.0.0.GA - Seam-2.1.1.GA + Seam-int_5.1.0.GA + JBoss5.1.GA --> or change it yourself in JBoss5.0.GA - Seam_before_2.1 + JBoss5.x --> exclude SeamInt deployer

Jay Balunas wrote: > Testing status for Seam 2.1.0.GA <http://2.1.0.GA> testing on windows XP. > > > JDK 6, AS 5 CR2 > ---------------------------- > itext - good > drools - good > seam-gen ear > - amazingly slow > - part of it was ajax4jsf logging below (but not all of it - need to > get this changed to trace). org.ajax4jsf.io.parser.FastHtmlParser] > (http-127.0.0.1-8080-1) Parser reached state is StateManager.DOCTYPE > > JDK 5, AS 5 CR2 > --------------------------- > booking - good > excel - good > seam-gen war - failed with war deployment error. > > testsuite - 1 fail - testPayMultiple > - | java.lang.AssertionError > at > org.jboss.seam.example.seampay.test.PaymentProcessorTest.testPayMultiple(PaymentProcessorTest.java:71) > > > | > > -- > blog: http://in.relation.to/Bloggers/Jay > > > ------------------------------------------------------------------------ > > _______________________________________________ > seam-dev mailing list > seam-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/seam-dev >

I've re-applied Seam-int 5.0.0.CR4 to AS_trunk. > That should take care of war deployment - I tested it yesterday on > non-reverted trunk and it worked. > > Will this fix any other issues from the previous status besides the war > deployment? > Afaik it's fixing these issues: - it recognizes war as possible Seam deployment - fixes Scanner::getTimestamp - changes jms TopicConnection

But I would still need jboss-seam-jpa.war example in 2.1.0.GA > <http://2.1.0.GA> version. > - adding Seam war example to AS testsuite > As I don't think we should move Seam testing version to 2.1.1 in > current AS_trunk. > Unless you guys are sure you can deliver 2.1.1.GA <http://2.1.1.GA> > before JBoss5.GA. > Which is probably not that hard ... ;-( > > I thought the rough plan for GA was a 2-3 weeks away? > Yes. But my guess is plans have changed a bit, due to yesterday's full rollback. ;-)

Otherwise I would suggest the following config: > - JBoss5.0.GA <http://JBoss5.0.GA> + Seam-2.1.0.GA > <http://Seam-2.1.0.GA> + Seam-int_5.0.0.GA <http://Seam-int_5.0.0.GA> > - Seam-2.1.1.GA <http://Seam-2.1.1.GA> + Seam-int_5.1.0.GA > <http://Seam-int_5.1.0.GA> + JBoss5.1.GA <http://JBoss5.1.GA> > --> or change it yourself in JBoss5.0.GA <http://JBoss5.0.GA> > - Seam_before_2.1 + JBoss5.x --> exclude SeamInt deployer > > I'm still not understanding what Seam-int_5.0.0.GA < > http://Seam-int_5.0.0.GA> is. Is it a deployer specifically for Seam on > AS 5? A sub project that is installed with AS 5 that helps the integration? > > Both. :-) Seam-int is: 1) MC part - currently Seam specific deployer - hopefully in the future some other optimization 2) AS part - JBossAS custom Seam impl; e.g. VFSScanner instead of URLScanner - for 2.1.1. we're thinking of optimizing how resources are looked up e.g. using JBoss5 existing lookup mechanisms (we already do it for EJB3) - MC components can be part of Seam components e.g. getting underlying TransactionManager from MC MC part will not change a lot. Where AS part will grow with Seam's changes. e.g. introduction of hooks for resources lookup optimization How this comes into JBossAS project is under the same name = jboss-seam-int. I then during the JBossAS instance build, place the in the right places: - MC part goes into JBossAS deployers - AS part goes into newly created lib-opt directory Once you deploy your Seam app, Seam+MC deployer knows which deployments are Seam deployments, and adds the Seam+AS part into deployment's classpath. Seam has a list of custom classes and if they are present they are loaded. e.g. VFS Scanner is checked, before you fallback to URLScanner Hope this explains it better. ;-)

On Tue, Oct 21, 2008 at 9:24 AM, Ales Justin <ales.justin(a)gmail.com&gt;wrote: > I've re-applied Seam-int 5.0.0.CR4 to AS_trunk. >> That should take care of war deployment - I tested it yesterday on >> non-reverted trunk and it worked. >> >> Will this fix any other issues from the previous status besides the war >> deployment? >> > > Afaik it's fixing these issues: > - it recognizes war as possible Seam deployment > - fixes Scanner::getTimestamp > - changes jms TopicConnection With the latest trunk from about 20 minutes ago I am still getting zip file exceptions with the JPA and hibernate war files. Perhaps there is another change needed to use the correct deployer?

> > > But I would still need jboss-seam-jpa.war example in 2.1.0.GA >> <http://2.1.0.GA> version. >> - adding Seam war example to AS testsuite >> As I don't think we should move Seam testing version to 2.1.1 in >> current AS_trunk. >> Unless you guys are sure you can deliver 2.1.1.GA <http://2.1.1.GA> >> before JBoss5.GA. >> Which is probably not that hard ... ;-( >> >> I thought the rough plan for GA was a 2-3 weeks away? >> > > Yes. > But my guess is plans have changed a bit, > due to yesterday's full rollback. ;-) > > Otherwise I would suggest the following config: >> - JBoss5.0.GA <http://JBoss5.0.GA> + Seam-2.1.0.GA >> <http://Seam-2.1.0.GA> + Seam-int_5.0.0.GA <http://Seam-int_5.0.0.GA> >> - Seam-2.1.1.GA <http://Seam-2.1.1.GA> + Seam-int_5.1.0.GA >> <http://Seam-int_5.1.0.GA> + JBoss5.1.GA <http://JBoss5.1.GA> >> --> or change it yourself in JBoss5.0.GA <http://JBoss5.0.GA> >> - Seam_before_2.1 + JBoss5.x --> exclude SeamInt deployer >> >> I'm still not understanding what Seam-int_5.0.0.GA < >> http://Seam-int_5.0.0.GA> is. Is it a deployer specifically for Seam on >> AS 5? A sub project that is installed with AS 5 that helps the integration? >> >> > > Both. :-) > > Seam-int is: > 1) MC part > - currently Seam specific deployer > - hopefully in the future some other optimization > > 2) AS part > - JBossAS custom Seam impl; e.g. VFSScanner instead of URLScanner > - for 2.1.1. we're thinking of optimizing how resources are looked up > e.g. using JBoss5 existing lookup mechanisms (we already do it for EJB3) > - MC components can be part of Seam components > e.g. getting underlying TransactionManager from MC > > MC part will not change a lot. > Where AS part will grow with Seam's changes. > e.g. introduction of hooks for resources lookup optimization > > How this comes into JBossAS project is under the same name = > jboss-seam-int. > I then during the JBossAS instance build, place the in the right places: > - MC part goes into JBossAS deployers > - AS part goes into newly created lib-opt directory > > Once you deploy your Seam app, > Seam+MC deployer knows which deployments are Seam deployments, > and adds the Seam+AS part into deployment's classpath. > Seam has a list of custom classes and if they are present they are loaded. > e.g. VFS Scanner is checked, before you fallback to URLScanner > > Hope this explains it better. ;-) > -- blog: http://in.relation.to/Bloggers/Jay

Explains it perfectly...but is this documented somewhere? This seems like great information that I don't want to lose when I push this message out of my inbox. If it's already documented, then perhaps an FAQ on swfk.org <http://swfk.org> could point to it.

Awesome. On Wed, Oct 22, 2008 at 4:52 AM, Ales Justin <ales.justin(a)gmail.com&gt;wrote: > Explains it perfectly...but is this documented somewhere? This seems like >> great information that I don't want to lose when I push this message out of >> my inbox. If it's already documented, then perhaps an FAQ on swfk.org < >> http://swfk.org> could point to it. >> > > http://www.jboss.org/community/docs/DOC-12848 > > I'll also add a link to this from swfk.org. > > -Ales > -- 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. _______________________________________________ seam-dev mailing list seam-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/seam-dev