axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Fabrício Cabral <>
Subject Re: Hold a socket connection to a legacy application
Date Tue, 17 Feb 2009 18:42:03 GMT
For historic purpose: I solved this problem using the sessions concept. How
I did:

1) Implements the Lifecycle interface to POJO service's class

2) add <service name="ServiceName" scope="application"> </service> to
axis2.xml and services.xml files

3) Overrride the init() and destroy() methos. In init() you should put your open
socket and others methods and in destroy() you must the socket close

Thanks everybody!

>> I guess all you need is how to manipulate a client socket in Java [1]. You
>> could use the SO_TIMEOUT = 0
> Will it maintain my socket connection opened after successives calls?
> Could I use *the same* socket to send another "command" to my legacy
> application? I'm asking it because I know by design web services are stateless,
> so I think that will be destroy all socket connections when it ends. I'm wrong?


View raw message