function readOnly(count){ }
Sign Up ›
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
Learn More

Browse by Topic
ShowAll Questionssorted byDate Posted
+ Start a Discussion
salesForceUsersalesForceUser 

anyone using weblogic to convert the WSDL?

Hi ,

I am using weblogic clientgen to convert the WSDL  to client stubs and am facing this issue. Anyone tried this and faced similar issue?

E:\sforceWeblogicVentaso>java -cp e:\wl810\server\lib\weblogic.jar;e:\wl810\serv
er\lib\webservices.jar;E:\wl810\jdk141_03\lib\tools.jar; weblogic.webservice.cli
entgen -wsdl sforceenterprise.wsdl -packageName sforce -clientJar sforce.jar
weblogic.webservice.tools.wsdlp.WSDLParseException: ERROR[WSDL Parser]:There is
no name attribute found for soap:fault in binding operation <operation  name="lo
gin">
 <soap:operation   soapAction="">
 </soap:operation>
 <input>
  <soap:body    parts="parameters"
    use="literal">
  </soap:body>
 </input>
 <output>
  <soap:body    use="literal">
  </soap:body>
 </output>
 <fault   name="LoginFault">
  <soap:fault    use="literal">
  </soap:fault>
 </fault>
 <fault   name="UnexpectedErrorFault">
  <soap:fault    use="literal">
  </soap:fault>
 </fault>
</operation>
        at weblogic.webservice.tools.wsdlp.WSDLParser.assertion(WSDLParser.java:
750)
        at weblogic.webservice.tools.wsdlp.WSDLParser.parseBindingOperation(WSDL
Parser.java:511)
        at weblogic.webservice.tools.wsdlp.WSDLParser.parseBinding(WSDLParser.ja
va:277)
        at weblogic.webservice.tools.wsdlp.WSDLParser.parsePort(WSDLParser.java:
217)
        at weblogic.webservice.tools.wsdlp.WSDLParser.parseService(WSDLParser.ja
va:169)
        at weblogic.webservice.tools.wsdlp.WSDLParser.parseDefinition(WSDLParser
.java:117)
        at weblogic.webservice.tools.wsdlp.WSDLParser.visit(WSDLParser.java:97)
        at weblogic.webservice.WebServiceFactory.createFromWSDL(WebServiceFactor
y.java:110)
        at weblogic.webservice.WebServiceFactory.createFromWSDL(WebServiceFactor
y.java:84)
        at weblogic.webservice.tools.build.internal.ClientGenImpl.getWSRunTimeFr
omWSDL(ClientGenImpl.java:735)
        at weblogic.webservice.tools.build.internal.ClientGenImpl.doClientGenFro
mWsdl(ClientGenImpl.java:410)
        at weblogic.webservice.tools.build.internal.ClientGenImpl.run(ClientGenI
mpl.java:343)
        at weblogic.webservice.clientgen.doClientGen(clientgen.java:194)
        at weblogic.webservice.clientgen.runBody(clientgen.java:86)
        at weblogic.utils.compiler.Tool.run(Tool.java:146)
        at weblogic.utils.compiler.Tool.run(Tool.java:103)
        at weblogic.webservice.clientgen.main(clientgen.java:213)

DevAngelDevAngel

Hi salesForceUser,

Thanks for the post.  We are aware of this problem with Weblogic's wsdl parser.  What is seen is a restrictive validation of the wsdl to ws-i specifications.  The error being reported is due to an "interpretation" of the spec.  I believe we are going to be adding this attribute name in the near future.  The work around is to add the names for each fault by hand and then re-run the clientgen with the modified version of the wsdl