Deployment problem - Weblogic 8.1 SP2

Question

I've created a simple, one-page project to test deployment to Weblogic 8.1 SP2.
I followed the instructions in http://developers.sun.com/prodtech/javatools/jscreator/learning/tutorials/2/weblogicdeploy.html except for the database related parts (my project does not access a database).
On startup, Weblogic fails to proload the FacesServlet for my app:
####<May 18, 2006 2:45:42 PM PDT> <Error> <HTTP> <hqp-vs-hypdev01> <ProtivitiServer> <main> <<WLS Kernel>> <> <BEA-101216> <Servlet: "Faces Servlet" failed to preload on startup in Web application: "HelloTest".
javax.servlet.ServletException
     at weblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubImpl.java:884)
     at weblogic.servlet.internal.ServletStubImpl.createInstances(ServletStubImpl.java:848)
     at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:787)
     at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:3252)
and when I try to access my Page1.jsp, Weblogic throws another (related?) exception:
<BEA-101017> <[ServletContext(id=1830320,name=HelloTest,context-path=/HelloTest)] Root cause of ServletException.
java.lang.NullPointerException
     at javax.faces.webapp.FacesServlet.init(FacesServlet.java:144)
     at weblogic.servlet.internal.ServletStubImpl$ServletInitAction.run(ServletStubImpl.java:993)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
     at weblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubImpl.java:869)
Any help with this? Do I need Weblogic 8.1 SP4?

Answer 1

hi,
0. Check WLS classpath in startWeblogic.{cmd.sh} for JSF jars
1. Check your web.xml with section conserning FacesServlet
it shoul look like:
<servlet>
<servlet-name>Faces Servlet</servlet-name>
<servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
<load-on-startup>1</load-on-startup>
</servlet>
2. Try to find any other servlet and look at its <load-on-startup> section.
Final Java Servlet Specification Ver. 2.4 page 127:
" The load-on-startup element indicates that this
servlet should be loaded (instantiated and have
its init() called) on the startup of the web
application. The optional contents of these
element must be an integer indicating the order in
which the servlet should be loaded. If the value
is a negative integer, or the element is not
present, the container is free to load the servlet
whenever it chooses. If the value is a positive
integer or 0, the container must load and
initialize the servlet as the application is
deployed. The container must guarantee that
servlets marked with lower integers are loaded
before servlets marked with higher integers. The
container may choose the order of loading of
servlets with the same load-on-start-up value "
Kind regards,
Alex
Message was edited by:
AKlimenko