Hi Daniel! As far as I understand the examples and the documentation, web services are simple classes. You can deploy them with the web-interface of Apache SOAP (e.g. at http://localhost:8080/soap/admin) or via the command line. In any case the class-files of the web-service must be available to Apache SOAP (e.g. in it's classes directory) AND instances of the web-service are created by Apache SOAP (depending on the scope property: request, session, ...).
That means (if I am right ;) - the life-cycle of those web-services is controlled by Apache SOAP - the web-services are running in the same webapp-context as Apache SOAP That seems to be the regular case, documented in many proof of concepts, magazines... Now I like to make an object/instance of another webapp available with Apache SOAP. It's life-cycle is independent of / not controlled by Apache SOAP. It's wihtin another webapp-context. This case is not described in any document I found. And because SOAP itself is discussed as an alternative to RMI or CORBA for inter-object communication, this should be possible... with RMI you're registering objects/instances too. Any idea? Thanks, Henrik >Hi Henrik, > >could you please tell me what you mean with registered objects or what are >registered objects. >I don�t understand it. > >thx >de.we. >____________________________________________ > >SinnerSchrader Deutschland GmbH >Communication & Technology > >mailto:[EMAIL PROTECTED] >http://www.sinnerschrader.com >fon +49.(0) 40.39 88 55-0 >fax +49.(0) 40.39 88 55-55 >gasstrasse 8-16 | 22761 hamburg | germany >____________________________________________
