Hi Thomas,
I had never seen "jndi:" as protocol descriptor before, but in the end I think it was
still an XML parser compatibility
issue. I was able to solve it by changing my implementation to work with crimson and
not using xerces anymore. It's a
good thing I was JAXP compatible so I just had to remove some lines that used the
"node.normalize()" method. Anyway,
until I completely removed xerces from the classpath, not even putting crimson.jar
before it in the classpath worked, it
kept on giving me strange errors like "class not found", "no such method" from classes
that were in the classpath and
methods that existed, and some "null pointer" also. This xml parser issue is a big
headache.
I think I read it was planned to make batik xml-parser-independent, is that true? My
opinion is that it will save batik
people lots of trouble, as they would get less messages regarding strange errors.
On the other hand, Orion is the servlet container (application server if you wish)
that we use, as it is one of the
fastest and it is free for educational institutions. If you don't mind the terrible
support, and the lack of
documentation, it is pretty good. It is actually the core of the new Oracle9IAS. As
many servlet containers nowadays, it
includes its own XML parser to read the configuration files, hence the conflict with
crimson. I actually had to upgrade
to a latest version, which also uses crimson, to get it to work. I think you'll get
lots of messages from people trying
to use batik inside servlets and getting weird problems with XML parsers, as it is a
common source of headaches. I wish
JDK2.3 solves it.
Thank you very much for your help,
D
Thomas E Deweese wrote:
> >>>>> "DL" == Daniel =?iso-8859-1?Q?L=F3pez?= <Daniel> writes:
>
> DL> Nobody in the users list could help me, as it might require an
> DL> inside knowledge of batik, so here I go: I'm trying to process an
> DL> SVG file inside a servlet to show a JPEG image and after dealing
> DL> with a couple of XML parser incompatibility issues, I've stumbled
> DL> into this error. When I process the SVG file, a sample file
> DL> provided with the batik-1.1rc, I get the error:
>
> DL> java.io.IOException: File
> DL>
>"jndi://D_/Apps/Test/Test/Test/WEB-INF/lib/batik-svg-dom.jar/org/apache/batik/dom/svg/resources/svg-20001102.dtd"
> DL> not found. The file batik-svg-dom.jar is in the classpath and it
> DL> is exactly in D:/Apps/Test/Test/Test/WEB-INF/lib/, I also checked
> DL> to see that the dtd file is in there and indeed, it is.
>
> DL> Any clues?
>
> Well, basically no...
>
> It appears that everything is fine on the Batik side of things.
> I've never noticed a 'jndi' protocol descriptor on a URL though. As I
> recall the Sun JDK uses 'jar' for a URL like the one above...
>
> DL> Platform is WinNT, Orion1.4.5, JDK1.3
>
> What is Orion? Is it possible that it's doing soming funny, with
> the URL stuff? Are you putting the jar files on the path in a 'weird'
> way?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
