Andrew John Savory wrote:

> On Sun, 21 Apr 2002, Conal Tuohy wrote:
>
> >     <image xmlns:xlink="http://www.w3.org/1999/xlink";
> xlink:href="Ba01S000.jpg"
>
> Try using an absolute URL for the href. I've had problems
> with relative
> hrefs.

Cheers, Andrew. I've tried relative and absolute URLs but I always get the
same result (even using the "data" protocol). Actually I'm convinced that
the problem is nothing to do with resolving the URL - the problem is that
the xml attribute "xlink:href" has not been correctly parsed, or at least
has not been passed to Batik correctly - when Batik comes to access this
attribute from its object model it isn't there.

When you say you've had problems with relative hrefs, do you mean you have
used images in SVG? Or were your href problems in some other context?

If you do have an example (anyone!) of an SVG containing an <image>, that
works, PLEASE let me see!

I have downloaded the batik and cocoon source and had a look at the code. So
far I've found nothing that looks wrong ... the URIs of the namespaces (in
particular the xlink namespace) I've used in my SVG files match the URIs
that Batik is expecting. If I remove the xmlns:xlink atttribute, then I get
an error that the "xlink" prefix is "unbound", as you'd expect. But with the
"xlink" prefix declared, I get this error message:

org.apache.batik.transcoder.TranscoderException: null
Enclosed Exception:
http://xml.apache.org:-1
The attribute 'xlink:href' of the element <image> is required

I think I will have better luck writing a separate servlet to create the
thumbnails, rather than using Cocoon. Perhaps I can come back to this
problem later and try to debug it, but I can't afford to spend any more time
on it at the moment.

Con


---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>

To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>

Reply via email to