I realize that a Seam 3 status update is overdue, so without further ado let me fill you in on where we are. From my previous blog, we are aiming to include these modules in Seam 3.0:
| Module | Target Version | Code Quality | Blockers |
|---|---|---|---|
| Drools 5 integration | 3.0 | Alpha | Weld Extensions Alpha 3 |
| Additional JSF 2 support | 3.0 | Beta | Seam Persistence Alpha 1 |
| Internationalization support | 3.0 | Alpha | JBoss Logging 3 |
| Seam Security | 3.0 | Alpha | Seam Persistence Alpha 1 and Seam XML Beta 1 |
| XML Configuration | 3.0 | Beta | Weld Extensions Alpha 3 |
| jBPM 3 support | 3.0 | Alpha | |
| Additional support for RESTEasy | 3.0 | Alpha | |
| Additional support for Servlet | 3.0 | Beta | |
| Seam Persistence | 3.0 | Alpha | Seam XML Beta1 |
| Javascript Remoting | 3.0 | Beta | |
| JMS events bridge | 3.0 | Alpha | |
| Support for GWT | 3.0 | RC | |
| Support for Wicket | 3.0 | RC | |
| Reporting (Excel and PDF support) | 3.0 or 3.1 | Alpha | |
| Seam Mail | 3.0 or 3.1 | Alpha | |
| Exception Handling | 3.0 or 3.1 | Alpha | |
| Scheduling support, including asynchronous events | 3.0 or 3.1 | Alpha | |
| Seam 2 Backwards Compatibility | 3.1 | ||
| Spring Integration | 3.1 | ||
| Support for JBoss ESB | 3.1 | ||
| Provisionally, support for jBPM 5 | 3.1 |
As you can see, all modules have been started, with many in or approaching Beta (feature complete). The primary blockers are getting Weld Extensions and XML Configuration API complete - you can expect these, and the waterfall of other module releases over the next few weeks.
Once we have have alpha or beta releases of all required modules for Seam 3.0 we will put out a beta of the whole distribution - again, expect this in the next few weeks.
We purposefully do not give even estimates of an overall release date - I can only say it will be ready when it is ready!
Update: if you want to track development of Seam 3, then checkout the wiki page which has an overview of the modules and will be kept up to date
I would love to see the mail module make it in for 3.0. Thanks for the update and coding efforts.
Where is the Wicket module? which is provided in seam2
Excellent point! It will be in 3.0, and is basically finished. I updated the table...
First of all: Thanks for the update. I'm sure you guys are doing a great job to get finished as fast as possible.
I'd like to use the opportunity to emphasize the importance of such updates. We, the Seam users / early adopters, usually have people in our companies to whom we need to justify our architectural decisions. And usually we are having a hard time justifying JEE 6 (it's not Spring) and Seam (it's not Spring either). Talking about time lines and productivity releases is a huge part of these discussions, and no, neither my boss nor the chief architect is not interested in any Alpha releases, and certainly I can't answer . Well, technically I could answer that, but only if I'm interested in using other frameworks in the next projects ;-)
So, please do keep us updated on a regular base, and please try to communicate as sustainable as possible. These information is badly needed...
Cheers, Jan
What about the 'Seam Application Framework'? This is listed on the main page but has no other details about actual status, either in the list above or in the status page from the Seam wiki.
Since this is a big part of Seam-gen I assume it will be there somewhere but I have clients that are concerned it is not mentioned more prominently in Seam 3 planning information.
Thanks Pete for the update... it was indeed way overdue! I can't agree more with what Jan Groth has already posted: please keep the information flow at a constant rate. This is important - especially for early adopters.
I know that it is hard to tell specific dates and I hate nothing more then being asked for an ETA myself. BUT I also know that IMHO is an unprofessional answer and frankly makes the project look like a non-serious student project.
Don't get me wrong, I do love Seam and the job you guys do and I want to use it in my projects. BUT with statements like that you don't exactly make my life easier selling Seam to decision makers who only know that a) it is not Spring and b) does not even have a release date...
Could you please provide some more information on that? I could not find the wicket module in the maven repository and I believe the version on trunk does not seem to have the right groupId (linked from Seam 3 Modules). There are a few issues related to this in SEAMWICKET, but is there anything we can use right now with a Seam 3 snapshot?
You can expect more info on our seam-gen successor (and with it the Seam Application Framework) soon :-)
We originally developed Wicket support under Weld (find it here), and have yet to repackage it as Seam Wicket - so for now, you should work with the Weld Wicket support.
I understand the frustration causes, and can only apologise. Once we get the first beta of Seam 3 out, we should be able to see the path to 3.0 much more clearly.
Thank you for the update! It's nice to hear, that Seam Development is going on. For the summer it looked like there was a BIG break in development. But now, in a little time, hopefully, we can really try Seam 3 ;-) Now it is more experiment the development.
Greetings Florian Hell
I agree with Jan. Well put.
Thanks guys for giving us some hope we'll be seeing Seam 3.0 before the end of the year. It makes sense to wait a bit longer because the underlying infrastructure (App Servers) still needs some catching up to do with regards to Java EE 6. So far, only Glassfish v3 has delivered on the Java EE 6 promise, and it seems that others are taking their sweet time, possibly aiming for 2011.
Btw, just out of curiosity, I don't see Gavin King being actively involved in Seam 3 anymore. Is this a correct observation?
Gavin isn't involved on a day-to-day basis with Seam 3, but is keeping up with where we are going, and providing invaluable advice :-)
Thanks, good to hear.
On another topic I'd like to provide some input from the architectural POV for the decision about the 4 components that are tagged with .
IMHO it would make a whole lot of sense to include and maybe also into the initial 3.0 release if possible while I wouldn't mind waiting for and until a later release.
The reason is that Exception handling and also the asynchronous events are very essential features to an application design while Reporting and Mail only serve one particular functional aspect of the application and integrating/changing them at a later stage should be reasonable easy as opposed to switch e.g. the Exception handling concepts.
Just my 2 cents...
Thorsten: I completely understand your statements about Exception Handling, that's why I'm doing it :) However, I am not part of JBoss / Red Hat and it's a community contributed module. I'm working when I can and documentation is standing my way right now. I'm hoping to have it ready in time for the Seam 3.0 Beta and am doing my best with the many things (including three small children) demanding my time. If you or anyone else is interested in helping out Feel free to find the code on GitHub (http://github.com/LightGuard/seam-exception-handling until all of Seam 3 is migrated to GitHub) and help out.
Nice to here that things moved forward and we'll have soon beta version. Just one comment regarding JBPM support. You've wrote jBPM 3 support, shouldn't it be JBPM 4 ? I suppose it's just a mistype :)
I don't think so. AFAIK JBPM 4 won't be supported. Only version 3 and at a later stage version 5. Seems like JBPM 4 was not exactly a huge success and never made it into the commercial JBoss stack.