axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephen Kilburn (JIRA)" <j...@apache.org>
Subject [jira] Updated: (AXIS2-3833) WSDL cached/not refreshed when service updated
Date Mon, 02 Jun 2008 16:25:44 GMT

     [ https://issues.apache.org/jira/browse/AXIS2-3833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Stephen Kilburn updated AXIS2-3833:
-----------------------------------

    Attachment: HelloSpring.aar.2
                HelloSpring.aar.1

HelloSpring.aar.1:  has one method called sayGreeting
HelloSpring.aar.2:  sayGreeting renamed sayWorldGreeting; method saySpecialGreeting added

> WSDL cached/not refreshed when service updated
> ----------------------------------------------
>
>                 Key: AXIS2-3833
>                 URL: https://issues.apache.org/jira/browse/AXIS2-3833
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>    Affects Versions: 1.4
>         Environment: XP SP2, Apache 2.2, Tomcat 5.5, JDK1.6.0_06
>            Reporter: Stephen Kilburn
>            Priority: Minor
>         Attachments: HelloSpring.aar.1, HelloSpring.aar.2
>
>
> I compile a service using Ant to an .aar and deploy it (using code modified from the
sample WeatherSpringService).  Service shows up correctly.  Then recompile it adding a new
method or change the name of an existing method.  When service is redeployed Axis2 listServices
still lists the old method name and none of the new methods are shown.  When I look at the
WSDL it is correct for the old service.
> I have confirmed that the new .aar has been deployed correctly, shut down and restarted
Tomcat, (tried other variations like shutting down Tomcat, deleting the .aar, starting up
Tomcat, then redeploying the .aar), shut down and restarted Apache, and cleared the browser
caches.  None of this has helped.  Shutting down Tomcat, deleting the Axis2 service, and reinstalling
the .war fixes this.  I have concluded from the system behaviour that Axis2 is caching its
generated WSDL for the service somewhere and isn't deciding to do a cache refresh.  I have
searched everywhere I imagine this information might be stored, but have been unsuccessful
in finding it.

-- 
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org


Mime
View raw message