hi,
www.acme.com has some solutions for gif encoding..
I guess you can just use awt for jpeg, and some other formats as well.
you might also want to take alook at www.imagemagick.org and especially
the Jmagick partition, I dont think Jmagick is yet available for win32
comps, only unix.
hope
That should be easy. Call a class that does all that and then load the
image. Do I misunderstand you?
At 10:54 PM 3/12/02 +0800, you wrote:
Hi everybody,
I am using tomcat4 on win 2000.
I have searched all the archives and almost all websites related with java,
to no avail.
My problem is
yilmaz wrote:
Hi everybody,
I am using tomcat4 on win 2000.
I have searched all the archives and almost all websites related with java,
to no avail.
My problem is manupulating images via servlets on Tomcat.
In fact , there are tons of examples on the internet and on the archives
Hi,
well, the question should be split into two subquestions:
1) how to serve requests for images
2) how to manipulate images before sending them back to clients
1.
The first is simple: create a servlet which receives an identifier (the name
of the image to generate). It can then get the bytes
Is the problem that the 'old' vs. newly generated image displays (with the
same .gif/.jpg name)? If that's the case then it's likely a problem with
browser image caching. The only way I found to get around that was to
generate unique image file names each time the new images were generated,
- Original Message -
From: yilmaz [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Sent: Tuesday, March 12, 2002 9:54 AM
Subject: image manipulating via servlets on tomcat4
Hi everybody,
I am using tomcat4 on win 2000.
I have searched all the archives and almost all
Thanks to all who answered my question.
My problem is , when i load an image via Toolkit class
like : Image img=Toolkit.getDefaultToolkit().getImage(imageURL);
Then create a BufferedImage object to write on it.
BufferedImage bi=new BufferedImage(...
Graphics g=bi.createGraphics();
Then I call
manipulating via servlets on tomcat4
Is the problem that the 'old' vs. newly generated image displays (with the
same .gif/.jpg name)? If that's the case then it's likely a problem with
browser image caching. The only way I found to get around that was to
generate unique image file names each
