IBM webMethods Hybrid Integration

IBM webMethods Hybrid Integration

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.



#Automation


#Applicationintegration
#webMethods
#Integration
 View Only
  • 1.  Creating Web Sevice Descriptor error!

    Posted 04/14/11 03:49 PM

    Hi when am trying to create a web service descriptor (provider) from a wsdl file (source WSDL URL) i get the following error in WM dev 8.0

    [ITD.0031.0001] Create Web service descriptor ‘IsysSales.ActualRevenueSvc:ActualRevenueSvc’ failed.

    When I click on details, I get the following,

    com.wm.app.b2b.server.ServiceException: java.lang.NullPointerException
    at wm.server.ws.wsdl2wsd(ws.java:1515)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at com.wm.app.b2b.server.JavaService.baseInvoke(JavaService.java:439)
    at com.wm.app.b2b.server.invoke.InvokeManager.process(InvokeManager.java:635)
    at com.wm.app.b2b.server.util.tspace.ReservationProcessor.process(ReservationProcessor.java:46)
    at com.wm.app.b2b.server.invoke.StatisticsProcessor.process(StatisticsProcessor.java:44)
    at com.wm.app.b2b.server.invoke.ServiceCompletionImpl.process(ServiceCompletionImpl.java:238)
    at com.wm.app.b2b.server.invoke.ValidateProcessor.process(ValidateProcessor.java:51)
    at com.wm.app.b2b.server.invoke.PipelineProcessor.process(PipelineProcessor.java:171)
    at com.wm.app.b2b.server.ACLManager.process(ACLManager.java:272)
    at com.wm.app.b2b.server.invoke.DispatchProcessor.process(DispatchProcessor.java:30)
    at com.wm.app.b2b.server.AuditLogManager.process(AuditLogManager.java:399)
    at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:539)
    at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:384)
    at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:234)
    at com.wm.app.b2b.server.comm.DefaultServerRequestHandler.handleMessage(DefaultServerRequestHandler.java:119)
    at com.wm.app.b2b.server.HTTPMessageHandler.process(HTTPMessageHandler.java:160)
    at com.wm.app.b2b.server.HTTPDispatch.handleRequest(HTTPDispatch.java:190)
    at com.wm.app.b2b.server.Dispatch.run(Dispatch.java:350)
    at com.wm.util.pool.PooledThread.run(PooledThread.java:131)
    at java.lang.Thread.run(Thread.java:619)
    Caused by: java.lang.NullPointerException
    at wm.server.ws.wsdl2wsd(ws.java:979)
    … 23 more

    am not sure what this error really means, any ideas? Help is really appreciated!


    #API-Management
    #soa
    #webMethods


  • 2.  RE: Creating Web Sevice Descriptor error!

    Posted 04/15/11 01:45 AM

    It is very possible that your WSDL is malformed. Or, the WSDL may contain features not supported by the webMethods version that your are using. Try validating your WSDL with a WSDL validation tool. Try importing your WSDL into a test tool such as soapUI and see if the tools finds your WSDL to be of valid form.


    #soa
    #webMethods
    #API-Management


  • 3.  RE: Creating Web Sevice Descriptor error!

    Posted 05/19/11 11:37 AM

    Also IS can’t cope with circular imports.
    The wsdl importing and xsd1 which imports xsd2 which imports xsd1.
    Other validation tools may find this OK, but IS will fail.


    #webMethods
    #API-Management
    #soa