tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Irving, Dave" <>
Subject RE: Interactions with org.apache.coyote.Request/Response
Date Tue, 18 Oct 2005 11:29:43 GMT
Remy Maucherat wrote:

> I think the conclusion is that your requirements are outside the use
cases for which 
> the servlet API was designed for, so besides reusing portions of the
code, most of 
> your request processing cannot quite run inside the main servlet

Yes - and after doing a bit more reading around the net, it seems that
this is indeed the general consensus.
It would appear that some great minds have spent some serious time
trying to see how this model could work - and have decided that it just
isn't going to. And Im not going to argue with them :o)

Fortunately, it turns out that ditching tomcat for this particular
use-case isn't such a bad thing. We just use the messaging model of axis
(not RPC), so do much of the parsing ourselves.
So, time to throw out the servlet API and Axis (proper) and have
asyncronous request / response processing, re-using axis to convert the
input stream to SOAP objects for us.

I think that is going to be far easier to pull that off than what I was
proposing before - which Im now beginning to appreciate was a bit crazy.

Will still be using tomcat in other areas though - its superb.


This e-mail and any attachment is for authorised use by the intended recipient(s) only. It
may contain proprietary material, confidential information and/or be subject to legal privilege.
It should not be copied, disclosed to, retained or used by, any other party. If you are not
an intended recipient then please promptly delete this e-mail and any attachment and all copies
and inform the sender. Thank you.

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

View raw message