You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Deepal Jayasinghe (JIRA)" <ji...@apache.org> on 2006/03/03 09:06:53 UTC

[jira] Resolved: (AXIS2-392) Hotupdate does not work on directories (for services deployed as directories instead of .aar files).

     [ http://issues.apache.org/jira/browse/AXIS2-392?page=all ]
     
Deepal Jayasinghe resolved AXIS2-392:
-------------------------------------

    Fix Version: 0.95
     Resolution: Fixed

fixed (wait till next commit :) )

> Hotupdate does not work on directories (for services deployed as directories instead of .aar files).
> ----------------------------------------------------------------------------------------------------
>
>          Key: AXIS2-392
>          URL: http://issues.apache.org/jira/browse/AXIS2-392
>      Project: Apache Axis 2.0 (Axis2)
>         Type: Bug
>   Components: deployment
>     Versions: 0.94
>  Environment: Windows XP Pro, JBoss
>     Reporter: Juanda Zeng
>     Priority: Minor
>      Fix For: 0.95

>
> This appears to be by design. The deployment engine only checks for the lastModified() value of the directory, which may not always be updated. For example:
> <axis-home>/
>    services/
>       MyService/
>          META-INF/
>             services.xml
>             services.wsdl
> When services.wsdl is ADDED, the lastModified value of META-INF is updated accordingly. But the lastModified value of MyService does not change.
> When services.xml is updated, the lastModified values of both META-INF and MyService do not change.
> SUGGESTED WORKAROUND FOR USERS:
> -------------------------------------------------------------
> After a service is updated, perform the following:
> 		 File file = new File(myServiceDirectory); // eg. "services/MyService"
> 		 file.setLastModified(System.currentTimeMillis());
> This will force the directory to appear as having been modified.

-- 
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