tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Januski, Ken" <>
Subject RE: RequestDispatcher.forward to cgi?
Date Fri, 05 Dec 2003 17:03:26 GMT

Now that I look at them closely I see that most of them are due to a looping
problem in my program. So it just logs over and over that it's forwarding
the request. I'll investigate to see if the loop is due to an error in my
progamming (certainly possible since I've had to tinker with a very large
controller servlet in order to incorporate this cgi page) or due to a
failure in forwarding.

What I was hoping in asking the question though was to find out whether
anyone had done this successfully or not. I'm happy to troubleshoot the
problem if I think there's a chance of success. But I hate to spend the time
on it if I'm just trying to do the impossible or the dumb.


-----Original Message-----
From: Tim Funk []
Sent: Thursday, December 04, 2003 9:21 PM
To: Tomcat Users List
Subject: Re: RequestDispatcher.forward to cgi?

Just curious ... what are the errors?


Januski, Ken wrote:

> I've finally managed to get cgi working in Tomcat. Now I need to forward
> from a servlet to a cgi page. But both RequestDispatcher.forward and
> RequestDispatcher.include are failing. I'm not surprised that include does
> but I thought it might be possible with forward.
> Since this is part of a large application that keeps track of the session
> I'd like to be able to include the cgi page in the application. But I'm
> beginning to think that's not possible. So I wonder if anyone knows
> it's possible to forward to a cgi page within the same Tomcat webapp. If
> I'll save myself a lot of trouble and just make it a separate webapp with
> just a cgi component.
> Thanks for any advice.
> Ken
> P.S. I'm using cgi with perl because I can't find a class to add IPTC
> information to a Jpg and I don't have time to write it myself. Such a
> does already exist in Perl.

To unsubscribe, e-mail:
For additional commands, e-mail:

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message