In article <[EMAIL PROTECTED]>,
 ddylla <[EMAIL PROTECTED]> wrote:

> I am using WebLogic8.1 sp3 and am trying to deploy an application that uses 
> struts-blank.war from the Struts 1.2.2 binary distribution. The .EAR that I 
> built errors when deploying and fails to run, complaining that it cannot 
> connect to jakarta.apache.org to validate some XML files. I downloaded the 
> DTDs 
> locally and modified the references to them in order to get things to work. 
> 
> I am behind a firewall. Does anyone know if there is a way to configure 
> weblogic or Struts to use a proxy?
> 
> Since I need to deploy my application to customers that may also be behind a 
> firewall or don't have an internet connection, I feel that I need to include 
> local copies of the DTDs. Unfortunately, I cannot get my deployment to find 
> them unless I specify the absolute paths to the files and this is not a 
> portable solution. Any ideas?



I'm having the same problem. This worked in Struts 1.1, so there must 
have been some change. Looking at the source for commons-validator, I 
see that it's trying to use local copies of the DTDs, rather than go out 
to the network. In org.apache.commons.validator.ValidatorResources, look 
at the variable "registrations." Struts also uses similar code when 
loading the struts-config file, and it seems to work there.

I noticed that the file it looks for, 
/org/apache/commons/validator/resources/validator_1_1_3.dtd, isn't in 
the commons-validator.jar included with Struts. This is noted in a bug 
report: http://issues.apache.org/bugzilla/show_bug.cgi?id=31094. So this 
is probably why it's failing.

Can you try patching the jar file with that DTD, and see if it works? 
You can get the DTD at 
http://jakarta.apache.org/commons/dtds/validator_1_1_3.dtd, and it goes 
into /org/apache/commons/validator/resources/validator_1_1_3.dtd. I 
won't be able to patch mine for a little while, but I'd like to know if 
this is the solution.

Thanks,
Jacob


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to