2 comments
Java 
Last week I tried to deploy an JSF application, that used to run under Tomcat, to a JBoss 4.0.4 server. I didn't expect any problems, but like most of the times I was too optimistic. The first thing I ran into was the following exception:
java.lang.NullPointerException at javax.faces.webapp.FacesServlet.init(FacesServlet.java:144)
After some searching I found that JBoss comes with MyFaces, while my application contained the RI jars. This seemed to be the problem so I removed them from the lib directory. The app deployed without errors, but no action mehods were called after submitting a form. The forms just submitted without ever reaching backing beans. No exceptions, no warnings, just a dead page.
After some more inspection I found that when putting the MyFaces jars in the lib directory of the application, evertything worked without problem again. After all not that strange, but it would be so much easier with some decent error messages.
2 comments
Yeah, coming with .net experience to the java world it can be very irritating the number of problems like this I come across. If container vendors only support their own implementation, why not have an explicit lib check when firing up the application. It would take them 10 minutes to code and save 1,000 individual developers 10 minutes…..
Dave
i like to deploy a simple jsf application with jboss1.4.03.can any one help me?
raji