Hi Rick,
its as I said:
It works, but in case of error the messages might be a little
confusing...
Now that it seems people using this feature I will give it an iteration.
So that it follows our ease of use maxime :-)
> I quit jBoss before it finished redeploying, so it saved an empty
> deployments Hashtable in J2EEDeployer. When it tried to do the
> redeployment, it found no Deployment instances in this.deployments, so
> it just skipped right to the log msg at the end.
>
> These log msgs seem to indicate that the deployment state was somehow
> recovered in some other way...e.g. by deserializing the whole state?? or
> something. An examination of the code showed otherwise. Is there a way
> to determine this situation and log something more correctly descriptive
> than...
>
> [J2ee deployer] deployment state recovered.
Well, actually the problem here is, that on MBean startup the usual
deploy procedure is started including downloading all files new. This
might not be wanted (or expected) I will change this.
BTW when the state was "nothing deployed" and I say "state recovered" I
expect "nothing deployed" as current state. But you re right I will make
it more explicit.
\Daniel
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
