WRB Java Cartridge caching a problem?

From: Robert Gordon <rgordon_at_acpub.duke.edu.nospam>
Date: 1997/06/13
Message-ID: <33a14bfc.326755119_at_news.duke.edu>#1/1


I'm new to Java programming with the WRB Java cartridge, and it seems that each time I alter a program I have to change the name of the class, or else stop and re-start the catridge. I am also unfamiliar with how to just re-start the cartridge and have been re-starting the WRB and OWL just to avoid having to clone classes. Unfortunately nobody here is any farther along than myself so I beg the mercy of those of you further down the road to explain it to me.

I tried using 'owsctl stop JAVA' and 'owsctl stop cartridge' and also stopping the actual process i.e. 'owsctl stop -p 12643' and all failed to do what I had hoped - just stop the java cartridge. Also, what if I have more than one instance of the cartridge running, how do I know which one handled my last request and cached the bytecode?

(if you want to reply via email - simply remove the nospam from the address)

Thanks very much for your time and consideration.

Robert Gordon Received on Fri Jun 13 1997 - 00:00:00 CEST

Original text of this message