#2 cli4j loses track of sticky sublevel

[Anonymous]

if you are in a "sticky" sublevel, say "foo" and you
type in a command not defined in cli.xml, eg "fred",
then the cli "loses track" of what level you are in.

Even though the prompt hinks you are still in the
sublevel, you cant run any of the legit commands for
that sublevel. Nor can you get back into the sublevel.

# ./cli.sh

Available commands:
foo The Sample Application Services Management.
blah The Other Sample Application Management.

CORPX-CLI [admin ]> foo
Available commands:
diagnose Sample Application Server Diagnose.
reload Sample Application Server Reload.
reset Sample Application Server Reset.
start Sample Application Server Invocation.
state Sample Application Server state.
stop Sample Application Server stop/shutdown.

CORPX-CLI [admin foo]> bar
Available commands:
diagnose Sample Application Server Diagnose.
reload Sample Application Server Reload.
reset Sample Application Server Reset.
start Sample Application Server Invocation.
state Sample Application Server state.
stop Sample Application Server stop/shutdown.

CORPX-CLI [admin foo]> reload
Unknown command: reload

Available commands:
foo The Sample Application Services Management.
blah The Other Sample Application Management.

CORPX-CLI [admin foo]> foo
Unknown command: foo

Available commands:
foo The Sample Application Services Management.
blah The Other Sample Application Management.

CORPX-CLI [admin foo]> quit