Well... has anything been written to the response before the forward?
If so, that'll do it.
If what you really want is to include the output of various servlets and
jsps in one response, you really need an aggrigator servlet that pulls
together the output of various servlets. In jsp land, the c:import tag
will do exactly this sort of thing.
--David
Deepa Paranjpe wrote:
Hi all,
This is not a question specific to tomcat but more about servlets.
I am using a dispatcher forward to invoke another servlet.
Why do I get an exception --> java.lang.IllegalStateException: Cannot forward after response has been committed
For some reason I am unable to find good documentation to do complicated servlets invocations. Does any one know?
Ole Ersoy <[EMAIL PROTECTED]> wrote:Incidentally - since we are talking about pooling - should the executor configuration be a tip? It allows the connectors to share a single thread pool, rather than each connector having its own. This seems like a memory and performance slurpee to me.
Cheers,
- Ole
myrealbruno wrote:
IMHO the only good reason to move a library out from an application and
place it into /common/lib (or /lib) is to get advantage of connection
pooling.
http://tomcat.apache.org/tomcat-5.5-doc/jndi-resources-howto.html
Then, yes, if you have different database versions you might find yourself
in the usual library versions nightmare.. :-)
-----Original Message-----
From: Diego Yasuhiko Kurisaki [mailto:[EMAIL PROTECTED]
Sent: 22 August 2007 00:35
To: Tomcat Users List
Subject: Re: 20 Tips for Using Tomcat in Production
I agree, i'm not willing to pay the management overhead of putting my shared
libraries to the tomcat common lib, unless my gains are very big in terms of
memory consumption.
I don't really think you should change for another one though, but you can
make regards about the cons of that approach.
Anyway, great work 5 stars.
On 8/21/07, Ben Souther wrote:
From:
Christopher Schultz
I also agree with David and, uh, David, that #6 is a little dubious.
Yes, moving shared libraries into the common/lib directory will save
you some memory, but it creates a management headache when it comes
to version numbers, WAR packaging, etc. Ideally, the WAR contains
everything the webapp needs. If you rely on the servlet container to
provide essential libraries, you are changing your deployment
strategy significantly.
+1
Starting with Servlet Spec 2.3 (I think) there has been an emphasis on
putting everything a web app needs to run into its war file. To put
include something that runs contrary to this 'best practice' in an
article of tips at this point in time doesn't sound like a good idea.
I would seriously consider replacing that one with something else.
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------
Boardwalk for $500? In 2007? Ha!
Play Monopoly Here and Now (it's updated for today's economy) at Yahoo! Games.
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
