[email protected] created AXIS2-5370:
------------------------------------------
Summary: Querying a WSDL from Axis2 returns an outdated service
description
Key: AXIS2-5370
URL: https://issues.apache.org/jira/browse/AXIS2-5370
Project: Axis2
Issue Type: Bug
Reporter: [email protected]
When a Web service archive (.aar) is deployed on Tomcat , then is modified an
re-deployed, querying the WSDL returns the "old" (cached?) WSDL which does not
reflect the latest changes. The service, however, contains the latest changes
and behaves accordingly.
The issue can be reproduced as follows:
1. Generate a simple Web service and deploy the archive."
2. Query the service's WSDL (using for example:
http://localhost:8080/axis2/services/myws?wsdl)
3. Modify the service in the .aar editor (for example by configuring Transport
binding, which demands the use of HTTPS)
4. Save and re-deploy the service
5. Query the WSDL once again. It returns the "old" WSDL (which does not contain
the Transport binding policy wit HTTPS transport)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.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]
