Thank you. It works now. I tried it before but I used SYSTEM instead of PUBLIC in the doctype.
Btw, I've done struts webapps also and I didn't have to use a local dtd. So I still think it's a myfaces problem. Maybe when myfaces parses the web.xml, it is calling an API that forces validation against the dtd? Anyway, I have the solution now. Thanks to everybody who chimed in. -----Original Message----- From: Stefan Frank [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 23, 2005 2:02 PM To: 'MyFaces Discussion' Subject: RE: MyFaces with Weblogic You can just change the reference to the dtd to a local reference - weblogic will not call out to the web then. I think tomcat has a mechanism to lookup the dtd inside WEB-INF, whereas weblogic tries to obey the reference and look it up. As far as I remember, there is a switch somewhere in the weblogic.xml to change this beahvior. This is not a myfaces-problem: You will have this problem with all jakarta-webapps (eg. Struts), as they all rely on this fallback to dtds in the WEB-INF. Cheers stf > -----Original Message----- > From: Steven Holmes [mailto:[EMAIL PROTECTED] > Sent: Mittwoch, 23. Februar 2005 19:00 > To: myfaces-user@incubator.apache.org > Subject: Re: MyFaces with Weblogic > > I went to great effort myself. Spent about three work days > but could never get it going. But in my case I was using > struts-faces. > > >>> [EMAIL PROTECTED] 2/23/2005 6:26:52 AM >>> > 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. ***********************************************************************
