I hope everyone had a restful end of year break.  Now that we're into the new year I'd like to make it a top priority to prepare a beta release for Seam 3.  To do this, we're first going to need at least a beta release for every single Seam module - the good news though for module leads, is if your module is already at Beta1 or higher, you don't need to do anything ;-) What I'd like to do is start off with a simple status check from each of the module leads for each of the modules that are still in alpha.  To the best of my knowledge this includes the following modules: Seam Catch (Alpha3) Seam International (Alpha 3) Seam JMS (Alpha 1) Seam REST (Alpha 2) Seam Security (Alpha2) Seam Servlet (Alpha 2) If your module is in the above list, can you please describe what is still required to be done to get your module to a beta release, and roughly how long you think it will take.  I'll start with the security module: Currently the security module is in good shape, however I'm expecting to make some further changes to the authenticator API to allow better integration between the external authentication module and the core security beans, such as Identity.  I estimate that this work will take approximately 2 weeks (so should be roughly completed by the 18th of Jan) after which I'll release beta 1. Once we have an update from all module leads then we can start setting target release dates.  Ideally I would like to get the beta released before the end of this month, ideally around the 21st. Thanks, Shane _______________________________________________ seam-dev mailing list seam-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/seam-dev

The current state of JMS is reflected on the module page fairly well. I'm currently in the process of doing general housekeeping: updating versions, logging, making sure tests pass in JBoss AS 6 Final thanks to help from John Ament. I've run into a few issues trying to test with HornetQ destinations which seems more like a HornetQ bug than a configuration issue at this point but all tests that were working in JBoss AS 6 M4 are once again working on the final release. All of this work has yet to be merged into the official seam-jms branch. Here's a quick rundown of what is left to be implemented: - Ingress routing: JMS -> CDI Events - Implement routing of events as described in JSR-299's spec draft dated 20090520: where we generate proxies for relevant interfaces with: @Observes interface JMSMapping { void myMapping(@Observes @SomeQualifier SomeType type, @MyTopic Topic topic); } - Flesh out EventBridge so that routes can be managed dynamically at run time (at least the API nailed down for Beta. Would be great to have it complete). Help will be required as I haven't had any time in the past months to work on this and have only very limited time currently. Best Regards, Jordan Ganoff On Tue, Jan 4, 2011 at 9:19 AM, Jason Porter <lightguard.jp(a)gmail.com&gt;wrote: > On Tue, Jan 4, 2011 at 04:07, Shane Bryzak <sbryzak(a)redhat.com&gt; wrote: > > I hope everyone had a restful end of year break. Now that we're into > > the new year I'd like to make it a top priority to prepare a beta > > release for Seam 3. To do this, we're first going to need at least a > > beta release for every single Seam module - the good news though for > > module leads, is if your module is already at Beta1 or higher, you don't > > need to do anything ;-) > > > > What I'd like to do is start off with a simple status check from each of > > the module leads for each of the modules that are still in alpha. To > > the best of my knowledge this includes the following modules: > > > > Seam Catch (Alpha3) > > Seam International (Alpha 3) > > Seam JMS (Alpha 1) > > Seam REST (Alpha 2) > > Seam Security (Alpha2) > > Seam Servlet (Alpha 2) > > > > If your module is in the above list, can you please describe what is > > still required to be done to get your module to a beta release, and > > roughly how long you think it will take. I'll start with the security > > module: > > > > Currently the security module is in good shape, however I'm expecting to > > make some further changes to the authenticator API to allow better > > integration between the external authentication module and the core > > security beans, such as Identity. I estimate that this work will take > > approximately 2 weeks (so should be roughly completed by the 18th of > > Jan) after which I'll release beta 1. > > > > Once we have an update from all module leads then we can start setting > > target release dates. Ideally I would like to get the beta released > > before the end of this month, ideally around the 21st. > > > > Thanks, > > Shane > > > > > > > > > > _______________________________________________ > > seam-dev mailing list > > seam-dev(a)lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/seam-dev > > > > > For Catch I have some API changes that are waiting a release, and one > feature that will a small bit of new API. After that it's good for a > beta. I had hoped to get that done in December, but holidays and > other family related things stopped that from happening. I could > easily do an Alpha 4 with what I have and push the new feature off to > the beta. Dan also did another release (or will be soon) of Solder > which will have some things that I'll need (currently it's in Catch, > but will be pulled up into Solder). > > -- > Jason Porter > http://lightguard-jp.blogspot.com > http://twitter.com/lightguardjp > > Software Engineer > Open Source Advocate > > PGP key id: 926CCFF5 > PGP key available at: keyserver.net, pgp.mit.edu > > _______________________________________________ > seam-dev mailing list > seam-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/seam-dev > -- Jordan Ganoff _______________________________________________ seam-dev mailing list seam-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/seam-dev

For Seam REST there are several minor code changes planned. Besides, there is some work to be done docs+examples but this can be postponed. The most challenging part is implementing headless facelets rendering which may or may not get into the next release based on how it goes. Otherwise, Jan 21 seems OK from my point of view. Btw, talking about facelets, isn't anyone planning on implementing the same thing? I mean backporting the Renderer component from Seam 2. This component allows facelets to be rendered outside of the JSF lifecycle. Certainly, we’ll need this component outside of REST - at least for mail, excel and pdf modules. Since I am not a JSF expert, any help in this area would be appreciated. J.

On 01/04/2011 12:07 PM, Shane Bryzak wrote: > I hope everyone had a restful end of year break.  Now that we're into > the new year I'd like to make it a top priority to prepare a beta > release for Seam 3.  To do this, we're first going to need at least a > beta release for every single Seam module - the good news though for > module leads, is if your module is already at Beta1 or higher, you don't > need to do anything ;-) > > What I'd like to do is start off with a simple status check from each of > the module leads for each of the modules that are still in alpha.  To > the best of my knowledge this includes the following modules: > > Seam Catch (Alpha3) > Seam International (Alpha 3) > Seam JMS (Alpha 1) > Seam REST (Alpha 2) > Seam Security (Alpha2) > Seam Servlet (Alpha 2) > > If your module is in the above list, can you please describe what is > still required to be done to get your module to a beta release, and > roughly how long you think it will take.  I'll start with the security > module: > > Currently the security module is in good shape, however I'm expecting to > make some further changes to the authenticator API to allow better > integration between the external authentication module and the core > security beans, such as Identity.  I estimate that this work will take > approximately 2 weeks (so should be roughly completed by the 18th of > Jan) after which I'll release beta 1. > > Once we have an update from all module leads then we can start setting > target release dates.  Ideally I would like to get the beta released > before the end of this month, ideally around the 21st. > > Thanks, > Shane > > > > > _______________________________________________ > seam-dev mailing list > seam-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/seam-dev _______________________________________________ seam-dev mailing list seam-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/seam-dev