[ http://issues.apache.org/jira/browse/JS2-196?page=history ]
Ate Douma closed JS2-196:
-------------------------
Resolution: Fixed
Fix Version: 2.0-dev/cvs
2.0-M2
See http://issues.apache.org/jira/browse/JS2-210.
Deployment has been completely rewritten.
> Stop trying when hot deployment fails
> -------------------------------------
>
> Key: JS2-196
> URL: http://issues.apache.org/jira/browse/JS2-196
> Project: Jetspeed 2
> Type: Improvement
> Versions: 2.0-M1
> Environment: Windows 2000, JBoss 4.0.1, Jetspeed-2 M1
> Reporter: Legolas Greenleaf
> Fix For: 2.0-dev/cvs, 2.0-M2
>
> The deployment of the pam.war fails during start-up, so the war is
> un-deployed, and a deploy is retried, which also fails. Unless the war file
> is removed from the file system, this process is iterated infinitely.
> The process follows these steps:
> 1. The ScannerThread detects a new war file in the deploy directory.
> 2. The Portlet war file is loaded.
> 3. The Portlet war file is deployed.
> 4. Error occurs during deployment.
> 5. The Portlet war file is un-deployed.
> 6. The Portlet file remains in the deploy dir to be detected when the
> ScannerThread wakes-up again.
--
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
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
