Seam 2.0 was released this morning, after 8 months in development!
Aside from new features, I think the most important thing about the new release is simply that the codebase is /much/ cleaner. The migration to JSF 1.2 allowed us to solve many problems and remove quite a few hacks. We also repackaged built-in components according to a much more logical schema.
Actually, this release has been ready for a couple of weeks, but we held the release back to spend time on compatibility testing with the upcoming JBoss Tools release. As excited as I am to see Seam2 finally out there, the full impact of the work we've been doing in these eight months won't be seen until JBoss Tools is officially released. I've spent many hours testing the Seam2 support over the past month, and at this point I'm super-excited about the potential of this tooling to increase productivity another notch. I can't wait to get out there and demo this to people!
Please read Norman's announcement :-)
Great News! I can't wait to see the final release of RHDS. I will apreciate to see a Time Picker in the next release of Seam.
Andres, a time picker is coming in a near release of richfaces.
BTW, have you checked out the new datepicker in richfaces? Much better than <s:calendar>...
Congratulations on shipping!
Congratulations! I started using Seam 2 when its name was 1.3 and it seems to me the best framework available for serious J2EE serious applications. And I tried many of them.
See you at JBoss convention in Orlando!
P.S. Why the richfaces calendar should be better then
Cool! I really missed a TimePicker :P Gavin, I have a question about GWT. I think serialize complete objects and send them to the client have impact on security constraints. I know the attribute in Remoting, but I don't know if it can exclude depending on current role. For example, if my role is
Continuation of previous comment:
I can't look at property , but if my role is , I need see that property.
Hi Andres, I'm not sure exactly what you're trying to say. I suggest you try asking the question in the user forum.
Try it :-)
Hehe, ok, my english is bad :P My suggestion is to declare WebRemote in a different way, depending on user role. For example, I would like to check permission with EL:
@WebRemode(exclude {@Exclude(value , when }) List getBankClients(){...}
However, I will try in the Seam Forum ;)
My suggestion was posted here . Sorry for derrailling this post, but I hate DTOs :P
thank you Seam Team. This is great news. One of the killer features here is the new Groovy support. That should really help improve productivity, especially when the Eclispe Plugin for Groovy gets even better.
Claus