[
https://issues.jboss.org/browse/JBDS-1602?page=com.atlassian.jira.plugin....
]
Brian Fitzpatrick commented on JBDS-1602:
-----------------------------------------
Lukas, I've been poking at your patch, which I think makes sense. But here's my
question. Obviously the patch will only handle one level of namespace prefix. Do you have
any examples of WSDLs that would be more complex and have more levels of namespace
prefixes?
My worry is that if we build it to handle the case described in this JIRA, which is a
single NS prefix, we're going to run into another more complicated version very
quickly that will break it.
Bill or Lukas, do you happen to have any other, more complicated examples?
Web Service Tester generates SOAP bodies that cause marshaling
issues
---------------------------------------------------------------------
Key: JBDS-1602
URL:
https://issues.jboss.org/browse/JBDS-1602
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Affects Versions: 4.0.0.GA
Environment: JBoss Developer Studio 4.0.0 on Mac OS X 10.6.6
Reporter: Bill Meyer
Assignee: Brian Fitzpatrick
Fix For: 4.1.0.GA
Attachments: jbds-1602-partial.patch, Jira - JBDS-1602.zip, testerutils.diff
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
Open JBDS 4, go to Window -> Show View -> Other -> Web Service Tester.
If I enter my WSDL and select the appropriate Service, Port, and Operation (there's
only 1), the SOAP Body gets filled in as:
<?xml version="1.0" encoding="utf-8" standalone="yes"
?>
<soap:Envelope
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" >
<soap:Body>
<getStockQuoteBySymbol xmlns =
"http://www.jboss.com/webservices/StockQuoteService">
<arg0>?</arg0>
</getStockQuoteBySymbol>
</soap:Body>
</soap:Envelope>
which seems to cause the operation invocation to choke with a NullPointerException. It
appears to be a problem with unmarshalling on the Web Service side. Interesting note is
that soapUI causes the same behavior when I copy the above SOAP envelope into soapUI and
execute the call.
If I change the SOAP envelope by moving the operation namespace to the top of the XML
body:
<?xml version="1.0" encoding="utf-8" standalone="yes"
?>
<soap:Envelope
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:stoc = "http://www.jboss.com/webservices/StockQuoteService" >
<soap:Body>
<stoc:getStockQuoteBySymbol>
<arg0>?</arg0>
</stoc:getStockQuoteBySymbol>
</soap:Body>
</soap:Envelope>
Everything executes perfectly. So, I am assuming that the Web Service Tester is
generating a SOAP Body that results in a failed web service invocation. I've tried
this with a few different web services (String and float args) and they all fail the
same.
I am trying to invoke a JAX-WS based web service. I have tried an ASMX-based web service
up on
webservicex.net (
http://www.webservicex.net/stockquote.asmx?WSDL) and not had the
same issue.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira