[ http://issues.apache.org/jira/browse/GERONIMO-1946?page=all ]
Joe Bohn updated GERONIMO-1946:
-------------------------------
Summary: SingleFileHotDeploy fixes for resolve, no force restart, empty
target, and messages (was: SingleFileHotDeploy does not correctly resolve the
configuration ID.)
Description:
The resolve method included in the new SingleFileHotDeploy function has some
processing to resolve a configuration ID that is not fully qualified. There
is a small error that cases it to not be able to return the id that it did
successfully resolve (it attempts to modify a reference to return the new
configID which won't work with pass by reference).
There is also a problem with server restart when the application hasn't
changed and forceDeploy was not specified. Currently the application is not
restarted.
We need to support the case where the target deploy location is empty when the
SingleFileHotDeployer gbean is deployed. This is a case where users want to
use this function for offline deploy and they haven't populated the target when
this initial gbean is deployed.
Finally, it would be nice to add some messages to communicate what this gbean
is doing with regard to deploy, redeploy, undeploy, etc....
was:The resolve method included in the new SingleFileHotDeploy function has
some processing to resolve a configuration ID that is not fully qualified.
There is a small error that cases it to not be able to return the id that it
did successfully resolve (it attempts to modify a reference to return the new
configID which won't work with pass by reference).
> SingleFileHotDeploy fixes for resolve, no force restart, empty target, and
> messages
> -----------------------------------------------------------------------------------
>
> Key: GERONIMO-1946
> URL: http://issues.apache.org/jira/browse/GERONIMO-1946
> Project: Geronimo
> Type: Bug
> Security: public(Regular issues)
> Components: deployment
> Versions: 1.1
> Environment: all
> Reporter: Joe Bohn
> Assignee: Joe Bohn
> Fix For: 1.1
> Attachments: 1946_SingleFileHotDeploy.patch
>
> The resolve method included in the new SingleFileHotDeploy function has some
> processing to resolve a configuration ID that is not fully qualified. There
> is a small error that cases it to not be able to return the id that it did
> successfully resolve (it attempts to modify a reference to return the new
> configID which won't work with pass by reference).
> There is also a problem with server restart when the application hasn't
> changed and forceDeploy was not specified. Currently the application is not
> restarted.
> We need to support the case where the target deploy location is empty when
> the SingleFileHotDeployer gbean is deployed. This is a case where users want
> to use this function for offline deploy and they haven't populated the target
> when this initial gbean is deployed.
> Finally, it would be nice to add some messages to communicate what this gbean
> is doing with regard to deploy, redeploy, undeploy, etc....
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
