you can have the SOAP service instantiate your app and have it run in the same VM instance. Or you can use the service locator pattern to provide a unique instance of your app.
francis >> -----Original Message----- >> From: Aleksandar Milanovic [mailto:[EMAIL PROTECTED]] >> Sent: Wednesday, October 10, 2001 5:13 PM >> To: Soap-User >> Subject: embedding SOAP capabilities in a standalone app >> >> >> Hi All, >> >> The Apache SOAP implementation requires that an application be >> deployed as a >> web application/service in the Tomcat web server for it to be able to use >> SOAP messaging. The app that I am designing will be standalone, >> and I want >> it to be independent of the SOAP implementation. However, I am >> encountering >> a problem in defining how the SOAP servlet and the rest of the >> application >> are going to communicate. >> The SOAP servlet lives in the JVM controlled by Tomcat, whereas >> my app lives >> in its own JVM. I could use RMI or some other way to transfer >> SOAP incoming >> messages from the SOAP servlet to my app (this would be >> something similar to >> the communication between the web container and the EJB >> container in J2EE), >> but I'd rather opt for a solution where the SOAP capabilities >> are embedded >> in my app. I should also note that I am not considering the use of a J2EE >> platform. >> Is there a way to run my app and the SOAP servlet in the same JVM? I was >> considering running my app as another thread, but this seemed cumbersome >> though possible. I am also considering using an RMI SOAP implementation >> because it should address this problem. >> >> Help is very appreciated. >> >> Alex >> -- >> >> Privileged or confidential information may be contained in this >> message. If >> this message was not intended for you, destroy it and notify us >> immediately. >> Opinions, conclusions, recommendations, and other information >> presented in >> this message are not given or necessarily endorsed by my >> employer or firm. >> >> >>
