Help

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:

ModuleTarget VersionCode QualityBlockers
Drools 5 integration3.0AlphaWeld Extensions Alpha 3
Additional JSF 2 support3.0BetaSeam Persistence Alpha 1
Internationalization support3.0AlphaJBoss Logging 3
Seam Security3.0AlphaSeam Persistence Alpha 1 and Seam XML Beta 1
XML Configuration3.0BetaWeld Extensions Alpha 3
jBPM 3 support3.0Alpha
Additional support for RESTEasy3.0Alpha
Additional support for Servlet3.0Beta
Seam Persistence3.0AlphaSeam XML Beta1
Javascript Remoting3.0Beta
JMS events bridge3.0Alpha
Support for GWT3.0RC
Support for Wicket3.0RC
Reporting (Excel and PDF support)3.0 or 3.1Alpha
Seam Mail3.0 or 3.1Alpha
Exception Handling3.0 or 3.1Alpha
Scheduling support, including asynchronous events3.0 or 3.1Alpha
Seam 2 Backwards Compatibility3.1
Spring Integration3.1
Support for JBoss ESB3.1
Provisionally, support for jBPM 53.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
20 comments:
 
24. Aug 2010, 17:56 CET | Link
Walter

I would love to see the mail module make it in for 3.0. Thanks for the update and coding efforts.

ReplyQuote
 
24. Aug 2010, 18:24 CET | Link

Where is the Wicket module? which is provided in seam2

 
24. Aug 2010, 19:59 CET | Link
hantsy wrote on Aug 24, 2010 12:24:
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...

 
24. Aug 2010, 21:00 CET | Link
jan groth

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 Seam will be ready when it is ready. 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

 
25. Aug 2010, 00:40 CET | Link
Stuart Smith

What about the 'Seam Application Framework'? This is listed on the main planned Seam 3 modules 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.

 
25. Aug 2010, 08:51 CET | Link
Thorsten

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 its done when its done 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...

 
25. Aug 2010, 10:54 CET | Link
Kariem Hussein | kariem.hussein(AT)gmail.com
Pete Muir wrote on Aug 24, 2010 13:59:
hantsy wrote on Aug 24, 2010 12:24:
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...

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?

 
25. Aug 2010, 12:24 CET | Link
Stuart Smith wrote on Aug 24, 2010 18:40:
What about the 'Seam Application Framework'? This is listed on the main planned Seam 3 modules 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.

You can expect more info on our seam-gen successor (and with it the Seam Application Framework) soon :-)

 
25. Aug 2010, 12:26 CET | Link
Kariem Hussein wrote on Aug 25, 2010 04:54:
Pete Muir wrote on Aug 24, 2010 13:59:
hantsy wrote on Aug 24, 2010 12:24:
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...
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?

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.

 
25. Aug 2010, 12:28 CET | Link
Thorsten wrote on Aug 25, 2010 02:51:
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...

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.

 
25. Aug 2010, 13:32 CET | Link

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

 
25. Aug 2010, 16:56 CET | Link
Greg L

I agree with Jan. Well put.

25. Aug 2010, 22:53 CET | Link
S Jaffry

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?

26. Aug 2010, 12:28 CET | Link

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 :-)

 
27. Aug 2010, 12:54 CET | Link
Thorsten
Pete Muir wrote on Aug 25, 2010 06:28:
Thorsten wrote on Aug 25, 2010 02:51:
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...
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.

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 3.0 or 3.1.

IMHO it would make a whole lot of sense to include Exception Handling and maybe also Scheduling support, including asynchronous events into the initial 3.0 release if possible while I wouldn't mind waiting for Reporting and Seam Mail 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...

 
27. Aug 2010, 16:04 CET | Link
Thorsten wrote on Aug 27, 2010 06:54:
Pete Muir wrote on Aug 25, 2010 06:28:
Thorsten wrote on Aug 25, 2010 02:51:
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...
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.
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 3.0 or 3.1. IMHO it would make a whole lot of sense to include Exception Handling and maybe also Scheduling support, including asynchronous events into the initial 3.0 release if possible while I wouldn't mind waiting for Reporting and Seam Mail 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.

 
29. Aug 2010, 20:00 CET | Link
Lukas Simokaitis | lukas.simokaitis(AT)gmail.com

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 :)

 
31. Aug 2010, 13:44 CET | Link
Thorsten
Lukas Simokaitis wrote on Aug 29, 2010 14:00:
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.

 
23. Dec 2013, 09:16 CET | Link

In a coverage by 60 Minutes, it is shown swiss rolex replica watches how innovative residents of Paraguay use a garbage heap in town to their advantage. Not only do the residents make a living from the disposal, but cheap rolex watches for sale they also use the trash to create musical instruments. In the capital city, trash is in abundance and can be found on the streets, in yards and even water sources. But though ugly trash surrounds the city, the residents don't let it get them down.

 
08. Jan 2014, 13:45 CET | Link

Design and implementation of software varies depending on the complexity of the software. For instance, design and creation of Microsoft Word software will take much more time than designing and developing Microsoft Notepad because of the difference in functionalities in each one.

Post Comment