tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From chas <>
Subject Re: inter-webapp communications
Date Thu, 01 Jan 1970 00:00:00 GMT
Thanks for the speedy response, Joseph.

At 18:47 05/04/2002 -0800, Joseph Molnar wrote:
>Generally people are using SOAP or XMLRPC or some other mechanism that would
>constitute being a 'web service'.

Was hoping to avoid SOAP or XMLRPC - they're a bit
beyond the end-developers who'll use my webapp and
it's just that added barrier to entry. 

Really, would love for them to be able to integrate
my webapp into their own website with no further 
experience other than the ability to write a servlet
(which I know they can).

Have just realized that RequestDispatcher won't cut
it either - because it relies on the called servlet
being within the same context (/...) which isn't the
case with a separate webapp.

Taglibs are certainly looking like the cleanest 
mechanism now... but I dislike JSPs myself.

still searching.

thanks again,


>----- Original Message -----
>From: "chas" <>
>To: <>
>Sent: Saturday, April 06, 2002 10:24 AM
>Subject: inter-webapp communications - anything better than
>> Is there any standard mechanism for inter-webapp communication ?
>> Perhaps an example would explain this better:
>> On my production server, our website is in <tomcat_home>/webapps/mainsite
>> This contains content, forms, JSPs, servlets, the standard corporate
>> Now, on my laptop I've created a standalone webapp for an events calendar,
>> and another webapp that is a discussion forum.
>> <tomcat_home>/webapps/eventscal
>> <tomcat_home>/webapps/forum
>> Of course, I can deploy these 2 webapps on the production server but
>> do not wish them to be independent sites. Instead, I wish to make
>> calls to these from the main website - treating them as individual
>> components.  For example, a servlet or JSP in my main site might
>> call (pseudocode) - eventscal.addEvent() or forum.addDisplayThread()
>> Is there a standard mechanism for this ?
>> Options I've considered :
>> a. Creating a custom taglib.  Don't wish to do this because I wish
>>    to be free of JSPs. Also, I still want to be able to deploy the
>>    webapp as a standalone application if needs be.
>> b. I could do this with RMI but that seems like overkill and slower
>>    performance. However, it has the advantage that it's scalable (if
>>    ever I had to deploy over multiple machines).
>> c. RequestDispatcher is the closest that I've seen and I'm happy
>>    to continue using this unless there is a better way to do it.
>> Really, I'm looking at the best mechanism for packaging a
>> webapp so that other people can use it as part of their
>> existing site. eg. one that is perhaps more J2EE or framework
>> friendly, so that the webapp can be used by a greater number
>> of people. If I'm going about this completely wrong, pls do say.
>> Thank you very much for bearing with me,
>> chas
>> --
>> To unsubscribe:   <>
>> For additional commands: <>
>> Troubles with the list: <>
>To unsubscribe:   <>
>For additional commands: <>
>Troubles with the list: <>

To unsubscribe:   <>
For additional commands: <>
Troubles with the list: <>

View raw message