Tony,
When you move your application into an operational environment, you would not want to have to delete the data directory each time you want to modify the state of your application. However, in a development environment, I've found that deleting this directory eliminates a number of strange behaviors associated with continuing to start/restart and redeploying artifacts. Now that you have your application running, it may be a good time to take a look at what happened to your system before the hinky behavior started. When you've identified that, I'll be able to help you track down the cause, and eliminate it. Glad to hear its working now! v/r, Mike Van ----- Original Message ----- From: "tony.cocco [via Karaf]" <[email protected]> To: "mikevan" <[email protected]> Sent: Thursday, September 15, 2011 12:58:52 PM Subject: Re: Exceptions when installing spring-jms. Steps I took: In cmd prompt: rd data /s In cmd prompt: bin\karaf In karaf shell: log:set DEBUG In karaf shell: features:install spring-jms Feature installed fine. I've tried the same things I've been doing and it works now. The only thing that has been done differently is the explicit call to rd data /s. Normally, I just use "bin\karaf clean" under the assumption it does the same thing. is it possible it doesn't? And once I get into this corrupted state I need to explicitly delete the data folder? If you reply to this email, your message will be added to the discussion below: http://karaf.922171.n3.nabble.com/Exceptions-when-installing-spring-jms-tp3333414p3339539.html To start a new topic under Karaf - User, email [email protected] To unsubscribe from Karaf - User, click here . ----- Mike Van Mike Van's Open Source Technologies Blog -- View this message in context: http://karaf.922171.n3.nabble.com/Exceptions-when-installing-spring-jms-tp3333414p3339650.html Sent from the Karaf - User mailing list archive at Nabble.com.
