axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sameera Jayasoma <sameera.madus...@gmail.com>
Subject Re: webservice design question
Date Fri, 16 Jan 2009 05:29:47 GMT
On Fri, Jan 16, 2009 at 1:27 AM, rouble <rouble@gmail.com> wrote:

> Hi All,
>
> I have a question on the basics of deploying web services.
>
> I want to understand, when tomcat deploys a service, does it create
> one instance of the class specified in className (in my case,
> ServiceBindingImpl) -- and continuously call the methods on that
> instance? Or does it create a new instance of className for every new
> connection?


This behavior is  depend on the Axis2 session scope that you have used.
Please have a look at the following article.

http://wso2.org/library/231

>
>
> For my application, I have a soap message coming in, that needs to be
> communicated to a main server process.
>
> I have written a axis based tomcat web service to receive the soap
> message, and it works great. Now in the business logic of the allowed
> method, I have the webservice send the soap message, using socket IPC,
> to a main server process.
>
> Now, I am wondering if I can move the entire server process into the
> tomcat webservice. I am trying to cut down on the number of components
> and the socket IPC.
>
> More specifically, does it make sense to have ServiceBindingImpl be my
> main server process? Or is there another way to have the server
> process be part of the tomcat webservice.
>
> I am wondering if someone can direct me on the best way to design this.
>
> TIA,
> rouble
>



-- 
Sameera
http://sameera-jayasoma.blogspot.com/
http://www.flickr.com/photos/sameera-jayasoma

Mime
View raw message