As everyone should know now, Seam is an important part of our Nuxeo 5 ECM stack.

We are currently using Seam 1.0.1, but it is nice to learn that Seam 1.1 is coming along, and it’s going to be very good.

There is a very nice (like always, on InfoQ) interview of Gavin King, Seam’s creator, that explains in details where Seam is headed (rest assured that Nuxeo 5.1 will include Seam 1.1, but let’s focus on the Nuxeo 5.0 release now ;) ).

“Cristiano”, from Faqs.it, has written a comment about our switch from Python to Java in his blog.

Here is my comment about his comment.

Hi Cristiano,

Thanks for your comments about our Java switch. I fully agree with you that a lot of innovations come from the OSS ecosystem, but there are some wrong facts in your remarks that I have to correct, including the following:

• Python, for instance, did actually copy Java’s syntax (and concept) for annotation (called decorators in Python-speak), not the other way around.

• Generics are irrelevant in dynamics languages, hence dynamic languages can’t have “out-innovated” Java on that matter.

• The sentence “Python doesn’t fit in the enterprise-class web apps market” is in part irrelevant for us, because we are not only in the web apps market, but also in the rich client market (with Eclipse RCP).

• Your opposition (in the last sentence) of “Java vs. OSS” is completely disconnected from the reality: Java is GPL now (or will be RSN), Java OSS communities (JBoss, Spring, Apache, Eclipse, Nuxeo…) are among the most active (if not the most active) OSS communities now. And some of these communities have a lot of money at their disposal, because these are projects for building enterprise-class OSS software (or middleware), backed by serious companies like Sun, IBM, Red Hat, or Nuxeo.

IMHO, OSS is now driving, in many ways, the development of Java, and this means that there is no need to oppose Java if you are (like I am) an OSS believer.