Denis,<br><br>Since the Red Hat shutdown just began, don't interpret silence on this thread as no response. You'll likely get some responses come Jan 4th.<br><br>I'll give some responses as I see it, but expect more replies/clarification in due time.<br>
<br><div class="gmail_quote">On Wed, Dec 23, 2009 at 8:28 AM, Denis Forveille <span dir="ltr"><<a href="mailto:denis.forveille@gmail.com">denis.forveille@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;">
It seems that everybody get very excited about the development of Seam<br>
v3 and that's cool.<br></blockquote><div><br>We are getting excited primarily to get some momentum behind Seam 3. In January things are really going to pick up. But it's a ways until we can really have something that comes near as complete as Seam 2 (meaning security, jbpm, drools, JSF, etc).<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
But what about the development of Seam v2?<br></blockquote><div> </div><blockquote style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;" class="gmail_quote"><div>Is there a planned released date of Seam v2.2.1? (There are currently<br>
1000+ JIRA entries for Seam v2, 100+ assigned to Seam v2.2.1)<br>
Will we have a Seam v2.2.2 (or maybe v2.3) in the future?<br></div></blockquote><div><br>We did discuss this in the Seam meeting last week. We are very likely going to be getting a release out in early 2010 (I don't know the estimated date) for reasons you cited and because we'll need changes anyway for the Seam 3 - Seam 2 bridging effort.<br>
<br></div><blockquote style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;" class="gmail_quote"><div>
<br>
Also for seam v2.0.3 which is in CR since months, should it be<br>
possible to either release this version or cancel it?<br></div></blockquote><div><br>I'm not sure. Stay tuned for a response on that.<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
As discussed in the weld forum, us, users of seam v2/EJB 3.0 but poor<br>
non glassfish v3 (or JBoss v6) users will have to wait for months<br>
before we'll be able to use weld and seam v3 in production.<br>
<br>
The question is what are the plans to maintain seam v2.2 until 1) seam<br>
3 is GA and 2) WebSphere/Oracle/WebLogic/<name your production AS<br>
here> offer a JEE6 compliant version of their AS?<br></blockquote><div><br>We understand that Java EE 6 is very cutting edge and migration to it will take time. As Gavin said on <a href="http://in.relation.to">in.relation.to</a>, if you already have a project in place or you need to deploy in the next couple months, Seam 2 is still a very solid choice. If you are looking further out, perhaps prototyping some projects, then EE 6 is definitely where you should be looking. (But you are going to have to mind the dust if you are tapping into Seam 3 modules, since they are in the early stages).<br>
<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
All our development is based now on Seam v2 (and I hope many other<br>
users in the world..) and we are very happy with it but I think a<br>
clear statement should be made on the strategy for Seam v2.x in the<br>
meantime for the current Seam users. Or maybe it is somewhere and i<br>
missed it?<br></blockquote><div><br>
Basically, don't confuse our excitement with abandonment. I think what you are looking for is some assurance for Seam 2 that haven't been clearly stated yet. It is our intention (from my understanding) that you will be able to continue to run Seam 2 applications on JBoss 6 (mixing Java EE, CDI, etc), which translates into bug fix releases. I think what you probably won't see in Seam 2 is new features (unless they are driven primarily by the community).<br>
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
Personally I will continue to commit bug fixes when I see the fit for<br>
this in Seam v2.x but what about the rest of you guys? At some point<br>
I'll for sure try to participate to the Seam v3/Seam v2 integration<br>
module when the time will come to migrate our apps (And WebSphere will<br>
provide an implementation of CDI).<br></blockquote><div><br>It's important that you come forward with these requests. Obviously, we want to make sure we are headed in the right direction, at the right pace to suit the needs of the users.<br>
<br>I'll ask again that you be patient for responses until after the holiday ;)<br><br>Cheers,<br><br>-Dan<br></div></div><br>-- <br>Dan Allen<br>Senior Software Engineer, Red Hat | Author of Seam in Action<br>Registered Linux User #231597<br>
<br><a href="http://mojavelinux.com">http://mojavelinux.com</a><br><a href="http://mojavelinux.com/seaminaction">http://mojavelinux.com/seaminaction</a><br><a href="http://www.google.com/profiles/dan.j.allen">http://www.google.com/profiles/dan.j.allen</a><br>