QE team has finished testing Seam 3.0.0.Final!
What has been tested?
- Unit tests for each module
- Examples testing for JBoss 6.0.0 Final and Glassfish 3.1 with updated Weld
- Simple cluster failover test
- Ensure that the tagged version of a module is the same as the bundled jar (diffJars)
- Verify that all dependencies are bundled in the dist zip
- Documentation review
- Searching for broken links
- Simple GWT example
There are 35 Issues (so far) affecting Seam 3.0.0.Final 
1 blocker (has been already fixed in the zip, SEAM-69)
1 critical (also already fixed in the zip, SEAM-68)
There are no unresolved blocker or critical bugs  and so the build can be released!
As a good (but late) student I'm starting using Jira on Seam Social this morning. And the 1st task I submited I got this error :
java.io.IOException: No space left on device
I guess the ML is not the best place to ask for help about that but I don't know how to contact jira support (is there jira for that ;-) ? )
I have a Java EE 6 project generated from Weld archetype (as
http://seamframework.org/Documentation/CDIQuickstartForMavenUsers). The test
included in the archetype is a simple empty test wihout any DB connection.
I've tried to use @Entitymanager in the test but I've got just a Null. Just
wondering if somebody is running tests on JSF, Entities, Controllers, EJB
etc... if yes, could you share the configuration ? or perhaps a simple
those tests ?
(The only Seam module that I'm using is JSF)
Sebastian E. Ovide
In last few day I have deeply thought over wicket modul features
essential to fully integrate with wicket framework. In wicket
architecture there is idea of model as a state bean. Its quite
different in terms of live cycle from scopes provided by CDI.
1. It is page scope (in some cirumstances more than one http request)
2. It is serialized after each request and store in session or disk.
Wicket modules misses integration throught model object with wicket
architecture so I've developed some integration with it. The idea is
that you can achieve CDI beans exactly in the same way like in JSF,
through expressionLanguage. So you can inject any named or other el
private SeamModel<String> label;
and later use it on your page directly:
Label label = new Label("headerLabel", headerLabelModel);
or wrap it by other wicket model:
private SeamModel<Registartion> registartion;
Form registrationForm = new Form("registartionForm", new
and later use it on whole form.
As I follow seam 3 for some time now I understand that this is time
for bugfix rather than adding new features. Is it possible to merge
this code before final realese?
Second feature is rather small and not soo excited as previous one.
I've prepared possiblity to inject ResourceStreamLocator. Deafault is
exactly the same as in wicket but I had also developed alternative
one, which enables throught configuration to change the place where
html file are stored. In my opinion it's also simplification.
If you would like me to contribute this two feature just let me know.
There was quite a lot of changes in this module since I fork it so
there could be some problem with clean merge.