Help

I'm glad to announce we've finally released Weld 1.1.1.Final.

The release includes a couple of nasty bug fixes, which specially gave Seam3 and GlassFish users a lot of trouble:

Another performance improvement:

And re-factored web containers integration, which now includes Jetty7+ support:

The non-maven distribution can be found at SF.net:

Thanks to everyone involved -- Stuart, Pete, Martin, Nicklas, ... Seam3 guys, ... to name a few. :-)

10 comments:
 
06. Apr 2011, 07:54 CET | Link
Marx

How to use it on JBoss AS 6.0? Should I include it in war, or upgrade in JBoss library?

ReplyQuote
 
06. Apr 2011, 07:58 CET | Link
Marx

weld-api-bom-1.1.1.Final.pom is not available

 
06. Apr 2011, 08:59 CET | Link

Is there a migration path for AS6 final? :)

Adam

 
06. Apr 2011, 10:23 CET | Link
Marx

I saw sth. like this for 1.1: http://seamframework.org/Community/UpgradeJBoss600ToUseWeld110

 
06. Apr 2011, 14:11 CET | Link

Ah this should work, thanks!

Adam

 
06. Apr 2011, 15:04 CET | Link
Marx wrote on Apr 06, 2011 01:58:
weld-api-bom-1.1.1.Final.pom is not available

Right, Weld 1.1.1 is still based on the Weld 1.1 API (this is totally correct - we don't change API or SPI in micro versions) so you would only expect to have weld-api-bom-1.1.Final.pom in the repo.

 
06. Apr 2011, 17:56 CET | Link
Thai
Marx wrote on Apr 06, 2011 01:54:
How to use it on JBoss AS 6.0? Should I include it in war, or upgrade in JBoss library?

And how to use it on Glassfish 3.x?

 
06. Apr 2011, 20:05 CET | Link
And how to use it on Glassfish 3.x?

http://www.seamframework.org/Seam3/Compatibility

 
08. Apr 2011, 16:21 CET | Link
Calebe Varga (cvarga) | calebe.varga(AT)gmail.com

In fact works.

Download the latest Jboss AS 6 compilation from jboss hudson

or download and compile yourself

Inside the yourconf/deployers/weld.deployer folder overwrite the weld-core-no-jsf.jar with the latest weld-core-1.1.1.Final.jar

I suggest you only overwrite the weld.deployer folder from the official JbossAS6.0.0-Final with the compiled one, i do not know what kind of bugs are on the other modules.

Have fun !

 
04. May 2011, 13:28 CET | Link
Marcos Hanaberas

Maybe the next version can fix the problem with sl4j (class conflict). For example: I can“t use Hibernate 3.6.3 with Weld in Tomcat, since the first needs sl4j 1.6 and the last 1.5. We changed weld to OWB to solve the problem, OWB is not mature yet (new problems).

Post Comment