Community
Participate
Working Groups
Hi Colleagues, For some reason Web Service Explorer is not able to execute methods of jee5 web services. It reports that the binding declared in such WSDL is unsupported. Pressing an operation in order to get it executed does nothing. No error message - just white screen. I'm attacing an example WSDL of an "echo" Web Service which is reported wrong by WS Explorer. Also I'm attaaching a small EJB 3.0 top-down implementation for this web service. In the same time the WSDL editor says that this is correct WSDL. Regards, Hristo
Created attachment 59982 [details] example WSDL Reported Wrong
Created attachment 59984 [details] EJB 3.0 Top-Down implementation for the wsdl reported wrong. Sources are inside the ear archive.
Hristo, it turns this is not a Java EE 5 issue. Instead, the WSE is having trouble recognizing the xmlns:soap namespace declarations on the <wsdl:binding> and/or <soap:address> elements. Adding the declaration xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" to the <wsdl:definitions> element works around the problem. You might want to try this just to make sure there are no other actual Java EE 5 message exchange issues lurking. Meanwhile, we'll try to investigate this for 1.5.4. Gil, would you please?
Ok this looks like a bug in wsdl4j. John Kaputin has informed me that he thinks this is fixed in the latest version of wsdl4j. Im not sure what version we are using right now I am trying to track this down.
Ok so we have found a problem in the wsdl4j we arent sure if it will be updated for 1.54 in fact tis most likely not. So we could do a translation in our code but it might be a bit tricky alot of work and a chance at causing breakage. Im wondering if this might be better delayed to the next release depending on its importance.
Hristo, from Gil's analysis and determination the problem is in the WSDL4J third party library, we don't have an obvious and safe solution to this, and yet it seems like a potentially nasty bug. Is the fact you opened this at "normal" severity a true reflection that this not a serious issue for you? More to the point, can we defer this to a later release?
Deferred out of WTP 1.5.4. I'm not sure when we can/should/must tackle this - WTP 2.0 or 3.0 - since this boils down to upgrading WSDL4J which will have potential impacts on several downstream components, not just the Web service tools and this scenario. Valentin, do you have a bug or RFE brewing to update WSDL4J we should tie ourselves to?
Hi Chris, I have the feeling it may be too late for 2.0 as well since we're in RC0 and I have not seen yet the plans for 3.0. There are a few bugs - this https://bugs.eclipse.org/bugs/show_bug.cgi?id=167416 one being an example - asking for newer WSDL4J versions for various reasons. We do not yet have an RFE dedicated to the upgrade.
Hi, It's not critical for 1.5.*, but it would really be pitty if we don't get it in wtp 2.0. This would mean that almost no SAP web services can be consumed using Web Services Explorer So the priority is higher than normal. So I'm setting it to major. From my point of view it's critical for Developers using SAP NetWeaver Developer Studio (based on eclipse) Regards, Hristo
*** Bug 164245 has been marked as a duplicate of this bug. ***
I just try below wsdl with WTP2.0, the webservice explorer version is 1.0.204 v200706030435, the result is failed, can't invoke the method the wsdl is : <?xml version="1.0" encoding="UTF-8"?> <definitions name="BookFinderServiceDefinitions" targetNamespace="http://com/vitria/hellowstutorial" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:s0="http://www.w3.org/2001/XMLSchema" xmlns:s1="http://com/vitria/hellowstutorial" xmlns:s2="http://schemas.xmlsoap.org/wsdl/soap/"> <types> </types> <message name="lookupResponse"> <part name="lookupReturn" type="s0:string"/> </message> <message name="lookup"> <part name="lookup_ParamA" type="s0:string"/> <part name="lookup_ParamB" type="s0:string"/> </message> <portType name="BookFinder"> <operation name="lookup" parameterOrder="lookup_ParamA lookup_ParamB"> <input message="s1:lookup"/> <output message="s1:lookupResponse"/> </operation> </portType> <binding name="BookFinderServiceSoapBinding" type="s1:BookFinder"> <s2:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/> <operation name="lookup"> <s2:operation soapAction="" style="rpc"/> <input> <s2:body namespace="http://com/vitria/hellowstutorial" parts="lookup_ParamA lookup_ParamB" use="literal"/> </input> <output> <s2:body namespace="http://com/vitria/hellowstutorial" parts="lookupReturn" use="literal"/> </output> </operation> </binding> <wsdl:service name="BookFinderService" xmlns:apwsdl="urn:com.amberpoint.wsdl" xmlns:e="http://com.amberpoint.messaging/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"><wsdl:port binding="s1:BookFinderServiceSoapBinding" name="BookFinderSoapPort"><soap:address location="http://pek-wkst220.qilinsoftcorp.qilinsoft.com:8080/eProxy/service/BookFinderSoapPort_Proxy"/><apwsdl:targetWSDL><apwsdl:URL>http://pek-wkst220.qilinsoftcorp.qilinsoft.com:7001/HelloWebServicesApplication/ServiceProxy.wsdl</apwsdl:URL><apwsdl:agentID>uuid:CB9B8A1C-036F-11DC-B6CD-54C46AA1AA77</apwsdl:agentID><apwsdl:uwsID>uuid:CF9FAC93-0370-11DC-B6CD-54C46AA1AA77</apwsdl:uwsID><apwsdl:uwsLocalname>BookFinderSoapPort_Proxy</apwsdl:uwsLocalname></apwsdl:targetWSDL></wsdl:port></wsdl:service></definitions>
Hi Valentin and Craig, I've opened bug 197197 to track the requirement to upgrade to the latest WSDL4J. Would it be possible to fix that in WTP 3.0? Gil, Could you please find out which version of WSDL4J would have this problem fixed so that we make sure that that version or a later one is picked up in bug 197197?
This may actually be caused by the WSDL EMF model. The WSE appears to be using the WSDL EMF model and not WSDL4J. Both these components implement the JWSDL interfaces. See bug 198390 for a fix that seems to address this.
This bug is a dup of 198390 which has been fixed in WTP 2.0.2. *** This bug has been marked as a duplicate of bug 198390 ***
Please verify the defect you originated with a recent WTP driver which could be found in: http://download.eclipse.org/webtools/downloads/ If defects in resolved state is not verified within a couple of weeks, the development team might verify and close the defect on the originator's behalf. Thank you for your attention!
Bug cleanup. Closing on behalf of the originator.
