SOAP classpath problem

I'm having a problems with an Enhydra 5.0 application and SOAP. The
application contains some SOAP services, and I also have a standalone app
which is a SOAP client and makes use of those services. The problem is that
in order to enable SOAP to find my services, I have to include my site's jar
on the multiserver classpath, and that somehow breaks the site. After I add
the site's jar to the multiserver classpath and restart multiserver, the
Enhydra application will start, but many pages begin dying at that point. I
believe most, if not all, of them use multipart (com.oreilly.servlet).

The standalone will properly launch and is able to find the SOAP services
and operate normally. The site just doesn't seem to like having it's jar on
the multiserver classpath, which I imagine has precedence over the classpath
settings described in the applications' conf file.

Has anybody else had similar problems with SOAP and Enhydra applications?
The services really need to exist within the application because I also use
DODS, and the services rely upon it to perform queries to the database. Do I
need to look into a custom classloader perhaps?

--
Chuck Rector
Internet Exposure, Inc.
http://www.iexposure.com
crector@xxxxxxxxxxxxx

Web Development - Web Marketing - ISP Services
(612) 676-1946