On Fri, Dec 4, 2009 at 11:13 PM, Samisa Abeysinghe <samisa@wso2.com> wrote: > I meant to say, Axis2! > Samisa... > > On Fri, Dec 4, 2009 at 11:08 PM, Samisa Abeysinghe <samisa@wso2.com> wrote: >> >> Folks, >> I looked at the Jiras after a loooong time and seems that there are >> quite a number of them as well as few ones with patches from users. >> May be it is a good time to fire up a new release. Thoughts are >> welcome. +1. I'll go through the Jira and fix them. What will be the version number? 1.7.0? Regards, Shankar >> Thanks, >> Samisa... >> -- >> Samisa Abeysinghe >> Director, Engineering - WSO2 Inc. >> >> http://www.wso2.com/ - "The Open Source SOA Company" > > > > -- > Samisa Abeysinghe > Director, Engineering - WSO2 Inc. > > http://www.wso2.com/ - "The Open Source SOA Company" > -- S.Uthaiyashankar Software Architect WSO2 Inc. http://wso2.com/ - "The Open Source SOA Company"
Samisa, Thanks for the response. I mentioned the _t because when I posted the message, the ONLY difference between the two services was their names. One has the _t and the other does not. So it seemed likely to me that the different behavior was related to their different names. This is not a big problem for me because I think I have a workaround. I guessed that the Axis2/C team would either recognize what's happening here, or would want to understand it sometime. Best regards, George -------------- Forwarded Message: -------------- From: Samisa Abeysinghe <samisa@wso2.com> To: Apache AXIS C User List <axis-c-user@ws.apache.org> Subject: Re: DLL path for libTestCases_t.so is set to libTestCases.so Date: Fri, 04 Dec 2009 17:19:58 +0000 AFAICT, _t has nothing to do with the problem you are facing. Samisa... On Wed, Oct 28, 2009 at 5:19 AM, <gsherwood@att.net> wrote: I have set up two services which (for now) are identical except for their names, TestCases and TestCases_t. The choice of the suffix _t is historical and has nothing to do with type names. libTestCases.so and libTestCases_t.so are placed in their respective directories: /usr/local/www/64.232.245.115/axis2c/services/TestCases and /usr/local/www/64.232.245.115/axis2c/services/TestCases_t However, log entries indicate the DLL path for libTestCases_t.so is not getting set correctly. Relevant entries include the following. [Tue Oct 27 19:22:33 2009] [debug] svc_builder.c(318) DLL path is : /usr/local/www/64.232.245.115/axis2c/services/TestCases/libTestCases.so [Tue Oct 27 19:22:33 2009] [debug] om_element.c(1114) There are no child elements for the node [Tue Oct 27 19:22:33 2009] [debug] svc_builder.c(318) DLL path is : /usr/local/www/64.232.245.115/axis2c/services/TestCases_t/libTestCases.so [Tue Oct 27 19:22:33 2009] [debug] om_element.c(1114) There are no child elements for the node ... [Tue Oct 27 19:22:33 2009] [error] class_loader.c(162) Loading shared library /usr/local/www/64.232.245.115/axis2c/services/TestCases_t/libTestCases.so Failed. DLERROR IS /usr/local/www/64.232.245.115/axis2c/services/TestCases_t/libTestCases.so: cannot open shared object file: No such file or directory If I depart from the usual naming convention (i.e. libTestCases_t.so for TestCases_t), and use the name in the DLL path instead (libTestCases.so), then the service works. Can anyone help with answers to these questions? 1. Is this behavior (dropping the _t suffix) a bug or a feature? 2. Is setting the name to the DLL path indicated in the log a legitimate workaround? 3. Am I likely to encounter future trouble with a service name ending in _t? Thanks, George Sherwood Testcover.com -- Samisa Abeysinghe Director, Engineering - WSO2 Inc. http://www.wso2.com/ - "The Open Source SOA Company"
On Fri, Dec 4, 2009 at 11:09 PM, Sam Carleton <scarleton@gmail.com> wrote: > Dimuthu, > > Where EXACTLY does one find the latest WSDL2C code? Is it in an build or > is it in the Axis2/Java SVN repository? > Axis2 svn. Samisa... > > Sam > > > On Thu, Dec 3, 2009 at 10:57 PM, Dimuthu Gamage <dimuthuc@gmail.com>wrote: > >> Hi, >> >> If you use the latest axis2 WSDL2C generator code, you don't need to >> create soap fault message manually as the generated code provide lot of >> support in generating fault message. >> >> Please have a look at this for the improved API, >> http://www.dimuthu.org/blog/2009/02/09/code-generate-custom-soap-faults-for-axis2c/ >> >> >> Thanks >> Dimuthu >> >> >> >> On Wed, Nov 18, 2009 at 3:49 AM, Doug Price <Doug.Price@presagis.com>wrote: >> >>> While I see that this approach allows the creation of user-defined fault >>> types, is it possible to also use it to specify the standard SOAP-ENV:Fault? >>> I see a struct named axiom_soap_fault_t in the distribution, but I can't >>> seem to return it from the axis2_svc_skel_*_on_fault() function because it >>> requires a pointer to the SOAP body to create one. Is there some other way >>> to return a standard SOAP fault from a service? >>> >>> >>> -- >>> Doug Price >>> Research Director | Presagis >>> >>> T. +1 972 943.2433 F. +1 469 467.4564 C. +1 469 867.8399 >>> >>> DISCLAIMER: This e-mail message is for the sole use of the intended >>> recipient(s) and may contain confidential and/or proprietary information. Do >>> not read, copy, or disseminate this message unless you are the addressee. >>> Any unauthorized review, use, disclosure or distribution is strictly >>> prohibited. If you have received this message in error, please contact the >>> sender by reply e-mail and delete the original and any copies from your >>> system. >>> >>> -----Original Message----- >>> >>> From: Amir Mousavizadegan [mailto:amir.mousavizadegan@cox.net] >>> Sent: Tuesday, November 17, 2009 10:29 AM >>> To: Apache AXIS C User List >>> Subject: Re: using faults w/ wsdl2c >>> >>> I did not write the sample codes nor the document, however in order to >>> get it working, you have to change the body of the generated code, or >>> create a replacement function as I did. >>> thx >>> Amir >>> ----- Original Message ----- >>> From: "Doug Price" <Doug.Price@presagis.com> >>> To: "Apache AXIS C User List" <axis-c-user@ws.apache.org> >>> Sent: Tuesday, November 17, 2009 11:05 AM >>> Subject: RE: using faults w/ wsdl2c >>> >>> >>> Just what I was looking for. Thanks so much. >>> >>> A quick follow up question on the code though. Is there a reason that >>> axis2_svc_skel_Division_on_fault() doesn't use the adv_divFault api to >>> create the fault? >>> >>> >>> -- >>> Doug Price >>> Research Director | Presagis >>> >>> T. +1 972 943.2433 F. +1 469 467.4564 C. +1 469 867.8399 >>> >>> DISCLAIMER: This e-mail message is for the sole use of the intended >>> recipient(s) and may contain confidential and/or proprietary information. >>> Do >>> not read, copy, or disseminate this message unless you are the addressee. >>> Any unauthorized review, use, disclosure or distribution is strictly >>> prohibited. If you have received this message in error, please contact >>> the >>> sender by reply e-mail and delete the original and any copies from your >>> system. >>> >>> -----Original Message----- >>> >>> From: Amir Mousavizadegan [mailto:amir.mousavizadegan@cox.net] >>> Sent: Tuesday, November 17, 2009 7:52 AM >>> To: Apache AXIS C User List >>> Subject: Re: using faults w/ wsdl2c >>> >>> Please see attached document >>> ----- Original Message ----- >>> From: "Doug Price" <Doug.Price@presagis.com> >>> To: <axis-c-user@ws.apache.org> >>> Sent: Monday, November 16, 2009 4:47 PM >>> Subject: using faults w/ wsdl2c >>> >>> >>> I created a simple web service w/ Axis2c using wsdl2c on a WSDL file I >>> created in Eclipse. The default functionality of this works fine. >>> However, >>> now I'd like to incorporate faults into my SOAP messages. I created a >>> fault >>> type in my WSDL and wsdl2c creates the wrappers for the fault message, >>> but >>> the service skeleton and client stubs files seem to hard coded to assume >>> no >>> faults are ever sent / received. For example, the client >>> axis2_stub_op_*() >>> function takes my request message type and returns my response message >>> type, >>> but doesn't seem to account for my fault type. Modifying the code, I can >>> see that the fault is received and correctly deserialized, but I'll have >>> to >>> continually hand edit the axis2_stub*.c and my client.c file as I make >>> modifications to my WSDL in order to make this work. >>> >>> The same is true on the service side w/ the axis2_skel*() functions. Am >>> I >>> missing something here, or are faults not supported w/ wsdl2c? >>> >>> -- >>> Doug Price >>> Research Director | Presagis >>> >>> T. +1 972 943.2433 F. +1 469 467.4564 C. +1 469 867.8399 >>> >>> DISCLAIMER: This e-mail message is for the sole use of the intended >>> recipient(s) and may contain confidential and/or proprietary information. >>> Do >>> not read, copy, or disseminate this message unless you are the addressee. >>> Any unauthorized review, use, disclosure or distribution is strictly >>> prohibited. If you have received this message in error, please contact >>> the >>> sender by reply e-mail and delete the original and any copies from your >>> system. >>> >>> >>> >>> >> >> >> -- >> Thanks, >> Dimuthu Gamage >> >> http://www.dimuthu.org >> http://www.wso2.org >> > > -- Samisa Abeysinghe Director, Engineering - WSO2 Inc. http://www.wso2.com/ - "The Open Source SOA Company"
Hi, I also try the REST delete and it is failing. Looks like a bug in the code in trunk. Can you please report this bug in axis2/c jira Thanks Dimuthu On Wed, Nov 25, 2009 at 2:09 AM, Ilia Gilderman <ilia.gilderman@xeround.com>wrote: > Yes, sure I did this > > > ------------------------------ > > *From:* Supun Kamburugamuva [mailto:supun06@gmail.com] > *Sent:* Tuesday, November 24, 2009 10:36 PM > *To:* Apache AXIS C User List > *Subject:* Re: echo_rest and DELETE http_method > > > > Hi, > > Not sure weather you have done this, but AFAIK you need to edit the > services.xml file to make them work. > > Thanks, > Supun. > > On Fri, Nov 20, 2009 at 7:19 PM, Ilia Gilderman < > ilia.gilderman@xeround.com> wrote: > > Hi > > It looks like the DELETE pieces does not work. I tried with > simple_axis2_server and mod_axis2 modules and echo_rest example. When I'm > adding –mDELETE option I got internal servers error (500) from httpd. Is it > known issue? What can be wrong with the sample? > > > > Thanks > > > > *Ilia Gilderman**, VP Product Development > **x**eround* > > *4 Derech Hahoresh St**. > P.O. Box 12621 > **Yehud, 56470 Israel* > *Office: +972-3-5390617 > Mobile: +972-54-4878091* > > ilia.gilderman@xeround.com > > > > > > > -- > Software Engineer, WSO2 Inc > http://wso2.org > supunk.blogspot.com > > -- Thanks, Dimuthu Gamage http://www.dimuthu.org http://www.wso2.org
On Fri, 2009-12-04 at 22:59 +0530, Samisa Abeysinghe wrote:
> You need to enable https in the axis2.xml conf file
>
Ah, thanks one step closer.
I still need to figure out how to see the exact xml that is being sent
and received from the server. I am getting a fault back and I suspect it
is because the WSSE header information is not correct. I should be
sending something like this to the server:
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://www.w3.org/2003/05/soap-envelope"
xmlns:SOAP-ENC="http://www.w3.org/2003/05/soap-encoding"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:c14n="http://www.w3.org/2001/10/xml-exc-c14n#"
xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401..."
xmlns:ds="http://www.w3.org/2000/09/xmldsig#"
xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis..."
xmlns:negdb="http://secure.negativeaddress.research.att.com/"
>
<SOAP-ENV:Header>
<wsse:Security SOAP-ENV:mustUnderstand="true">
<wsse:UsernameToken
wsu:Id="apache"
>
<wsse:Username>apache</wsse:Username>
<wsse:Password Type="http://docs.oasis-open.org/wss...">
password
</wsse:Password>
</wsse:UsernameToken>
</wsse:Security>
</SOAP-ENV:Header>
<SOAP-ENV:Body>
...
While I think I've engaged rampart properly to add the header
information, the debugging log does not include the data sent to the
server.
ASE
I meant to say, Axis2! Samisa... On Fri, Dec 4, 2009 at 11:08 PM, Samisa Abeysinghe <samisa@wso2.com> wrote: > Folks, > I looked at the Jiras after a loooong time and seems that there are > quite a number of them as well as few ones with patches from users. > > May be it is a good time to fire up a new release. Thoughts are > welcome. > > Thanks, > Samisa... > > -- > Samisa Abeysinghe > Director, Engineering - WSO2 Inc. > > http://www.wso2.com/ - "The Open Source SOA Company" > -- Samisa Abeysinghe Director, Engineering - WSO2 Inc. http://www.wso2.com/ - "The Open Source SOA Company"
Dimuthu, Where EXACTLY does one find the latest WSDL2C code? Is it in an build or is it in the Axis2/Java SVN repository? Sam On Thu, Dec 3, 2009 at 10:57 PM, Dimuthu Gamage <dimuthuc@gmail.com> wrote: > Hi, > > If you use the latest axis2 WSDL2C generator code, you don't need to create > soap fault message manually as the generated code provide lot of support in > generating fault message. > > Please have a look at this for the improved API, > http://www.dimuthu.org/blog/2009/02/09/code-generate-custom-soap-faults-for-axis2c/ > > > Thanks > Dimuthu > > > > On Wed, Nov 18, 2009 at 3:49 AM, Doug Price <Doug.Price@presagis.com>wrote: > >> While I see that this approach allows the creation of user-defined fault >> types, is it possible to also use it to specify the standard SOAP-ENV:Fault? >> I see a struct named axiom_soap_fault_t in the distribution, but I can't >> seem to return it from the axis2_svc_skel_*_on_fault() function because it >> requires a pointer to the SOAP body to create one. Is there some other way >> to return a standard SOAP fault from a service? >> >> >> -- >> Doug Price >> Research Director | Presagis >> >> T. +1 972 943.2433 F. +1 469 467.4564 C. +1 469 867.8399 >> >> DISCLAIMER: This e-mail message is for the sole use of the intended >> recipient(s) and may contain confidential and/or proprietary information. Do >> not read, copy, or disseminate this message unless you are the addressee. >> Any unauthorized review, use, disclosure or distribution is strictly >> prohibited. If you have received this message in error, please contact the >> sender by reply e-mail and delete the original and any copies from your >> system. >> >> -----Original Message----- >> >> From: Amir Mousavizadegan [mailto:amir.mousavizadegan@cox.net] >> Sent: Tuesday, November 17, 2009 10:29 AM >> To: Apache AXIS C User List >> Subject: Re: using faults w/ wsdl2c >> >> I did not write the sample codes nor the document, however in order to >> get it working, you have to change the body of the generated code, or >> create a replacement function as I did. >> thx >> Amir >> ----- Original Message ----- >> From: "Doug Price" <Doug.Price@presagis.com> >> To: "Apache AXIS C User List" <axis-c-user@ws.apache.org> >> Sent: Tuesday, November 17, 2009 11:05 AM >> Subject: RE: using faults w/ wsdl2c >> >> >> Just what I was looking for. Thanks so much. >> >> A quick follow up question on the code though. Is there a reason that >> axis2_svc_skel_Division_on_fault() doesn't use the adv_divFault api to >> create the fault? >> >> >> -- >> Doug Price >> Research Director | Presagis >> >> T. +1 972 943.2433 F. +1 469 467.4564 C. +1 469 867.8399 >> >> DISCLAIMER: This e-mail message is for the sole use of the intended >> recipient(s) and may contain confidential and/or proprietary information. >> Do >> not read, copy, or disseminate this message unless you are the addressee. >> Any unauthorized review, use, disclosure or distribution is strictly >> prohibited. If you have received this message in error, please contact the >> sender by reply e-mail and delete the original and any copies from your >> system. >> >> -----Original Message----- >> >> From: Amir Mousavizadegan [mailto:amir.mousavizadegan@cox.net] >> Sent: Tuesday, November 17, 2009 7:52 AM >> To: Apache AXIS C User List >> Subject: Re: using faults w/ wsdl2c >> >> Please see attached document >> ----- Original Message ----- >> From: "Doug Price" <Doug.Price@presagis.com> >> To: <axis-c-user@ws.apache.org> >> Sent: Monday, November 16, 2009 4:47 PM >> Subject: using faults w/ wsdl2c >> >> >> I created a simple web service w/ Axis2c using wsdl2c on a WSDL file I >> created in Eclipse. The default functionality of this works fine. >> However, >> now I'd like to incorporate faults into my SOAP messages. I created a >> fault >> type in my WSDL and wsdl2c creates the wrappers for the fault message, but >> the service skeleton and client stubs files seem to hard coded to assume >> no >> faults are ever sent / received. For example, the client >> axis2_stub_op_*() >> function takes my request message type and returns my response message >> type, >> but doesn't seem to account for my fault type. Modifying the code, I can >> see that the fault is received and correctly deserialized, but I'll have >> to >> continually hand edit the axis2_stub*.c and my client.c file as I make >> modifications to my WSDL in order to make this work. >> >> The same is true on the service side w/ the axis2_skel*() functions. Am I >> missing something here, or are faults not supported w/ wsdl2c? >> >> -- >> Doug Price >> Research Director | Presagis >> >> T. +1 972 943.2433 F. +1 469 467.4564 C. +1 469 867.8399 >> >> DISCLAIMER: This e-mail message is for the sole use of the intended >> recipient(s) and may contain confidential and/or proprietary information. >> Do >> not read, copy, or disseminate this message unless you are the addressee. >> Any unauthorized review, use, disclosure or distribution is strictly >> prohibited. If you have received this message in error, please contact the >> sender by reply e-mail and delete the original and any copies from your >> system. >> >> >> >> > > > -- > Thanks, > Dimuthu Gamage > > http://www.dimuthu.org > http://www.wso2.org >
Folks,
I looked at the Jiras after a loooong time and seems that there are
quite a number of them as well as few ones with patches from users.
May be it is a good time to fire up a new release. Thoughts are welcome.
Thanks,
Samisa...
--
Samisa Abeysinghe
Director, Engineering - WSO2 Inc.
http://www.wso2.com/ - "The Open Source SOA Company"
On Fri, Dec 4, 2009 at 10:53 PM, Adam Edgar <aedgar@research.att.com> wrote: > I think I've managed to get some of it working but can't tell if the > proper headers are being generated. Is there a way to dump the traffic > being sent to the server? > > Also when I try : > > url="https://localhost:8443/axis2/services/NegativeAddressSecureService"; > stub = axis2_stub_create_NegativeAddressSecureService(env,home,url); > > I get : > > op_client.c(949) Cannot infer transport > op_client.c(954) End:axis2_op_client_infer_transport > op_client.c(407) Op client execute failed. Cannot find transport out. > > > Is there something I need to do to enable https as it doesn't fail for > http? > You need to enable https in the axis2.xml conf file Samisa... > ASE > > > On Fri, 2009-12-04 at 22:42 +0530, Samisa Abeysinghe wrote: > > Rampart is an independent project. Hence, the generated code does not > > have Rampart specific stuff. > > > > > > For Rampart stuff, you have to engage the module and provide the > > security policies etc at client level programatically. > > > > > > Samisa... > > > > On Fri, Dec 4, 2009 at 10:39 PM, Adam Edgar <aedgar@research.att.com> > > wrote: > > Is there a good start to finish tutorial for rampart/c for > > creating a > > client starting with a WSDL file? Basically, right no I have > > written a > > WSDL and used wsdl2c to generate the source for the client but > > it does > > not seem to have any rampart code in it. If I run the server > > without > > WSSE it works but not when I try to secure it. I've managed to > > find > > documentation scattered about but nothing comprehensive. > > > > All I'm trying to do is use UserName/Password authentication > > across > > https. This is probably real simple but I can't seem to find > > the last > > little bit of info to get it done. > > > > ASE > > > > > > > > > > -- > > Samisa Abeysinghe > > Director, Engineering - WSO2 Inc. > > > > http://www.wso2.com/ - "The Open Source SOA Company" > > > > > -- Samisa Abeysinghe Director, Engineering - WSO2 Inc. http://www.wso2.com/ - "The Open Source SOA Company"
I think I've managed to get some of it working but can't tell if the proper headers are being generated. Is there a way to dump the traffic being sent to the server? Also when I try : url="https://localhost:8443/axis2/services/NegativeAddressSecureService"; stub = axis2_stub_create_NegativeAddressSecureService(env,home,url); I get : op_client.c(949) Cannot infer transport op_client.c(954) End:axis2_op_client_infer_transport op_client.c(407) Op client execute failed. Cannot find transport out. Is there something I need to do to enable https as it doesn't fail for http? ASE On Fri, 2009-12-04 at 22:42 +0530, Samisa Abeysinghe wrote: > Rampart is an independent project. Hence, the generated code does not > have Rampart specific stuff. > > > For Rampart stuff, you have to engage the module and provide the > security policies etc at client level programatically. > > > Samisa... > > On Fri, Dec 4, 2009 at 10:39 PM, Adam Edgar <aedgar@research.att.com> > wrote: > Is there a good start to finish tutorial for rampart/c for > creating a > client starting with a WSDL file? Basically, right no I have > written a > WSDL and used wsdl2c to generate the source for the client but > it does > not seem to have any rampart code in it. If I run the server > without > WSSE it works but not when I try to secure it. I've managed to > find > documentation scattered about but nothing comprehensive. > > All I'm trying to do is use UserName/Password authentication > across > https. This is probably real simple but I can't seem to find > the last > little bit of info to get it done. > > ASE > > > > > -- > Samisa Abeysinghe > Director, Engineering - WSO2 Inc. > > http://www.wso2.com/ - "The Open Source SOA Company" >
AFAICT, _t has nothing to do with the problem you are facing. Samisa... On Wed, Oct 28, 2009 at 5:19 AM, <gsherwood@att.net> wrote: > I have set up two services which (for now) are identical except for their > names, TestCases and TestCases_t. The choice of the suffix _t is historical > and has nothing to do with type names. libTestCases.so and libTestCases_t.so > are placed in their respective directories: > /usr/local/www/64.232.245.115/axis2c/services/TestCases and > /usr/local/www/64.232.245.115/axis2c/services/TestCases_t > However, log entries indicate the DLL path for libTestCases_t.so is not > getting set correctly. Relevant entries include the following. > [Tue Oct 27 19:22:33 2009] [debug] svc_builder.c(318) DLL path is : > /usr/local/www/64.232.245.115/axis2c/services/TestCases/libTestCases.so > [Tue Oct 27 19:22:33 2009] [debug] om_element.c(1114) There are no child > elements for the node > [Tue Oct 27 19:22:33 2009] [debug] svc_builder.c(318) DLL path is : > /usr/local/www/64.232.245.115/axis2c/services/TestCases_t/libTestCases.so > [Tue Oct 27 19:22:33 2009] [debug] om_element.c(1114) There are no child > elements for the node > ... > [Tue Oct 27 19:22:33 2009] [error] class_loader.c(162) Loading shared > library /usr/local/www/ > 64.232.245.115/axis2c/services/TestCases_t/libTestCases.so Failed. > DLERROR IS /usr/local/www/ > 64.232.245.115/axis2c/services/TestCases_t/libTestCases.so: cannot open > shared object file: No such file or directory > If I depart from the usual naming convention (i.e. libTestCases_t.so for > TestCases_t), and use the name in the DLL path instead (libTestCases.so), > then the service works. > Can anyone help with answers to these questions? > 1. Is this behavior (dropping the _t suffix) a bug or a feature? > 2. Is setting the name to the DLL path indicated in the log a legitimate > workaround? > 3. Am I likely to encounter future trouble with a service name ending in > _t? > Thanks, > George Sherwood > Testcover.com > > > -- Samisa Abeysinghe Director, Engineering - WSO2 Inc. http://www.wso2.com/ - "The Open Source SOA Company"
Rampart is an independent project. Hence, the generated code does not have Rampart specific stuff. For Rampart stuff, you have to engage the module and provide the security policies etc at client level programatically. Samisa... On Fri, Dec 4, 2009 at 10:39 PM, Adam Edgar <aedgar@research.att.com> wrote: > Is there a good start to finish tutorial for rampart/c for creating a > client starting with a WSDL file? Basically, right no I have written a > WSDL and used wsdl2c to generate the source for the client but it does > not seem to have any rampart code in it. If I run the server without > WSSE it works but not when I try to secure it. I've managed to find > documentation scattered about but nothing comprehensive. > > All I'm trying to do is use UserName/Password authentication across > https. This is probably real simple but I can't seem to find the last > little bit of info to get it done. > > ASE > > -- Samisa Abeysinghe Director, Engineering - WSO2 Inc. http://www.wso2.com/ - "The Open Source SOA Company"
Is there a good start to finish tutorial for rampart/c for creating a client starting with a WSDL file? Basically, right no I have written a WSDL and used wsdl2c to generate the source for the client but it does not seem to have any rampart code in it. If I run the server without WSSE it works but not when I try to secure it. I've managed to find documentation scattered about but nothing comprehensive. All I'm trying to do is use UserName/Password authentication across https. This is probably real simple but I can't seem to find the last little bit of info to get it done. ASE
Hi, Unfortunately with the current setup there is no proper way to solve that conflict. One possible solution is to provide a parameter to set the prefix as you suggested, but there is no such thing implemented. Can you please create a jira to implement this option? Thanks Dimuthu On Sat, Oct 31, 2009 at 4:47 PM, Andrew Grissom <andrew_grissom@yahoo.com>wrote: > I have a project where I have multiple WSDLs that contain a types with the > same name, but with different definitions, and methods with the same name > but different parameters. When I generate the code using: > > WSDL2C -uri MyWSDL1.wsdl -d adb -u -o $OUTPUT_DIR > > Everything is fine if I create separate executables for accessing each > WSDL. However, if I compile them together I get numerous duplicate symbols. > > If there a way in WSDLC to have it generate something like: > > adb_<prefix>_MyType or adb_<prefix>_MyMethod_create > > instead of: > > adb_MyType or adb_MyMethod_create > > I attempted to use the -p option when starting WSDL2C but it does not > appear to do anything. > > Am I missing something? > > -- Thanks, Dimuthu Gamage http://www.dimuthu.org http://www.wso2.org
Hi, If you use the latest axis2 WSDL2C generator code, you don't need to create soap fault message manually as the generated code provide lot of support in generating fault message. Please have a look at this for the improved API, http://www.dimuthu.org/blog/2009/02/09/code-generate-custom-soap-faults-for-axis2c/ Thanks Dimuthu On Wed, Nov 18, 2009 at 3:49 AM, Doug Price <Doug.Price@presagis.com> wrote: > While I see that this approach allows the creation of user-defined fault > types, is it possible to also use it to specify the standard SOAP-ENV:Fault? > I see a struct named axiom_soap_fault_t in the distribution, but I can't > seem to return it from the axis2_svc_skel_*_on_fault() function because it > requires a pointer to the SOAP body to create one. Is there some other way > to return a standard SOAP fault from a service? > > > -- > Doug Price > Research Director | Presagis > > T. +1 972 943.2433 F. +1 469 467.4564 C. +1 469 867.8399 > > DISCLAIMER: This e-mail message is for the sole use of the intended > recipient(s) and may contain confidential and/or proprietary information. Do > not read, copy, or disseminate this message unless you are the addressee. > Any unauthorized review, use, disclosure or distribution is strictly > prohibited. If you have received this message in error, please contact the > sender by reply e-mail and delete the original and any copies from your > system. > > -----Original Message----- > > From: Amir Mousavizadegan [mailto:amir.mousavizadegan@cox.net] > Sent: Tuesday, November 17, 2009 10:29 AM > To: Apache AXIS C User List > Subject: Re: using faults w/ wsdl2c > > I did not write the sample codes nor the document, however in order to > get it working, you have to change the body of the generated code, or > create a replacement function as I did. > thx > Amir > ----- Original Message ----- > From: "Doug Price" <Doug.Price@presagis.com> > To: "Apache AXIS C User List" <axis-c-user@ws.apache.org> > Sent: Tuesday, November 17, 2009 11:05 AM > Subject: RE: using faults w/ wsdl2c > > > Just what I was looking for. Thanks so much. > > A quick follow up question on the code though. Is there a reason that > axis2_svc_skel_Division_on_fault() doesn't use the adv_divFault api to > create the fault? > > > -- > Doug Price > Research Director | Presagis > > T. +1 972 943.2433 F. +1 469 467.4564 C. +1 469 867.8399 > > DISCLAIMER: This e-mail message is for the sole use of the intended > recipient(s) and may contain confidential and/or proprietary information. > Do > not read, copy, or disseminate this message unless you are the addressee. > Any unauthorized review, use, disclosure or distribution is strictly > prohibited. If you have received this message in error, please contact the > sender by reply e-mail and delete the original and any copies from your > system. > > -----Original Message----- > > From: Amir Mousavizadegan [mailto:amir.mousavizadegan@cox.net] > Sent: Tuesday, November 17, 2009 7:52 AM > To: Apache AXIS C User List > Subject: Re: using faults w/ wsdl2c > > Please see attached document > ----- Original Message ----- > From: "Doug Price" <Doug.Price@presagis.com> > To: <axis-c-user@ws.apache.org> > Sent: Monday, November 16, 2009 4:47 PM > Subject: using faults w/ wsdl2c > > > I created a simple web service w/ Axis2c using wsdl2c on a WSDL file I > created in Eclipse. The default functionality of this works fine. > However, > now I'd like to incorporate faults into my SOAP messages. I created a > fault > type in my WSDL and wsdl2c creates the wrappers for the fault message, but > the service skeleton and client stubs files seem to hard coded to assume no > faults are ever sent / received. For example, the client axis2_stub_op_*() > function takes my request message type and returns my response message > type, > but doesn't seem to account for my fault type. Modifying the code, I can > see that the fault is received and correctly deserialized, but I'll have to > continually hand edit the axis2_stub*.c and my client.c file as I make > modifications to my WSDL in order to make this work. > > The same is true on the service side w/ the axis2_skel*() functions. Am I > missing something here, or are faults not supported w/ wsdl2c? > > -- > Doug Price > Research Director | Presagis > > T. +1 972 943.2433 F. +1 469 467.4564 C. +1 469 867.8399 > > DISCLAIMER: This e-mail message is for the sole use of the intended > recipient(s) and may contain confidential and/or proprietary information. > Do > not read, copy, or disseminate this message unless you are the addressee. > Any unauthorized review, use, disclosure or distribution is strictly > prohibited. If you have received this message in error, please contact the > sender by reply e-mail and delete the original and any copies from your > system. > > > > -- Thanks, Dimuthu Gamage http://www.dimuthu.org http://www.wso2.org
Hi: I have an Axis2c client program, which can connect to a single HTTPS web service without any problem. A certificate file (PEM) is stored for the HTTPS server. Now multiple HTTPS web services need to be supported, I think a keystore file should be prepared, however don't know how to do that. Can anybody help? Thanks. Steven
You can create a Jira. If you can find the problem please attach a patch as
well.
Thanks,
Supun..
On Wed, Nov 25, 2009 at 2:34 AM, Jose M Medina V <
jose_medina@wesamconsulting.com> wrote:
> What is the procedure to get this work?
>
> Regards,
>
> On Nov 24, 2009, at 4:09 PM, Supun Kamburugamuva wrote:
>
> I think the way you get endpoint_ref is correct. But I'm not sure from your
> comment weather endpoint_ref is NULL or a filed inside endpoint_ref is NULL.
> In any case it should be a bug.
>
> Thanks,
> Supun..
>
> On Wed, Oct 21, 2009 at 11:55 PM, Jose M Medina V <
> jose_medina@wesamconsulting.com> wrote:
>
>> Hi, I try to get the target endpoint address in a services in Axis2c, I
>> put the following code in the invoke function in the skeleton library:
>>
>> axis2_endpoint_ref_t *endpoint_ref = NULL;
>> const axis2_char_t *address = NULL;
>> .
>> .
>> .
>> endpoint_ref = axis2_msg_ctx_get_to(msg_ctx, env);
>> if(endpoint_ref)
>> {
>> AXIS2_LOG_DEBUG(env->log, AXIS2_LOG_SI, "%s%s
>> if(endpoint_ref)",pdesWebServ->nombre_web,nombreFuncion);
>> address = axis2_endpoint_ref_get_address(endpoint_ref, env);
>> if (address)
>> {
>> AXIS2_LOG_DEBUG(env->log, AXIS2_LOG_SI, "%s%s if
>> (address)",pdesWebServ->nombre_web,nombreFuncion);
>> }
>> }
>>
>> When I run this, I got NULL in endpoint_ref variable, so I don’t know it
>> was something wrong with this code.
>> It is the correct way to get the endpoint address or exists another way to
>> get that info.
>>
>> Thank in advance.
>>
>> ------------------------------------------------------------
>> José M. Medina V.
>> Wesam Consulting
>> jose_medina@wesamconsulting.com
>> Mobile: +58(416)613-3302 +58(414)019-0580
>> Ofc: +58(212)959-4155 Ext. 204
>> BB pin: 31E562BF
>> Caracas - Venezuela
>>
>>
>>
>>
>>
>>
>>
>
>
> --
> Software Engineer, WSO2 Inc
> http://wso2.org
> supunk.blogspot.com
>
>
>
> ------------------------------------------------------------
> José M. Medina V.
> Wesam Consulting
> jose_medina@wesamconsulting.com
> Mobile: +58(416)613-3302 +58(414)019-0580
> Ofc: +58(212)959-4155 Ext. 204
> BB pin: 31E562BF
> Caracas - Venezuela
>
>
>
>
>
>
>
--
Software Engineer, WSO2 Inc
http://wso2.org
supunk.blogspot.com
What is the procedure to get this work?
Regards,
On Nov 24, 2009, at 4:09 PM, Supun Kamburugamuva wrote:
> I think the way you get endpoint_ref is correct. But I'm not sure from your comment weather
endpoint_ref is NULL or a filed inside endpoint_ref is NULL. In any case it should be a bug.
>
> Thanks,
> Supun..
>
> On Wed, Oct 21, 2009 at 11:55 PM, Jose M Medina V <jose_medina@wesamconsulting.com>
wrote:
> Hi, I try to get the target endpoint address in a services in Axis2c, I put the following
code in the invoke function in the skeleton library:
>
> axis2_endpoint_ref_t *endpoint_ref = NULL;
> const axis2_char_t *address = NULL;
> .
> .
> .
> endpoint_ref = axis2_msg_ctx_get_to(msg_ctx, env);
> if(endpoint_ref)
> {
> AXIS2_LOG_DEBUG(env->log, AXIS2_LOG_SI, "%s%s if(endpoint_ref)",pdesWebServ->nombre_web,nombreFuncion);
> address = axis2_endpoint_ref_get_address(endpoint_ref, env);
> if (address)
> {
> AXIS2_LOG_DEBUG(env->log, AXIS2_LOG_SI, "%s%s if (address)",pdesWebServ->nombre_web,nombreFuncion);
> }
> }
>
> When I run this, I got NULL in endpoint_ref variable, so I don’t know it was something
wrong with this code.
> It is the correct way to get the endpoint address or exists another way to get that info.
>
> Thank in advance.
>
> ------------------------------------------------------------
> José M. Medina V.
> Wesam Consulting
> jose_medina@wesamconsulting.com
> Mobile: +58(416)613-3302 +58(414)019-0580
> Ofc: +58(212)959-4155 Ext. 204
> BB pin: 31E562BF
> Caracas - Venezuela
>
>
>
>
>
>
>
>
>
> --
> Software Engineer, WSO2 Inc
> http://wso2.org
> supunk.blogspot.com
>
>
------------------------------------------------------------
José M. Medina V.
Wesam Consulting
jose_medina@wesamconsulting.com
Mobile: +58(416)613-3302 +58(414)019-0580
Ofc: +58(212)959-4155 Ext. 204
BB pin: 31E562BF
Caracas - Venezuela
I think the way you get endpoint_ref is correct. But I'm not sure from your
comment weather endpoint_ref is NULL or a filed inside endpoint_ref is NULL.
In any case it should be a bug.
Thanks,
Supun..
On Wed, Oct 21, 2009 at 11:55 PM, Jose M Medina V <
jose_medina@wesamconsulting.com> wrote:
> Hi, I try to get the target endpoint address in a services in Axis2c, I put
> the following code in the invoke function in the skeleton library:
>
> axis2_endpoint_ref_t *endpoint_ref = NULL;
> const axis2_char_t *address = NULL;
> .
> .
> .
> endpoint_ref = axis2_msg_ctx_get_to(msg_ctx, env);
> if(endpoint_ref)
> {
> AXIS2_LOG_DEBUG(env->log, AXIS2_LOG_SI, "%s%s
> if(endpoint_ref)",pdesWebServ->nombre_web,nombreFuncion);
> address = axis2_endpoint_ref_get_address(endpoint_ref, env);
> if (address)
> {
> AXIS2_LOG_DEBUG(env->log, AXIS2_LOG_SI, "%s%s if
> (address)",pdesWebServ->nombre_web,nombreFuncion);
> }
> }
>
> When I run this, I got NULL in endpoint_ref variable, so I don’t know it
> was something wrong with this code.
> It is the correct way to get the endpoint address or exists another way to
> get that info.
>
> Thank in advance.
>
> ------------------------------------------------------------
> José M. Medina V.
> Wesam Consulting
> jose_medina@wesamconsulting.com
> Mobile: +58(416)613-3302 +58(414)019-0580
> Ofc: +58(212)959-4155 Ext. 204
> BB pin: 31E562BF
> Caracas - Venezuela
>
>
>
>
>
>
>
--
Software Engineer, WSO2 Inc
http://wso2.org
supunk.blogspot.com
Yes, sure I did this ________________________________ From: Supun Kamburugamuva [mailto:supun06@gmail.com] Sent: Tuesday, November 24, 2009 10:36 PM To: Apache AXIS C User List Subject: Re: echo_rest and DELETE http_method Hi, Not sure weather you have done this, but AFAIK you need to edit the services.xml file to make them work. Thanks, Supun. On Fri, Nov 20, 2009 at 7:19 PM, Ilia Gilderman <ilia.gilderman@xeround.com<mailto:ilia.gilderman@xeround.com>> wrote: Hi It looks like the DELETE pieces does not work. I tried with simple_axis2_server and mod_axis2 modules and echo_rest example. When I'm adding -mDELETE option I got internal servers error (500) from httpd. Is it known issue? What can be wrong with the sample? Thanks Ilia Gilderman, VP Product Development xeround 4 Derech Hahoresh St. P.O. Box 12621 Yehud, 56470 Israel Office: +972-3-5390617 Mobile: +972-54-4878091 ilia.gilderman@xeround.com<mailto:ilia.gilderman@xeround.com> -- Software Engineer, WSO2 Inc http://wso2.org supunk.blogspot.com<http://supunk.blogspot.com>
Hi, Not sure weather you have done this, but AFAIK you need to edit the services.xml file to make them work. Thanks, Supun. On Fri, Nov 20, 2009 at 7:19 PM, Ilia Gilderman <ilia.gilderman@xeround.com>wrote: > Hi > > It looks like the DELETE pieces does not work. I tried with > simple_axis2_server and mod_axis2 modules and echo_rest example. When I'm > adding –mDELETE option I got internal servers error (500) from httpd. Is it > known issue? What can be wrong with the sample? > > > > Thanks > > > > *Ilia Gilderman**, VP Product Development** > **x**eround*** > > *4 Derech Hahoresh St**.** > P.O. Box 12621 > **Yehud, 56470 Israel* > *Office: +972-3-5390617** > Mobile: +972-54-4878091* > > ilia.gilderman@xeround.com > > > -- Software Engineer, WSO2 Inc http://wso2.org supunk.blogspot.com
Hi It looks like the DELETE pieces does not work. I tried with simple_axis2_server and mod_axis2 modules and echo_rest example. When I'm adding -mDELETE option I got internal servers error (500) from httpd. Is it known issue? What can be wrong with the sample? Thanks Ilia Gilderman, VP Product Development xeround 4 Derech Hahoresh St. P.O. Box 12621 Yehud, 56470 Israel Office: +972-3-5390617 Mobile: +972-54-4878091 ilia.gilderman@xeround.com<mailto:ilia.gilderman@xeround.com>
I encountered timeouts using an Axis2/C client and a service using the Axis2/C server module. Here's what I found to solve the problem, FYI. The client error log indicates the timeout: [Thu Nov 19 18:30:56 2009] [debug] http_client.c(571) http client , response timed out [Thu Nov 19 18:30:56 2009] [error] http_client.c(574) Response timed out [Thu Nov 19 18:30:56 2009] [error] http_sender.c(1381) status_code < 0 [Thu Nov 19 18:30:56 2009] [error] engine.c(179) Transport sender invoke failed [Thu Nov 19 18:30:56 2009] [error] TestCases.c(239) Stub invoke FAILED: Error code: 92 :: Response timed out The default timeout is 60000 ms (1 minute) as given in axis2_http_transport.h To increase the timeout to the required value of 300 seconds (300000 ms), I set the option in the client as follows. axis2_options_set_timeout_in_milli_seconds(options, env, 300000); Responses taking more than 2 minutes are now returning properly. George -------------- Forwarded Message: -------------- From: Sam Carleton <scarleton@miltonstreet.com> To: Apache AXIS C User List <axis-c-user@ws.apache.org> Subject: Re: [ot] adjusting timeouts Date: Sun, 15 Nov 2009 22:29:04 +0000 George, Actually, after a bit more investigation I discovered the error was between the keyboard and chair... The .Net client is setting up the binding at runtime... I discovered that that after the .Net client set SendTimeout to 10 minutes, it set it to 25 seconds. Opps! Sam On Sun, Nov 15, 2009 at 4:01 PM, <gsherwood@att.net> wrote: I too am interested in how to set the timeout for the Axis2/C module. Rarely my application will need up to 300 seconds (the Apache httpd default). But I have not tried that yet. Thanks, George -------------- Original message from Sam Carleton <scarleton@miltonstreet.com>: -------------- My Axis2/C code is being used by a .Net client and being hosted via Apache 2.2 and mod_axis2. I have set the SendTimeout on the .Net binding to 10 minutes but things are still timing out in about 30 seconds. I am wondering if anyone in this forum has run into this problem and has any suggestions on setting on either apache or the .net side to extend the timeout.
Looking the message, It looks ok to me.When a soap12 message is sent, it should contain the content type application/soap+xml and for a soap11 message, it should be text/xml. There is no issue with axis2/c inter operating with .net. Regards Nandika On Wed, Nov 4, 2009 at 8:49 PM, Dimitri Pararas <dpararas@schedsys.com>wrote: > Damitha Kumarage wrote: > >> Dimitri Pararas wrote: >> >>> I seem to be having some difficulty creating the proper headers for my >>> request using Axis2/c. I am creating a simple request using the hello >>> client as a base. When I send my request to the simple server included with >>> the axis2/c (after adding a dumb service) the request works properly. When >>> I send it to the actual server I receive this error "Transport identified >>> SOAP version does not match with SOAP message version" (#195) the header >>> created looks like this >>> POST /foobar/services/FoobarService HTTP/1.1 >>> User-Agent: Axis2C/1.6.0 >>> Content-Length: 420 >>> Content-Type: application/soap+xml;charset=UTF-8 >>> Host: mercury:21083 >>> >>> <soapenv:Envelope xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope"><soapenv:Body><getTaskValidity><acNum>0001</acNum><layoverDate>2009-11-1</layoverDate><newStation>BOS</newStation><origStation>LHR</origStation><arrivalDateTime>2009-11-1 >>> 20:00</arrivalDateTime><callerID> >>> POST /Foobar/services/foobarService HTTP/1.1 >>> User-Agent: Axis2C/1.6.0 >>> Content-Length: 420 >>> Content-Type: application/soap+xml;charset=UTF-8 >>> >> I think you have done a mistake here when copying the soap message to this >> mail message by copying the http headers again at the end. Are you sure your >> soap message have no mistakes. >> I guess your actual service is a dot net service >> >> thanks, >> Damitha >> >>> >>> I am using the axis2_svc_client_send_receive to send this request, and I >>> have not been able to figure out what the problem is and how to manipulate >>> the header even if I did. Thanks >>> Dimitri >>> >>> >>> >> >> I used a TCP sniffer to grab the response, I didn't know what might be > important so I pasted it all. Looking at it again, it seems like maybe I > pasted a request and inadvertently included the http headers from the second > request also. When you say "I guess your actual service is a dot net > service" do you mean a dot net implementation of SOAP or something totally > different? I am fairly certain that it should be a soap service, does Axis > not work with dot net SOAP? > Dimitri > -- http://nandikajayawardana.blogspot.com/ WSO2 Inc: http://www.wso2.com
While I see that this approach allows the creation of user-defined fault types, is it possible to also use it to specify the standard SOAP-ENV:Fault? I see a struct named axiom_soap_fault_t in the distribution, but I can't seem to return it from the axis2_svc_skel_*_on_fault() function because it requires a pointer to the SOAP body to create one. Is there some other way to return a standard SOAP fault from a service? -- Doug Price Research Director | Presagis T. +1 972 943.2433 F. +1 469 467.4564 C. +1 469 867.8399 DISCLAIMER: This e-mail message is for the sole use of the intended recipient(s) and may contain confidential and/or proprietary information. Do not read, copy, or disseminate this message unless you are the addressee. Any unauthorized review, use, disclosure or distribution is strictly prohibited. If you have received this message in error, please contact the sender by reply e-mail and delete the original and any copies from your system. -----Original Message----- From: Amir Mousavizadegan [mailto:amir.mousavizadegan@cox.net] Sent: Tuesday, November 17, 2009 10:29 AM To: Apache AXIS C User List Subject: Re: using faults w/ wsdl2c I did not write the sample codes nor the document, however in order to get it working, you have to change the body of the generated code, or create a replacement function as I did. thx Amir ----- Original Message ----- From: "Doug Price" <Doug.Price@presagis.com> To: "Apache AXIS C User List" <axis-c-user@ws.apache.org> Sent: Tuesday, November 17, 2009 11:05 AM Subject: RE: using faults w/ wsdl2c Just what I was looking for. Thanks so much. A quick follow up question on the code though. Is there a reason that axis2_svc_skel_Division_on_fault() doesn't use the adv_divFault api to create the fault? -- Doug Price Research Director | Presagis T. +1 972 943.2433 F. +1 469 467.4564 C. +1 469 867.8399 DISCLAIMER: This e-mail message is for the sole use of the intended recipient(s) and may contain confidential and/or proprietary information. Do not read, copy, or disseminate this message unless you are the addressee. Any unauthorized review, use, disclosure or distribution is strictly prohibited. If you have received this message in error, please contact the sender by reply e-mail and delete the original and any copies from your system. -----Original Message----- From: Amir Mousavizadegan [mailto:amir.mousavizadegan@cox.net] Sent: Tuesday, November 17, 2009 7:52 AM To: Apache AXIS C User List Subject: Re: using faults w/ wsdl2c Please see attached document ----- Original Message ----- From: "Doug Price" <Doug.Price@presagis.com> To: <axis-c-user@ws.apache.org> Sent: Monday, November 16, 2009 4:47 PM Subject: using faults w/ wsdl2c I created a simple web service w/ Axis2c using wsdl2c on a WSDL file I created in Eclipse. The default functionality of this works fine. However, now I'd like to incorporate faults into my SOAP messages. I created a fault type in my WSDL and wsdl2c creates the wrappers for the fault message, but the service skeleton and client stubs files seem to hard coded to assume no faults are ever sent / received. For example, the client axis2_stub_op_*() function takes my request message type and returns my response message type, but doesn't seem to account for my fault type. Modifying the code, I can see that the fault is received and correctly deserialized, but I'll have to continually hand edit the axis2_stub*.c and my client.c file as I make modifications to my WSDL in order to make this work. The same is true on the service side w/ the axis2_skel*() functions. Am I missing something here, or are faults not supported w/ wsdl2c? -- Doug Price Research Director | Presagis T. +1 972 943.2433 F. +1 469 467.4564 C. +1 469 867.8399 DISCLAIMER: This e-mail message is for the sole use of the intended recipient(s) and may contain confidential and/or proprietary information. Do not read, copy, or disseminate this message unless you are the addressee. Any unauthorized review, use, disclosure or distribution is strictly prohibited. If you have received this message in error, please contact the sender by reply e-mail and delete the original and any copies from your system.
I did not write the sample codes nor the document, however in order to get it working, you have to change the body of the generated code, or create a replacement function as I did. thx Amir ----- Original Message ----- From: "Doug Price" <Doug.Price@presagis.com> To: "Apache AXIS C User List" <axis-c-user@ws.apache.org> Sent: Tuesday, November 17, 2009 11:05 AM Subject: RE: using faults w/ wsdl2c Just what I was looking for. Thanks so much. A quick follow up question on the code though. Is there a reason that axis2_svc_skel_Division_on_fault() doesn't use the adv_divFault api to create the fault? -- Doug Price Research Director | Presagis T. +1 972 943.2433 F. +1 469 467.4564 C. +1 469 867.8399 DISCLAIMER: This e-mail message is for the sole use of the intended recipient(s) and may contain confidential and/or proprietary information. Do not read, copy, or disseminate this message unless you are the addressee. Any unauthorized review, use, disclosure or distribution is strictly prohibited. If you have received this message in error, please contact the sender by reply e-mail and delete the original and any copies from your system. -----Original Message----- From: Amir Mousavizadegan [mailto:amir.mousavizadegan@cox.net] Sent: Tuesday, November 17, 2009 7:52 AM To: Apache AXIS C User List Subject: Re: using faults w/ wsdl2c Please see attached document ----- Original Message ----- From: "Doug Price" <Doug.Price@presagis.com> To: <axis-c-user@ws.apache.org> Sent: Monday, November 16, 2009 4:47 PM Subject: using faults w/ wsdl2c I created a simple web service w/ Axis2c using wsdl2c on a WSDL file I created in Eclipse. The default functionality of this works fine. However, now I'd like to incorporate faults into my SOAP messages. I created a fault type in my WSDL and wsdl2c creates the wrappers for the fault message, but the service skeleton and client stubs files seem to hard coded to assume no faults are ever sent / received. For example, the client axis2_stub_op_*() function takes my request message type and returns my response message type, but doesn't seem to account for my fault type. Modifying the code, I can see that the fault is received and correctly deserialized, but I'll have to continually hand edit the axis2_stub*.c and my client.c file as I make modifications to my WSDL in order to make this work. The same is true on the service side w/ the axis2_skel*() functions. Am I missing something here, or are faults not supported w/ wsdl2c? -- Doug Price Research Director | Presagis T. +1 972 943.2433 F. +1 469 467.4564 C. +1 469 867.8399 DISCLAIMER: This e-mail message is for the sole use of the intended recipient(s) and may contain confidential and/or proprietary information. Do not read, copy, or disseminate this message unless you are the addressee. Any unauthorized review, use, disclosure or distribution is strictly prohibited. If you have received this message in error, please contact the sender by reply e-mail and delete the original and any copies from your system.
Just what I was looking for. Thanks so much. A quick follow up question on the code though. Is there a reason that axis2_svc_skel_Division_on_fault() doesn't use the adv_divFault api to create the fault? -- Doug Price Research Director | Presagis T. +1 972 943.2433 F. +1 469 467.4564 C. +1 469 867.8399 DISCLAIMER: This e-mail message is for the sole use of the intended recipient(s) and may contain confidential and/or proprietary information. Do not read, copy, or disseminate this message unless you are the addressee. Any unauthorized review, use, disclosure or distribution is strictly prohibited. If you have received this message in error, please contact the sender by reply e-mail and delete the original and any copies from your system. -----Original Message----- From: Amir Mousavizadegan [mailto:amir.mousavizadegan@cox.net] Sent: Tuesday, November 17, 2009 7:52 AM To: Apache AXIS C User List Subject: Re: using faults w/ wsdl2c Please see attached document ----- Original Message ----- From: "Doug Price" <Doug.Price@presagis.com> To: <axis-c-user@ws.apache.org> Sent: Monday, November 16, 2009 4:47 PM Subject: using faults w/ wsdl2c I created a simple web service w/ Axis2c using wsdl2c on a WSDL file I created in Eclipse. The default functionality of this works fine. However, now I'd like to incorporate faults into my SOAP messages. I created a fault type in my WSDL and wsdl2c creates the wrappers for the fault message, but the service skeleton and client stubs files seem to hard coded to assume no faults are ever sent / received. For example, the client axis2_stub_op_*() function takes my request message type and returns my response message type, but doesn't seem to account for my fault type. Modifying the code, I can see that the fault is received and correctly deserialized, but I'll have to continually hand edit the axis2_stub*.c and my client.c file as I make modifications to my WSDL in order to make this work. The same is true on the service side w/ the axis2_skel*() functions. Am I missing something here, or are faults not supported w/ wsdl2c? -- Doug Price Research Director | Presagis T. +1 972 943.2433 F. +1 469 467.4564 C. +1 469 867.8399 DISCLAIMER: This e-mail message is for the sole use of the intended recipient(s) and may contain confidential and/or proprietary information. Do not read, copy, or disseminate this message unless you are the addressee. Any unauthorized review, use, disclosure or distribution is strictly prohibited. If you have received this message in error, please contact the sender by reply e-mail and delete the original and any copies from your system.
Please see attached document ----- Original Message ----- From: "Doug Price" <Doug.Price@presagis.com> To: <axis-c-user@ws.apache.org> Sent: Monday, November 16, 2009 4:47 PM Subject: using faults w/ wsdl2c I created a simple web service w/ Axis2c using wsdl2c on a WSDL file I created in Eclipse. The default functionality of this works fine. However, now I'd like to incorporate faults into my SOAP messages. I created a fault type in my WSDL and wsdl2c creates the wrappers for the fault message, but the service skeleton and client stubs files seem to hard coded to assume no faults are ever sent / received. For example, the client axis2_stub_op_*() function takes my request message type and returns my response message type, but doesn't seem to account for my fault type. Modifying the code, I can see that the fault is received and correctly deserialized, but I'll have to continually hand edit the axis2_stub*.c and my client.c file as I make modifications to my WSDL in order to make this work. The same is true on the service side w/ the axis2_skel*() functions. Am I missing something here, or are faults not supported w/ wsdl2c? -- Doug Price Research Director | Presagis T. +1 972 943.2433 F. +1 469 467.4564 C. +1 469 867.8399 DISCLAIMER: This e-mail message is for the sole use of the intended recipient(s) and may contain confidential and/or proprietary information. Do not read, copy, or disseminate this message unless you are the addressee. Any unauthorized review, use, disclosure or distribution is strictly prohibited. If you have received this message in error, please contact the sender by reply e-mail and delete the original and any copies from your system.
I created a simple web service w/ Axis2c using wsdl2c on a WSDL file I created in Eclipse. The default functionality of this works fine. However, now I'd like to incorporate faults into my SOAP messages. I created a fault type in my WSDL and wsdl2c creates the wrappers for the fault message, but the service skeleton and client stubs files seem to hard coded to assume no faults are ever sent / received. For example, the client axis2_stub_op_*() function takes my request message type and returns my response message type, but doesn't seem to account for my fault type. Modifying the code, I can see that the fault is received and correctly deserialized, but I'll have to continually hand edit the axis2_stub*.c and my client.c file as I make modifications to my WSDL in order to make this work. The same is true on the service side w/ the axis2_skel*() functions. Am I missing something here, or are faults not supported w/ wsdl2c? -- Doug Price Research Director | Presagis T. +1 972 943.2433 F. +1 469 467.4564 C. +1 469 867.8399 DISCLAIMER: This e-mail message is for the sole use of the intended recipient(s) and may contain confidential and/or proprietary information. Do not read, copy, or disseminate this message unless you are the addressee. Any unauthorized review, use, disclosure or distribution is strictly prohibited. If you have received this message in error, please contact the sender by reply e-mail and delete the original and any copies from your system.
George, Actually, after a bit more investigation I discovered the error was between the keyboard and chair... The .Net client is setting up the binding at runtime... I discovered that that after the .Net client set SendTimeout to 10 minutes, it set it to 25 seconds. Opps! Sam On Sun, Nov 15, 2009 at 4:01 PM, <gsherwood@att.net> wrote: > I too am interested in how to set the timeout for the Axis2/C module. > Rarely my application will need up to 300 seconds (the Apache httpd > default). But I have not tried that yet. > Thanks, > George > > -------------- Original message from Sam Carleton < > scarleton@miltonstreet.com>: -------------- > > My Axis2/C code is being used by a .Net client and being hosted via Apache > 2.2 and mod_axis2. I have set the SendTimeout on the .Net binding to 10 > minutes but things are still timing out in about 30 seconds. I am wondering > if anyone in this forum has run into this problem and has any suggestions on > setting on either apache or the .net side to extend the timeout. > >
I too am interested in how to set the timeout for the Axis2/C module. Rarely my application will need up to 300 seconds (the Apache httpd default). But I have not tried that yet. Thanks, George -------------- Original message from Sam Carleton <scarleton@miltonstreet.com>: -------------- My Axis2/C code is being used by a .Net client and being hosted via Apache 2.2 and mod_axis2. I have set the SendTimeout on the .Net binding to 10 minutes but things are still timing out in about 30 seconds. I am wondering if anyone in this forum has run into this problem and has any suggestions on setting on either apache or the .net side to extend the timeout.
My Axis2/C code is being used by a .Net client and being hosted via Apache 2.2 and mod_axis2. I have set the SendTimeout on the .Net binding to 10 minutes but things are still timing out in about 30 seconds. I am wondering if anyone in this forum has run into this problem and has any suggestions on setting on either apache or the .net side to extend the timeout.
Hi, I try to get the target endpoint address in a services in Axis2c, I put the following code
in the invoke function in the skeleton library:
axis2_endpoint_ref_t *endpoint_ref = NULL;
const axis2_char_t *address = NULL;
.
.
.
endpoint_ref = axis2_msg_ctx_get_to(msg_ctx, env);
if(endpoint_ref)
{
AXIS2_LOG_DEBUG(env->log, AXIS2_LOG_SI, "%s%s if(endpoint_ref)",pdesWebServ->nombre_web,nombreFuncion);
address = axis2_endpoint_ref_get_address(endpoint_ref, env);
if (address)
{
AXIS2_LOG_DEBUG(env->log, AXIS2_LOG_SI, "%s%s if (address)",pdesWebServ->nombre_web,nombreFuncion);
}
}
When I run this, I got NULL in endpoint_ref variable, so I don’t know it was something wrong
with this code.
It is the correct way to get the endpoint address or exists another way to get that info.
Thank in advance.
------------------------------------------------------------
José M. Medina V.
Wesam Consulting
jose_medina@wesamconsulting.com
Mobile: +58(416)613-3302 +58(414)019-0580
Ofc: +58(212)959-4155 Ext. 204
BB pin: 31E562BF
Caracas - Venezuela
Damitha Kumarage wrote: > Dimitri Pararas wrote: >> I seem to be having some difficulty creating the proper headers for >> my request using Axis2/c. I am creating a simple request using the >> hello client as a base. When I send my request to the simple server >> included with the axis2/c (after adding a dumb service) the request >> works properly. When I send it to the actual server I receive this >> error "Transport identified SOAP version does not match with SOAP >> message version" (#195) the header created looks like this >> POST /foobar/services/FoobarService HTTP/1.1 >> User-Agent: Axis2C/1.6.0 >> Content-Length: 420 >> Content-Type: application/soap+xml;charset=UTF-8 >> Host: mercury:21083 >> >> <soapenv:Envelope >> xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope"><soapenv:Body><getTaskValidity><acNum>0001</acNum><layoverDate>2009-11-1</layoverDate><newStation>BOS</newStation><origStation>LHR</origStation><arrivalDateTime>2009-11-1 >> 20:00</arrivalDateTime><callerID> >> POST /Foobar/services/foobarService HTTP/1.1 >> User-Agent: Axis2C/1.6.0 >> Content-Length: 420 >> Content-Type: application/soap+xml;charset=UTF-8 > I think you have done a mistake here when copying the soap message to > this mail message by copying the http headers again at the end. Are > you sure your soap message have no mistakes. > I guess your actual service is a dot net service > > thanks, > Damitha >> >> I am using the axis2_svc_client_send_receive to send this request, >> and I have not been able to figure out what the problem is and how to >> manipulate the header even if I did. Thanks >> Dimitri >> >> > > I used a TCP sniffer to grab the response, I didn't know what might be important so I pasted it all. Looking at it again, it seems like maybe I pasted a request and inadvertently included the http headers from the second request also. When you say "I guess your actual service is a dot net service" do you mean a dot net implementation of SOAP or something totally different? I am fairly certain that it should be a soap service, does Axis not work with dot net SOAP? Dimitri
Dimitri Pararas wrote: > I seem to be having some difficulty creating the proper headers for my > request using Axis2/c. I am creating a simple request using the hello > client as a base. When I send my request to the simple server > included with the axis2/c (after adding a dumb service) the request > works properly. When I send it to the actual server I receive this > error "Transport identified SOAP version does not match with SOAP > message version" (#195) the header created looks like this > POST /foobar/services/FoobarService HTTP/1.1 > User-Agent: Axis2C/1.6.0 > Content-Length: 420 > Content-Type: application/soap+xml;charset=UTF-8 > Host: mercury:21083 > > <soapenv:Envelope > xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope"><soapenv:Body><getTaskValidity><acNum>0001</acNum><layoverDate>2009-11-1</layoverDate><newStation>BOS</newStation><origStation>LHR</origStation><arrivalDateTime>2009-11-1 > 20:00</arrivalDateTime><callerID> > POST /Foobar/services/foobarService HTTP/1.1 > User-Agent: Axis2C/1.6.0 > Content-Length: 420 > Content-Type: application/soap+xml;charset=UTF-8 I think you have done a mistake here when copying the soap message to this mail message by copying the http headers again at the end. Are you sure your soap message have no mistakes. I guess your actual service is a dot net service thanks, Damitha > > I am using the axis2_svc_client_send_receive to send this request, and > I have not been able to figure out what the problem is and how to > manipulate the header even if I did. Thanks > Dimitri > > -- __________________________________________________________________ Damitha Kumarage Technical Lead; WSO2 Inc. "Oxygenating the Web Service Platform; " http://www.wso2.com/ blog: " http://damithakumarage.wordpress.com/ __________________________________________________________________
I seem to be having some difficulty creating the proper headers for my request using Axis2/c. I am creating a simple request using the hello client as a base. When I send my request to the simple server included with the axis2/c (after adding a dumb service) the request works properly. When I send it to the actual server I receive this error "Transport identified SOAP version does not match with SOAP message version" (#195) the header created looks like this POST /foobar/services/FoobarService HTTP/1.1 User-Agent: Axis2C/1.6.0 Content-Length: 420 Content-Type: application/soap+xml;charset=UTF-8 Host: mercury:21083 <soapenv:Envelope xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope"><soapenv:Body><getTaskValidity><acNum>0001</acNum><layoverDate>2009-11-1</layoverDate><newStation>BOS</newStation><origStation>LHR</origStation><arrivalDateTime>2009-11-1 20:00</arrivalDateTime><callerID> POST /Foobar/services/foobarService HTTP/1.1 User-Agent: Axis2C/1.6.0 Content-Length: 420 Content-Type: application/soap+xml;charset=UTF-8 I am using the axis2_svc_client_send_receive to send this request, and I have not been able to figure out what the problem is and how to manipulate the header even if I did. Thanks Dimitri
As Seniors at the University of Alabama we have been assigned an industry analysis for the software industry specifically regarding Hydra, Axis, and Gsoap. We are currently trying to define who uses this product, what the product is used for and why this product. Any help in determining these issues will be greatly appreciated. We appreciate your time and attention to this matter. Thank You, Jessica Bush GBA 490 Team Lead University of Alabama -- View this message in context: http://old.nabble.com/Marketing-Analysis-GBA-490-tp26157783p26157783.html Sent from the Axis - C++ - User mailing list archive at Nabble.com.
I have a project where I have multiple WSDLs that contain a types with the same name, but with
different definitions, and methods with the same name but different parameters. When I generate
the code using:
WSDL2C -uri MyWSDL1.wsdl -d adb -u -o $OUTPUT_DIR
Everything is fine if I create separate executables for accessing each WSDL. However, if
I compile them together I get numerous duplicate symbols.
If there a way in WSDLC to have it generate something like:
adb_<prefix>_MyType or adb_<prefix>_MyMethod_create
instead of:
adb_MyType or adb_MyMethod_create
I attempted to use the -p option when starting WSDL2C but it does not appear to do anything.
Am I missing something?
I have set up two services which (for now) are identical except for their names, TestCases and TestCases_t. The choice of the suffix _t is historical and has nothing to do with type names. libTestCases.so and libTestCases_t.so are placed in their respective directories: /usr/local/www/64.232.245.115/axis2c/services/TestCases and /usr/local/www/64.232.245.115/axis2c/services/TestCases_t However, log entries indicate the DLL path for libTestCases_t.so is not getting set correctly. Relevant entries include the following. [Tue Oct 27 19:22:33 2009] [debug] svc_builder.c(318) DLL path is : /usr/local/www/64.232.245.115/axis2c/services/TestCases/libTestCases.so [Tue Oct 27 19:22:33 2009] [debug] om_element.c(1114) There are no child elements for the node [Tue Oct 27 19:22:33 2009] [debug] svc_builder.c(318) DLL path is : /usr/local/www/64.232.245.115/axis2c/services/TestCases_t/libTestCases.so [Tue Oct 27 19:22:33 2009] [debug] om_element.c(1114) There are no child elements for the node ... [Tue Oct 27 19:22:33 2009] [error] class_loader.c(162) Loading shared library /usr/local/www/64.232.245.115/axis2c/services/TestCases_t/libTestCases.so Failed. DLERROR IS /usr/local/www/64.232.245.115/axis2c/services/TestCases_t/libTestCases.so: cannot open shared object file: No such file or directory If I depart from the usual naming convention (i.e. libTestCases_t.so for TestCases_t), and use the name in the DLL path instead (libTestCases.so), then the service works. Can anyone help with answers to these questions? 1. Is this behavior (dropping the _t suffix) a bug or a feature? 2. Is setting the name to the DLL path indicated in the log a legitimate workaround? 3. Am I likely to encounter future trouble with a service name ending in _t? Thanks, George Sherwood Testcover.com
Hi, William, "Nagy Vilmos" <nvili77@gmail.com> writes: > Hi, > > the axiom_text_create method can be used to create a text node in Axis2/C. > How can I create a CDATA section node? AFAIK, CDATA is not implemented with axiom yet. I may be wrong. thanks, Dinesh