Great! Many thanks to Seam team. May I learn when Seam 2.2.1.CR3 will be available? We can't wait to use JSF 2 in Seam 2.
Any idea when the artifacts will be pushed to maven? That's blocking me from upgrading right now.
Can this security patch be applied to 2.2.0.GA? We are going live in the near future so it's unlikely we can wait for 2.2.1.GA to come out.
Why cannot you use 2.2.1.CR2?
If you don't want to use JSF2 or JBoss AS 6, It is our best current release for now.
We don't plan to back port security fix(es) to previous version.
Marek Novotny wrote on Aug 12, 2010 14:28:
Look at https://repository.jboss.org/nexus/content/repositories/releases
It's very out of date, https://repository.jboss.org/nexus/content/repositories/releases/jboss/jboss-seam/ has 2.0.0.BETA1 as the most recent release
ASAP all 17 issues will be resolved ;-). Unfortunately I am not working full time on the release and I have assigned most issues for CR3. Be patient or help with some of the issues from opened issues.
Anyway situation is not so pessimistic, my guess is this early autumn.
Marek Novotny wrote on Aug 12, 2010 14:56:
you are looking for wrong groupId. Correct is org.jboss.seam.
Ah, sorry, thanks.
One of the bugs for CR3 is https://jira.jboss.org/browse/JBSEAM-4576
Do you have any details? In what scenarios does the leak occur? Every time a new entity is instantiated? I guess not, otherwise it would have been very high priority.
I will try to explain the background of JBSEAM-4576.
It is based on Mark Struberg's findings from OpenWebBeans project (Apache's implementation of CDI spec). He find out a few issues in using Javassist, which could loss of perm-gen space with every invocation. We know about memory leaks in heap and perm-gen spaces. So Seam 2 is doing some of workarounds, which Mark discovered. He cloned javassist source code at github - http://github.com/struberg/javassist and applied his suggested fixes.
What we need is to get new release of Javassist to fix officially these issues.
So as a summary, you don't have to worry about Seam memory leaks related to javassist usage, which Mark described. They are important, but Seam 2 workaround-ed them.
This release rocks. Nowadays, we try to migrate from
the great seam-gen, and trying to use the add-on
add-ivysupport. But the template is a little outdated. Let me show you (extract from ivy-build.xml):
<property name="central.repo" value="http://repo1.maven.org/maven2"/> <property name="jboss.repo" value="http://repository.jboss.org/maven2"/> <!-- centralize some key artifact versions --> <property name="seam.version" value="2.1.2"/> <property name="jsf.version" value="1.2_12"/> <property name="richfaces.version" value="3.3.1.GA"/> <property name="icefaces.version" value="1.8.1"/> <property name="jboss-embedded.version" value="beta3.SP10"/>
I think is a good and nice
TO DOfor the next release update the versions and the repositories. Thanks to Dan Allen for the add-on, great job.
Good check. Could you file a JIRA issue?