First of all section 4.4.1 tells us to set jboss-dist property in build.xml. That propety does not exist. You need to set the environmment variables JBOSS_HOME otherwise the build fails.Now I am STILL getting a failusre message that I'm not sure what to do with:C:\gettingstarted\jsfejb3>antBuildfile: build.xml

Some help would be appreciated. It's very hard to figure out exactly what I need to do because the build.xml is really convoluted and its unclear which line the error message line number is referring to.

and the other line I referenced before the seam comments went like this>property name="jsflib" location="${jboss.home}/server/default/deploy/jboss-web.deploy/jsf-libs" / <>property name="jsflib" location="${jboss.home}/server/default/deploy/jbossweb.sar/jsf-libs" / <

When trying to deploy the ear file I get this exception:vfszip:/usr/jboss/jboss-5.0.0.CR2/server/default/deploy/jsfejb3.ear -> org.jboss .xb.binding.JBossXBRuntimeException: Failed to resolve schema nsURI= location=pe rsistence

Thanks for that jaikiran.I was wrong by the way, the jsfejb3.ear project is using seam or at least the jsf-facelets.jar which the build file was indicating as coming fromfileset dir="${seamlib}/lib" includes="jsf-facelets.jar"Perhaps the getting started documentation should be revised to indicate that seam should be installed and configured before trying the examples.

Unfortunately in my case "seam" didn't work with jboss-5.0.0.CR2While deploying the booking seam example I had issues with JBOSS not being able to extract one of the jars, yet I could browse into the jar it indicated with my file manager (on Linux). I tired setting up with a shallower context for JBOSS but it didn't help. I noticed in the server log there were several issues with ORB and other items while loading the stock jboss-5.0.0.CR2 extracted system without ever having deployed anything yet. In any case I'm going to try jboss-4.2.3.GA-jdk6.zip as at least seam says it works with JBoss AS 4.2.X

As rtaylor says, the example does require jsf-facelets.jar, so the getting started guide should advise downloading and unpacking seam, then setting the seamlib property of build.xml to wherever you have unpacked seam to.

And since it does require this jar, don't comment out the lines from the build.xml as suggested at the start of this thread.

These types of problems trying to run examples are really annoying..I've spent a lot of time and made some headway with jsfeJB3 (fixed the build and deploy problems mentioned earlier) but now when you try to create a todo or list them it fails with

Since I recently just clawed my way through getting the jsfejb3 example running on JBoss AS 5.1.0.GA. I thought I'd post what got it all working for me if it's a help to others. The problems I had were the following:

This fix was, as mentioned in another post, to add in some XML Schema attributes to persistence.xml

3. After compiling and deploying the ejb-jsf todo app, jboss logged the following error when I connectedwith the webapp in my browser:

Missing Built-in Tag Libraries! Make sure they are included within the META-INF directory of Facelets' Jar

I fixed this by downloading jboss-seam-2.2.0.GA, and replacing my jsf-facelets.jar with the one from seam. I'm unsure of the version of this newer jsf-facelets.jar from seam, but the one that I had problems with was 1.1.15B1.

4. Finally, I got this error when attempting to run the todo web app:

Unable to create managed bean todoBean. The following problems were found: - Bean or property class TodoBean for managed bean todoBean cannot be found

I modified build.xml so that TodoBean.class is placed in 'WEB-INF/classes' in app.war instead of at the top level of the war file. I assume there was some change to classloading or the configuration in JBoss 5 that causes this. I'm sure there are other ways to resolve this, but this worked. It may be that this is something related to seam, who knows.

For me it's important to be able to get through examples that *don't* use seam as well as those that do. It's hard enough to understand umpteen different Java EE technologies before throwing seam into the mix.