axis-c-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sérgio Gomes" <sergiomdgo...@gmail.com>
Subject Re: Header parameters being ignored
Date Thu, 27 Mar 2008 10:26:32 GMT
Hi Dimuthu,

Thanks for the update, let me know if you'd like me to do some testing
once it's done.

In the meantime, is there any way I can overcome this, by, say,
providing the header part of the XML myself?

Cheers,
Sérgio

---
On Thu, Mar 27, 2008 at 4:22 AM, Dimuthu Gamage <dimuthuc@gmail.com> wrote:
> Hi Sérgio,
>  Currently WSDL2C doesn't support picking headers from the wsdl. The
>  classes are generated because it support in wsdl2java tool. Anyway I m
>  right now working in that and the class name problem. Hope I can fix
>  this for the client side within this week
>
>  Thanks
>  Dimuthu
>
>
>
>  On Thu, Mar 27, 2008 at 2:30 AM, Sérgio Gomes <sergiomdgomes@gmail.com> wrote:
>  > Hello again,
>  >
>  >  When sending my SOAP messages, I noticed that the headers were always
>  >  empty, even though the WSDL2C tool generated support for the header
>  >  fields:
>  >
>  >  adb_getAllAdWordsCampaignsResponse_t*
>  >             axis2_stub_op_CampaignService_getAllAdWordsCampaigns(
>  >  axis2_stub_t *stub, const axutil_env_t *env,
>  >
>  >  adb_getAllAdWordsCampaigns_t* _getAllAdWordsCampaigns,
>  >
>  >  adb_useragent_t* _useragent22,
>  >
>  >  adb_password_t* _password23,
>  >                                                         adb_email_t* _email24,
>  >
>  >  adb_clientEmail_t* _clientEmail25,
>  >
>  >  adb_clientCustomerId_t* _clientCustomerId26,
>  >
>  >  adb_developerToken_t* _developerToken27,
>  >
>  >  adb_applicationToken_t* _applicationToken28);
>  >
>  >  (There is also a bug that prevents the correct generation of the class
>  >  names, but it has already been confirmed and will be fixed, according
>  >  to the reply I received when I posted that issue)
>  >  (WSDL can be found at
>  >  https://adwords.google.com/api/adwords/v11/CampaignService?wsdl )
>  >
>  >  As you can see, the function header has all the items that should
>  >  appear on the SOAP header (useragent, password, etc), yet when I
>  >  analyzed the generated .c file, I noticed that these parameters were
>  >  being used nowhere, and thus the header would always be empty.
>  >
>  >  Any tips on this issue? Also, is there an alternate way to set the
>  >  outgoing SOAP header, so that I can work around the issue?
>  >
>  >
>  >  Thanks,
>  >  Sérgio
>  >
>  >  ---------------------------------------------------------------------
>  >  To unsubscribe, e-mail: axis-c-user-unsubscribe@ws.apache.org
>  >  For additional commands, e-mail: axis-c-user-help@ws.apache.org
>  >
>  >
>
>  ---------------------------------------------------------------------
>  To unsubscribe, e-mail: axis-c-user-unsubscribe@ws.apache.org
>  For additional commands, e-mail: axis-c-user-help@ws.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-user-help@ws.apache.org


Mime
View raw message