I did find JPEGImageWriter in batik-codec.jar so I don't have to include it in
my own code. But JPEGTranscoder still needed to be fixed to use
JPEGImageWriter instead of . . .
ImageWriter writer =
ImageWriterRegistry.getInstance().getWriterFor("image/jpeg");
which returned null.
-----Original Message-----
From: Jeremias Maerki [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 06, 2008 8:49 AM
To: [email protected]
Subject: Re: org.apache.batik.transcoder.TranscoderException: null
Indeed, this work-around shouldn't be necessary. I assume it's just that
the batik-codec.jar is not in the classpath.
On 06.03.2008 15:36:08 Helder Magalhães wrote:
> > Success! I now have an image written to my OutputStream! I just
> > included JPEGTranscoder and JPEGImageWriter in my own code. Thank you
> > very much everybody!
>
> Great! :-)
>
> Nevertheless, IMHO it's still important to understand if the behavior
> you experienced was due to misuse of Batik API (could the experts
> enlighten here?) or if you just worked around an existing issue
> (erroneously missing classes) - if so, best would be to report and
> make sure it's fixed in a later release and that others benefit from
> this! ;-)
>
> Regards,
>
> Helder Magalhães
>
Jeremias Maerki
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
