You should also check your firewall, especially in production: It may happen that the firewall blocks outgoing requests.
I normally change the dtd-references to local references: I usually package the dtd's for the specs I use with the web-app. I vaguely remember that there is a switch somewhere to turn off the validation, but this is actually a quite useful feature that produces some meaningful errors when your web.xml is screwed up. > -----Original Message----- > From: Virtudazo, Dennis (Exchange) [mailto:[EMAIL PROTECTED] > Sent: Dienstag, 15. Februar 2005 18:08 > To: MyFaces Discussion > Subject: RE: Help using myface with Weblogic > > My internet connection is always up (I'm connected via lan). > However I'm confused why in weblogic myfaces appears to try > to validate the dtd whereas in Tomcat it appears that it > doesn't. I'm deploying basically the same webapp. I didn't > set anything in either weblogic or tomcat for the proxy > userid and password to get through the firewall. > > I'm also trying to use local dtd but running into other problems. > > -----Original Message----- > From: Srikanth Madarapu [mailto:[EMAIL PROTECTED] > Sent: Tuesday, February 15, 2005 11:59 AM > To: MyFaces Discussion > Subject: RE: Help using myface with Weblogic > > > Is your internet connection up? I had similar issue once when > the apache > server went down. > > -----Original Message----- > From: Virtudazo, Dennis (Exchange) [mailto:[EMAIL PROTECTED] > Sent: Tuesday, February 15, 2005 11:27 AM > To: MyFaces Discussion > Subject: Help using myface with Weblogic > > > I'm having a problem running myfaces with weblogic 8.1. I have tried > with Tomcat with no problems. > However in weblogic, first I'm getting the following in the log: > > SEVERE: Unable to parse web.xml > java.net.UnknownHostException: java.sun.com > > > 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) > > > And then when I access my jsp (jsf) I get the following: > > Feb 15, 2005 11:28:11 AM net.sourceforge.myfaces.webapp.webxml.WebXml > getWebXml > SEVERE: net.sourceforge.myfaces.webapp.webxml.WebXml.init > must be called > before! > > <Feb 15, 2005 11:28:11 AM EST> <Error> <HTTP> <BEA-101046> > <[ServletContext(id=3 1404162,name=adminweb,context-path=/racs2)] > net.sourceforge.myfaces.webapp.webxm > l.WebXml.init must be called before! > java.lang.IllegalStateException: > net.sourceforge.myfaces.webapp.webxml.WebXml.in > it must be called before! > at > net.sourceforge.myfaces.webapp.webxml.WebXml.getWebXml(WebXml.java:12 > 8) > at > net.sourceforge.myfaces.application.jsp.JspViewHandlerImpl.getServlet > Mapping(JspViewHandlerImpl.java:343) > at > net.sourceforge.myfaces.application.jsp.JspViewHandlerImpl.renderView > (JspViewHandlerImpl.java:209) > > > Has anyone used myfaces with weblogic 8.1? I don't know why it would > complain about unknown host exception for java.sun.com when > I'm running > tomcat from the same machine and I don't get the error with > tomcat. I'm > behind a firewall and have to go through an http proxy to get to the > internet. > > I've tried using both javax.servlet.faces.FacesServlet and > net.sourceforge.myfaces.webapp.MyFacesServlet with the same result. > > > > ************************************************************** > ********* > 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. > ************************************************************** > ********* > >
