Hi Minal
Oh, there's a big difference between saying you got
a 'security exceptoin' when the message is actually 'sealing violatoin'. (I wish
there was a SealingViolationException to make these kinds of things more obvious
but there you go).
"sealing violation" is one of those yucky CLASSPATH
problems. This is generally caused by a bad classpath where bits of a JAR X is
loaded from one place then other bits of another JAR Y are loaded which expect
the original bits to be loaded from its jar, but they've already been loaded
from X and so causing a conflict.
This usually indicates duplications on the
classpath. Without knowing your classpath its hard to guess the real cause but
I'd say its probably one of these things
* set your CLASSPATH to only dom4j-full.jar and
you'll be fnie
* set your CLASSPATH to only dom4j.jar and only one
XML parser (crimson.jar or xerces.jar) and you'll be fine
The problem may well be that you have one or more
jars with the SAX distribution on the classspath, e.g. sax.jar and
dom4j-full.jar or dom4j-full.jar and xerces.jar.
So I'd clean your CLASSPATH up a bit and you should
be fine.
A quick word of warning, be very, very careful
about *ever* putting jars into the $JAVA_HOME/jre/lib/ext directory - its easy
to forget what you put there and for conflicts to occur.
I hope that helps
James
|
- [dom4j-user] (no subject) Tobias Rademacher
- [dom4j-user] (no subject) Tobias Rademacher
- [dom4j-user] (no subject) Minal Ashar
- Re: [dom4j-user] (no subject) James Strachan
- [dom4j-user] (no subject) James Strachan
- [dom4j-user] (no subject) toby-wan-kenobi
- [dom4j-user] (no subject) toby-wan-kenobi
- [dom4j-user] (no subject) Christian Bjørnbak
- Re: [dom4j-user] (no subject) Dane Foster
- [dom4j-user] (no subject) Nicholas Sanderson
- [dom4j-user] (no subject) JavaXML Developer
- [dom4j-user] (no subject) Wannheden, Knut
- [dom4j-user] (no subject) Leticia ELFASSI
- [dom4j-user] (no subject) Leticia ELFASSI
- SV: [dom4j-user] (no subject) Christian Holmqvist, IT, Posten