#20 Async Operation causes error processing WSDL

closed
nobody
None
5
2006-03-13
2006-01-10
Anonymous
No

In a WSDL with async operations (input only) the
operations up to the async operation are read but the
async operation reports an error processing the WSDL
(but I couldn't find details about the error) and the
processing stops at that point. If there is a place
that I can get details I would be happy to add them
here.

Discussion

  • Ole Lensmar
    Ole Lensmar
    2006-01-10

    Logged In: YES
    user_id=838515

    ok thanks.. I haven't had a go at async operations yet but
    will try to fix this in the upcoming 1.1 release..

    regards!

    /Ole

     
  • Logged In: NO

    I'm trying to debug and fix this as I really need to deal
    with WSDL with async operations. My first step is just
    getting past the loading of the async operation (not trying
    to invoke it). The initial cause is due to the call to the
    call
    to 'com.eviware.soapui.impl.wsdl.WsdlOperation.setOutputName
    ' since the name is 'null'. However, at that point I need
    to go
    into 'com.eviware.soapui.config.OperationConfig.setOutputNam
    e', but the source for the ''com.eviware.soapui.config'
    package is not included in the soapui distribution (just
    the jar with the class files).

    Is there a different distribution to get the source for
    these classes?

     
  • Ole Lensmar
    Ole Lensmar
    2006-01-17

    Logged In: YES
    user_id=838515

    I'm currently fixing this for the 1.x release.. please try
    to changing the following statement:

    op.setOutputName( operation.getBindingOutput().getName() );

    in
    com.eviware.soapui.impl.wsdl.support.SoapHttpBindingImporter to

    if( operation.getBindingOutput() != null )
    op.setOutputName( operation.getBindingOutput().getName());

    and let me know if that helps..

    regards!

    /Ole

     
  • Ed Silky
    Ed Silky
    2006-01-18

    Logged In: YES
    user_id=1429799

    That fixed reading in a new WSDL. Similar changes need to
    be made in three places in
    com.eviware.soapui.impl.wsdl.WsdlInterface.updateDefinition.
    At line 379, 425, and 450 (just search
    for 'getBindingOutput') -
    if (newOperation.getBindingOutput() != null)
    wsdlOperation.setOutputName( newOperation.getBindingOutput
    ().getName() );

    To fix updating a definition.

    Thanks.
    -Ed

     
  • Ole Lensmar
    Ole Lensmar
    2006-01-18

    Logged In: YES
    user_id=838515

    great.. I've moved relevant code into WsdlOperation and
    removed it from updateDefinition and importBinding so it
    isn't duplicated in several places.. Thanks for helping out,
    let me know if you have any more issues..

    regards!

    /Ole

     
  • Ed Silky
    Ed Silky
    2006-01-18

    Logged In: YES
    user_id=1429799

    Any idea when you might post an update? (for the JWS)

    Thanks.

     
  • Ole Lensmar
    Ole Lensmar
    2006-01-18

    Logged In: YES
    user_id=838515

    I hope to have a new version ready in the beginning of
    february (2-3 weeks)..

    regards,

    /Ole

     
  • Ole Lensmar
    Ole Lensmar
    2006-02-27

    Logged In: YES
    user_id=838515

    ok.. this is in the 1.5beta1 release.. please let me know if
    you have any more troubles.

    regards!

    /Ole

     
  • Ole Lensmar
    Ole Lensmar
    2006-02-27

    • status: open --> pending
     
  • Logged In: YES
    user_id=1312539

    This Tracker item was closed automatically by the system. It was
    previously set to a Pending status, and the original submitter
    did not respond within 14 days (the time period specified by
    the administrator of this Tracker).

     
    • status: pending --> closed