[
https://issues.apache.org/jira/browse/AXIS2-1596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487364
]
simishag commented on AXIS2-1596:
---------------------------------
I did some additional testing and it looks like this issue only occurs if the
service scope is set to "application" in services.xml. If the scope is
"request", "SOAPSession" or "TransportSession" then hot update appears to work
fine.
This is perhaps the intended behavior and makes sense, but I think it would be
helpful to document this better.
> Re-Deployment is somewhat unreliable.
> -------------------------------------
>
> Key: AXIS2-1596
> URL: https://issues.apache.org/jira/browse/AXIS2-1596
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: deployment
> Affects Versions: 1.1
> Environment: Win XP SP2, Mozilla Firefox 1.5.0.7, Tomcat 5.5.20.
> Reporter: Rainer Menzner
> Assigned To: Deepal Jayasinghe
> Priority: Minor
>
> When recompiling a service and re-deploying the resulting archive, it can
> happen that the status of the tomcat / webservice is not exactly predictable.
> Alas, this effect is not reproducable. I encountered the following two
> situations:
> 1) After changing the function body of a webservice method, recompiling and
> re-deploying (at least the archive file has been copied!), the webservice
> method executed the previous code.
> 2) After renaming a function, the page
> http://localhost:8080/axis2/services/listServices showed both the former
> function at the new function.
> Restarting tomcat solves these problems. However, according to what is
> documented, one should rely on deployment by coyping the archive file.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
