<br><br><div class="gmail_quote">On Tue, Oct 21, 2008 at 12:05 PM, Jay Balunas <span dir="ltr"><<a href="mailto:tech4j@gmail.com">tech4j@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br><br><div class="gmail_quote"><div class="Ih2E3d">On Tue, Oct 21, 2008 at 9:24 AM, Ales Justin <span dir="ltr"><<a href="mailto:ales.justin@gmail.com" target="_blank">ales.justin@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I've re-applied Seam-int 5.0.0.CR4 to AS_trunk.<br>
That should take care of war deployment - I tested it yesterday on<br>
non-reverted trunk and it worked.<br>
<br>
Will this fix any other issues from the previous status besides the war deployment? <br>
</blockquote>
<br></div>
Afaik it's fixing these issues:<br>
- it recognizes war as possible Seam deployment<br>
- fixes Scanner::getTimestamp<br>
- changes jms TopicConnection</blockquote></div><div><br>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?</div></div></blockquote><div><br>A seam-gen war project also fails if deployed as a zipped war. If you use "seam explode" it deploys and appears to work fine.<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="gmail_quote"><div><br> </div><div><div></div><div class="Wj3C7c"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div>
But I would still need jboss-seam-jpa.war example in <a href="http://2.1.0.GA" target="_blank">2.1.0.GA</a><br></div>
<<a href="http://2.1.0.GA" target="_blank">http://2.1.0.GA</a>> version.<div><br>
- adding Seam war example to AS testsuite<br>
As I don't think we should move Seam testing version to 2.1.1 in<br>
current AS_trunk.<br></div>
Unless you guys are sure you can deliver <a href="http://2.1.1.GA" target="_blank">2.1.1.GA</a> <<a href="http://2.1.1.GA" target="_blank">http://2.1.1.GA</a>><div><br>
before JBoss5.GA.<br>
Which is probably not that hard ... ;-(<br>
<br>
I thought the rough plan for GA was a 2-3 weeks away?<br>
</div></blockquote>
<br>
Yes.<br>
But my guess is plans have changed a bit,<br>
due to yesterday's full rollback. ;-)<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div>
Otherwise I would suggest the following config:<br></div>
- <a href="http://JBoss5.0.GA" target="_blank">JBoss5.0.GA</a> <<a href="http://JBoss5.0.GA" target="_blank">http://JBoss5.0.GA</a>> + <a href="http://Seam-2.1.0.GA" target="_blank">Seam-2.1.0.GA</a><br>
<<a href="http://Seam-2.1.0.GA" target="_blank">http://Seam-2.1.0.GA</a>> + <a href="http://Seam-int_5.0.0.GA" target="_blank">Seam-int_5.0.0.GA</a> <<a href="http://Seam-int_5.0.0.GA" target="_blank">http://Seam-int_5.0.0.GA</a>><br>
- <a href="http://Seam-2.1.1.GA" target="_blank">Seam-2.1.1.GA</a> <<a href="http://Seam-2.1.1.GA" target="_blank">http://Seam-2.1.1.GA</a>> + <a href="http://Seam-int_5.1.0.GA" target="_blank">Seam-int_5.1.0.GA</a><br>
<<a href="http://Seam-int_5.1.0.GA" target="_blank">http://Seam-int_5.1.0.GA</a>> + <a href="http://JBoss5.1.GA" target="_blank">JBoss5.1.GA</a> <<a href="http://JBoss5.1.GA" target="_blank">http://JBoss5.1.GA</a>><br>
--> or change it yourself in <a href="http://JBoss5.0.GA" target="_blank">JBoss5.0.GA</a> <<a href="http://JBoss5.0.GA" target="_blank">http://JBoss5.0.GA</a>><div><br>
- Seam_before_2.1 + JBoss5.x --> exclude SeamInt deployer<br>
<br></div>
I'm still not understanding what <a href="http://Seam-int_5.0.0.GA" target="_blank">Seam-int_5.0.0.GA</a> <<a href="http://Seam-int_5.0.0.GA" target="_blank">http://Seam-int_5.0.0.GA</a>> is. Is it a deployer specifically for Seam on AS 5? A sub project that is installed with AS 5 that helps the integration? <br>
</blockquote>
<br>
Both. :-)<br>
<br>
Seam-int is:<br>
1) MC part<br>
- currently Seam specific deployer<br>
- hopefully in the future some other optimization<br>
<br>
2) AS part<br>
- JBossAS custom Seam impl; e.g. VFSScanner instead of URLScanner<br>
- for <a href="http://2.1.1." target="_blank">2.1.1.</a> we're thinking of optimizing how resources are looked up<br>
e.g. using JBoss5 existing lookup mechanisms (we already do it for EJB3)<br>
- MC components can be part of Seam components<br>
e.g. getting underlying TransactionManager from MC<br>
<br>
MC part will not change a lot.<br>
Where AS part will grow with Seam's changes.<br>
e.g. introduction of hooks for resources lookup optimization<br>
<br>
How this comes into JBossAS project is under the same name = jboss-seam-int.<br>
I then during the JBossAS instance build, place the in the right places:<br>
- MC part goes into JBossAS deployers<br>
- AS part goes into newly created lib-opt directory<br>
<br>
Once you deploy your Seam app,<br>
Seam+MC deployer knows which deployments are Seam deployments,<br>
and adds the Seam+AS part into deployment's classpath.<br>
Seam has a list of custom classes and if they are present they are loaded.<br>
e.g. VFS Scanner is checked, before you fallback to URLScanner<br>
<br>
Hope this explains it better. ;-)<br>
</blockquote></div></div></div><br><br clear="all"><div><div></div><div class="Wj3C7c"><br>-- <br>blog: <a href="http://in.relation.to/Bloggers/Jay" target="_blank">http://in.relation.to/Bloggers/Jay</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>blog: <a href="http://in.relation.to/Bloggers/Jay">http://in.relation.to/Bloggers/Jay</a><br>