Re: Mac OS X build problems - Axis 1.0.0

[Simon Parker]

Samisa -

Many thanks for your response.

I downloaded axis2c-src-1.1.0 and tried again. Far fewer 'multiple  
definitions of symbol' messages this time, but still not error free.


gcc -dynamiclib ${wl}-flat_namespace ${wl}-undefined ${wl}suppress - 
o .libs/libaxis2_mod_addr.0.1.0.dylib  .libs/addr_in_handler.o .libs/ 
addr_out_handler.o .libs/mod_addr.o  -lpthread ../../../axiom/src/ 
om/.libs/libaxis2_axiom.dylib /Users/simon/product_builds/axis2c- 
src-1.1.0/axiom/src/parser/guththila/.libs/libaxis2_parser.dylib / 
Users/simon/product_builds/axis2c-src-1.1.0/guththila/src/.libs/ 
libguththila.dylib /Users/simon/product_builds/axis2c-src-1.1.0/util/ 
src/.libs/libaxutil.dylib /Users/simon/product_builds/axis2c- 
src-1.1.0/util/src/minizip/.libs/libaxis2_minizip.dylib ../../../util/ 
src/.libs/libaxutil.dylib ../../../src/core/engine/.libs/ 
libaxis2_engine.dylib /Users/simon/product_builds/axis2c-src-1.1.0/ 
neethi/src/.libs/libneethi.dylib /Users/simon/product_builds/axis2c- 
src-1.1.0/src/core/transport/http/common/.libs/ 
libaxis2_http_common.dylib /Users/simon/product_builds/axis2c- 
src-1.1.0/axiom/src/om/.libs/libaxis2_axiom.dylib /Users/simon/ 
product_builds/axis2c-src-1.1.0/src/core/engine/.libs/ 
libaxis2_engine.dylib -lz -ldl  -install_name  /usr/local/axis2c/ 
modules/addressing/libaxis2_mod_addr.0.dylib -Wl,- 
compatibility_version -Wl,2 -Wl,-current_version -Wl,2.0

ld: multiple definitions of symbol _axis2_remove_instance
.libs/mod_addr.o definition of _axis2_remove_instance in section  
(__TEXT,__text)
../../../src/core/engine/.libs/libaxis2_engine.dylib 
(raw_xml_in_out_msg_recv.o) definition of _axis2_remove_instance

ld: multiple definitions of symbol _axis2_get_instance
.libs/mod_addr.o definition of _axis2_get_instance in section  
(__TEXT,__text)
../../../src/core/engine/.libs/libaxis2_engine.dylib 
(raw_xml_in_out_msg_recv.o) definition of _axis2_get_instance

/usr/bin/libtool: internal link edit command failed
make[4]: *** [libaxis2_mod_addr.la] Error 1
make[3]: *** [all-recursive] Error 1
make[2]: *** [all-recursive] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2

best regards

Simon

On 22 Aug 2007, at 02:03, Samisa Abeysinghe wrote:

Hopefully, this issue is resolved by now in the latest svn. This  
was done after 1.0.0 release.
Please try the source of 1.1.0 RC1 hosted here: http:// 
people.apache.org/~samisa/1.1.0-RC1/


Thanks,
Samisa...

Simon Parker wrote:


Hi -

I'm trying to build the axis2c-src-1.0.0 source distribution on a  
MacBook Pro. The Mac OS X release is:


*Darwin Simons-MacBook-Pro.local 8.10.1 Darwin Kernel Version  
8.10.1: Wed May 23 16:33:00 PDT 2007; root:xnu-792.22.5~1/ 
RELEASE_I386 i386 i386*


Having run ./configure successfully I get the following error when  
doing a make:


*ld: multiple definitions of symbol _axutil_error_messages *
*.libs/hash.o definition of _axutil_error_messages in section  
(__DATA,__common)*
*.libs/allocator.o definition of _axutil_error_messages in section  
(__DATA,__common)*
*.libs/env.o definition of _axutil_error_messages in section  
(__DATA,__common)*
*.libs/error.o definition of _axutil_error_messages in section  
(__DATA,__common)*

.
.
.etc

Has anyone managed to resolve this issue as yet?

thanks in advance

Simon




--
Samisa Abeysinghe : WSO2 WSF/C
"http://wso2.org/projects/wsf/c? 
WSO2 Web Services Framework/C - 
 Open source C library for providing&nbs 
p;and consuming Web services"



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Is AXIS2/C what I need?

[Carlos Escobar]

Samisa:

By your reply i can say over safe ground that i can use axis and/or axis2 (both 
for c/c++) in a production environment without surprises, am i right?

Well, another reason for stopping our trying axis was due to the difficulties 
we had installing it, hope you or any of the mailing list members can help... 
i'll be posting my experience tomorrow at work (i'm at home now), but what i 
recall is always having trouble with the AxisXMLParser.Dll thing. I haven't 
fully tried Axis 2 for C/C++, but I'd like to hear comments/recommendations on 
which one would be better to use.

Thanks

Carlos
-- Original Message --
From: Samisa Abeysinghe <[EMAIL PROTECTED]>
Reply-To: "Apache AXIS C User List" 
Date:  Wed, 22 Aug 2007 06:53:47 +0600

>Carlos Escobar Zarzar wrote:
>> Hi Frank,
>>
>> It has to.. at our company we ceased researching axis due to it's
>> development status, but have been using gSOAP for most of our C/C++
>> webservices, and of course, they all pack a wsdl with them ;) now
>> where that parser is being used I don't know, but I can tell for sure
>> it does parse them.
>Axis2/C also have the contract first model of development.
>>
>> We had success communicating a webservice written in a z/OS server
>> with a Windows XP C++ client which was built using gSOAP.
>Axis2/C has proved to interop with .NET and J2EE with basic SOAP as well
>as WS-* level.
>
>Samisa...
>>
>> Hope that helps
>>
>> Carlos
>>
>> Frank Zhou escribió:
>>> Thanks much for your replies. I had quite a bit of
>>> experience with AXIS-J but not gSOAP or AXIS-c. Does
>>> gSOAP come with a WSDL parser with APIs to allow me
>>> traverse the various parts of a WSDL? In my
>>> application, I do not intend to deploy just one web
>>> services (so no code generation), I need to be able to
>>> parse any standard WSDLs.
>>>
>>> Thanks much.
>>> Frank
>>> --- cara <[EMAIL PROTECTED]> wrote:
>>>
>>>
 Frank,

 Hi again. Just to cover our reasons for using gsoap:

 1. It is older software ... fewer bugs. Lower risk
 for a production project.
 2. We used it for an rpc wsdl, so nothing too fancy
 as far as wsdls go.
 3. Our legacy C++ software developers and
 integration team knows almost
 nothing about building C++ code with ant (they
 dislike all things java).
 4. Axis2 for java was not ready for production so
 (at the time) we did not
 consider Axis2/c.

 On 8/20/07, Samisa Abeysinghe <[EMAIL PROTECTED]>
 wrote:

> Frank Zhou wrote:
>
>> Hi All,
>>
>> I am trying to build a web service application
>>
 in c++,

>> and now investigate to see if AXIS2/c can
>>
 satisfy my

>> needs. Specifically, I have the following
>> requirements:
>>
>> (1) The library supports common web services
>>
 standards

>>  like SOAP/HTTP/WSDL et cetera. I will use it to
>>
 build

>>  a web service client application (web service
>>  consumer).
>>
>>
> Axis2/C can handle SOAP over HTTP. But there are
>
 some TODOs pending in

> WSDL space.
>
>> (2) It should provides a rich set of APIs for me
>>
 to

>>  traverse through a WSDL and make SOAP/HTTP
>>
 calls. In

>>  particular, I need a WSDL parser so that I can
>>
 parse

>> a
>>  WSDL (given the WSDL file or the URL)to get the
>>  definitions. I DO NOT NEED TO CONVERT THE WSDL
>>
 TO

>>  C++ code, just need to parse a WSDL to get the
>>  definitions, later on I will traverse the
>>
 parsed

>>  objects to get the services, operations,
>>
 messages

>>  and types (XML schemas) et cetera to build my
>>
 only

>>  datastore for a given WSDL. This way I can
>>  dynamically handle different WSDLs in my
>>
 application

>>  without generating the c++ code stubs every
>>
 time.

> As mentioned earlier, there is a piece of code
>
 written in Axis2/C called

> woden, that can deal with the WSDL functionality
>
 that you are looking for.

> Unfortunately that is not in the main source tree,
>
 because we could not

> maintain it -  due to lack of contributors in that
>
 space.

> At some point, however, someone will again start
>
 looking into that, at

> which point you would have WSDL handling features.
>
>> (3) The library is in c++ and available for
>> multi-platforms, like windows, linux and unix et
>> cetera.
>>
>>
> Axis2/C is a C library, that works on Windows,
>
 Solaris, MacOS and Linux.

>> Please let me know if AXIS2/c is a good choice
>>
 to me.

>> and how it is compared to gSOAP?
>>
>>
> I am not in a position to do a formal comparison
>
 on Axis

Re: SOAP Fault Segmentation Fault

[Nandika Jayawardana]

Hi Edward,
It is not possible to cast axiom_node_t* pointer to axiom_soap_body_t type.
One thing you could do in order to process the fault is following.

Use axis2_svc_client_get_last_response_has_fault check whether the received
message is a fault at client side. Then you can use
axis2_svc_client_get_last_response_soap_envelope
function to obtain the received soap envelope and then obtain the soap body
and soap fault etc from the soap envelope.

Regards
Nandika



On 8/21/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> I am just to run this snippet of code that I have designed:
>
> if (axiom_soap_body_has_fault((axiom_soap_body_t*)create_resp,
> env))
> {
> axiom_soap_fault_t* fault =
> axiom_soap_body_get_fault(
> (axiom_soap_body_t*)create_resp, env);
>
> axiom_soap_fault_code_t* code =
> axiom_soap_fault_get_code(fault, env);
> axiom_soap_fault_value_t* value =
> axiom_soap_fault_code_get_value(code, env);
> axis2_char_t* text =
> axiom_soap_fault_value_get_text(value,
>
> env);
> printf("\n%s\n", text);
>
> axiom_soap_fault_reason_t* reason =
> axiom_soap_fault_get_reason(fault, env);
> axiom_soap_fault_text_t* reason_text =
>
> axiom_soap_fault_reason_get_first_soap_fault_text(
> reason, env);
> axis2_char_t* value_text =
> axiom_soap_fault_text_get_text(reason_text,
> env);
> printf("\n%s\n", value_text);
> }
>
> create_resp is type-casted since it is originally an object of type
> axiom_node_t*.  I am trying to test how to process a SOAP fault that the
> client receives from the server.  If I comment out the second portion of
> the if section (the part starting with the code object), I see (null)
> printed out for value_text, which is not what I expected.  When I keep
> in the second portion, I get a segmentation fault on the line:
> axis2_char_t* text = axiom_soap_fault_value_get_text(value, env);  Here
> is the exact part that the error occurs:
>
> Program received signal SIGSEGV, Segmentation fault.
> axiom_node_get_node_type (om_node=0x772e772f2f3a, env=0x508340) at
> om_node.c:811
> 811 return om_node->node_type;
>
> Is this an error on my end or bug in the Axis2/C library?  Also, seeing
> (null) for value_text is not correct, as I can see the returning SOAP
> fault payload, and the Value is not null is the payload.  The server is
> supposed to return a SOAP 1.1 message, but the payload is in SOAP 1.2.
> Could that be the issue for the null problem?
>
> Thanks for the help on my two issues!
> Edward
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
[EMAIL PROTECTED]
WSO2 Inc: http://www.wso2.com

Re: SOAP fault builder

[Dinesh Premalal]

Hi Subra,
"Subra A Narayanan" <[EMAIL PROTECTED]> writes:

> I modified the axis2_raw_xml_in_out_msg_recv_invoke_business_logic_sync
> function to log the soap fault message to axis2.log file just before it 
> returns
> and see the correct soap fault message. So something happens after this point
> which makes the apache http server send a 500 Internal server error to the
> client.
were you able to log those fault to axis2.log? My feeling is, there
might be some misconfiguration in apache server. Did you try with
axis2_http_server? 

> My second question was, is there a way to return custom error numbers and 
> error
> message to the myservice_on_fault function so that the error number/msg can be
> included in the soap fault. Right now only predefined AXIS2 error message can
> be set using AXIS2_ERROR_SET. I understand that I can modify axutil_error.h
> file but it says that the error codes are reserved for modules. Is there any
> other better way of doing this?
AFAIK, there is no such a mechanism. However I think we should
provide custom error mechanism to user. May be an extension for
current axis2 error mechanism will be helpful. 

Thoughts ???

thanks,
Dinesh
-- 
Dinesh Premalal
http://xydinesh.wordpress.com/
GPG ID : A255955C
GPG Key Finger Print : C481 E5D4 C27E DC34 9257  0229 4F44 266E A255 955C

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[ANN] WSO2 Web Services Framework (WSF)/C v1.0.1 Released

[Samisa Abeysinghe]

WSO2 Web Services Framework (WSF)/C v1.0.1 Released
===

WSO2 WSF/C team is pleased to announce the release of WSO2 WSF/C v1.0.1.

WSO2 Web Services Framework/C (WSO2 WSF/C) is a standards compliant, 
enterprise grade, open source, C library for providing and consuming Web 
services in C.


WSO2 WSF/C is based on a family of Apache open source projects,
including Apache Axis2/C, Apache Rampart/C, Apache Sandesha2/C and 
Apache Savan/C. It is released under the Apache License V2.0 as well.



You can download this release from:
  http://dist.wso2.org/products/wsf/c/1.0.1

For more information, please visit our project home page:
  http://wso2.org/projects/wsf/c

-
Key Features
=
  1. Attachments with MTOM
  * Binary optimized
  * Non-optimized (Base64 binary)
  2. WS-Addressing
  * Version 1.0
  * Submission
  3. WS-Policy
  4. WS-Security
  * UsernameToken
  * Signing
  * Encryption
  5. WS-ReliableMessaging
  6. WS-Eventing
  7. SSL enabled Transport layer
  8. XMPPtransport layer
  9. TCP transport layer
 10. wsclient command line tool to consume Web services

--
Known Issues
==
 1. There can be memory leaks when using WS-ReliableMessaging. Please
refer to the Apache Sandesha2/C README file located in the sandesha2 folder.
 2. WS-ReliableMessaging and WS-Security does not work with the 
Guththila parser.


---
Reporting Problems
===
Issues can be reported using the public JIRA available at:
  https://wso2.org/jira/browse/WSFC


Contact Us


Please subscribe to our user or developer mailing lists. For details on 
how to subscribe please visit: http://wso2.org/projects/wsf/c#mail


We welcome your feedback on this implementation.
Thank you for your interest in WSO2 WSF/C.

-- WSO2 WSF/C Team --


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Mac OS X build problems - Axis 1.0.0

[Samisa Abeysinghe]

Hopefully, this issue is resolved by now in the latest svn. This was 
done after 1.0.0 release.
Please try the source of 1.1.0 RC1 hosted here: 
http://people.apache.org/~samisa/1.1.0-RC1/


Thanks,
Samisa...

Simon Parker wrote:


Hi -

I'm trying to build the axis2c-src-1.0.0 source distribution on a 
MacBook Pro. The Mac OS X release is:


*Darwin Simons-MacBook-Pro.local 8.10.1 Darwin Kernel Version 8.10.1: 
Wed May 23 16:33:00 PDT 2007; root:xnu-792.22.5~1/RELEASE_I386 i386 i386*


Having run ./configure successfully I get the following error when 
doing a make:


*ld: multiple definitions of symbol _axutil_error_messages *
*.libs/hash.o definition of _axutil_error_messages in section 
(__DATA,__common)*
*.libs/allocator.o definition of _axutil_error_messages in section 
(__DATA,__common)*
*.libs/env.o definition of _axutil_error_messages in section 
(__DATA,__common)*
*.libs/error.o definition of _axutil_error_messages in section 
(__DATA,__common)*

.
.
.etc

Has anyone managed to resolve this issue as yet?

thanks in advance

Simon




--
Samisa Abeysinghe : WSO2 WSF/C
"http://wso2.org/projects/wsf/c?WSO2 Web Services Framework/C - Open source C library for providing and consuming Web services";


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Is AXIS2/C what I need?

[Samisa Abeysinghe]

Carlos Escobar Zarzar wrote:

Hi Frank,

It has to.. at our company we ceased researching axis due to it's 
development status, but have been using gSOAP for most of our C/C++ 
webservices, and of course, they all pack a wsdl with them ;) now 
where that parser is being used I don't know, but I can tell for sure 
it does parse them.

Axis2/C also have the contract first model of development.


We had success communicating a webservice written in a z/OS server 
with a Windows XP C++ client which was built using gSOAP.
Axis2/C has proved to interop with .NET and J2EE with basic SOAP as well 
as WS-* level.


Samisa...


Hope that helps

Carlos

Frank Zhou escribió:

Thanks much for your replies. I had quite a bit of
experience with AXIS-J but not gSOAP or AXIS-c. Does
gSOAP come with a WSDL parser with APIs to allow me
traverse the various parts of a WSDL? In my
application, I do not intend to deploy just one web
services (so no code generation), I need to be able to
parse any standard WSDLs.

Thanks much.
Frank
--- cara <[EMAIL PROTECTED]> wrote:

  

Frank,

Hi again. Just to cover our reasons for using gsoap:

1. It is older software ... fewer bugs. Lower risk
for a production project.
2. We used it for an rpc wsdl, so nothing too fancy
as far as wsdls go.
3. Our legacy C++ software developers and
integration team knows almost
nothing about building C++ code with ant (they
dislike all things java).
4. Axis2 for java was not ready for production so
(at the time) we did not
consider Axis2/c.

On 8/20/07, Samisa Abeysinghe <[EMAIL PROTECTED]>
wrote:


Frank Zhou wrote:
  

Hi All,

I am trying to build a web service application


in c++,


and now investigate to see if AXIS2/c can


satisfy my


needs. Specifically, I have the following
requirements:

(1) The library supports common web services


standards


 like SOAP/HTTP/WSDL et cetera. I will use it to


build


 a web service client application (web service
 consumer).



Axis2/C can handle SOAP over HTTP. But there are
  

some TODOs pending in


WSDL space.
  

(2) It should provides a rich set of APIs for me


to


 traverse through a WSDL and make SOAP/HTTP


calls. In


 particular, I need a WSDL parser so that I can


parse


a
 WSDL (given the WSDL file or the URL)to get the
 definitions. I DO NOT NEED TO CONVERT THE WSDL


TO


 C++ code, just need to parse a WSDL to get the
 definitions, later on I will traverse the


parsed


 objects to get the services, operations,


messages


 and types (XML schemas) et cetera to build my


only


 datastore for a given WSDL. This way I can
 dynamically handle different WSDLs in my


application


 without generating the c++ code stubs every


time.


As mentioned earlier, there is a piece of code
  

written in Axis2/C called


woden, that can deal with the WSDL functionality
  

that you are looking for.


Unfortunately that is not in the main source tree,
  

because we could not


maintain it -  due to lack of contributors in that
  

space.


At some point, however, someone will again start
  

looking into that, at


which point you would have WSDL handling features.
  

(3) The library is in c++ and available for
multi-platforms, like windows, linux and unix et
cetera.



Axis2/C is a C library, that works on Windows,
  

Solaris, MacOS and Linux.


Please let me know if AXIS2/c is a good choice


to me.


and how it is compared to gSOAP?



I am not in a position to do a formal comparison
  

on Axis2/C vs. gSOAP.


However, here is an overview:
- Axis2/C comes with Apache license, and gSOAP
  

comes with GNU license


- Axis2/C is just two years old, gSOAP has
  

been around for much longer


- Axis2/C is based on Axis2 architecture, an
  

architecture designed


to cope with extensions and addition of new WS-*
  

spec implementations.


You would have to refer to gSOAP site on their
  

architecture


- Axis2/C already have full WS-Security and
  

WS-RM implementations,


to my knowledge, gSOAP do not have those specs
  

implemented fully.


(http://www.bloglines.com/blog/samisa?id=57)
- Axis2/C has a comparatively simple
  

deployment model. You get


Apache2 and IIS modules with Axis2/C. If you are
  

using apache module to


deploy, it is one off configuration. But if gSOAP,
  

you have to configure


Apache server for each and every service that you
  

cant to deploy.


   - Axis2/C has the ability to support many other
  

transports. It


already support HTTP and TCP. WSO2 WSF/C has
  

implemented an XMPP


transport and one of the GSOC students is
  

implementing and SMTP


trans

Re: Is AXIS2/C what I need?

[Samisa Abeysinghe]

cara wrote:

Frank,

Hi again. Just to cover our reasons for using gsoap:

1. It is older software ... fewer bugs. Lower risk for a production 
project.

But it does not have that many WS-* coverage that Axis2/C has

2. We used it for an rpc wsdl, so nothing too fancy as far as wsdls go.

Axis2/C focus on doclit model
3. Our legacy C++ software developers and integration team knows 
almost nothing about building C++ code with ant (they dislike all 
things java).

Ant was used by Axis C++ project. Axis2/C uses GNU make.
4. Axis2 for java was not ready for production so (at the time) we did 
not consider Axis2/c.

Axis2/Java is being used in production, so is Axis2/C.

Samisa...


On 8/20/07, *Samisa Abeysinghe* < [EMAIL PROTECTED] 
> wrote:


Frank Zhou wrote:
> Hi All,
>
> I am trying to build a web service application in c++,
> and now investigate to see if AXIS2/c can satisfy my
> needs. Specifically, I have the following
> requirements:
>
> (1) The library supports common web services standards
>  like SOAP/HTTP/WSDL et cetera. I will use it to build
>  a web service client application (web service
>  consumer).
>
Axis2/C can handle SOAP over HTTP. But there are some TODOs pending in
WSDL space.
> (2) It should provides a rich set of APIs for me to
>  traverse through a WSDL and make SOAP/HTTP calls. In
>  particular, I need a WSDL parser so that I can parse
> a
>  WSDL (given the WSDL file or the URL)to get the
>  definitions. I DO NOT NEED TO CONVERT THE WSDL TO
>  C++ code, just need to parse a WSDL to get the
>  definitions, later on I will traverse the parsed
>  objects to get the services, operations, messages
>  and types (XML schemas) et cetera to build my only
>  datastore for a given WSDL. This way I can
>  dynamically handle different WSDLs in my application
>  without generating the c++ code stubs every time.
>
As mentioned earlier, there is a piece of code written in Axis2/C
called
woden, that can deal with the WSDL functionality that you are
looking for.
Unfortunately that is not in the main source tree, because we
could not
maintain it -  due to lack of contributors in that space.
At some point, however, someone will again start looking into
that, at
which point you would have WSDL handling features.
> (3) The library is in c++ and available for
> multi-platforms, like windows, linux and unix et
> cetera.
>
Axis2/C is a C library, that works on Windows, Solaris, MacOS and
Linux.
> Please let me know if AXIS2/c is a good choice to me.
> and how it is compared to gSOAP?
>
I am not in a position to do a formal comparison on Axis2/C vs. gSOAP.
However, here is an overview:
- Axis2/C comes with Apache license, and gSOAP comes with GNU
license
- Axis2/C is just two years old, gSOAP has been around for
much longer
- Axis2/C is based on Axis2 architecture, an architecture
designed
to cope with extensions and addition of new WS-* spec implementations.
You would have to refer to gSOAP site on their architecture
- Axis2/C already have full WS-Security and WS-RM implementations,
to my knowledge, gSOAP do not have those specs implemented fully.
(http://www.bloglines.com/blog/samisa?id=57)
- Axis2/C has a comparatively simple deployment model. You get
Apache2 and IIS modules with Axis2/C. If you are using apache
module to
deploy, it is one off configuration. But if gSOAP, you have to
configure
Apache server for each and every service that you cant to deploy.
   - Axis2/C has the ability to support many other transports. It
already support HTTP and TCP. WSO2 WSF/C has implemented an XMPP
transport and one of the GSOC students is implementing and SMTP
transport. To my knowledge, gSOAP only support HTTP transport

HTH

Regards,
Samisa...


> Thanks very much.
> Frank
>
>
>
>
>


> Need a vacation? Get great deals
> to amazing places on Yahoo! Travel.
> http://travel.yahoo.com/
>
>
-
> To unsubscribe, e-mail: [EMAIL PROTECTED]

> For additional commands, e-mail: [EMAIL PROTECTED]

>
>
>


--
Samisa Abeysinghe : WSO2 WSF/C
"

http://wso2.org/projects/wsf/c?WSO2 Web Services Framework/C - Open source C library for providing and consuming Web services

"



-
To unsubscri

Re: Is AXIS2/C what I need?

[Carlos Escobar Zarzar]

Hi Frank,

It has to.. at our company we ceased researching axis due to it's 
development status, but have been using gSOAP for most of our C/C++ 
webservices, and of course, they all pack a wsdl with them ;) now where 
that parser is being used I don't know, but I can tell for sure it does 
parse them.


We had success communicating a webservice written in a z/OS server with 
a Windows XP C++ client which was built using gSOAP.


Hope that helps

Carlos

Frank Zhou escribió:

Thanks much for your replies. I had quite a bit of
experience with AXIS-J but not gSOAP or AXIS-c. Does
gSOAP come with a WSDL parser with APIs to allow me
traverse the various parts of a WSDL? In my
application, I do not intend to deploy just one web
services (so no code generation), I need to be able to
parse any standard WSDLs.

Thanks much.
Frank
--- cara <[EMAIL PROTECTED]> wrote:

  

Frank,

Hi again. Just to cover our reasons for using gsoap:

1. It is older software ... fewer bugs. Lower risk
for a production project.
2. We used it for an rpc wsdl, so nothing too fancy
as far as wsdls go.
3. Our legacy C++ software developers and
integration team knows almost
nothing about building C++ code with ant (they
dislike all things java).
4. Axis2 for java was not ready for production so
(at the time) we did not
consider Axis2/c.

On 8/20/07, Samisa Abeysinghe <[EMAIL PROTECTED]>
wrote:


Frank Zhou wrote:
  

Hi All,

I am trying to build a web service application


in c++,


and now investigate to see if AXIS2/c can


satisfy my


needs. Specifically, I have the following
requirements:

(1) The library supports common web services


standards


 like SOAP/HTTP/WSDL et cetera. I will use it to


build


 a web service client application (web service
 consumer).



Axis2/C can handle SOAP over HTTP. But there are
  

some TODOs pending in


WSDL space.
  

(2) It should provides a rich set of APIs for me


to


 traverse through a WSDL and make SOAP/HTTP


calls. In


 particular, I need a WSDL parser so that I can


parse


a
 WSDL (given the WSDL file or the URL)to get the
 definitions. I DO NOT NEED TO CONVERT THE WSDL


TO


 C++ code, just need to parse a WSDL to get the
 definitions, later on I will traverse the


parsed


 objects to get the services, operations,


messages


 and types (XML schemas) et cetera to build my


only


 datastore for a given WSDL. This way I can
 dynamically handle different WSDLs in my


application


 without generating the c++ code stubs every


time.


As mentioned earlier, there is a piece of code
  

written in Axis2/C called


woden, that can deal with the WSDL functionality
  

that you are looking for.


Unfortunately that is not in the main source tree,
  

because we could not


maintain it -  due to lack of contributors in that
  

space.


At some point, however, someone will again start
  

looking into that, at


which point you would have WSDL handling features.
  

(3) The library is in c++ and available for
multi-platforms, like windows, linux and unix et
cetera.



Axis2/C is a C library, that works on Windows,
  

Solaris, MacOS and Linux.


Please let me know if AXIS2/c is a good choice


to me.


and how it is compared to gSOAP?



I am not in a position to do a formal comparison
  

on Axis2/C vs. gSOAP.


However, here is an overview:
- Axis2/C comes with Apache license, and gSOAP
  

comes with GNU license


- Axis2/C is just two years old, gSOAP has
  

been around for much longer


- Axis2/C is based on Axis2 architecture, an
  

architecture designed


to cope with extensions and addition of new WS-*
  

spec implementations.


You would have to refer to gSOAP site on their
  

architecture


- Axis2/C already have full WS-Security and
  

WS-RM implementations,


to my knowledge, gSOAP do not have those specs
  

implemented fully.


(http://www.bloglines.com/blog/samisa?id=57)
- Axis2/C has a comparatively simple
  

deployment model. You get


Apache2 and IIS modules with Axis2/C. If you are
  

using apache module to


deploy, it is one off configuration. But if gSOAP,
  

you have to configure


Apache server for each and every service that you
  

cant to deploy.


   - Axis2/C has the ability to support many other
  

transports. It


already support HTTP and TCP. WSO2 WSF/C has
  

implemented an XMPP


transport and one of the GSOC students is
  

implementing and SMTP


transport. To my knowledge, gSOAP only support
  

HTTP transport


HTH

Regards,
Samisa...


  

Thanks very much.
Frank







___

Re: Is AXIS2/C what I need?

[Frank Zhou]

Hi Cara, 

Thanks much for your replies. I had quite a bit of
experience with AXIS-J but not gSOAP or AXIS-c. Does
gSOAP come with a WSDL parser with APIs to allow me
traverse the various parts of a WSDL? In my
application, I do not intend to deploy just one web
services (so no code generation), I need to be able to
parse any standard WSDLs.

Thanks much.
Frank
--- cara <[EMAIL PROTECTED]> wrote:

> Frank,
> 
> Hi again. Just to cover our reasons for using gsoap:
> 
> 1. It is older software ... fewer bugs. Lower risk
> for a production project.
> 2. We used it for an rpc wsdl, so nothing too fancy
> as far as wsdls go.
> 3. Our legacy C++ software developers and
> integration team knows almost
> nothing about building C++ code with ant (they
> dislike all things java).
> 4. Axis2 for java was not ready for production so
> (at the time) we did not
> consider Axis2/c.
> 
> On 8/20/07, Samisa Abeysinghe <[EMAIL PROTECTED]>
> wrote:
> >
> > Frank Zhou wrote:
> > > Hi All,
> > >
> > > I am trying to build a web service application
> in c++,
> > > and now investigate to see if AXIS2/c can
> satisfy my
> > > needs. Specifically, I have the following
> > > requirements:
> > >
> > > (1) The library supports common web services
> standards
> > >  like SOAP/HTTP/WSDL et cetera. I will use it to
> build
> > >  a web service client application (web service
> > >  consumer).
> > >
> > Axis2/C can handle SOAP over HTTP. But there are
> some TODOs pending in
> > WSDL space.
> > > (2) It should provides a rich set of APIs for me
> to
> > >  traverse through a WSDL and make SOAP/HTTP
> calls. In
> > >  particular, I need a WSDL parser so that I can
> parse
> > > a
> > >  WSDL (given the WSDL file or the URL)to get the
> > >  definitions. I DO NOT NEED TO CONVERT THE WSDL
> TO
> > >  C++ code, just need to parse a WSDL to get the
> > >  definitions, later on I will traverse the
> parsed
> > >  objects to get the services, operations,
> messages
> > >  and types (XML schemas) et cetera to build my
> only
> > >  datastore for a given WSDL. This way I can
> > >  dynamically handle different WSDLs in my
> application
> > >  without generating the c++ code stubs every
> time.
> > >
> > As mentioned earlier, there is a piece of code
> written in Axis2/C called
> > woden, that can deal with the WSDL functionality
> that you are looking for.
> > Unfortunately that is not in the main source tree,
> because we could not
> > maintain it -  due to lack of contributors in that
> space.
> > At some point, however, someone will again start
> looking into that, at
> > which point you would have WSDL handling features.
> > > (3) The library is in c++ and available for
> > > multi-platforms, like windows, linux and unix et
> > > cetera.
> > >
> > Axis2/C is a C library, that works on Windows,
> Solaris, MacOS and Linux.
> > > Please let me know if AXIS2/c is a good choice
> to me.
> > > and how it is compared to gSOAP?
> > >
> > I am not in a position to do a formal comparison
> on Axis2/C vs. gSOAP.
> > However, here is an overview:
> > - Axis2/C comes with Apache license, and gSOAP
> comes with GNU license
> > - Axis2/C is just two years old, gSOAP has
> been around for much longer
> > - Axis2/C is based on Axis2 architecture, an
> architecture designed
> > to cope with extensions and addition of new WS-*
> spec implementations.
> > You would have to refer to gSOAP site on their
> architecture
> > - Axis2/C already have full WS-Security and
> WS-RM implementations,
> > to my knowledge, gSOAP do not have those specs
> implemented fully.
> > (http://www.bloglines.com/blog/samisa?id=57)
> > - Axis2/C has a comparatively simple
> deployment model. You get
> > Apache2 and IIS modules with Axis2/C. If you are
> using apache module to
> > deploy, it is one off configuration. But if gSOAP,
> you have to configure
> > Apache server for each and every service that you
> cant to deploy.
> >- Axis2/C has the ability to support many other
> transports. It
> > already support HTTP and TCP. WSO2 WSF/C has
> implemented an XMPP
> > transport and one of the GSOC students is
> implementing and SMTP
> > transport. To my knowledge, gSOAP only support
> HTTP transport
> >
> > HTH
> >
> > Regards,
> > Samisa...
> >
> >
> > > Thanks very much.
> > > Frank
> > >
> > >
> > >
> > >
> > >
> >
>

> > > Need a vacation? Get great deals
> > > to amazing places on Yahoo! Travel.
> > > http://travel.yahoo.com/
> > >
> > >
>
-
> > > To unsubscribe, e-mail:
> [EMAIL PROTECTED]
> > > For additional commands, e-mail:
> [EMAIL PROTECTED]
> > >
> > >
> > >
> >
> >
> > --
> > Samisa Abeysinghe : WSO2 WSF/C
> > "
> >
>
http://wso2.org/projects/wsf/c?WSO2 Web Services Framework/C - Open source C library for providing and consuming Web services
> > "
> >
> >
> >
> >
>

Re: Is AXIS2/C what I need?

[cara]

Frank,

Hi again. Just to cover our reasons for using gsoap:

1. It is older software ... fewer bugs. Lower risk for a production project.
2. We used it for an rpc wsdl, so nothing too fancy as far as wsdls go.
3. Our legacy C++ software developers and integration team knows almost
nothing about building C++ code with ant (they dislike all things java).
4. Axis2 for java was not ready for production so (at the time) we did not
consider Axis2/c.

On 8/20/07, Samisa Abeysinghe <[EMAIL PROTECTED]> wrote:
>
> Frank Zhou wrote:
> > Hi All,
> >
> > I am trying to build a web service application in c++,
> > and now investigate to see if AXIS2/c can satisfy my
> > needs. Specifically, I have the following
> > requirements:
> >
> > (1) The library supports common web services standards
> >  like SOAP/HTTP/WSDL et cetera. I will use it to build
> >  a web service client application (web service
> >  consumer).
> >
> Axis2/C can handle SOAP over HTTP. But there are some TODOs pending in
> WSDL space.
> > (2) It should provides a rich set of APIs for me to
> >  traverse through a WSDL and make SOAP/HTTP calls. In
> >  particular, I need a WSDL parser so that I can parse
> > a
> >  WSDL (given the WSDL file or the URL)to get the
> >  definitions. I DO NOT NEED TO CONVERT THE WSDL TO
> >  C++ code, just need to parse a WSDL to get the
> >  definitions, later on I will traverse the parsed
> >  objects to get the services, operations, messages
> >  and types (XML schemas) et cetera to build my only
> >  datastore for a given WSDL. This way I can
> >  dynamically handle different WSDLs in my application
> >  without generating the c++ code stubs every time.
> >
> As mentioned earlier, there is a piece of code written in Axis2/C called
> woden, that can deal with the WSDL functionality that you are looking for.
> Unfortunately that is not in the main source tree, because we could not
> maintain it -  due to lack of contributors in that space.
> At some point, however, someone will again start looking into that, at
> which point you would have WSDL handling features.
> > (3) The library is in c++ and available for
> > multi-platforms, like windows, linux and unix et
> > cetera.
> >
> Axis2/C is a C library, that works on Windows, Solaris, MacOS and Linux.
> > Please let me know if AXIS2/c is a good choice to me.
> > and how it is compared to gSOAP?
> >
> I am not in a position to do a formal comparison on Axis2/C vs. gSOAP.
> However, here is an overview:
> - Axis2/C comes with Apache license, and gSOAP comes with GNU license
> - Axis2/C is just two years old, gSOAP has been around for much longer
> - Axis2/C is based on Axis2 architecture, an architecture designed
> to cope with extensions and addition of new WS-* spec implementations.
> You would have to refer to gSOAP site on their architecture
> - Axis2/C already have full WS-Security and WS-RM implementations,
> to my knowledge, gSOAP do not have those specs implemented fully.
> (http://www.bloglines.com/blog/samisa?id=57)
> - Axis2/C has a comparatively simple deployment model. You get
> Apache2 and IIS modules with Axis2/C. If you are using apache module to
> deploy, it is one off configuration. But if gSOAP, you have to configure
> Apache server for each and every service that you cant to deploy.
>- Axis2/C has the ability to support many other transports. It
> already support HTTP and TCP. WSO2 WSF/C has implemented an XMPP
> transport and one of the GSOC students is implementing and SMTP
> transport. To my knowledge, gSOAP only support HTTP transport
>
> HTH
>
> Regards,
> Samisa...
>
>
> > Thanks very much.
> > Frank
> >
> >
> >
> >
> >
> 
> > Need a vacation? Get great deals
> > to amazing places on Yahoo! Travel.
> > http://travel.yahoo.com/
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> >
>
>
> --
> Samisa Abeysinghe : WSO2 WSF/C
> "
> http://wso2.org/projects/wsf/c?WSO2 Web Services Framework/C - Open source C library for providing and consuming Web services
> "
>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Re: SOAP fault builder

[Subra A Narayanan]

Hey Nandika,

Thanks for your reply. Looking at the
axis2_raw_xml_in_out_msg_recv_invoke_business_logic_sync function in
raw_xml_in_out_msg_recv.c was very helpful.

So I modified my code accordingly and I think I might have found a bug in
the framework. This is what I did

1. Set error status to AXIS2_FAILURE using AXIS2_ERROR_SET
2. Return NULL from my service
3. Implement myservice_on_fault function and create an axiom node which gets
added to the soap fault details node.

No when I try return a soap fault, the server sends a 500 Internal Server
error to the client. Chris Darroch created a JIRA issue late last year about
this bug here => https://issues.apache.org/jira/browse/AXIS2C-328 but I dont
think the bug has been fixed (pls correct me if I am wrong). I used TcpMon
to capture the response and this is what the client sees:

HTTP/1.1 500 Internal Server Error Date: Tue, 21 Aug 2007 17:39:55 GMT
Server: Apache/2.0.59 (rPath) Content-Length: 613 Connection: close
Content-Type: text/html; charset=iso-8859-1  

500 Internal Server Error

Internal Server Error
The server encountered an internal error or
misconfiguration and was unable to complete
your request.
Please contact the server administrator,
 [EMAIL PROTECTED] and inform them of the time the error occurred,
and anything you might have done that may have
caused the error.
More information about this error may be available
in the server error log.

Apache/2.0.59 (rPath) Server at 168.159.116.42 Port 80


I modified the axis2_raw_xml_in_out_msg_recv_invoke_business_logic_sync
function
to log the soap fault message to axis2.log file just before it returns and
see the correct soap fault message. So something happens after this point
which makes the apache http server send a 500 Internal server error to the
client.



My second question was, is there a way to return custom error numbers and
error message to the myservice_on_fault function so that the error
number/msg can be included in the soap fault. Right now only predefined
AXIS2 error message can be set using AXIS2_ERROR_SET. I understand that I
can modify axutil_error.h file but it says that the error codes are reserved
for modules. Is there any other better way of doing this?


Thank you folks!

Subra






On 8/21/07, Nandika Jayawardana <[EMAIL PROTECTED]> wrote:
>
> Hi Subra,
>
> To send a fault from the service you can do the following.
> In the invoke function of the service skeleton set an the error status to
> AXIS2_FALSE
> and return NULL. You can use the AXIS2_ERROR_SET macro to set the error
> status.
>
> Then implement the on_fault function in the skeleton to return the error
> message you want to return. This will be added to the fault detail section.
>
> When axis2 calls invoke function and finds that it returned null, it will
> check the error status.
> If the error status if AXIS2_FALSE , then a fault is returned.
>
> You do not have to be concerned about the soap version of the fault.
> Depending on the received
> message's soap version an appropriate  soap fault will be returned.
>
> You can have a look at
> axis2_raw_xml_in_out_msg_recv_invoke_business_logic_sync function
> in raw_xml_in_out_msg_recv.c file to understand how the fault is
> processed.
>
> Regards,
> Nandika
>
>
> On 8/21/07, Subra A Narayanan <[EMAIL PROTECTED]> wrote:
> >
> > Hey Nandika,
> >
> > Did you get a chance to look at my questions? I would really appreciate
> > ur input on these.
> >
> > Thanks so much!
> >
> > Subra
> >
> > On 8/17/07, Subra A Narayanan <[EMAIL PROTECTED]> wrote:
> > >
> > > Hey Nandika,
> > >
> > > So I tried your suggestion but I have a doubt. I am just modifying the
> > > 'math' webservice from the samples folder.
> > >
> > > The 'add' operation returns a axiom_node_t * on success, which is
> > > nothing but the soap message. But I want to return a soap fault from the
> > > 'add' operation if lets say one of the parameters was missing from the
> > > request or it was a decimal number. If I follow what you asked me to do,
> > > what do I return from the add function? I have to return a axiom_node_t
> > > *? But from your email I thought you meant that if I set the soap
> > > fault to the message context, the soap fault will automatically be 
> > > returned
> > > to the client. I dont understand how do I stop further processing and 
> > > return
> > > a soap fault to the client.
> > >
> > > So I did some further digging in to the axis code and found this
> > > function in axiom_soap_envelope.h:
> > >
> > > AXIS2_EXTERN axiom_node_t* AXIS2_CALL
> > > axiom_soap_envelope_get_base_node(axiom_soap_envelope_t *envelope,
> > > const axutil_env_t *env);
> > >
> > >
> > > so this gives me access to the soap fault message as a axiom_node_t*.
> > > And upon error in the 'add' operation, I just return it to the client. Is
> > > this the right way to do it? I am missing something here.
> > >
> > > Now one more important thing. When I call
> > > axiom_soap_envelope_get_base_node, it seems to retu

Mac OS X build problems - Axis 1.0.0

[Simon Parker]

Hi -

I'm trying to build the axis2c-src-1.0.0 source distribution on a  
MacBook Pro. The Mac OS X release is:


Darwin Simons-MacBook-Pro.local 8.10.1 Darwin Kernel Version 8.10.1:  
Wed May 23 16:33:00 PDT 2007; root:xnu-792.22.5~1/RELEASE_I386 i386 i386


Having run ./configure successfully I get the following error when  
doing a make:


ld: multiple definitions of symbol _axutil_error_messages
.libs/hash.o definition of _axutil_error_messages in section  
(__DATA,__common)
.libs/allocator.o definition of _axutil_error_messages in section  
(__DATA,__common)
.libs/env.o definition of _axutil_error_messages in section  
(__DATA,__common)
.libs/error.o definition of _axutil_error_messages in section  
(__DATA,__common)

.
.
.etc

Has anyone managed to resolve this issue as yet?

thanks in advance

Simon

SOAP Fault Segmentation Fault

[Liu_Edward]

I am just to run this snippet of code that I have designed:

if (axiom_soap_body_has_fault((axiom_soap_body_t*)create_resp,
env))
{
axiom_soap_fault_t* fault = 
axiom_soap_body_get_fault(
(axiom_soap_body_t*)create_resp, env);

axiom_soap_fault_code_t* code = 
axiom_soap_fault_get_code(fault, env);
axiom_soap_fault_value_t* value = 
axiom_soap_fault_code_get_value(code, env);
axis2_char_t* text =
axiom_soap_fault_value_get_text(value, 

env);
printf("\n%s\n", text);

axiom_soap_fault_reason_t* reason = 
axiom_soap_fault_get_reason(fault, env);
axiom_soap_fault_text_t* reason_text = 

axiom_soap_fault_reason_get_first_soap_fault_text(
reason, env);
axis2_char_t* value_text = 
axiom_soap_fault_text_get_text(reason_text,
env);
printf("\n%s\n", value_text);
}

create_resp is type-casted since it is originally an object of type
axiom_node_t*.  I am trying to test how to process a SOAP fault that the
client receives from the server.  If I comment out the second portion of
the if section (the part starting with the code object), I see (null)
printed out for value_text, which is not what I expected.  When I keep
in the second portion, I get a segmentation fault on the line:
axis2_char_t* text = axiom_soap_fault_value_get_text(value, env);  Here
is the exact part that the error occurs:

Program received signal SIGSEGV, Segmentation fault.
axiom_node_get_node_type (om_node=0x772e772f2f3a, env=0x508340) at
om_node.c:811
811 return om_node->node_type;

Is this an error on my end or bug in the Axis2/C library?  Also, seeing
(null) for value_text is not correct, as I can see the returning SOAP
fault payload, and the Value is not null is the payload.  The server is
supposed to return a SOAP 1.1 message, but the payload is in SOAP 1.2.
Could that be the issue for the null problem?

Thanks for the help on my two issues!
Edward


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: SOAP fault builder

[Nandika Jayawardana]

Hi Subra,

To send a fault from the service you can do the following.
In the invoke function of the service skeleton set an the error status to
AXIS2_FALSE
and return NULL. You can use the AXIS2_ERROR_SET macro to set the error
status.

Then implement the on_fault function in the skeleton to return the error
message you want to return. This will be added to the fault detail section.

When axis2 calls invoke function and finds that it returned null, it will
check the error status.
If the error status if AXIS2_FALSE , then a fault is returned.

You do not have to be concerned about the soap version of the fault.
Depending on the received
message's soap version an appropriate  soap fault will be returned.

You can have a look at
axis2_raw_xml_in_out_msg_recv_invoke_business_logic_sync function
in raw_xml_in_out_msg_recv.c file to understand how the fault is processed.

Regards,
Nandika


On 8/21/07, Subra A Narayanan <[EMAIL PROTECTED]> wrote:
>
> Hey Nandika,
>
> Did you get a chance to look at my questions? I would really appreciate ur
> input on these.
>
> Thanks so much!
>
> Subra
>
> On 8/17/07, Subra A Narayanan <[EMAIL PROTECTED]> wrote:
> >
> > Hey Nandika,
> >
> > So I tried your suggestion but I have a doubt. I am just modifying the
> > 'math' webservice from the samples folder.
> >
> > The 'add' operation returns a axiom_node_t * on success, which is
> > nothing but the soap message. But I want to return a soap fault from the
> > 'add' operation if lets say one of the parameters was missing from the
> > request or it was a decimal number. If I follow what you asked me to do,
> > what do I return from the add function? I have to return a axiom_node_t
> > *? But from your email I thought you meant that if I set the soap fault
> > to the message context, the soap fault will automatically be returned to the
> > client. I dont understand how do I stop further processing and return a soap
> > fault to the client.
> >
> > So I did some further digging in to the axis code and found this
> > function in axiom_soap_envelope.h:
> >
> > AXIS2_EXTERN axiom_node_t* AXIS2_CALL
> > axiom_soap_envelope_get_base_node(axiom_soap_envelope_t *envelope, 
> > constaxutil_env_t *env);
> >
> >
> > so this gives me access to the soap fault message as a axiom_node_t*.
> > And upon error in the 'add' operation, I just return it to the client. Is
> > this the right way to do it? I am missing something here.
> >
> > Now one more important thing. When I call
> > axiom_soap_envelope_get_base_node, it seems to returning a soap1.2 fault
> > message rather than a soap1.1 message even though I set *
> >
> > *soapVersion = AXIOM_SOAP11;
> >
> > Why is that? Is there a way to get soap1.1 fault message?
> >
> >
> > I hope my questions are clear. Thanks so much for your help!
> >
> >
> > Subra
> >
> >
> >
> > On 8/17/07, Subra A Narayanan <[EMAIL PROTECTED]> wrote:
> > >
> > > Thanks Nandika. I will give it a shot.
> > >
> > > Have a good weekend!
> > >
> > > On 8/17/07, Nandika Jayawardana < [EMAIL PROTECTED] > wrote:
> > > >
> > > > Hi Subra,
> > > >
> > > > You can create a soap11 fault using following lines.
> > > >
> > > > int soap_version = AXIOM_SOAP11;
> > > >
> > > > soap_envelope = axiom_soap_envelope_create_default_soap_envelope
> > > > (env, soap_version);
> > > >
> > > > soap_body = axiom_soap_envelope_get_body(soap_envelope, env);
> > > >
> > > > soap_fault = axiom_soap_fault_create_default_fault (env,
> > > > soap_body, "fault code" , "fault reason"
> > > > , soap_version);
> > > >
> > > > axis2_msg_ctx_set_fault_soap_envelope(msg_ctx, env, soap_envelope);
> > > >
> > > > You can set the fault to the msg_ctx and it will be returned to the
> > > > client.
> > > >
> > > > Regards
> > > >
> > > > Nandika
> > > >
> > > >
> > > >
> > > > On 8/17/07, Subra A Narayanan <[EMAIL PROTECTED] > wrote:
> > > > >
> > > > > Hello folks,
> > > > >
> > > > > I am trying ti build a SOAP1.1 fault and return to the ws client.
> > > > > I am having some difficulty understanding how to go about this. I 
> > > > > have tryng
> > > > > to dig through the source code but was wondering if you guys have some
> > > > > sample code. If you have it that would be very helpful in 
> > > > > understanding the
> > > > > usage.
> > > > >
> > > > > In the meantime I will continue to dig through the source code to
> > > > > try to understand.
> > > > >
> > > > > Thanks as usual!
> > > > >
> > > > > Subra
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > [EMAIL PROTECTED]
> > > > WSO2 Inc: http://www.wso2.com
> > >
> > >
> > >
> >
>


-- 
[EMAIL PROTECTED]
WSO2 Inc: http://www.wso2.com