[
https://jira.jboss.org/browse/JBIDE-6457?page=com.atlassian.jira.plugin.s...
]
Brian Fitzpatrick commented on JBIDE-6457:
------------------------------------------
Delivered fix to work around the missing child root element. In this case, we'll
simply grab the Response tag and its children and put all of it in the XML editor.
Also delivered a fix for generating SOAP Request messages. Need to do further testing
there to see what can be done about multiple WSDL/Schema imports scattered throughout a
complex WSDL.
And delivered a tweak to the WSDL browse dialog to allow it to be used in a slightly
different context. Though the main use case is to allow providing a WSDL and specifying a
service/port/operation combo to test, I'm also looking at using it in the context of
browsing a UDDI repository to get WSDL details about registered services.
[tester] Opening invocation results doesn't always work from the
SOAP response message
--------------------------------------------------------------------------------------
Key: JBIDE-6457
URL:
https://jira.jboss.org/browse/JBIDE-6457
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Webservices
Affects Versions: 3.2.0.M1
Reporter: Brian Fitzpatrick
Assignee: Brian Fitzpatrick
Fix For: 3.2.0.M1
When invoking a web services and perusing the SOAP response, there's a menu option to
just view the response tag or contents vs. showing the entire SOAP response in an XML
editor. Currently this runs into an issue when the response element doesn't have a
child that's a root.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira