Help

I'm pleased to announce the release of Weld 1.0.0 - the announcements have been flowing in over the last few days, but this is my favorite!

You can find some quick download links below or you can pull the artifacts from the maven central repository.

Weld is used in GlassFish V3 and the upcoming JBoss AS EE 6 Preview release release (watch Jason's blog for more!). We also have support for Servlet containers such as Tomcat and Jetty. JSF support is built in, but with Weld you could use Wicket as your view layer, and Swing, or even JavaFX is supported via the Java SE support. If you are an OSGi fan, there's a bundle.

If you are just getting started, there are a few examples in the distribution to guide you (look for instructions in the reference guide, and each example has a readme.txt). If you are looking for help, try our forums, or perhaps join us on IRC.

I intend to do regular releases of Weld from now on (around 8-10 weeks apart), and for 1.0.1 we'll be concentrating on running an indepth performance and scalability analysis (as well as fixing those bugs you report!). Those of you who follow us closely will know that we've been concentrating on Weld/JSR-299 recently, but with 1.0.0 out, you can expect to see our attention swing back to Seam 3 - so watch this space, as soon as we have nightly builds to try out, I'll post instructions :-)

One omission from the CR1 release was the reference documentation -- since then a lot of effort has been put into the reference guide and the JavaDoc for the CDI API - make sure you check it out!

[Weld Download] | [Weld JIRA] | [CDI Javadoc] [ Reference Guide] | [Weld Release Notes] ]

19 comments:
 
12. Nov 2009, 23:22 CET | Link

Downloading...

ReplyQuote
 
12. Nov 2009, 23:24 CET | Link

I have just noticed that Seam is LGPL and Weld is APL... So.. Seam 3 will be?

ReplyQuote
 
12. Nov 2009, 23:51 CET | Link

AFAIK we are planning to stick with the LGPL.

Weld, as the CDI RI had to be APL to agree with JCP licensing.

ReplyQuote
 
13. Nov 2009, 00:20 CET | Link
Hernan Moreno

Great news finally after a long wait ... I'm downloading Weld 1.0...

ReplyQuote
16. Nov 2009, 06:34 CET | Link
junico

Hi Pete, I'm reading the guide, and really liked the job You guys have done, thanks

The only problem is that I could not get the login example to work with the @PersistenceContext injection, it is always null on method invocation,

I'm using glassfish v3 prelude

thanks for any help

ReplyQuote
16. Nov 2009, 07:11 CET | Link

Well, if it's null (rather than the container reporting an error) it kinda sounds more like a bug in glassfish.

I'm assuming you did create an entity named User, together with a persistence.xml file, right?

ReplyQuote
16. Nov 2009, 19:34 CET | Link
Nik

I'm no glassfish user but I recall some thread from the Weld forum saying something like not included in Prelude, grab a fresher build

ReplyQuote
17. Nov 2009, 05:02 CET | Link

Hi people, thanks for the replies.

Gavin you were right, I forgot to turn User in an @Entity, duh for me :) but there is a problem with glassfish and weld

see this:

My Link and this

My Link

If I can get it to work, I will post here some steps to get a simple ear running with all the stack mentioned.

Thanks

ReplyQuote
17. Nov 2009, 05:18 CET | Link

Victor, from that link it looks like it is a fixed bug in GlassFish, correct?

ReplyQuote
17. Nov 2009, 05:29 CET | Link

As Ludovic Champen says in the thread: if the file beans.xml has whitespaces or something else, when it should be totally empty, some crazy crash occur in glassfish ( they said Weld throws an error while parsing it) and the ear goes to an inconsistent state.

workaround (copied);

1 - undeploy if needed the bad app 2 - delete the domains/domain1/generated/policy/YOURAPPNAME directory which contain wrong state. 3 - delete the beans.xml in the web app (or make sure it is REALLY empty, even a space in it would break) Was your beans.xml absolutely empty???Maybe not the first time you tried to deploy. 4 - create an empty beans.xml as well in the META-INF of the ejb module, this is necessary to see these named things for weld in the ejbmodule It should then work. (at least it does for us)

ReplyQuote
17. Nov 2009, 06:17 CET | Link

here is the ear example of weld 1.0 working on glassfish v3, it uses jsf, jpa and ejb3

EAR

and take care of the beans.xml, it must be REALLY empty ;-)

thank You all for your help!

ReplyQuote
17. Nov 2009, 06:20 CET | Link
junico

I can't believe that all these things are working without ONE single jar inside the ear.

Thanks again

ReplyQuote
17. Nov 2009, 15:46 CET | Link
Ian smith

Speaking of bugs in Glassfish, are you guys aware that Weld doesn't even appear as a library after doing after upgrading from build 68 of Glassfish? The OSGI jar is there but no XSD . . . .

Can't wait to try some of this stuff . . .

HTH,

Ian ;)

ReplyQuote
18. Nov 2009, 18:24 CET | Link
Ian Smith

Tried netbeans-dev-200911171401 nightly, which does not recognize jee 6 servers, so no joy here either :(

ReplyQuote
 
26. Nov 2009, 16:13 CET | Link
Ian Smith

Still no weld jars appearing as of glassfish-cdi 3.0.74 . . . . is this sabotage? ;)

ReplyQuote
 
26. Nov 2009, 18:35 CET | Link
Ian Smith wrote on Nov 26, 2009 10:13:
Still no weld jars appearing as of glassfish-cdi 3.0.74 . . . . is this sabotage? ;)

Ian, are you talking about in Net Beans? As Weld is present in my build of GF (which IIRC is 74) 

$> ls glassfishv3/glassfish/modules/weld*
glassfishv3/glassfish/modules/weld-integration.jar
glassfishv3/glassfish/modules/weld-osgi-bundle.jar

If you are talking about Net Beans, make sure you report an issue in their issue tracker!

ReplyQuote
 
26. Nov 2009, 19:09 CET | Link
Ian Smith

Yeah, the jars are there, but they are not visible in the JEE libraries section of Netbeans projects. Not so good for your PR . . .

I'll check the Netbeans/Glassfish side.

ReplyQuote
 
30. Nov 2009, 18:19 CET | Link

Thanks Ian, post me back the issue link if you get no help on that side, I can chat to the GlassFish guys I know who have responsibility for this.

ReplyQuote
 
01. Dec 2009, 17:22 CET | Link
Ian Smith

Hi Pete, thanks for replying. Was waiting for Netbeans 6.8 RC, which is now out, and the weld-osgi-jar is now visible under Libraries. I have only had a chance for a brief look to ensure that the right package names are there, and I believe they now are. Can't spend too much time on this at work (!) but I will try some examples at home, at last! However, the signs are good so hopefully this is now resolved. Regards, Ian.

ReplyQuote
Post Comment