<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
In the interest of brevity, here's a link to a shared filter in JIRA
that displays the remaining open issues. Since my last update,
we've slipped a little bit - we're now up to 62 issues. <br>
<br>
<a
href="https://issues.jboss.org/secure/IssueNavigator.jspa?mode=hide&requestId=12314291">https://issues.jboss.org/secure/IssueNavigator.jspa?mode=hide&requestId=12314291</a><br>
<br>
In regards to the Glassfish issues, we're taking the following
steps:<br>
<br>
1) Created a new compatibility module - <a
href="https://github.com/seam/compatibility">https://github.com/seam/compatibility</a><br>
<br>
This module will consist of tests solely designed to test the
compatibility of a container. We currently have tests in Solder
(and other modules) that test compatibility issues, these tests will
be moved into the compatibility module and we'll be creating new
tests as we come across undiscovered issues. The intent is for the
QE guys to take ownership of this module so that we have a single
set of tests that we can run in various containers to check for
compliance.<br>
<br>
2) Document all known compatibility issues in one place<br>
<br>
Dan has made a start on this already - see <a
href="http://seamframework.org/Seam3/CompatibilityHome">http://seamframework.org/Seam3/Compatibility</a>.
This page is the definitive source on compatibility issues, and
should contain all our notes and research about known issues.
Ideally, we should have JIRA links for each issue that's listed on
this page.<br>
<br>
It's my intent that these issues with Glassfish don't hold up the
3.0 Final release. There will be some definite problems with
running Seam in a GF container, however we've reached the point
where there are no reasonable workarounds for some of the newly
discovered issues. We are going to continue our research efforts
and do our best to collaborate with the Glassfish developers to
resolve these issues, however our message should be that Seam 3 is
compliant with the CDI specification, and any issues with using it
in Glassfish are due to bugs in Glassfish itself. Please don't blog
or tweet about any of this at the moment until we have a chance to
touch base with the Glassfish team to make them aware of the issues.<br>
<br>
Thanks,<br>
Shane<br>
<br>
<br>
On 23/03/11 18:40, Shane Bryzak wrote:
<blockquote cite="mid:4D89B1E6.7070301@redhat.com" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
I've decided to update the list twice a day, to be a bit more
granular. The good news is we're already down to 59 issues. The
bad news is that a potentially serious Glassfish issue has popped
up. At the moment we're still in the research phase, but as soon
as we have something more concrete I'll post an update.<br>
</blockquote>
<br>
</body>
</html>