xmlgraphics-batik-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Thomas DeWeese <Thomas.DeWe...@Kodak.com>
Subject Re: xerces path problem
Date Mon, 17 Jan 2005 17:14:13 GMT
michael sorens wrote:

> (1) What is the "appropriate JRE directory" and where is this documented?

    Sorry, I don't know off the top of my head, I suspect you can
Google it as fast as I can, and you might learn a bit about how
the classpath works.

> (2) If what you say is true, then the directions (on the batik web site) 
> to install and run the rasterizer are misleading at best... 
> clarification would be helpful.

    Can you be more specific about what you think is misleading?
As far as I can see, The reason you are having problems is because you
are not using the xerces library that is packaged with the binary
distribution.  It is true that this (not entirely common) case is not
covered by the directions but I think it's unfair to call the
directions misleading.

> On Mon, 17 Jan 2005 09:35:09 -0500, Thomas DeWeese 
> <Thomas.DeWeese@Kodak.com> wrote:
> 
>> michael sorens wrote:
>>
>>> from this command:
>>>
>>>     java -jar batik-rasterizer.jar build.svg
>>>
>>> I'm running xerces 2.6.2, and both xmlParserAPIs.jar and xercesimpl.jar
>>> are in my class path, so why is the SAXParser not being found?
>>
>>
>>     I am under the impression that when using -jar your classpath is
>> not used (I know the -cp option is ignored).  You can place the
>> Jar files in the appropriate JRE directory to have them searched,
>> or you can use just -cp (referencing all the needed jars) and specify
>> the Main to use as normal.
>>
>>> As a side question, I thought all jars needed to be in the classpath,
>>> but I notice that I do not have to put all the batik library jars
>>> explicitly in the classpath; having them in a subordinate lib directory
>>> seems enough to find them. Any explanation (or documentation pointer) on
>>> how this works would be appreciated.
>>
>>
>>     This is how jar files are supposed to work.  There is a classpath
>> entry in the manifest that specifies what other jar files should be
>> included with this one (see xml-batik/sources/batik-rasterizer.mf).
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: batik-users-unsubscribe@xml.apache.org
>> For additional commands, e-mail: batik-users-help@xml.apache.org
>>
>>
>>
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: batik-users-unsubscribe@xml.apache.org
> For additional commands, e-mail: batik-users-help@xml.apache.org
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: batik-users-unsubscribe@xml.apache.org
For additional commands, e-mail: batik-users-help@xml.apache.org


Mime
View raw message