|
RE: Enhydra: Possible Caching Problem Solution: msg#00047java.enhydra.general
Okay, I finally found the culprit. I really can't believe I didn't realize this earlier, but I am also using SOAP and currently the only way I've devised to get it to find my services (which are in the Enhydra application) is to put one of the jars explicitly on multiserver's classpath in its startup script. After performing subsequent deployments without modifying the startup script, the older jar was also included in the classpath and caused all that pain and suffering! That clinches it; I've definitely got to find a better way to get my SOAP services recognized. And while I'm at it I'll see about scraping together enough money for a new brain. ;-) -- Chuck Rector Internet Exposure, Inc. http://www.iexposure.com crector@xxxxxxxxxxxxx Web Development - Web Marketing - ISP Services (612) 676-1946
|
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | RE: Switch Enhydra to URL rewriting mode, Laurent Comte |
|---|---|
| Next by Date: | Re: RE: Switch Enhydra to URL rewriting mode, Terry Steichen |
| Previous by Thread: | RE: Switch Enhydra to URL rewriting mode (<<<<<<<< THIS IS AN AUTOMATED RESPONSE >>>>>>>>>), Kirk Yamamoto |
| Next by Thread: | Porting Enhydra SuperServlet to Jetty, Massimo Lusetti |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |