Re: Force-saving router/swiftlet configuration from inside a Swiftlet

Ahh, many thanks - I wondered if that was the way to go about it.

I'm having issues using that approach however - whichever command I execute (save, help, sr routername etc), execute(..) throws a NullPointerException inside java.lang.StringTokenizer (line 146, JDK 1.4.2_19 with SwiftMQ 7.5.1). A debug inspection shows that CliExecutorImpl and SwiftUtilities.tokenize(..) is passing a null string to the StringTokenizer with a delimiter of "/".

Any idea why would this be? I'm guessing this is supposed to be a context path in which to execute the command, so if doing this during a swiftlet's startup, is the context in which to execute not set correctly at that time?