Also just as a note, I found that I need to clean out both the "work" and the "tmp" directories in the server instance home and then restart to get a clean JBoss/Tomcat. I needed it so often I wrote an ant target to do it.
Erik
Rick Reumann wrote:
I'm still stumped. I stopped server, deleted all temp files, re-deployed, and get the same error with jboss3.2.5 (listed below)
What I find odd is if I remove all the rules that have depends="" in them and redploy with the modified validation-rules then everything is fine. Very frustrating.
11:02:13,530 INFO [ValidatorPlugIn] Loading validation rules file from '/WEB-INF/validator-rules.xml'
11:02:13,546 INFO [ValidatorPlugIn] Loading validation rules file from '/WEB-INF/validation.xml'
11:02:13,686 ERROR [Digester] Begin event threw exception
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
<snip>
Caused by: java.lang.NullPointerException
at java.util.StringTokenizer.<init>(StringTokenizer.java:146)
at java.util.StringTokenizer.<init>(StringTokenizer.java:162)
at org.apache.commons.validator.ValidatorAction.setDepends(ValidatorAction.java:255)
... 147 more
11:02:13,921 ERROR [ValidatorPlugIn] Skipping all validation
java.lang.NullPointerException
at org.apache.commons.digester.Digester.createSAXException(Digester.java:2540)
at org.apache.commons.digester.Digester.createSAXException(Digester.java:2566)
Rick Reumann wrote the following on 10/5/2004 8:56 AM:
Erik Weber wrote the following on 10/5/2004 1:36 AM:
Zoinks, JBoss 3.2.4 (on unix) and 3.2.5 (on win 2000) have been able to parse the default validator-rules.xml (version 1.1, which has several 'depends=""') for me without any problems. However, I did run into some problems with parsing errors on hot redeploys, but never could discover a pattern to them. I don't recall seeing your particular error. One thing I discovered that helped in my case was to invalidate any existing sessions before a hot redeploy. Sorry to be of little help.
Are you sure that is a parsing error?
No, I'm not sure at all:) Let me look into some more things today. I wonder if maybe it's using a cached version of an invalid rules file that I had replaced but I never cleared out the temp directory. I'll try that when I get to work. Thanks for the help.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]