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. ;-)