You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Jarek Gawor (JIRA)" <ji...@apache.org> on 2011/06/03 22:38:47 UTC
[jira] [Created] (GERONIMO-5994) Hot deployer has a couple of
issues
Hot deployer has a couple of issues
-----------------------------------
Key: GERONIMO-5994
URL: https://issues.apache.org/jira/browse/GERONIMO-5994
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Components: Hot Deploy Dir
Affects Versions: 3.0
Reporter: Jarek Gawor
Assignee: Jarek Gawor
Th hot deployer has a couple of issues:
1) The hot deployer incorrectly compares the lastModified() time of a module file with time the module was actually deployed. These times are always different and it causes the module to be unnecessarily redeployed on the next server startup.
2) If a module placed in the hot deployment directory fails to deploy, it is automatically removed from the directory. In general since the user put the file there only the user should be able to delete it. The only exception is when the user undeploys the module via other means, i.e. via the admin console or command line tools.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-5994) Hot deployer has a couple of
issues
Posted by "Jarek Gawor (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-5994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jarek Gawor resolved GERONIMO-5994.
-----------------------------------
Resolution: Fixed
Fix Version/s: 3.0
> Hot deployer has a couple of issues
> -----------------------------------
>
> Key: GERONIMO-5994
> URL: https://issues.apache.org/jira/browse/GERONIMO-5994
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Hot Deploy Dir
> Affects Versions: 3.0
> Reporter: Jarek Gawor
> Assignee: Jarek Gawor
> Fix For: 3.0
>
>
> Th hot deployer has a couple of issues:
> 1) The hot deployer incorrectly compares the lastModified() time of a module file with time the module was actually deployed. These times are always different and it causes the module to be unnecessarily redeployed on the next server startup.
> 2) If a module placed in the hot deployment directory fails to deploy, it is automatically removed from the directory. In general since the user put the file there only the user should be able to delete it. The only exception is when the user undeploys the module via other means, i.e. via the admin console or command line tools.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-5994) Hot deployer has a couple of
issues
Posted by "Jarek Gawor (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-5994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13044053#comment-13044053 ]
Jarek Gawor commented on GERONIMO-5994:
---------------------------------------
In revision 1131238 I committed changes to address the two issues described above. I also re-factored the code a bit (more is needed) to make it easier to enable the hot deployer to handle OSGi bundles and regular Java EE modules.
> Hot deployer has a couple of issues
> -----------------------------------
>
> Key: GERONIMO-5994
> URL: https://issues.apache.org/jira/browse/GERONIMO-5994
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Hot Deploy Dir
> Affects Versions: 3.0
> Reporter: Jarek Gawor
> Assignee: Jarek Gawor
>
> Th hot deployer has a couple of issues:
> 1) The hot deployer incorrectly compares the lastModified() time of a module file with time the module was actually deployed. These times are always different and it causes the module to be unnecessarily redeployed on the next server startup.
> 2) If a module placed in the hot deployment directory fails to deploy, it is automatically removed from the directory. In general since the user put the file there only the user should be able to delete it. The only exception is when the user undeploys the module via other means, i.e. via the admin console or command line tools.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira