There isn't much else I can tell you besides to check the notes on the sun website so
you understand what the problem is and can
figure out how you might go about fixing it.
You might find the attached class useful in identifying which jar files have potential
conflicts though I haven't made any effort to
find out which packages are sealed. (which wouldn't be that big a deal)
It operates on the current classpath so you might have to use the -cp option so it
checks the classpath of your application.
HTH
> -----Original Message-----
> From: Aristide Aragon [mailto:[EMAIL PROTECTED]]
> Sent: Friday, May 25, 2001 9:47 AM
> To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: FATAL: configuration error
>
>
> > sealing violation is new in jdk 1.3 and addresses a
> potential security
> > problem. The java web site has notes on this. > > You can
> mess with the
> > order of the jar files on your class path to work around
> the problem.
> >
> > I put together a small util to check package definition
> conflicts and
> > found that xerces.jar (and likely xalan.jar), crimson.jar
> and > saxon.jar
> > all, for convenience, include some each of the dom, sax and
> jaxp packages.
>
> I tried 'playing' with my classpath and it didn't work, I
> still ge that error.
> I came up with this classpath:
>
> /usr/local/jakarta/jaxp-1.1/jaxp.jar:/usr/local/jakarta/jaxp-1
.1/xalan.jar:/usr/local/jakarta/jsse1.0.2/lib/jsse.jar:/usr/local/jakarta/jsse1.0.2/lib/jnet.jar:/usr/local/jakart>
a/jsse1.0.2/lib/jcert.jar:/usr/local/jakarta/jakarta-servletap
> i/lib/servlet.jar:/usr/local/jakarta/jakarta-ant-1.3/build/lib
> /ant.jar:/usr/local/jakarta/jaxp-1.1/parser.jar
>
> and it still does't work. I tried placing xalan.jar before
> jaxp.jar, I also removed jaxp.jar and it still gve me the
> sealing violation. There was a crimson.jar in there, I
> removed it. I also tried removing xalan, but then I would get
> classes not found.
>
> Could you help me solve that?
>
> Thanks in advane
>
> Aristide
>
>
PackageConflicts.java
