I didn't have to put the dtd in the war for the tomcat installation. Also when I tried this, I ran into other problems.. I eventually gave up because it became a bigger problem than the original, eventually I just used the reference implementation of JSF. Btw, I've never had to put the dtd in the war in any of the previous war files I've deployed.
However if other people are using MyFaces with weblogic without putting their dtds in the war, then there must be another solution. Is there perhaps a configuration to tell MyFaces not to validate the xml? How are you guys deploying your webapps? -----Original Message----- From: Avishay Balderman [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 23, 2005 11:20 AM To: MyFaces Discussion Subject: Re: MyFaces with Weblogic looks like it tries to fetch the web.xml dtd from Sun. Can you put the dtd inside the war? On Wed, 23 Feb 2005 11:09:55 -0500, Virtudazo, Dennis (Exchange) <[EMAIL PROTECTED]> wrote: > I'm at service pack 3. > > My problem is that apparently when the myfaces servletcontext listener > startsup it tries to validate the web.xml against the dtd and cannot > access the sun website. Below is the error: > > Feb 15, 2005 11:26:01 AM > net.sourceforge.myfaces.webapp.StartupServletContextLis > tener initFaces > SEVERE: Error initializing ServletContext > javax.faces.FacesException: java.net.UnknownHostException: java.sun.com > at > net.sourceforge.myfaces.webapp.webxml.WebXmlParser.parse(WebXmlParser > .java:105) > at > net.sourceforge.myfaces.webapp.webxml.WebXml.init(WebXml.java:140) > at > net.sourceforge.myfaces.webapp.StartupServletContextListener.initFace > s(StartupServletContextListener.java:105) > at > net.sourceforge.myfaces.webapp.StartupServletContextListener.contextI > nitialized(StartupServletContextListener.java:85) > > I'm running behind a firewall and I have access to the internet but I > do have to go through an http proxy that requires authentication. > However, when I drop the examples war file in Tomcat, it just runs > without a problem. My tomcat installation is in the same machine. I > didn't configure tomcat with the userid & password for the firewall > (nor do I know how) so I can only assume that myfaces is not > validating the xml when run in tomcat. > > Did you have this problem? > > Matthias, Yes I did try "org.apache.myfaces.webapp.MyFacesServlet" > instead of "jjavax.faces.webapp.FacesServlet". I get a different > error when I use "javax.faces.webapp.FacesServlet". > > -----Original Message----- > From: John Langley [mailto:[EMAIL PROTECTED] > Sent: Wednesday, February 23, 2005 9:36 AM > To: MyFaces Discussion > Cc: Virtudazo, Dennis (Exchange) > Subject: RE: MyFaces with Weblogic > > Yep, everyday. I run 8.1 sp4 with myfaces 1.0.8 and previously with > 1.0.7. What sp level are you at with WebLogic and what is your error? > > Langley > > -----Original Message----- > From: Virtudazo, Dennis (Exchange) [mailto:[EMAIL PROTECTED] > Sent: Wednesday, February 23, 2005 9:27 AM > To: MyFaces Discussion > Subject: MyFaces with Weblogic > > Has anybody on this list successfully run MyFaces on Weblogic 8.1? > > ********************************************************************** > * > Bear Stearns is not responsible for any recommendation, solicitation, > offer or agreement or any information about any transaction, customer > account or account activity contained in this communication. > *********************************************************************** > > ********************************************************************** > * > Bear Stearns is not responsible for any recommendation, solicitation, > offer or agreement or any information about any transaction, customer > account or account activity contained in this communication. > *********************************************************************** > > -- Avishay Balderman *********************************************************************** Bear Stearns is not responsible for any recommendation, solicitation, offer or agreement or any information about any transaction, customer account or account activity contained in this communication. ***********************************************************************
