Tags
Authors
Genuitec switches course part deux
I am glad that Genuitec finally made their changes to Hibernate Tools publicly available at their open source resources page. That is all that I/we ever asked for.
Genuitec switches course :-)
Wow, amazing how quickly my last blog entry got results! Since I posted it, it appears that Genuitec have decided to comply with the LGPL and provide their modifications to Hibernate tools in source form:
Genuitec CEO beclowns himself
In an amazingly intemperate and irrational blog entry:
This is a pretty big day for the Hibernate family. We welcome three new top level projects:
Exadel and JBoss partnership
Exadel and JBoss are partnering to build a unified development environment for enterprise Java, comparable to Microsoft's .Net. Please read the announcement here:
Thoughts on Seam 1.2
This release was not meant to be such a big one. We had originally intended to call it 1.1.7, but when we sat down and looked at the size of the changelog since the 1.1.6 release, we realized that there were simply too many changes for a point release. So it got a very last minute rebranding ;-)
Seam 1.2 GA is out
Seam 1.2 introduces many improvements including out of the box integration with the Spring Framework, EL support in HQL/EJB-QL, entity level security, SSL redirection, simplified configuration, improvements to orchestation via pages.xml and many enhancements to seam-gen, including support for composite keys and circular associations and integration of Ajax4JSF.
EL in QL
By the way, my favorite new Seam 1.2 feature is this one:
Seam 1.1.6 is out
Seam 1.1.6 features several important bugfixes and new features for Seam/Security,
including remember me
functionality, integration of JCaptcha, support for automatic
redirects to and from the login page when authorization checks fail and a minor API
redesign. Seam's exception handling facility was totally redesigned, to be much more
robust and work better with Seam/Security. Also, the seam-gen tool now integrates
Seam/Security. This work was all based upon the huge volume of user feedback we
received since the 1.1.5 release.