"max.andersen(a)jboss.com" wrote : no jsf impl is needed for Seam projects - it
uses the built in one from JBoss 4.2.
|
| btw. one caveat...any chance you have a capital letter at the first position of the
name ? e.g. MyProject ?
|
| Then try with e.g. myProject instead - yes i know it sounds crazy but that is a known
caveat in the latest releases ;(
Yes, the project name was SeamProject, like the one used in the documentation example.
I created a new project called "myproject" and it also didn't work.
It seems strange to me that JBoss would automatically supply the class
org.apache.myfaces.webapp.StartupServletContextListener, because I searched under
/opt/jboss-4.2 for *myfaces* and found nothing.
I tried providing MyFaces as the JSF implementation and got another error:
16:01:27,799 WARN [JBossJSFConfigureListener] MyFaces JSF implementation found! This
version of JBoss AS ships with the
java.net implementation of JSF. There are known issues
when mixing JSF implementations. This warning does not apply to MyFaces component
libraries such as Tomahawk. However, myfaces-impl.jar and myfaces-api.jar should not be
used without disabling the built-in JSF implementation. See the JBoss wiki for more
details.
| 16:01:28,531 ERROR [STDERR] javax.faces.FacesException:
org.ajax4jsf.framework.DebugLifecycleFactory
No way out...
By the way, one more suggestion: when using JBoss 4.2, JBoss Tools waits for the server to
start before opening the browser. When using JBoss 5.0, it doesn't.
Thanks.
VÃtor
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4159022#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...