You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-user@xml.apache.org by fanyun <yu...@vtradex.com> on 2001/07/10 11:33:40 UTC

how soap caches? (a stupid question?)

Hi:

I am new to soap.  I have tested the address sample code.  

I wonder whether the soap frame calls the java application for every request.  Will it cause bad performance.

 Has any caching mechanism  to solve the performance problem in apache soap?  Or is there any other soap implementation have the caching mechanism.




Regards

fanyun

RE: how soap caches? (a stupid question?)

Posted by Eduardo Yánez <ey...@eversystems.com>.
The deployment of a service allows you to specify if the service is per-request (so each time a request arrives a new object is created and destroyed when the request is completed), if the service is per-session (the object last until the session with the client is finished) and if the service is per-application (the soap service last until the soap server finishes).

May be you want use the third option, so the class is loaded on the VM all the time.

Deployment file:
...
	<isd:provider type="java" scope="Request|Session|Application" methods="list-of-methods">
...

Regards, 
E.Y.

-----Original Message-----
From: fanyun [mailto:yun.fan@vtradex.com]
Sent: Martes, 10 de Julio de 2001 05:34 a.m.
To: Soap-User
Subject: how soap caches? (a stupid question?)


Hi:

I am new to soap.  I have tested the address sample code.  

I wonder whether the soap frame calls the java application for every request.  Will it cause bad performance.

 Has any caching mechanism  to solve the performance problem in apache soap?  Or is there any other soap implementation have the caching mechanism.




Regards

fanyun


RE: how soap caches? (a stupid question?)

Posted by Eduardo Yánez <ey...@eversystems.com>.
The deployment of a service allows you to specify if the service is per-request (so each time a request arrives a new object is created and destroyed when the request is completed), if the service is per-session (the object last until the session with the client is finished) and if the service is per-application (the soap service last until the soap server finishes).

May be you want use the third option, so the class is loaded on the VM all the time.

Deployment file:
...
	<isd:provider type="java" scope="Request|Session|Application" methods="list-of-methods">
...

Regards, 
E.Y.

-----Original Message-----
From: fanyun [mailto:yun.fan@vtradex.com]
Sent: Martes, 10 de Julio de 2001 05:34 a.m.
To: Soap-User
Subject: how soap caches? (a stupid question?)


Hi:

I am new to soap.  I have tested the address sample code.  

I wonder whether the soap frame calls the java application for every request.  Will it cause bad performance.

 Has any caching mechanism  to solve the performance problem in apache soap?  Or is there any other soap implementation have the caching mechanism.




Regards

fanyun