WSDL Issue (AXIS2)...?

Last post 10-21-2009 23:11 by phillips. 3 replies.
Page 1 of 1 (4 items)
Next
Previous
Sort Posts:
  • phillips 10-21-2009 16:19

    • Top 150 Contributor
    • Joined on 03-14-2008
    • Posts: 23

    WSDL Issue (AXIS2)...?

    Hello,

     

    I'm using AXIS2 to generate Java classes from the WSDL at...

     

    http://www.zenfolio.com/api/1.1/zfapi.asmx?wsdl

     

    ...but notice that the SOAPAction for AuthenticatePlain is as follows...

     

    <soap:operation soapAction="http://www.zenfolio.com/api/1.1/AuthenticatePlain" style="document"/>

     

    ...when trying to authenticate using AXIS2, I get the following...

     

    Exception in thread "main" org.apache.axis2.AxisFault: HTTPS connection required

     

    ...and am wondering whether the WSDL is correct (i.e. soapAction="https://....)

     

    When I manually change the action to HTTPS in the generated class, I get the following however...

     

    Exception in thread "main" org.apache.axis2.AxisFault: Server did not recognize the value of HTTP Header SOAPAction: https://www.zenfolio.com/api/1.1/AuthenticatePlain

     

    Not sure what that's about. I should point out that the LoadPublicProfile request seems to work (using AXIS2)

  • phillips 10-21-2009 16:43 In reply to

    • Top 150 Contributor
    • Joined on 03-14-2008
    • Posts: 23

    Re: WSDL Issue (AXIS2)...?

    I should point out that when I copied the WSDL locally and updated the http to https, and regenerated the Java classes, I had the same 'Server did not recognize the value of HTTP Header SOAPAction...' error message.

  • AF [Zenfolio] 10-21-2009 22:42 In reply to

    • Top 10 Contributor
    • Joined on 03-01-2008
    • San Francisco Bay Area, California
    • Posts: 583

    Re: WSDL Issue (AXIS2)...?

    You need not modify the WSDL, you just need to call this method over an HTTPS connection. Not sure how this is done with Java wrappers generated by AXIS2.

    -- AF [Zenfolio]
  • phillips 10-21-2009 23:11 In reply to

    • Top 150 Contributor
    • Joined on 03-14-2008
    • Posts: 23

    Re: WSDL Issue (AXIS2)...?

    To be honest, WSDL and AXIS2 are both industry standards. If generated AXIS2 classes cannot communicate with a SOAP service using the WSDL provided, something is wrong (or rather non-standard) on the server end.

    I note that AXIS2 generated classes relating to methods that require authentication do not seem to require a previously generated authentication token to be passed in. This implies that state needs to be kept somewhere and that is not part of what AXIS2 does. Whilst the server seems to remember the token (I assume in a session), the client also needs to maintain that same token (outside of AXIS2).

    I was hoping to use AXIS2 instead of my own home grown SOAP envelope builders so as to cut down on my need to contact support and more rapidly respond to API version changes.

Page 1 of 1 (4 items)