[
https://issues.apache.org/jira/browse/GERONIMO-4420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan updated GERONIMO-4420:
---------------------------
Attachment: Geronimo-4420.patch
While invoking DeploymentContext.getConfigurationData() in the Deployer.install
method, a DeploymentException may be threw due to the gbean verification
failure.
But the codes are not in the try-catch block, so the configuration dir is not
added to the DeployerReapter's deleting list.
Please help to review the patch, it passed the unit testing of the
geronimo-deployment module.
Thanks !
> Create Files under repository even if fail to deploy a jar having problems.
> ---------------------------------------------------------------------------
>
> Key: GERONIMO-4420
> URL: https://issues.apache.org/jira/browse/GERONIMO-4420
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: deployment
> Affects Versions: 2.1.3
> Environment: OS:Any platform
> Reporter: viola.lu
> Priority: Minor
> Fix For: 2.1.4, 2.2
>
> Attachments: Geronimo-4420.patch, testejb.jar
>
>
> Defect transfers from GEP:
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-534
> Steps:
> 1.Deploy attached testejb.jar, and this jar has some problems in it.So when
> deploy it via command or admin console, errors exist.
> 2.But in repository, files for this deployed jar are created already.If i
> redeploy this jar or deploy it second time, it will inform me : it exists in
> repository, i should remove it manually from repository.
> no log in server.log.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
