Charles, I am not sure how much help I will be, since I have not used Enhydra. I can only speak from the perspective of the J2EE specification.
Is your site deployed as a Web application, e.g. is it packaged as a war file? Apache SOAP, and the services deployed on it, are usually part of a Web application or a separate Web application themselves. In your case, it seems you could either deploy Apache SOAP and your services as part of the Web application for your site, or as a separate Web application. Your jar can (should?) be deployed within each Web application, or once "globally". I don't know how to translate this to Enhydra terminology, nor do I know if there are bugs related to this (Tomcat, for example, has had bugs with imperfect isolation of webapp-specific classes). Personally, I think it is better practice to put application code at the webapp level, even if this means you load multiple copies for multiple webapps. I do not understand why your standalone apps break if your jar is not in the multiserver classpath. What should Enhydra's classpath have to do with a standalone app running in a separate VM? You can always specify the standalone app's classpath with -classpath on the java command line, anyway. Scott Nichol ----- Original Message ----- From: "Charles Rector" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, November 26, 2002 8:10 AM Subject: Provider Classes > Is it possible to explicitly reference a provider class with an absolute > path? I am having classpath woes. > > A website I am developing with Enhydra 5.0 is dying when I include my site's > jar in multiserver's classpath (so SOAP will be able to find my services, > which exist as part of my site's code). Apparently this conflicts with the > jar which is specified in the classpath information for the site (Enhydra > 5.0 application) from within multiserver's admin (the same jar). Although I > have tried specifying the jar on the multiserver classpath only, and > removing the reference to it from the site's specialized classpath in the > multiserver admin -- I still encountered the same problem. > > The site works in concert with a standalone Java application, which has my > SOAP clients. When my site is dying, the standalone will run fine. But of > course, removing my site's jar from the multiserver classpath causes the > standalone to longer work, since it cannot find my SOAP services. So I can > get either my site or the standalone running, but not both at the same time. > > It looks like I basically just need some way to tell SOAP where my provider > classes are without having to tweak the classpath for multiserver. Has > anybody experienced a similar dilemma before? I've been stumped on this for > over 2 weeks now, and I'm starting to feel a bit discouraged. :-( > > -- > Chuck Rector > Internet Exposure, Inc. > http://www.iexposure.com > [EMAIL PROTECTED] > > Web Development - Web Marketing - ISP Services > (612) 676-1946 > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
