[ http://issues.apache.org/jira/browse/AXIS2-827?page=all ]
Deepal Jayasinghe reassigned AXIS2-827:
---------------------------------------
Assign To: Deepal Jayasinghe
> aar file is locked if it fails to deploy
> ----------------------------------------
>
> Key: AXIS2-827
> URL: http://issues.apache.org/jira/browse/AXIS2-827
> Project: Apache Axis 2.0 (Axis2)
> Type: Bug
> Components: deployment
> Versions: 1.0
> Environment: Axis2 1.0 nightly snapshot dated June 17, 2006. Tomcat. WinXP.
> Reporter: Kent Tong
> Assignee: Deepal Jayasinghe
> Priority: Minor
>
> Similar to AXIS2-673 (which has been resolved). The difference is that if the
> aar file fails to deploy, then the aar file is locked and can't be deleted.
> In my case, my service fails to deploy because it is using a module which has
> not been deployed yet:
> <serviceGroup>
> <service name="FooService">
> <module ref="someUnknownModule"/>
> ...
> </service>
> </serviceGroup>
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
