RE: SOAP + DODS

Ah!

That makes sense, about the class not being found. I had eventually found
out yesterday that I needed to include dods.jar in our multiserver's
classpath. Yes, this is a multiserver app with presentation objects (Mike).
The version of SOAP I'm using is 2.3.1.

Now that I've finally got everything working, I have one last slight
annoyance left. As my services are inside my multiserver app, currently the
only way I've been able to get SOAP to find my services is by including my
app's jar directly in the multiserver class path. This wouldn't be so bad,
except every time we deploy an app to the server, we do so with a new
timestamped filename, and then tweak the app's conf file as appropriate to
point to this new jar.

I'm not sure of the specifics, but one of my fellow employees determined
once upon a time that there were problems with multiserver correctly loading
new or modified classes in a freshly deployed jar which is simply
overwritten. Something about it being the Java class loader's fault.

At any rate, since a new filename is used each time, this means that every
time I deploy my app, I also have to tweak the multiserver startup script to
include the new jar and then restart multiserver. Obviously this can get
harassing, not only for me, but for all the people connected to all the
other apps running on the same server (20+).

Another fellow employee mentioned that he had read about being able to
decompress soap.war into enhydra/webapps/soap and then dropping the jar
files into enhydra/webapps/soap/WEB-INF/lib, at which point Enhydra would
supposedly magically search the jars present there and SOAP would be able to
find my services. However, we were unable to get this to work.

Has anybody had similar troubles?

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

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

> -----Original Message-----
> From: enhydra-admin@xxxxxxxxxxx [mailto:enhydra-admin@xxxxxxxxxxx]On
> Behalf Of Luís Fraga
> Sent: Wednesday, October 16, 2002 4:37 AM
> To: enhydra@xxxxxxxxxxx
> Subject: Re: Enhydra: SOAP + DODS
>
>
> Hi Mike!
>
> The method you suggested to deploy Glue works indeed. However you must
> notice that when you shut down your webapp you are not shutting down the
> DodsStandaloneTest application properly. The container calls Glue
> ServletServer "destroy" and will never call your DodsStandaloneTest
> shutdown.
> I mentioned this issue in mails I sent last week but as I still don't
> know how to handle this, I came back for more..:)
>
> What happens when I destroy a webapp in this fashion (without cleaning
> out all resources)?
> Are there any references to the DodsStandaloneTest app remaining in the
> Multiserver that were not freed? (Database Managers, Application
> registry?)
> If there are, do these references prevent the Multiserver to properly
> clean out the web app on unload?
>
> As for Charles fault, I don't know what Soap engine you are using but if
> it is Glue faults like that usually mean that the class was not found
>
> com/lutris/dods/builder/generator/query/QueryException
>
> I am not sure where that class is in 5.0 but maybe you need to add
> dods.jar to you classpath.
>
> Regards,
>     Luís
>
> Mike Warne wrote:
>
> >Hi Charles,
> >
> >Have you checked your multiserver logs for additional info on
> the exception?
> >I'm not sure what kind of application you have written.  Is it a
> Web App (WAR)? Or is it a multiserver application, using
> presentation objects?
> >
> >My only experience with SOAP has been with "GLUE".
> >
> >DODS uses services provided by Enhydra.  So any thread of
> execution must be wrapped with Enhydra.register and
> Enydra.unregister calls when attemtpting to use DODS.
> >Remember this must be done for each request.
> >
> >I looked at the StandAlone class you referred to in the
> archives. I've never used it,  but I believe that you will need
> to do something like this:
> >
> >1.  When you initialize your app, or servlet..
> >    Instantiate your DodsStandaloneTest class.
> >    DodsStandaloneTest application = new
> DodsStandaloneTest(configFileName);
> >
> >2.  Your SOAP methods will need access to the application
> variable, and must use it to register with Enhydra.  That way
> DODS can get access to the DB manager and other stuff it needs.
> Enhydra.register takes your current thread ID and stores it in a
> HashTable together with the application instance.  That way it
> can map DODS calls made by a thread, to the correct DB manager.
> >
> >Enydra.register(application);
> >try {
> >  run your DODS methods here...
> >} finally {
> >   Enhydra.unRegister();
> >}
> >
> >Hope this helps, however I have not yet tried this.
> >Mike.
> >
> >-----Original Message-----
> >From: Charles Rector [mailto:crector@xxxxxxxxxxxxx]
> >Sent: Monday, October 14, 2002 11:29 AM
> >To: enhydra@xxxxxxxxxxx
> >Subject: Enhydra: SOAP + DODS
> >
> >
> >Hey, I'm using Enhydra 5.0 and DODS and have recently set up
> SOAP on one of
> >our (my company's) servers. I have a service deployed and have written a
> >client which communicates with it. I believe it's set up
> correctly, as far
> >as what's talking to what and where -- if I specify a differing
> ID, it tells
> >me it is an unknown service, and if I alter the URL I get an
> >UnknownHostException. There seems to be one last piece from the puzzle
> >missing, however, since when I run my client I receive the
> following fault
> >code and string:
> >
> >     SOAP-ENV:Server
> >     com/lutris/dods/builder/generator/query/QueryException
> >
> >While browsing through this mailing list I found a
> DodsStandaloneTest class,
> >which I attempted to use by pointing it to the appropriate conf
> file on our
> >server, but to no effect -- perhaps I'm simply using it incorrectly.
> >
> >Does anybody have an idea as to what might be my problem? Even a link to
> >some relevant information would be much appreciated. Thanks!
> >
> >--
> >Chuck Rector
> >Internet Exposure, Inc.
> >http://www.iexposure.com
> >crector@xxxxxxxxxxxxx
> >
> >Web Development - Web Marketing - ISP Services
> >(612) 676-1946
> >
> >_______________________________________________
> >Enhydra mailing list
> >Enhydra@xxxxxxxxxxx
> >http://www.enhydra.org/mailman/listinfo.cgi/enhydra
> >
> >_______________________________________________
> >Enhydra mailing list
> >Enhydra@xxxxxxxxxxx
> >http://www.enhydra.org/mailman/listinfo.cgi/enhydra
> >
> >
> >
> >
>
>
>
> _______________________________________________
> Enhydra mailing list
> Enhydra@xxxxxxxxxxx
> http://www.enhydra.org/mailman/listinfo.cgi/enhydra
>