I'm playing around with J2EEDeployer. Deployed a .ear containing 1 .war
and 2 ejb.jar files. Then shutdown jBoss and restarted. J2EEDeployer
attempts first undeploy. ContainerFactory.undeploy() is called to
undeploy the ejb apps. The following exception is thrown because the
requested url is not currently deployed...which seems like correct
behavior to me.
public void undeploy(URL url)
throws DeploymentException
{
// Get application from table
Application app = (Application)deployments.get(url);
// Check if deployed
if (app == null)
{
throw new DeploymentException("URL not deployed");
The problem is that the log msg (I think) is confusing. At least it was
to me before I looked into the code...I misinterpreted this to mean that
something might be amiss. ...the msg is:
"unable to undeploy module xxx.jar: URL not deployed"
A better msg might be something like:
"undeploy skipped OK for module xxx.jar: module not currently
deployed"
Cheers,
Rick Horowitz
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
