Also this tutorial uses JSF RI from Sun, can you show me how to use it with MyFaces?

Thanks in advance

Please try this procedure instead: http://www.seamframework.org/Documentation/WeldQuickstartForMavenUsers

I’ll update that post to reflect the fact that nearly the entire tutorial has been reduced to a few command lines. The JBoss team is actively working with the community to make adopting Java EE features as easy as possible with projects like the archetype project.

Thanks,
Steven

javax.servlet
jstl
1.2
runtime

Should be

javax.faces
jsf-impl
runtime
2.0.0-RC

I tried your example and it works fine, thanks for the quick start. However if I try to update the JSF 2 dependencies to latest version the injection stops working!

Here is what I changed the JSF dependancies to in the pom.xml

From

javax.faces
jsf-impl
runtime
2.0.0-RC

javax.servlet
jstl
1.2
runtime

To

javax.faces
jsf-api
2.0.2-FCS

javax.faces
jsf-impl
runtime
2.0.2-FCS

Creating the war file and deploying to Tomcat works fine though.

Regards,

Touch in *NIX simply creates an empty file. I added that command to reduce the chances of someone forgetting to create a file or putting it in the wrong directory. For example one user had issues because he forgot to create the empty beans.xml file. The touch command is designed to avoid that.

Simply create the folders and files in the Overview section in Windows explorer or eclipse and move on to writing the actual code.

If you want to work on your Maven skills and skip the manual steps, there’s an even easier way. I’ve been working with the kind folks at JBoss to create maven archetype that creates all the files you need to get started.

The instructions are here: http://www.seamframework.org/Documentation/WeldQuickstartForMavenUsers Once these archetypes get published to the maven repo (hopefully soon), this entire tutorial becomes 2 maven commands. For now, you have to check out the code and build it.

Finally, I included my original source in the “Download the Code” section if you want to just have a working project to play with.

Thanks for commenting and checking out Weld.

In the last month, I have been working with the Weld team to try to make CDI and Weld as accessible and easy to use as possible to new users. Hopefully, in a month or 2, users in your situation will find it CDI and JSF 2.0 incredibly easy to get started with.

Thanks,
Steven

I have a problem with setting up this example under Windows. I am not familiar with Maven but I get stuck with the command:
touch pom.xml src/main/webapp/WEB-INF/web.xml src/main/webapp/WEB-INF/beans.xml src/main/java/org/bogus/HelloWorld.java src/main/webapp/index.xhtml src/test/resources/jetty-env.xml

The touch command and I figured out that it is part of a mvn plugin. I have also tried calling “mvn touch …” but I only get this a “BUILD FAILURE” with:
Invalid task ‘touch’: you must specify a valid lifecycle phase, or a goal in the format plugin:goal or pluginGroupId:pluginArtifactId:pluginVersion:goal

Can anybody Help?

Thanks in advance,
Tai
P.S.: using mkdir under windows you have to replace “/” with “\”

mvn clean package jetty:run-war

just putting the jetty-evn.xml file into the webapp/WEB-INF folder.

However, your statement is only correct in existing applications spring-enabled applications where your package has been previously registered. Also, Spring doesn’t really handle scoping. Spring IOC handles singleton and non-singleton (the equivalent of @Request). You have to use WebFlow to get Conversation or Session scoping.

As far as JBoss propaganda or being misinformed. I am actually a Spring 2.5 user migrating towards CDI. Weld is just an implementation of JSR 299, part of JEE 6. I’m not sure of the reason why, but Spring didn’t feel like contributing to the JSR, so it is led by Gavin King of JBoss. You could easily use the Apache implementation of CDI (OpenWebBeans) if you had issues with JBoss.

The difference between CDI and Spring 2.5 is that by adding an empty beans.xml file, you’re ready to start using CDI. To write the same tutorial in Spring, I would have to:

1. Create a Spring config.
2. Register EACH package in the config.
3. Modify your web.xml to initialize the Spring listener.
4. Modify your face-config.

In the end, you still couldn’t declare a bean as @ConversationScoped through Spring.

CDI is not a revolutionary improvement over Spring IOC so much as it’s an evolutionary improvement. I personally still like Spring and would not be so enamored with CDI if Spring had decent, first-class integration with JSF. SpringSource added JSF integration as a afterthought with WebFlow and it is very cumbersome to use for anything other than long multi-page flows.

If you use JSF, CDI is a huge improvement over Spring. If you don’t, then it’ll do a few things slightly better, but probably isn’t worth gutting your entire infrastructure out for if you’re already invested in a non-JSF-webframework.

The specifications and implementation of the various components of JEE6 are just now getting finalized. They have excellent APIs and potential. Once greater integration and testing documentation is out in the wild, I think you’ll find JEE6 to be a compelling alternative to whatever you’re using now.

Thanks again for reading and responding,
Steven