Service classloading issues when undeploying and redeploying a service with the
same name.
------------------------------------------------------------------------------------------
Key: AXIS2-3297
URL: https://issues.apache.org/jira/browse/AXIS2-3297
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: kernel
Affects Versions: 1.3
Environment: Windows XP/Jboss 4.2.
Reporter: Tony Dean
I have a service called 'Maker' that generates new services upon client
requests. If it creates and deploys a new service called 'myService' for
instance and then later removes this service (deletes from repository), and
then generates an entirely new service with the same name, but with totally
different functionality (ie., class name is the same, but has different
functionality, the service.xml is similar, and the wsdl is totally different),
it appears that when the client invokes the new service that the original
service's (the service that was removed) class is executed instead of the class
that is associated with the new service. It appears that Axis2 is performing
some service caching that is not getting replaced by new service deployment.
If I stop and restart the jboss server such that Axis2 is started from scratch,
it loads everything just fine and the new class for that service is executed
when the service is invoked by the client just as expected.
--
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]
