Re: Linker error

[Selvaratnam Uthaiyashankar]

Hi,

I think you are using Axis2/C binary release and you compile your
program using MinGW? Is that correct?

Axis2/C binary was compiled using microsoft compilers (visual studio).
 So, I don't think you can use that with MinGW. Did you try to compile
your client code with visual studio?

Regards,
Shankar

On Thu, Feb 18, 2010 at 7:50 PM, Søren Berggreen  wrote:
> Hi
>
> I'm using Axis2/C version 1.6.0 on a windows client.
> I've noticed there are differences between windows and linux in the folder
> layout of Axis2/C.
>
> Company rules prohibit me from attaching my client, but I've attached 3
> files:
>
> SearchDocs_Compile_Log -> The log showing all the linker errors as they are
> outputted from Dec-C++.
> BuildLog.htm -> Build log from Visual Studio also showing linker errors.
> Makefile.win -> The makefile.
>
> Regards
> Søren
>
> On Thu, Feb 18, 2010 at 5:38 AM, Selvaratnam Uthaiyashankar
>  wrote:
>>
>> Hi,
>>
>> can you attach your client and the makefile? Which Axis2/C version you
>> are using?
>>
>> Regards,
>> Shankar
>>
>> On Wed, Feb 17, 2010 at 6:05 PM, Søren Berggreen 
>> wrote:
>> > Hi.
>> >
>> > I'm trying to build a client to a axis2c service, but I keep getting
>> > linker
>> > errors saying something like:
>> >
>> > File: test_client.o
>> > In function 'main':
>> > [Linker error] undefined reference to '_imp__axutil_env_create_all'
>> > [Linker error] undefined reference to '_imp__axutil_strcmp'
>> > [Linker error] undefined reference to '_imp__axutil_error_get_message'
>> > [Linker error] undefined reference to '_imp__axis2_stub_free'
>> > [Linker error] undefined reference to '_imp__axutil_env_free'
>> > etc
>> >
>> > I'm doing the build on a Windows XP Pro.
>> >
>> > I've also tried on an Ubuntu, which gives me no errors during the
>> > linking
>> > process, but instead gives me:
>> > Segmentation fault: 0xb7f882e6 in __do_global_dtors_aux ()
>> >
>> > I've included the axis2c lib files in the linker options.
>> >
>> > --
>> > Med venlig hilsen/Best regards
>> > Søren H. Berggreen
>> >
>>
>>
>>
>> --
>> S.Uthaiyashankar
>> Software Architect
>> WSO2 Inc.
>> http://wso2.com/ - "lean . enterprise . middleware"
>
>
>
> --
> Med venlig hilsen/Best regards
> Søren H. Berggreen
>



-- 
S.Uthaiyashankar
Software Architect
WSO2 Inc.
http://wso2.com/ - "lean . enterprise . middleware"

Re: Linker error

[Selvaratnam Uthaiyashankar]

Hi,

can you attach your client and the makefile? Which Axis2/C version you
are using?

Regards,
Shankar

On Wed, Feb 17, 2010 at 6:05 PM, Søren Berggreen  wrote:
> Hi.
>
> I'm trying to build a client to a axis2c service, but I keep getting linker
> errors saying something like:
>
> File: test_client.o
> In function 'main':
> [Linker error] undefined reference to '_imp__axutil_env_create_all'
> [Linker error] undefined reference to '_imp__axutil_strcmp'
> [Linker error] undefined reference to '_imp__axutil_error_get_message'
> [Linker error] undefined reference to '_imp__axis2_stub_free'
> [Linker error] undefined reference to '_imp__axutil_env_free'
> etc
>
> I'm doing the build on a Windows XP Pro.
>
> I've also tried on an Ubuntu, which gives me no errors during the linking
> process, but instead gives me:
> Segmentation fault: 0xb7f882e6 in __do_global_dtors_aux ()
>
> I've included the axis2c lib files in the linker options.
>
> --
> Med venlig hilsen/Best regards
> Søren H. Berggreen
>



-- 
S.Uthaiyashankar
Software Architect
WSO2 Inc.
http://wso2.com/ - "lean . enterprise . middleware"

Re: [Axis2[ Time for a release?

[Selvaratnam Uthaiyashankar]

On Fri, Dec 4, 2009 at 11:13 PM, Samisa Abeysinghe  wrote:
> I meant to say, Axis2!

> Samisa...
>
> On Fri, Dec 4, 2009 at 11:08 PM, Samisa Abeysinghe  wrote:
>>
>> Folks,
>>     I looked at the Jiras after a lng 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"

Re: crash with arbitrary rest post data

[Selvaratnam Uthaiyashankar]

Hi Tamas,

I think it is a bug. Can you create a Jira for this? I'll fix it ASAP.

Regards,
Shankar

2009/9/30 Tamás Martinec :
> Hi,
>
> What is the situation with this
>
> http://www.mail-archive.com/axis-c-dev@ws.apache.org/msg16788.html
>
> issue?
>
> I am trying to create a service that receives arbitrary strings as
> HTTP POST data.
>
> The services I created crash very much like echo in the above link.
>
> The echo sample crashes if the post data is empty, or content is not
> according to the
>
> text=sometext
>
> pattern.
>
> Here are the messages:
>
> SENDING DATA..
> /* sending time = 23:57:14*/
> /* message uuid = eb01af8d-4d6b-45a3-8bbf-2f80f43acbd2*/
> -
> POST /axis2/services/echo/echoString HTTP/1.0
> Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg,
> application/vnd.ms-excel, application/msword,
> application/vnd.ms-powerpoint, */*
> Accept-Language: en-us
> Accept-Encoding: gzip, deflate
> User-Agent: Mozilla/4.0
> Content-Length: 6
> Host: LOCALHOST
> Content-Type: application/x-www-form-urlencoded
>
> text
>
> RETRIEVING DATA..
> /* retrieving time = 23:57:14*/
> /* time throughput = 0 sec(s)*/
> -
> HTTP/1.0 500 Internal Server Error
> Date: Thu Sep 24 23:57:14 2009 GMT
> Server: Axis2C/1.6.0 (Simple Axis2 HTTP Server)
> Content-Type: text/html
> Content-Length: 210
>
> 500 Internal Server
> ErrorInternal Server ErrorThe server
> encountered an unexpected condition which prevented it from fulfilling
> the request.
>
>
> And the call stack for the crash:
>
>    axis2_engine.dll!axis2_http_status_line_free(axis2_http_status_line
> * status_line=0x, const axutil_env * env=0x006dd498)  Line 143
> + 0x3 bytes    C
>     
> axis2_engine.dll!axis2_http_simple_response_free(axis2_http_simple_response
> * simple_response=0x006df500, const axutil_env * env=0x006dd498)  Line
> 117    C
>     
> axis2_engine.dll!axis2_http_out_transport_info_impl_free(axis2_http_out_transport_info
> * http_out_transport_info=0x006de700, const axutil_env *
> env=0x006dd498)  Line 158    C
>     
> axis2_engine.dll!axis2_http_out_transport_info_free(axis2_http_out_transport_info
> * http_out_transport_info=0x006de700, const axutil_env *
> env=0x006dd498)  Line 206 + 0x12 bytes    C
>     
> axis2_engine.dll!axis2_out_transport_info_impl_free(axis2_out_transport_info
> * out_transport_info=0x006de700, const axutil_env * env=0x006dd498)
> Line 61    C
>     axis2_engine.dll!axis2_msg_ctx_free(axis2_msg_ctx *
> msg_ctx=0x006dfa38, const axutil_env * env=0x006dd498)  Line 444 +
> 0x20 bytes    C
>     axis2_engine.dll!axis2_http_worker_process_request(axis2_http_worker
> * http_worker=0x006dc350, const axutil_env * env=0x006dd498,
> axis2_simple_http_svr_conn * svr_conn=0x006dd4e0,
> axis2_http_simple_request * simple_request=0x006e0b18)  Line 2009    C
>     axis2_http_receiver.dll!axis2_svr_thread_worker_func(axutil_thread_t
> * thd=0x006df870, void * data=0x006dc608)  Line 260 + 0x18 bytes    C
>     axutil.dll!dummy_worker(void * opaque=0x006df870)  Line 88 + 0x15
> bytes    C
>     kernel32.dll!7c80b729()
>     [Frames below may be incorrect and/or missing, no symbols loaded
> for kernel32.dll]
>
> Seems like axis2_http_status_line_free wants to free something already freed..
>
> And this is the end of the log:
>
> [Thu Sep 24 23:57:14 2009] [debug]
> c:\axis2c-repo\src\core\transport\http\common\http_worker.c(200)
> Client HTTP version HTTP/1.0
> [Thu Sep 24 23:57:14 2009] [debug]
> c:\axis2c-repo\src\core\engine\rest_disp.c(114) Checking for service
> using target endpoint address :
> http://127.0.0.1:9090/axis2/services/echo/echoString
>
>
> [Thu Sep 24 23:57:14 2009] [debug]
> c:\axis2c-repo\src\core\engine\rest_disp.c(135) Service found using
> target endpoint address
> [Thu Sep 24 23:57:14 2009] [debug]
> c:\axis2c-repo\src\core\util\core_utils.c(772) Checking for operation
> using REST HTTP Location fragment : /echoString
> [Thu Sep 24 23:57:14 2009] [debug]
> c:\axis2c-repo\src\core\util\core_utils.c(834) Operation found using
> target endpoint uri fragment
> [Thu Sep 24 23:57:14 2009] [debug]
> c:\axis2c-repo\src\core\engine\phase.c(210) Invoke the handler
> request_uri_based_dispatcher within the phase Transport
> [Thu Sep 24 23:57:14 2009] [debug]
> c:\axis2c-repo\src\core\engine\phase.c(210) Invoke the handler
> AddressingInHandler within the phase Transport
> [Thu Sep 24 23:57:14 2009] [info]  Starting addressing in handler
> [Thu Sep 24 23:57:14 2009] [info]
> c:\axis2c-repo\src\modules\mod_addr\addr_in_handler.c
> [Thu Sep 24 23:57:14 2009] [debug]
> c:\axis2c-repo\src\core\engine\phase.c(210) Invoke the handler
> addressing_based_dispatcher within the phase Transport
> [Thu Sep 24 23:57:14 2009] [debug]
> c:\axis2c-repo\src\core\engine\phase.c(210) Invoke the handler
> rest_dispatcher within the phase Dispatch
> [Thu Sep 24 23:57:14 2009] [debug]
> c:\axis2c-repo\src\core\engine\phase.c(210) Invoke the handler
> soap_message_body_based_dispa

Including message context as a parameter in code generated skeleton.

[Uthaiyashankar]

Hi,

Currently, Skeleton generated does not include message context as part
of the method signature. For example, following is an operation
generated in the skeleton.

adb_divResponse_t* axis2_skel_Calculator_div (const axutil_env_t *env,
  adb_div_t *_div1);


However, for some services, we need msg_ctx. Specially, if our service
logic depends on the user name from rampart, we need to access
msg_ctx. Can we add it as an additional parameter? Like given below:

adb_divResponse_t* axis2_skel_Calculator_div (const axutil_env_t *env,
axis2_msg_ctx_t *msg_ctx,
  adb_div_t *_div1);

Thoughts?

Regards,
Shankar

-- 
S.Uthaiyashankar
Software Architect
WSO2 Inc.
http://wso2.com/ - "The Open Source SOA Company"

Re: have to remove patented algorithms (IDEA, MDC2 and RC5) in OpenSSL, will this affect SSL and ws-security?

[Uthaiyashankar]

On Fri, Jul 17, 2009 at 4:58 AM, Gordon Brown wrote:
> Hi List,
>
> A quick question. Due to company policy, I have to remove the patented
> algorithms from OpenSSL and build the library from the source code. The
> algorithms I need to remove are the following:  IDEA, MDC2 and RC5. I am
> wondering if this removal will affect the support of SSL in axis2/c and
> ws-security in rampart/c.

These algorithms are not used by Axis2/C or Rampart/C. AFAIK, removing
these algorithms will not affect Axis2/C and Rampart/C.

Regards,
Shankar


>
> Please advise. Thanks in advance!
>
> Gordon
>



-- 
S.Uthaiyashankar
Software Architect
WSO2 Inc.
http://wso2.com/ - "The Open Source SOA Company"

Re: specifying the interface of the Axis2 web server

[Uthaiyashankar]

Hi Patrick Cosmo,

Thank you for the explanation. Current implementation does not have
support for passing interface information. It will just get one of the
interface available in the system. Possibly, we can add this (sending
which interface to be used) as a feature. Can you create a jira for
this new feature?

Regards,
Shankar

On Tue, Jul 7, 2009 at 12:47 PM, Patrick Cosmo wrote:
> Hi,
>
> I'm using Axis2/C version 1.6.0.
>
> Here's my question: I have a server with 2 NICs (Network Interface Cards) on 
> it. One NIC has the public IP address 207.102.214.78 (for example), and the 
> other NIC has the private IP address 192.168.3.1.
>
> So, my server has 2 IP addresses.
>
> I'm using Axis2/C to build a service that supports a WSDL/SOAP API. So, I'm 
> not using Apache Httpd or IIS, rather I'm using the "axis2_http_server.exe".
>
> More specifically, I'm using the same code used to build the Axis2/C 
> "axis2_http_server.exe", but I'm embedding this code in my own application by 
> building the axis2/c code as a library that my application links to, and 
> starting the service using the same code found in the main( ) method of:
>
> "axis2c\src\core\transport\http\server\simple_axis2_server\http_server_main.c"
>
> But since I've not modified the code at all, for all intents and purposes 
> this is just the "axis2_http_server.exe" server being run from inside another 
> application.
>
> Although one advantage I have is that if the "axis2_http_server.exe" does not 
> support a command line switch allowing me to configure the interface, but 
> DOES (?) provide a programmatic way of setting the interface, then I can take 
> advantage of that.
>
> So, what I need to be able to do is "configure" or somehow "tell" the 
> axis2_http_server what IP address(es) it should listen at for client requests.
>
> Is there any way to do this?
>
> thanks,
> Patrick Cosmo
> Incognito Software Inc.
> Senior Software Design Engineer
> T: +1(604)678-2855
> F: +1(604)688-4339
> E: pco...@incognito.com
> www.incognito.com
>
>
>
> -Original Message-
> From: uthaiyashan...@gmail.com [mailto:uthaiyashan...@gmail.com] On Behalf Of 
> Uthaiyashankar
> Sent: Monday, July 06, 2009 10:59 PM
> To: Apache AXIS C Developers List
> Subject: Re: specifying the interface of the Axis2 web server
>
> On Mon, Jul 6, 2009 at 10:53 PM, Patrick Cosmo wrote:
>> On a multi-homed machine, if I want the web server to listen on only
>> one of the interfaces (specified by IP address), is there a way to do this?
>
> I didn't get the question right. Can you explain a bit? Is it related to 
> Apache Httpd or IIS? Which version of Axis2/C you are using?
>
> Regards,
> Shankar
>
>>
>>
>
>
>
> --
> S.Uthaiyashankar
> Software Architect
> WSO2 Inc.
> http://wso2.com/ - "The Open Source SOA Company"
>



-- 
S.Uthaiyashankar
Software Architect
WSO2 Inc.
http://wso2.com/ - "The Open Source SOA Company"

Re: specifying the interface of the Axis2 web server

[Uthaiyashankar]

On Mon, Jul 6, 2009 at 10:53 PM, Patrick Cosmo wrote:
> On a multi-homed machine, if I want the web server to listen on only one of
> the interfaces (specified by IP address), is there a way to do this?

I didn't get the question right. Can you explain a bit? Is it related
to Apache Httpd or IIS? Which version of Axis2/C you are using?

Regards,
Shankar

>
>



-- 
S.Uthaiyashankar
Software Architect
WSO2 Inc.
http://wso2.com/ - "The Open Source SOA Company"

Re: wrong braces in samples/configure.ac?

[Uthaiyashankar]

Hi Saravanan,

Thank you for providing the patch.

Sorry to bother you, but can you create a jira [1] and attach this
patch? It is easy to manage and keep track.

Regards,
Shankar

[1] https://issues.apache.org/jira/browse/AXIS2C

On Sun, Jul 5, 2009 at 9:22 PM, T. P. Saravanan wrote:
>
> I feel the braces are wrong in some places in samples/configure.ac.
> Diffs below.  Somebody with more autoconf knowledge merge it, if
> appropriate.
>
> ---
>
> Index: samples/configure.ac
> ===
> --- samples/configure.ac        (revision 791255)
> +++ samples/configure.ac        (working copy)
> @@ -85,7 +85,7 @@
>  [  --with-axis2[=PATH]     Find the AXIS2 header files in 'PATH'.
>     'PATH' should point to AXIS2 include files location.
>     If you omit the '=PATH' part completely, the configure script will
> search
> -    '$(AXIS2C_HOME)/include/axis2-1.6.0' for AXIS2 headers.],
> +    '${AXIS2C_HOME}/include/axis2-1.6.0' for AXIS2 headers.],
>  [ case "$withval" in
>   no)
>     AC_MSG_RESULT(no)
> @@ -95,9 +95,9 @@
>     dnl Find axiom include dir in the path
>     if test -d $withval; then
>         axis2inc="-I$withval"
> -    dnl else find the axiom include dir in $(AXIS2C_HOME)/include
> -    elif test -d '$(AXIS2C_HOME)/include'; then
> -        axis2inc="-I$(AXIS2C_HOME)/include/axis2-1.6.0"
> +    dnl else find the axiom include dir in ${AXIS2C_HOME}/include
> +    elif test -d '${AXIS2C_HOME}/include'; then
> +        axis2inc="-I${AXIS2C_HOME}/include/axis2-1.6.0"
>     else
>         AC_MSG_ERROR(could not find axis2. stop)
>     fi
>
>
> ---
>
> Regards,
> Saravanan.
>



-- 
S.Uthaiyashankar
Software Architect
WSO2 Inc.
http://wso2.com/ - "The Open Source SOA Company"

Re: soap in client call contains gabage character -- A critical bug in guththila writer

[Uthaiyashankar]

Hi Gordon,

I'll have a look. Can you create a jira and attach the patch and the test code?

Regards,
Shankar

On Mon, Jun 8, 2009 at 11:40 PM, Gordon Brown wrote:
> Can anyone in the development team please take a look at this one bug in
> Guththila component?
> At least the potential fix I provided in this message thread?
>
> ==
> The potential fix is to define GUTHTHILA_BUF_POS as the following:
>
>      if ((_buffer)->pre_tot_data > _pos)
>       return ((_buffer)->buff[(_buffer)->cur_buff-1] + _pos);
>  else
>       return ((_buffer)->buff[(_buffer)->cur_buff] + _pos -
> (_buffer)->pre_tot_data);
> ==
> It is a problem in the buffer management, so without fixing this bug, users
> should not use guththila at this point.
>
> Thanks!
> Gordon
> 
> From: Gordon Brown 
> To: axis-c-dev@ws.apache.org; shan...@wso2.com; sam...@wso2.com
> Cc: axis-c-u...@ws.apache.org
> Sent: Friday, June 5, 2009 2:15:42 PM
> Subject: Re: soap in client call contains gabage character -- A critical bug
> in guththila writer
>
> OK, since no one reply to my question, I have to debug the code and found
> out that guththila has a bug in managing buffer when seriazlize thea axiom
> tree (the soap structure) before actually send out the request, and I have a
> potential fix. This is really a critical bug I think, so I hope some
> developers can take a look at this problem. I am attaching the test
> input data and code snappet to reproduce the problem.
>
> Basically, the bug occurs in guththila_xml_writer.c.
> The guththila_xml_writer (I call it the soap serializer) maintains an array
> of buffers dynamically when it writes the soap structure into the buffers.
> The bug will occur in the following situation:
>
> Let's say I have an element 12345
> somewhere in the soap structure. Now before this element, there are lots of
> other elements, and when the  guththila_xml_writer  trys to process this
> element, the first buffer is ALMOST full, it does not have enough space
> to write the whole element name  (the start tag) into the
> buffer, it has to create a new buffer, so it writes  first buffer (still a few more bytes left empty), and writes "doDeleteFirst"
> at the very beginning of the second buffer.
>
> The first buffer (Buffer length 16384):
> --
> |**
> The second buffer (Buffer length 32768):
> ---
> |doDeleteFirst-|
>
> As the second buffer becomes the current buffer, when the writer trys to
> process the end tag (),  it uses an elem stack to track
> the namespace prefix and localname as in the following code: (starting from
> line 1396)
>
>
>   elem->name = guththila_tok_list_get_token(&wr->tok_list, env);
>
>   elem->prefix = guththila_tok_list_get_token(&wr->tok_list, env);
>
>   elem->name->start = GUTHTHILA_BUF_POS(wr->buffer, elem_start);
>
>   elem->name->size = elem_len;
>
>   elem->prefix->start = GUTHTHILA_BUF_POS(wr->buffer,
> elem_pref_start);
>
>   elem->prefix->size = pref_len;
>
>
> The macro GUTHTHILA_BUF_POS  is defined as this:
>
> #ifndef GUTHTHILA_BUF_POS
> #define GUTHTHILA_BUF_POS(_buffer, _pos)
>  ((_buffer).buff[(_buffer).cur_buff] + _pos - (_buffer).pre_tot_data)
> #endif
> The bug occurs when it calcuate elem->prefix->start =
> GUTHTHILA_BUF_POS(wr->buffer, elem_pref_start):
>
> The elem_pref_start has a value of 16375, the pre_tot_data has a value of
> 16379 (the first buffer length is 16384), they are calculated based on the
> first buffer data, but the current buffer is the second one, so
> elem->prefix->start points to gabage!
>
> I hope this makes sense to you. Use my test case you will see this quickly.
> When you run the same XML data I attached, first set a break point at line
> 392 in the file guththila_xml_writer_wrapper, and set the hit count as 514
> in the break properties (the 514th element in ), then
> debug step by step.
>
> The potential fix is to define GUTHTHILA_BUF_POS as the following:
>
>      if ((_buffer)->pre_tot_data > _pos)
>       return ((_buffer)->buff[(_buffer)->cur_buff-1] + _pos);
>  else
>       return ((_buffer)->buff[(_buffer)->cur_buff] + _pos -
> (_buffer)->pre_tot_data);
> GUTHTHILA_BUF_POS is used everywhere, so I really hope some developer can
> take over this case and fix it!
>
> Thanks!
> Gordon
>
> 
> From: Gordon Brown 
> To: axis-c-u...@ws.apache.org
> Cc: axis-c-dev@ws.apache.org
> Sent: Wednesday, June 3, 2009 12:49:21 AM
> Subject: soap in client call contains gabage character -- Very very puzzling
>
> Hi All,
>
> I need urgent help with a

[ANN][Rampart/C] Apache Rampart/C 1.3.0 Released

[Uthaiyashankar]

We are pleased to announce the release of Apache Rampart/C version 1.3.0.
You can download this release from
http://ws.apache.org/rampart/c/download.cgi

Key features
-
1. Ability to send and verify UsernameTokens with
- Username and PlainText password
- Username and Digested password

2. Ability to send Timestamp tokens

3. SOAP message encryption
- With derived key support for improved security
- Symmetric and Asymmetric modes of operations
- Support for AES and Tripple DES encryption
- Signature encryption
- Keys encryption

4. SOAP message signature
- XML signature with RSA-SHA1
- Message authentication with HMAC-SHA1
- Signature confirmation support
- SOAP Header signing

5. WS-Security Policy (spec 1.1 & spec 1.2) based configurations
- Support for both Symmetric as well as Asymmetric policy bindings
- Support for different modes of key identifiers
- Support for different algorithm suites
[Basic128, Basic 192, Basic256, TrippleDES, Basic128Rsa15,
Basic192Rsa15,Basic256Rsa15, TripleDesRsa15]
- Support for IssuedToken assertion in client side.
- Support for SAMLToken assertion.

6. Replay detection support
- Easy to use built-in replay detection module
- Ability to deploy a customized replay detection module

7. Different protection orders
- Encrypt before signing
- Sign before encrypting

8. Extensible modules
- Password callback module
- Authentication module
- Credentials module
- Replay detection module
- Secure conversation token module

9. Keys management
- Support for X509 token profile
- Support for Key identifiers, Thumb prints, Issuer/Serial pairs,
Embedded and Direct references
- Support for PKCS12 keystore

10. WS-Secure Conversation Language support
- Establishing Security Context and thereby maintaining a session
- Per message key derivation
- Support for stored securtiy context token
- Rahas module support to give STS functionality to a service

11. WS-Trust Language support
- Security Token Services (STS)
- STS Client
- Server and Client entrophy support

12. SAML Support
- Support for Creation and Processing of SAML Core 1.1 Assertions
- SAML Token as Sign Supporting Token
- Signing and Encryption with SAML

10. Other
- Easy to use deployment scripts
- A comprehensive set of samples

Major Changes Since Last Release

1. WS-Secure Conversation Language support
2. WS-Trust Language support
3. Rahas module to give STS support to a service
4. PKCS12 Keystore support
5. Security Policy 1.2 support
6. Memory leak fixes
7. Many bug fixes

Apache Rampart/C 1.3.0 works with the Apache Axis2/C 1.6.0
http://ws.apache.org/axis2/c/download.cgi

Issues can be reported here.
http://issues.apache.org/jira/browse/RAMPARTC

We welcome your early feedback.
Thank you for your interest in Rampart/C.

--Apache Rampart/C Team--
http://ws.apache.org/rampart/c/

Re: [VOTE][Rampart/C] Apache Rampart/C 1.3.0 Release

[Uthaiyashankar]

Hi,

The vote thread has being open for more than 72 hours to vote. We got 8
votes for the release[1]. This includes 3 PMC votes. Therefore release
artifacts are ready for release and I am closing this vote thread and
will go ahead with the release.

Vote Summery
---
PMC Votes  3
Non-PMC Votes   5
Total Votes  8
-1's  0

Thank you everyone for voting Rampart/C 1.3.0.

Regards,
Shankar


[1] http://www.mail-archive.com/axis-c-dev@ws.apache.org/msg16715.html

On Tue, May 19, 2009 at 12:12 PM, Uthaiyashankar  wrote:
> Hi,
>
> I have uploaded the Apache Rampart/C 1.3.0 release artifacts here:
> http://people.apache.org/~shankar/rampartc/1_3_0/take1/
>
> The key is here:
> http://people.apache.org/~shankar/rampartc/1_3_0/take1/KEYS
>
>
> Please test, review and vote on the release artifacts for Apache
> Rampart/C 1.3.0 release.
> Please test it with Apache Axis2/C 1.6.0, which can be downloaded from here:
> http://ws.apache.org/axis2/c/download.cgi
>
> Here is my vote +1.
>
> Regards,
> Shankar
>
> --
> S.Uthaiyashankar
> Software Architect
> WSO2 Inc.
> http://wso2.com/ - "The Open Source SOA Company"
>



-- 
S.Uthaiyashankar
Software Architect
WSO2 Inc.
http://wso2.com/ - "The Open Source SOA Company"

[VOTE][Rampart/C] Apache Rampart/C 1.3.0 Release

[Uthaiyashankar]

Hi,

I have uploaded the Apache Rampart/C 1.3.0 release artifacts here:
http://people.apache.org/~shankar/rampartc/1_3_0/take1/

The key is here:
http://people.apache.org/~shankar/rampartc/1_3_0/take1/KEYS


Please test, review and vote on the release artifacts for Apache
Rampart/C 1.3.0 release.
Please test it with Apache Axis2/C 1.6.0, which can be downloaded from here:
http://ws.apache.org/axis2/c/download.cgi

Here is my vote +1.

Regards,
Shankar

-- 
S.Uthaiyashankar
Software Architect
WSO2 Inc.
http://wso2.com/ - "The Open Source SOA Company"

Re: when Basic authentication is on, each cleint call sends out two request to server

[Uthaiyashankar]

Hi Gordon,

 This is absolutely unacceptable. This means that Basic authentication is
> not supported in axis2/c.
>
> I was browsing the bug database and noticed that there is a bug reported (
> https://issues.apache.org/jira/browse/AXIS2C-1244)
> for this problem. Is there any plan to resolve this issue?
>


Yes, we have to fix it before next release.

Regards,
Shankar


-- 
S.Uthaiyashankar
Software Architect
WSO2 Inc.
http://wso2.com/ - "The Open Source SOA Company"

[Rampart/C] Apache Rampart/C 1.3.0 RC1

[Uthaiyashankar]

Hi,

I have packed and uploaded Apache Rampart/C 1.3.0 RC1 here [1]. Please test
it with Apache Axis2/C 1.6.0 here [2], and send your feedback.

Regards,
Shankar

[1]http://people.apache.org/~shankar/rampartc/1_3_0/rc1/
[2]http://ws.apache.org/axis2/c/download.cgi


-- 
S.Uthaiyashankar
Software Architect
WSO2 Inc.
http://wso2.com/ - "The Open Source SOA Company"

Re: [VOTE][AXIS2]Apache Axis2/C 1.6.0 Release artificats - Take2

[Uthaiyashankar]

Hi,

I tested in Windows.

Here is my vote +1.

Regards,
Shankar

On Fri, Apr 17, 2009 at 4:27 PM, Manjula Peiris  wrote:

> Hi,
>
> I have uploaded the Apache Axis2/C 1.6.0 release artifacts here.
>
> http://people.apache.org/~manjula/release/1.6.0/
>
> The keys are here.
>
> http://people.apache.org/~manjula/release/1.6.0/KEYS
>
> If the release artifacts are fine please vote for Axis2/C 1.6.0 release.
>
> Here is my vote +1.
>
> Thanks,
> -Manjula
>
>
>
> --
> Manjula Peiris
> Senior Software Engineer
> WSO2 Inc.
> Oxygenating the Web Service Platform.
> http://wso2.org/
> Blog: http://manjula-peiris.blogspot.com/
>
>


-- 
S.Uthaiyashankar
Software Architect
WSO2 Inc.
http://wso2.com/ - "The Open Source SOA Company"

Re: Axis2/C 1.6.0 RC2

[Uthaiyashankar]

Hi Manjula,

There are some issues
(1) Sample binary location is given as $AXIS2C_HOME/bin/samples in INSTALL
file. It has to be changed according to current folder structure
(2) Folder structure given in section 2.2 (Using Binary Release), 2.3.2
(Compiling the Source) of INSTALL file is not correct. Again, has to be
according to current folder structure.
(3) dual samples are crashing in windows
(4) Linux binary distribution's README and INSTALL file contents are wrong.
It contains tcpmon contents.
(5) Binary distributions do not have ChangeLog file (Do we need them? I
think we should)
(6) Sample binary location mentioned in html documents are wrong.

Regards,
Shankar




On Tue, Mar 10, 2009 at 11:16 AM, Manjula Peiris  wrote:

> Hi all,
>
> I have packed and uploaded Apache Axis2/C 1.6.0 RC2 here [1]. Please
> test and send your feedback.
>
> [1] 
> http://people.apache.org/~manjula/release/1.6.0/rc2/
>
> Thanks,
> -Manjula.
>
>
>
> --
> Manjula Peiris
> Senior Software Engineer
> WSO2 Inc.
> Oxygenating the Web Service Platform.
> http://wso2.org/
> Blog: http://manjula-peiris.blogspot.com/
>
>


-- 
S.Uthaiyashankar
Software Architect
WSO2 Inc.
http://wso2.com/ - "The Open Source SOA Company"

Re: downloaded axis2/c 1.4 cannot load rampart/c module when start axis2_http_serve

[Uthaiyashankar]

Hi,

Rampart/C 1.2 binary was built using openssl 0.9.8d. It will only work with
versions 0.9.8d or 0.9.8e. If you have any other version, you have to get
the Rampart/C source and build.

Regards,
Shankar

On Thu, Mar 12, 2009 at 5:49 AM, Raymond Zhou  wrote:

> Hi All,
>
> I downloaded axis2/c 1.4 binary build and rampart/c 1.2 binary build, and I
> followed steps to do the configurations, I am having trouble starting
> axis2_http_server.exe when I engaged rampart/c. If I don't engage rampart/c,
> I have no problem at all, I can start the http server, and ran the client
> examples. But when I engaged the rampart/c, I got the following error and
> axis2_http_server.exe won't start:
>
>
>


-- 
S.Uthaiyashankar
Software Architect
WSO2 Inc.
http://wso2.com/ - "The Open Source SOA Company"

Re: Savan/C 1.0 Release

[Uthaiyashankar]

+1 for the release

Regards,
Shankar

On Thu, Mar 5, 2009 at 10:19 AM, Damitha Kumarage wrote:

> Hi devs,
>
> I propose we do a Apache Savan/C 1.0 release. I would like to be the
> release manager.
> Currently following features are implemented
>
>  1. Support for WS-Eventing Specification August 2004.
>  2. Support for Subscribe, Unsubscribe, Renew and GetStatus operations.
>  3. Support for subscription management endpoint which could be the
> Event Source itself or separate subscription management endpoint.
>  4. Pluggable storage managers. Currently support three storage managers
> namely
>  - Sqlite based embedded storage manager
>  - Service based storage manager.
>  - WSO2 registry based storage manager.
>
>  5. Pluggable filtering support for server side.
>  6. Interoperability with Apache Savan/Java implementation.
>  7. Interoperablity with WSO2 ESB/Eventing stack.  6. Support for both SOAP
> 1.1 and 1.2.
>  7. Comprehensive samples to test scenarios.
>  8. Documentation
>
> Your suggestions are welcome.
>
> Thanks,
> Damitha.
> --
> __
>
> Damitha Kumarage
> http://people.apache.org/
> __
>



-- 
S.Uthaiyashankar
Software Architect
WSO2 Inc.
http://wso2.com/ - "The Open Source SOA Company"

Re: [Fwd: Re: client dynamic invocation]

[Uthaiyashankar]

On Thu, Mar 5, 2009 at 9:31 AM, Manjula Peiris  wrote:

> Hi,
>
> Since we have removed Wooden and XMLschema code long time back, there is
> no point of keeping this function. So I would like to remove this from
> the API. WDYT ?



+1

Regards,
Shankar


>
>
>
>
> --
> Manjula Peiris
> Senior Software Engineer
> WSO2 Inc.
> Oxygenating the Web Service Platform.
> http://wso2.org/
> Blog: http://manjula-peiris.blogspot.com/
>
>
> -- Forwarded message --
> From: Manjula Peiris 
> To: Apache AXIS C User List 
> Date: Wed, 04 Mar 2009 10:27:35 +0530
> Subject: Re: client dynamic invocation
> Actually this function is not usable. Axis2/C uses WSDL2C tool comes
> with Axis2/Java to generate code. You can't just give a WSDL to Axis2/C
> alone and expect for dynamic invocation. We should remove this function.
>
> -Manjula.
>
>
> On Tue, 2009-03-03 at 16:41 +, Philippe Brun (perso) wrote:
> > Manjula Peiris a écrit :
> > > On Tue, 2009-03-03 at 12:10 +, Philippe Brun (perso) wrote:
> > >> I'm new to webservices. Not that it is part of my use case, just to
> set up the background :-)
> > >>
> > >> I'm trying to access a webservice to send SMSes. The provider supplies
> a php example which retrieves
> > >> the wsdl file and invokes the ws dynamically. I was trying to
> reproduce this.
> > >
> > > So you should start from WSDL2C tool and generate code for the WSDL.
> >
> > Sorry, my explanation wasn't clear : for me, dynamic was at runtime not
> for coding.
> > axis2_svc_client_create_for_dynamic_invocation takes a .wsdl as one of
> its parameters, so it sounded ok.
> >
> > >
> > >> Manjula Peiris a écrit :
> > >>> What is your use case ?
> > >>>
> > >>> On Tue, 2009-03-03 at 10:13 +, Philippe Brun (perso) wrote:
> >  Hi,
> > 
> >  I'm trying to use axis2_svc_client_create_for_dynamic_invocation,
> but it fails with a 0 error code.
> > 
> >  Looking at the code in svc_client.c, it appears that it fails after
> :
> >   svc_client->options = axis2_options_create(env);
> >  The test fails because svc_client->svc is NULL
> >   if (svc_client->svc)
> > 
> >  I'm certainly missing something. Can anyone help ?
> > 
> >  Thanks in advance
> >  Philippe
> > >>>
> > >
> > >
>
>
>


-- 
S.Uthaiyashankar
Software Architect
WSO2 Inc.
http://wso2.com/ - "The Open Source SOA Company"

Re: Axis2/C 1.6.0 RC1

[Uthaiyashankar]

Hi,

On a second thought, $AXIS2C_HOME/bin/samples/lib does not make much sense
:)

So we have two options,

(1) create $AXIS2C_HOME/samples and put all sample binary(currently inside
$AXIS2C_HOME/bin/samples) inside $AXIS2C_HOME/samples/bin and put sample
library inside $AXIS2C_HOME/samples/lib

(2) put all the sample libraries inside $AXIS2C_HOME/bin/samples

WDYT?

Regards,
Shankar

On Thu, Mar 5, 2009 at 10:13 AM, Uthaiyashankar  wrote:

> Hi Dinesh,
>
> On Thu, Mar 5, 2009 at 9:34 AM, Dinesh Premalal wrote:
>
>> Hi,
>>
>> Manjula Peiris  writes:
>> > Even though they are libraries those are samples. For example in
>> > Rampart/C we installed passwordcallback libraries in bin/samples. Shall
>> > I make them to be installed in bin/samples or is there any other better
>> > place ?
>>
>> 1. 'bin' directory
>>
>>   I think it should contains executables only. In this case those
>>   directories contains shared libraries therefore it is not the right
>>   place.
>>
>> 2. 'lib' directory
>>
>>   This is the place shared library should place. However these are
>>   just shared libraries of a sample(ie. it is not a part of
>>   Axis2/C core).
>>
>> Due to these reason I think those directories should place under
>> samples/lib. Please correct me If I'm mistaken.
>
>
>
> What you are suggesting is $AXIS2C_HOME/bin/samples/lib or
> $AXIS2C_HOME/samples/lib?
>
> I think, it is better to put it inside $AXIS2C_HOME/bin/samples/lib (we
> don't have $AXIS2C_HOME/samples upto now)
>
> Regards,
> Shankar
>
>
>
>>
>>
>> thanks,
>> Dinesh
>>
>
>
>
> --
> S.Uthaiyashankar
> Software Architect
> WSO2 Inc.
> http://wso2.com/ - "The Open Source SOA Company"
>
>
>


-- 
S.Uthaiyashankar
Software Architect
WSO2 Inc.
http://wso2.com/ - "The Open Source SOA Company"

Re: Axis2/C 1.6.0 RC1

[Uthaiyashankar]

Hi Dinesh,

On Thu, Mar 5, 2009 at 9:34 AM, Dinesh Premalal  wrote:

> Hi,
>
> Manjula Peiris  writes:
> > Even though they are libraries those are samples. For example in
> > Rampart/C we installed passwordcallback libraries in bin/samples. Shall
> > I make them to be installed in bin/samples or is there any other better
> > place ?
>
> 1. 'bin' directory
>
>   I think it should contains executables only. In this case those
>   directories contains shared libraries therefore it is not the right
>   place.
>
> 2. 'lib' directory
>
>   This is the place shared library should place. However these are
>   just shared libraries of a sample(ie. it is not a part of
>   Axis2/C core).
>
> Due to these reason I think those directories should place under
> samples/lib. Please correct me If I'm mistaken.



What you are suggesting is $AXIS2C_HOME/bin/samples/lib or
$AXIS2C_HOME/samples/lib?

I think, it is better to put it inside $AXIS2C_HOME/bin/samples/lib (we
don't have $AXIS2C_HOME/samples upto now)

Regards,
Shankar



>
>
> thanks,
> Dinesh
>



-- 
S.Uthaiyashankar
Software Architect
WSO2 Inc.
http://wso2.com/ - "The Open Source SOA Company"

Re: rampart/c compilation error related to openSSL

[Uthaiyashankar]

Hi,

It is a known problem in openssl (NOT in Rampart/C :D ) . Have a look at [1]
to solve it.

Regards,
Shankar

[1] http://wso2.org/forum/thread/3861


On Tue, Feb 24, 2009 at 6:37 AM, Raymond Zhou  wrote:

> Hi All,
>
> I am using open source axis2/c and rampart/c to build a secure web service
> client.  I am now getting some openSSL related compilation errors in windows
> XP, here are the details:
>
> (1) If I downloaded the binary version of openSSL, I can compile axis2/c
> and rampart/c without any problem, and the functionalities seem work fine.
>
> (2) If I downloaded openSSL source and compile it by myself (I have to do
> this in order to avoid a name comflict of libeay32.dll with another
> product), I can compile the source without any problem, but I will get
> compilation errors when I try to compile rampart/c (axis2/c went fine). I
> tried openSSL-0.9.8.h and openSSL-0.9.8i, same problem. The error messages
> are like the following:
>
> C:\OpenSSL\include\openssl\x509.h(207) : error C2059: syntax error : 'type'
> C:\OpenSSL\include\openssl\x509.h(929) : error C2059: syntax error : 'type'
> C:\OpenSSL\include\openssl\x509.h(929) : error C2143: syntax error :
> missing ')' before '('
> C:\OpenSSL\include\openssl\x509.h(929) : error C2143: syntax error :
> missing ')' before '('
> C:\OpenSSL\include\openssl\x509.h(929) : error C2091: function returns
> function
> C:\OpenSSL\include\openssl\x509.h(929) : error C2091: function returns
> function
>  .
>
> I noticed that the x509.h from my own build is different from the one in
> the downloaded binary version (attached in this message).
>
> The commands I used to compile the openSSL source is copied from the file
> INSTALL.W32, specifically as the following:
>
> (1) perl Configure VC-WIN32 --prefix=c:/openssl/dir
> (2) ms\do_ms
> (3) nmake -f ms\ntdll.mak
> (4) nmake -f ms\ntdll.mak install
>
>  Any clues what I am getting the compilation errors?
>
> Thanks much in advance.
>
> Raymond
>
>


-- 
S.Uthaiyashankar
Software Architect
WSO2 Inc.
http://wso2.com/ - "The Open Source SOA Company"

Re: Values of message context are not persisting

[Uthaiyashankar]

Hi,

Can you provide more details? Are you using simple axis server or http?
Which version of Axis2/C you are using? Give the code segment which is
storing and retrieving.

Regards,
Shankar

On Fri, Feb 13, 2009 at 1:24 PM, Nair, Anushree wrote:

>  Hello,
>
>
>
>In order to support Sessions I added a parameter  *<< axis2_char_t*
> Session_ID>>* in the message context structure described in the file 
> *msg_ctx.c
> and msg_ctx.h*.
>
>
>
>I also added the corresponding set and get functions to read this
> parameter.
>
>
>
>   Now I want to set *the Session_ID* in *Session_In_Handler* and read
> these later in the message receiver.
>
>
>
>   For doing this, before setting the property I make the msg_ctx keep alive
> by using the command
>
>
>
> *status = axis2_msg_ctx_set_keep_alive(msg_ctx, env, 1);*
>
>
>
>  Now when I read the msg_ctx in my message receiver, I am able to read the
> message context original parameters like *axis2_svc_grp_ctx,
> axis2_svc_grp_ctx_id*, etc successfully but
>
>
>
>   I the parameter that I have added (Session_ID) gives me a garbage value.
>
>
>
>  Can somebody please instruct me what I am doing wrong. I need some
> assistance here urgently.
>
>
>
>  Thanx,
>
> Shivam.
>
>
>



-- 
S.Uthaiyashankar
Software Architect
WSO2 Inc.
http://wso2.com/ - "The Open Source SOA Company"

Re: Operation and message level policies in client side

[Uthaiyashankar]

On Thu, Jan 29, 2009 at 11:23 PM, Manjula Peiris  wrote:

> On Thu, 2009-01-29 at 15:45 +0500, Supun Kamburugamuva wrote:
> > How about adding another method with a name like
> > axis2_svc_client_set_policy_with_type. We can have a default value for
> > axis2_policy_types in the first method.
>
> +1. So this will be an API addition rather than an API change. And most
> users are using axis2_svc_client_set_policy.


+1

Regards,
Shankar


>
>
> >
> > Supun.
> >
> >
> > On Thu, Jan 29, 2009 at 2:49 PM, Manjula Peiris 
> > wrote:
> > Hi devs,
> >
> > In order to fix
> > https://issues.apache.org/jira/browse/AXIS2C-619 we need
> > to change the following function signature in the svc_client
> > API.
> >
> > AXIS2_EXTERN axis2_status_t AXIS2_CALL
> > axis2_svc_client_set_policy(
> >axis2_svc_client_t * svc_client,
> >const axutil_env_t * env,
> >neethi_policy_t * policy)
> >
> > I am proposing to add the policy_type defined in
> > axis2_policy_include.h
> > as a parameter.
> >
> > So the function signature will become,
> >
> > AXIS2_EXTERN axis2_status_t AXIS2_CALL
> > axis2_svc_client_set_policy(
> >axis2_svc_client_t * svc_client,
> >const axutil_env_t * env,
> >neethi_policy_t * policy,
> >axis2_policy_types type)
> >
> > WDYT ?
> >
> > Thanks,
> > -Manjula.
> >
> >
> > --
> > Manjula Peiris
> > Senior Software Engineer
> > WSO2 Inc.
> > Oxygenating the Web Service Platform.
> > http://wso2.org/
> > Blog: http://manjula-peiris.blogspot.com/
> >
>
>


-- 
S.Uthaiyashankar
Software Architect
WSO2 Inc.
http://wso2.com/ - "The Open Source SOA Company"

Xpath header files location

[Uthaiyashankar]

Hi devs,

Is there any particular reason why axiom_xpath.h is inside axiom/include and
all other xpath related header files are inside axiom/src/xpath/ ? Can't we
have all the header files inside axiom/include?

Regards,
Shankar

-- 
S.Uthaiyashankar
Software Architect
WSO2 Inc.
http://wso2.com/ - "The Open Source SOA Company"

Re: Can I always assume axis2_desc_t children are axis2_msg_t ?

[Uthaiyashankar]

On Tue, Jan 6, 2009 at 10:32 AM, Damitha Kumarage wrote:

> Manjula Peiris wrote:
>
>> Hi,
>>
>> While fixing https://issues.apache.org/jira/browse/AXIS2C-1313
>> I came across $subject. Currently axis2_desc_add_child() method call
>> only from op.c. But according to the Axis2 architecture it shouldn't
>> only be axis2_msg_t. WDYT ?
>>
>>
> AFAIK it could be only axis2_msg_t. Perhaps you are wondering why in that
> method signature child is a void pointer without specifically being a
> axis2_msg_t. And as I remember this was originally designed to be used for
> any parent in the description hierarchy to add a child. However it was not
> used in that way.
> So may be to avoid confusion we may pass axis2_msg_t there instead of void
> pointer.


+1. Even when freeing, it is blindly converting the void* ro axis2_msg_t *.
It is better to change it to axis2_msg_t*.

Regards,
Shankar


>
>
> thanks,
> Damitha
>
>> Thanks,
>> -Manjula
>>
>>
>>
>
>
> --
> __
>
> Damitha Kumarage
> http://people.apache.org/
> __
>



-- 
S.Uthaiyashankar
Software Architect
WSO2 Inc.
http://wso2.com/ - "The Open Source SOA Company"

Re: Problem with build axis2c 1.5.0 on Solaris with CC compiler

[Uthaiyashankar]

Hi,

AFAIK, we never tested with cc compiler. Is it possible for you install gcc
and try? You can get gcc from www.sunfreeware.com

Regards,
Shankar

On Tue, Dec 23, 2008 at 8:36 PM, Andriy Vitkovskyy wrote:

> Hi,
>
> I trying to build axis2c 1.5.0 on Solaris 9
>
> I have a problem
>
> checking build system type... sparc-sun-solaris2.9
> checking host system type... sparc-sun-solaris2.9
> checking target system type... sparc-sun-solaris2.9
> 
> make
> .
> cc -shared  .libs/hash.o .libs/allocator.o .libs/env.o .libs/error.o
> .libs/stream.o .libs/log.o .libs/string.o .libs/string_util.o
> .libs/qname.o .libs/array_list.o .libs/linked_list.o .libs/utils.o
> .libs/dir_handler.o .libs/file_handler.o .libs/class_loader.o
> .libs/network_handler.o .libs/file.o .libs/uuid_gen.o
> .libs/thread_pool.o .libs/property.o .libs/types.o .libs/param.o
> .libs/param_container.o .libs/dll_desc.o .libs/url.o .libs/stack.o
> .libs/generic_obj.o .libs/base64.o .libs/uri.o .libs/date_time.o
> .libs/base64_binary.o .libs/properties.o .libs/rand.o
> .libs/date_time_util.o .libs/version.o .libs/duration.o .libs/md5.o
> .libs/http_chunked_stream.o .libs/digest_calc.o -Wl,--whole-archive
> ../src/platforms/unix/.libs/libaxis2_unix.a -Wl,--no-whole-archive
>
> -L/export/home/odugin/sources/odugin/mds2/src/3rdparty/axis2c/src/../../../../intermediate/sunos.cc58/lib/
> -lm -lpthread -lz -ldl -lsocket -lnsl -lc  -xarch=v9 -xarch=v9
> -Wl,-soname -Wl,libaxutil.so.0 -o .libs/libaxutil.so.0.5.0
> ld: fatal: file libaxutil.so.0: open failed: No such file or directory
>
>uname -a
> SunOS ADP 5.9 Generic_118558-10 sun4u sparc SUNW,Ultra-Enterprise
>
>ld -V
> GNU ld version 2.11.2 (with BFD 2.11.2)
>  Supported emulations:
>   elf32_sparc
>   elf64_sparc
>
>
>
> What is wrong?
>
> thanks
>



-- 
S.Uthaiyashankar
Software Architect
WSO2 Inc.
http://wso2.com/ - "The Open Source SOA Company"

Re: RE : RE : Multi-threading

[Uthaiyashankar]

Hi,


Hello Patrick,
>
> > But if I signal the main thread from the callback, to free the
> > resources, the callback might be switched out directly after this
> > signal, and the main thread might free the resources before the
> > callback ended and the axis framework used them.
>
> Yes, this is a pretty serious limitation.  I have been trying to find
> out if Axis2/C provides a way to either know the thread id of the
> communication threads created internally or to be notified exactly when
> the threads exit.  As you suggest, this is treated as an implementation
> detail and we are expected to code without a precise notification of
> when these threads finishes their tasks.
>
> It sounds like you would like to free resources on a per-call basis.  Is
> that right?  I'm quite new to the Axis2/C architecture so perhaps a more
> experienced person could suggest a mechanism that would fit into the
> existing methodology and provide this extra feature.  My impression is
> that the design philosophy so far is to free resources after all calls
> are completed.
>

Current implementation does not provide a way to free resources on a
per-call basis. I agree with Patrick, we should provide a callback to free
the resources.

Regards,
Shankar


>
>
> > With the fd_set in winsock and the select() function, you can wait
> > at a maximum of 64 (current implementation) sockets at once.
> > With I/O Completion Ports you can use one thread for an infinite
> > number of ports... But I think they don't fit well in the modular
> > (transportation) design of axis
>
> That's very interesting.  I'm curious as to more of the details of how
> this functions... If you have one thread waiting on 12 sockets and want
> to make a new call, can this thread begin the next call, or does a
> second thread open the socket and pass the job of waiting on it to the
> first thread?
>
> I think we would all agree that your use case would benefit from adding
> this capability to Axis2/C.  You mention a potential conflict with the
> modular design of Axis; there is also the idea that making such a
> powerful feature accessible to the average programmer using Axis could
> be a challenge.  Maybe the solution would be to add a new communication
> mode instead of changing all asynchronous communication to
> one-thread-multi-socket.  I wish I understood the Axis2/C architecture
> more fully because this would be an interesting area to contribute.
>
> The pleasure is all mine in this conversation.  So far I am learning
> more about winsock :)
>  _
>
> "Ce message est confidentiel, a l'usage exclusif du destinataire
> ci-dessus et son contenu ne represente en aucun cas un engagement de la
> part de AXA, sauf en cas de stipulation expresse et par ecrit de la part
> de AXA. Toute publication, utilisation ou diffusion, meme partielle,
> doit etre autorisee prealablement. Si vous n'etes pas destinataire de ce
> message, merci d'en avertir immediatement l'expediteur."
>
> "This e-mail message is confidential, for the exclusive use of the
> addressee and its contents shall not constitute a commitment by AXA,
> except as otherwise specifically provided in writing by AXA. Any
> unauthorized disclosure, use or dissemination, either whole or partial,
> is prohibited. If you are not the intended recipient of the message,
> please notify the sender immediately."
>



-- 
S.Uthaiyashankar
Software Architect
WSO2 Inc.
http://wso2.com/ - "The Open Source SOA Company"

Re: [Axis2] VOTE Danushka Menikkumbura as Commiter

[Uthaiyashankar]

+1

Regards,
Shankar

On Mon, Dec 1, 2008 at 3:41 PM, Damitha Kumarage <[EMAIL PROTECTED]>wrote:

> Hi Devs,
>
> I would like to nominate Danushka Menikkumbura to be an Axis2/C commiter.
>
> Danushka has implemented AMQP transport for Axis2/C project and he has
> applied several patches to the Axis2/C code base for the same purpose. He
> has also contributed patches to Sandesha2/C and has been active in mailing
> lists.
>
> I am confident that Danushka will continue to be an valuble contributor to
> Axis2/C project.
>
> Following are the links to the patches he submitted for Axis2/C and
> Sandesha2/C projects.
>
> Here is my vote. +1
>
> Thanks,
> Damitha
>
> Axis2/C
> =
>
> [1]https://issues.apache.org/jira/browse/AXIS2C-1300
> [2]https://issues.apache.org/jira/browse/AXIS2C-1299
> [3]https://issues.apache.org/jira/browse/AXIS2C-1298
> [4]https://issues.apache.org/jira/browse/AXIS2C-1293
> [5]https://issues.apache.org/jira/browse/AXIS2C-1292
> [6]https://issues.apache.org/jira/browse/AXIS2C-1291
> [7]https://issues.apache.org/jira/browse/AXIS2C-1193
> [8]https://issues.apache.org/jira/browse/AXIS2C-1191
> [9]https://issues.apache.org/jira/browse/AXIS2C-1131
> [10]https://issues.apache.org/jira/browse/AXIS2C-1104
>
> Sandesha2/C
> 
>
> [1]https://issues.apache.org/jira/browse/SANDESHA2C-71
> [2]https://issues.apache.org/jira/browse/SANDESHA2C-70
> [3]https://issues.apache.org/jira/browse/SANDESHA2C-69
> --
> __
>
> Damitha Kumarage
> http://people.apache.org/
> __
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
S.Uthaiyashankar
Software Architect
WSO2 Inc.
http://wso2.com/ - "The Open Source SOA Company"

Re: printing parts of a node

[Uthaiyashankar]

[EMAIL PROTECTED] wrote:

I tried to understand how I could use the serialize sub tree method but
I don't...
I know how to get the node values but I also need to get the node name,
how can I do this?
  

Hi Indra,

try axiom_element_get_localname  and axiom_element_get_namespace

Regards,
Shankar.


I'm very thankful for a reply

Regards
Indra

-Original Message-
From: Samisa Abeysinghe [mailto:[EMAIL PROTECTED] 
Sent: den 5 november 2008 15:57

To: Apache AXIS C Developers List
Subject: Re: printing parts of a node

[EMAIL PROTECTED] wrote:
  

Hello!
I want to print the parameter names in a node and not the parameter
values. 
For example: 
13 
I want to print or get the hold of: param1 param2 but not 1 and 3


Does anyone know how this can be done?
  



This can be done using the serialize sub tree method. Please have a look

at the node header file.

Samisa...
  

/Indra


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




  

Internal Virus Database is out of date.
Checked by AVG - http://www.avg.com 
Version: 8.0.175 / Virus Database: 270.8.5/1759 - Release Date:


10/31/2008 4:10 PM
  
  




  



--
S.Uthaiyashankar
Software Architect
WSO2 Inc. 
http://wso2.com/ - "The Open Source SOA Company" 



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

Re: a HTTPS/SSL question

[Uthaiyashankar]

Dmitry Goncharov wrote:

Hi,


Dumindu Pallewela wrote:
Anyway, if it is only for testing, what you can do is to follow the 
Axis2/C manual and retrieve the server cert from the server. [1] 
(refer to sec. 13.1.2 Configuration). Well you can do this even if it 
was not for testing, but it is not recommended to do so.


Thanks,
Dumindu.

Why is this not recommended?


What the manual says is, get the certificate from the end point and set 
it as CA certificate. In this case, you are excluding the trust 
verification, or you are doing it manually, which is not recommended, 
since any intruders can impersonate the service (e.g by /DNS Spoofing)/ 
and issue the certificate and thereby get your secret details.


Regards,
Shankar.


Thanks, Dmitry




--
S.Uthaiyashankar
Software Architect
WSO2 Inc. 
http://wso2.com/ - "The Open Source SOA Company" 



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

Re: a HTTPS/SSL question

[Uthaiyashankar]

Hi Vivian,

see my comments...

Vivian Wang wrote:

Hi Dumindu,

So is it hard to provide such an option (turn on/off validation)?
I think this limitation really restrict axis2/c's usage under SSL.
In my case, I would like to access salesforce web service using a WSDL
refered to by the URL:

https://na2.salesforce.com/services/wsdl/metadata

All I know is this URL, and I don't know the CA certificate and server cert, 
and I am not sure if they have one.


They DO have one. otherwise, you can't communicate through https.


 I also have no way to know they server host and port,


use server host as "na2.salesforce.com" and port as "443".  If you are 
on windows,


openssl s_client -connect na2.salesforce.com:443

will give you the certificate. If you are on Linux, check the 
corresponding command in Axis2/C manual.


Regards,
Shankar.


 so I won't be able to get their cert using the openSSL commands listed in the 
axis2/c manual.

Any workarounds?

Thanks!

Vivian


  

Hi Vivian,
Please find my comment inline:

On Wed, Oct 29, 2008 at 11:44 PM, Vivian Wang ><[EMAIL PROTECTED]>wrote:

So is there an option in axis2/c that I can turn off the certificate


validation?
  

No we don't support that at the moment.




I think this is important because from a client point of view, lots of
times when I want to access a web service under SSL using https://.. I
know that is the site I want to go.
  

Yes web browsers do support that, but in reality you don't know if
that truly is the site that you want to access, if you don't have the
server's certificate beforehand. (someone can spoof dns and appear
themselves as https://foo.com). Yes I have neglected about well known
Certificate Authorities for simplicity. If you trust the CA that issued >the
server cert, all you need is the CA's certificate.




And just like you said, browsers will ask you if you want to trust the >site
and I can say yes or no.It would also be very inconvenient for a client >to
have to get the certificate from a service provide (they may not give >you).
  



  

Anyway, if it is only for testing, what you can do is to follow the >Axis2/C
manual and retrieve the server cert from the server. [1] (refer to
sec. 13.1.2 Configuration). Well you can do this even if it was not for
testing, but it is not recommended to do so.



  

Thanks,
Dumindu.



  

[1] http://ws.apache.org/axis2/c/docs/axis2c_manual.html#ssl_client





  


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



  



--
S.Uthaiyashankar
Software Architect
WSO2 Inc. 
http://wso2.com/ - "The Open Source SOA Company" 



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

Re: Rest enhancements

[Uthaiyashankar]

Uthaiyashankar wrote:

Hi,

Thank you very much for the patch. Can you please create a jira in [1] 
and attach the patch file? Then it would be easy to manage and track it.
When attaching the file, remember to select "Grant license to ASF for 
inclusion in ASF works (as per the Apache License 
<http://www.apache.org/licenses/LICENSE-2.0> §5) " option.


Regards,
Shankar.


[1] https://issues.apache.org/jira/browse/AXIS2C



Luís Bilo wrote:

Hi,

I've been also working on some enhancements for axis in order to
support some required features to our project.  We are using axis2/c
module for apache instead of the standalone server, changes are  not
tested for the standalone.

#1 Adds http headers to msg_ctx when using axis2/c module for apache
I noticed however this functionality were only implemented for the
standalone server. When using the axis module for apache  http headers
were not added to the msg_ctx so they were not accessible @ the inflow
handlers level for instance.

#2 Adds forbidden definition tags for http forbidden code which is
missing in standard release

 #define AXIS2_HTTP_RESPONSE_FORBIDDEN_CODE_VAL 403
 #define AXIS2_HTTP_RESPONSE_HTTP_FORBIDDEN_CODE_NAME "Forbidden"
 #define AXIS2_HTTP_RESPONSE_HTTP_FORBIDDEN "403 Forbidden"

#3 Adds support to specify feedback for REST requests, when a module
failure occurs.

This issue is related to the difference between soap and rest
requests. When an inflow handler fails two things can happen depending
on the request type:

- For SOAP requests, the inflow handler chain is broken, and all the
outflow fault handlers are invoked. The response soap envelope
response containing a default fault is built by axis in between these
phases, so we can edit the fault accordingly @ the outflow fault
handlers.
- For REST requests, the inflow handler chain is also broken, but the
outflow fault handlers are not invoked. This is not a problem, and is
probably intended, since unlike soap there is no need to create a soap
envelope. The thing is when this happens it always returned 202
ACCEPTED, which is not enough to provide any feedback to the user who
made the request.

@ the inflow handler is now possible to set the desired status code
desired for the response, extra http headers, and/or http content. It
was already possible before, changes just weren't propagated to the
actual response.

inflow handler example with the patch:
..
// For REST requests
if (doing_rest && AXIS2_FAILURE == result)
{

axis2_msg_ctx_set_status_code(msg_ctx, env,
AXIS2_HTTP_RESPONSE_HTTP_UNAUTHORIZED_CODE_VAL);
AXIS2_LOG_ERROR(env->log, AXIS2_LOG_SI, 
"[Inflow][authentication_in]

HTTP status code unauthorized");
   
axutil_stream_t *stream = axutil_stream_create_basic(env);

axis2_char_t *http_content = axutil_strcat(env,
AXIS2_HTTP_RESPONSE_HTTP_UNAUTHORIZED, "\n", NULL);
axutil_stream_write(stream, env, http_content, 
axutil_strlen(http_content));
axis2_msg_ctx_set_transport_out_stream(msg_ctx, env, 
stream);   
}

return result;

}

I think these features may also be of interest for axis2/c users, at
least for us they seemed important, and would be nice to to have to
patch these to each new release of axis. The diff's follow in
attachment.

Regards,
Luís Bilo
  



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






--
S.Uthaiyashankar
Software Architect
WSO2 Inc. 
http://wso2.com/ - "The Open Source SOA Company" 



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

Re: Rest enhancements

[Uthaiyashankar]

Hi,

Thank you very much for the patch. Can you please create a jira in [1] 
and attach the patch file? Then it would be easy to manage and track it.
When attaching the file, remember to select "Grant license to ASF for 
inclusion in ASF works (as per the Apache License 
 §5) " option.


Regards,
Shankar.

Luís Bilo wrote:

Hi,

I've been also working on some enhancements for axis in order to
support some required features to our project.  We are using axis2/c
module for apache instead of the standalone server, changes are  not
tested for the standalone.

#1 Adds http headers to msg_ctx when using axis2/c module for apache
I noticed however this functionality were only implemented for the
standalone server. When using the axis module for apache  http headers
were not added to the msg_ctx so they were not accessible @ the inflow
handlers level for instance.

#2 Adds forbidden definition tags for http forbidden code which is
missing in standard release

 #define AXIS2_HTTP_RESPONSE_FORBIDDEN_CODE_VAL 403
 #define AXIS2_HTTP_RESPONSE_HTTP_FORBIDDEN_CODE_NAME "Forbidden"
 #define AXIS2_HTTP_RESPONSE_HTTP_FORBIDDEN "403 Forbidden"

#3 Adds support to specify feedback for REST requests, when a module
failure occurs.

This issue is related to the difference between soap and rest
requests. When an inflow handler fails two things can happen depending
on the request type:

- For SOAP requests, the inflow handler chain is broken, and all the
outflow fault handlers are invoked. The response soap envelope
response containing a default fault is built by axis in between these
phases, so we can edit the fault accordingly @ the outflow fault
handlers.
- For REST requests, the inflow handler chain is also broken, but the
outflow fault handlers are not invoked. This is not a problem, and is
probably intended, since unlike soap there is no need to create a soap
envelope. The thing is when this happens it always returned 202
ACCEPTED, which is not enough to provide any feedback to the user who
made the request.

@ the inflow handler is now possible to set the desired status code
desired for the response, extra http headers, and/or http content. It
was already possible before, changes just weren't propagated to the
actual response.

inflow handler example with the patch:
..
// For REST requests
if (doing_rest && AXIS2_FAILURE == result)
{

axis2_msg_ctx_set_status_code(msg_ctx, env,
AXIS2_HTTP_RESPONSE_HTTP_UNAUTHORIZED_CODE_VAL);
AXIS2_LOG_ERROR(env->log, AXIS2_LOG_SI, 
"[Inflow][authentication_in]
HTTP status code unauthorized");

axutil_stream_t *stream = axutil_stream_create_basic(env);
axis2_char_t *http_content = axutil_strcat(env,
AXIS2_HTTP_RESPONSE_HTTP_UNAUTHORIZED, "\n", NULL);
axutil_stream_write(stream, env, http_content, 
axutil_strlen(http_content));
axis2_msg_ctx_set_transport_out_stream(msg_ctx, env, stream);   

}

return result;
}

I think these features may also be of interest for axis2/c users, at
least for us they seemed important, and would be nice to to have to
patch these to each new release of axis. The diff's follow in
attachment.

Regards,
Luís Bilo
  



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



--
S.Uthaiyashankar
Software Architect
WSO2 Inc. 
http://wso2.com/ - "The Open Source SOA Company" 



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

Re: a HTTPS/SSL question

[Uthaiyashankar]

Hi,

When you access an https endpoint, the certificate of that endpoint 
should be validated whether it can be trusted. This validation is based 
on, whether we trust any of the CA's of the certificate. This is same as 
what happened in a browser. If you access any https and if the browser 
can't validate the trust path, it will not allow (or give you a warning) 
to access the end point. AFAIK, in Axis2/C, we give the certificate 
chain file to verify this. I think, soapUI allows you access the 
endpoint without validating the certificate.


Regards,
Shankar


Vivian Wang wrote:

Hi, there,

I have a web service client using axis2/c to access a Salesforce.com web site 
that is protected with SSL (the url starts with https://). I didn't give a 
certificate chain file path in the configuration file axis2.xml, so the web 
service client failed. However, if I use soapUI (a free downloaded web service 
testing tool) to access the same serivce without giving any SSL related setting 
(just like accessing a service starting with http://), it all goes fine. What 
is the difference here? Is there any setting I can do in axis2/c to make it 
work as soapUI?

I noticed another similar thing. When a wsdl parser (from axis-j 1.4) tring to 
retrieve a SSL-protected wsdl (I set it up in TOMCAT) using a URL that starts 
with https:, I have a provide a client keystore (using jsse 
system.setProperty()) otherwise I will get an error saying something like 
trustedstore not found, but soapUI was just fine loading the same wsdl. What's 
really going on?

Any help is much appreciated!

Vivian

   



  


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



  



--
S.Uthaiyashankar
Software Architect
WSO2 Inc. 
http://wso2.com/ - "The Open Source SOA Company" 



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

Re: APIs for ws-security paramenters

[Uthaiyashankar]

Hi Raymond,

Raymond Zhou wrote:

Hi, Uthaiyashankar,
 
I might actually be able to do the patch (providing APIs). But before I go

to talk to my boss,  could you give me some estimates of the scope.
I did not dig deep into the code, but I imagine it shouldn't be that
complicated. I can pass the parameters from axis2/c just like 
rampart/c is currently doing for username/password, right?
  


Yes, you are correct. It is not a complicated stuff. I think you can do 
it in one or two days.


 
Another question: How do I test my web service client to make sure 
ws-security works? I need a web service server that support ws-security,
right? How can I set up and find such a server? Any help is really 
appreciated.
  


You can use policies inside sample 5 and set up the server to test the 
functionality.


Regards,
Shankar.


Thanks a bunch!
Frank

--- On Thu, 10/23/08, Uthaiyashankar <[EMAIL PROTECTED]> wrote:

From: Uthaiyashankar <[EMAIL PROTECTED]>
Subject: Re: APIs for ws-security paramenters
To: [EMAIL PROTECTED]
Cc: "Apache AXIS C Developers List" 
Date: Thursday, October 23, 2008, 5:21 AM

Hi Raymond,

No plans as of now. Will be adding the APIs when time permits.. Do you 
need it urgently? Infact, it would be great if you can provide a patch :)


Regards,
Shankar

Raymond Zhou wrote:
  

Hi, Uthaiyashankar,
 
Thanks much for the info. I am a bit surprised that we can only set the


few parameters programmably. I don't think it's ideal for client users
to set up so many parameters in a complicated xml file in a file system. For my
self, I would certainly like to provide a UI for client users to configure all
the different parameters, just like what soapUI does. but without the rampart
APIs, I would not be able to do that. Any plans that you will be able to provide
the APIs?
  
 
Thanks again!

Raymond

--- On Thu, 10/23/08, Uthaiyashankar <[EMAIL PROTECTED]> wrote:

From: Uthaiyashankar <[EMAIL PROTECTED]>
Subject: Re: APIs for ws-security paramenters
To: "Apache AXIS C Developers List"



  

Cc: [EMAIL PROTECTED], [EMAIL PROTECTED]
Date: Thursday, October 23, 2008, 3:31 AM

Hi Raymond,

For client side, you can set username, password, password type and time 
to live parameters programatically.  However, other options (like 
certificate, key, etc.) have to be set using policy files. We have to 
implement missing options. You can find more details from [1]


Regards,
Shankar

[1] https://issues.apache.org/jira/browse/RAMPARTC-56


Raymond Zhou wrote:
  


Hi there,
 
I am planning to use rampart-c as a module in my axis2/c to support 
ws-security in a web service client application. I know I can 
configure the policy files in the client repository. My question is 
that if all these variables/parameters can be set programmably using 
some sort of APIs. I want to do this because I would like to save the 
parameters in a database tables instead of a local file and I also 
want to be able to develop a UI for users to easily set/edit/change 
the values.
 
Thanks!

Raymond



  
  




  



--
S.Uthaiyashankar
Software Architect
WSO2 Inc. 
http://wso2.com/ - "The Open Source SOA Company" 



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

Re: APIs for ws-security paramenters

[Uthaiyashankar]

Hi Raymond,

No plans as of now. Will be adding the APIs when time permits.. Do you 
need it urgently? Infact, it would be great if you can provide a patch :)


Regards,
Shankar

Raymond Zhou wrote:

Hi, Uthaiyashankar,
 
Thanks much for the info. I am a bit surprised that we can only set the few parameters programmably. I don't think it's ideal for client users to set up so many parameters in a complicated xml file in a file system. For my self, I would certainly like to provide a UI for client users to configure all the different parameters, just like what soapUI does. but without the rampart APIs, I would not be able to do that. Any plans that you will be able to provide the APIs?
 
Thanks again!

Raymond

--- On Thu, 10/23/08, Uthaiyashankar <[EMAIL PROTECTED]> wrote:

From: Uthaiyashankar <[EMAIL PROTECTED]>
Subject: Re: APIs for ws-security paramenters
To: "Apache AXIS C Developers List" 
Cc: [EMAIL PROTECTED], [EMAIL PROTECTED]
Date: Thursday, October 23, 2008, 3:31 AM

Hi Raymond,

For client side, you can set username, password, password type and time 
to live parameters programatically.  However, other options (like 
certificate, key, etc.) have to be set using policy files. We have to 
implement missing options. You can find more details from [1]


Regards,
Shankar

[1] https://issues.apache.org/jira/browse/RAMPARTC-56


Raymond Zhou wrote:
  

Hi there,
 
I am planning to use rampart-c as a module in my axis2/c to support 
ws-security in a web service client application. I know I can 
configure the policy files in the client repository. My question is 
that if all these variables/parameters can be set programmably using 
some sort of APIs. I want to do this because I would like to save the 
parameters in a database tables instead of a local file and I also 
want to be able to develop a UI for users to easily set/edit/change 
the values.
 
Thanks!

Raymond






  



--
S.Uthaiyashankar
Software Architect
WSO2 Inc. 
http://wso2.com/ - "The Open Source SOA Company" 



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

Re: APIs for ws-security paramenters

[Uthaiyashankar]

Hi Raymond,

For client side, you can set username, password, password type and time 
to live parameters programatically.  However, other options (like 
certificate, key, etc.) have to be set using policy files. We have to 
implement missing options. You can find more details from [1]


Regards,
Shankar

[1] https://issues.apache.org/jira/browse/RAMPARTC-56


Raymond Zhou wrote:

Hi there,
 
I am planning to use rampart-c as a module in my axis2/c to support 
ws-security in a web service client application. I know I can 
configure the policy files in the client repository. My question is 
that if all these variables/parameters can be set programmably using 
some sort of APIs. I want to do this because I would like to save the 
parameters in a database tables instead of a local file and I also 
want to be able to develop a UI for users to easily set/edit/change 
the values.
 
Thanks!

Raymond





--
S.Uthaiyashankar
Software Architect
WSO2 Inc. 
http://wso2.com/ - "The Open Source SOA Company" 



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

Re: REST support on Axis2/C

[Uthaiyashankar]

By the way, correct url is 
http://172.31.24.198:1983/axis2/services/echo/get_echo/Hello


Regards,
Shankar

Uthaiyashankar wrote:

Hi,

I think the problem is browser dependent. When I checked with Firefox, 
it is failing. But works, when I checked with IE. FireFox sends a 
header "Accept-Charset" which causes problem. When I capture the 
message using tcpmon, and then remove that header, it works. We have 
to debug and find the problem.


Regards,
Shankar.

Gupta, Shivam wrote:

Ok.. I get your point. I apologize for misunderstanding the issue.

However, I do have enabled the GET method in my service before firing 
the request from the browser. For your reference, I have attached the 
services.xml and am also listing the various URI that I entered in 
the browser to access the service :



http://172.31.24.198:1983/axis2/services/get_echo/Hello
http://172.31.24.198:1983/axis2/services/echo/get_echo/Hello

http://172.31.24.198:1983/axis2/services/get_echo/"Hello";

http://172.31.24.198:1983/axis2/services/echo/get_echo/"Hello";

Please guide me.
Shivam.

-Original Message-
From: Samisa Abeysinghe [mailto:[EMAIL PROTECTED]
Sent: Friday, October 17, 2008 9:59 AM
To: Apache AXIS C Developers List
Subject: Re: REST support on Axis2/C

Gupta, Shivam wrote:
 

Hi,

   Yes I have. Infact, if I haven't enabled it, even the echo_rest 
client should not have worked.


echo_rest uses a POST, and your browser request uses a GET.

Samisa...

 

Please help.

Thanks,
Shivam.

-Original Message-
From: Samisa Abeysinghe [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 15, 2008 7:48 PM
To: Apache AXIS C Developers List
Subject: Re: REST support on Axis2/C

Have you enabled GET method in your service?

Samisa...

Gupta, Shivam wrote:

   

Hello,

I have been trying to invoke the echo web service supplied with
Axis2/C using REST based invocation. When I try using the echo_rest
client, the service responds just fine.

   However, when I try to invoke the echo web sercvice using a web
browser, I get no response from the Axis. The browser just hangs in a
wait state. Could you tell me what could possibly be going wrong? I
entered the following query styring in the URL window of the browser:


http://172.31.24.18:2106/axis2c/services/echo/echoString?text='hello'
<http://172.31.24.18:2106/axis2c/services/echo/echoString?text=%27hel
l
o%27>

It would be great if you could help me here.

Thanks,
Shivam.
-
-
--


No virus found in this incoming message.
Checked by AVG - http://www.avg.com
Version: 8.0.173 / Virus Database: 270.8.0/1724 - Release Date:
10/14/2008 2:02 AM



  

--
Samisa Abeysinghe
Director, Engineering; WSO2 Inc.

http://www.wso2.com/ - "The Open Source SOA Company"


-
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]

--
--


No virus found in this incoming message.
Checked by AVG - http://www.avg.com
Version: 8.0.173 / Virus Database: 270.8.0/1726 - Release Date:
10/15/2008 7:29 AM






--
Samisa Abeysinghe
Director, Engineering; WSO2 Inc.

http://www.wso2.com/ - "The Open Source SOA Company"


-
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]






--
S.Uthaiyashankar
Software Architect
WSO2 Inc. 
http://wso2.com/ - "The Open Source SOA Company" 



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

Re: REST support on Axis2/C

[Uthaiyashankar]

Hi,

I think the problem is browser dependent. When I checked with Firefox, 
it is failing. But works, when I checked with IE. FireFox sends a header 
"Accept-Charset" which causes problem. When I capture the message using 
tcpmon, and then remove that header, it works. We have to debug and find 
the problem.


Regards,
Shankar.

Gupta, Shivam wrote:

Ok.. I get your point. I apologize for misunderstanding the issue.

However, I do have enabled the GET method in my service before firing the 
request from the browser. For your reference, I have attached the services.xml 
and am also listing the various URI that I entered in the browser to access the 
service :


http://172.31.24.198:1983/axis2/services/get_echo/Hello
http://172.31.24.198:1983/axis2/services/echo/get_echo/Hello

http://172.31.24.198:1983/axis2/services/get_echo/"Hello";

http://172.31.24.198:1983/axis2/services/echo/get_echo/"Hello";

Please guide me.
Shivam.

-Original Message-
From: Samisa Abeysinghe [mailto:[EMAIL PROTECTED]
Sent: Friday, October 17, 2008 9:59 AM
To: Apache AXIS C Developers List
Subject: Re: REST support on Axis2/C

Gupta, Shivam wrote:
  

Hi,

   Yes I have. Infact, if I haven't enabled it, even the echo_rest client 
should not have worked.


echo_rest uses a POST, and your browser request uses a GET.

Samisa...

  

Please help.

Thanks,
Shivam.

-Original Message-
From: Samisa Abeysinghe [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 15, 2008 7:48 PM
To: Apache AXIS C Developers List
Subject: Re: REST support on Axis2/C

Have you enabled GET method in your service?

Samisa...

Gupta, Shivam wrote:



Hello,

I have been trying to invoke the echo web service supplied with
Axis2/C using REST based invocation. When I try using the echo_rest
client, the service responds just fine.

   However, when I try to invoke the echo web sercvice using a web
browser, I get no response from the Axis. The browser just hangs in a
wait state. Could you tell me what could possibly be going wrong? I
entered the following query styring in the URL window of the browser:


http://172.31.24.18:2106/axis2c/services/echo/echoString?text='hello'


It would be great if you could help me here.

Thanks,
Shivam.
-
-
--


No virus found in this incoming message.
Checked by AVG - http://www.avg.com
Version: 8.0.173 / Virus Database: 270.8.0/1724 - Release Date:
10/14/2008 2:02 AM



  

--
Samisa Abeysinghe
Director, Engineering; WSO2 Inc.

http://www.wso2.com/ - "The Open Source SOA Company"


-
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]

--
--


No virus found in this incoming message.
Checked by AVG - http://www.avg.com
Version: 8.0.173 / Virus Database: 270.8.0/1726 - Release Date:
10/15/2008 7:29 AM






--
Samisa Abeysinghe
Director, Engineering; WSO2 Inc.

http://www.wso2.com/ - "The Open Source SOA Company"


-
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]



--
S.Uthaiyashankar
Software Architect
WSO2 Inc. 
http://wso2.com/ - "The Open Source SOA Company" 



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

Re: REST support on Axis2/C

[Uthaiyashankar]

Gupta, Shivam wrote:

Hi,

   Yes I have. Infact, if I haven't enabled it, even the echo_rest client should not have worked. 


If you are using echo service from current trunk, only POST method is 
enabled in service.xml. So, echo_rest client will work(by default it 
will do POST) but not the invocation from browser. As samisa said, you 
have to enable GET method in service.xml of echo service and then try.


If you can capture the message using tcpmon, then you can see whether 
client is doing POST or GET. If it is GET, then if you could attach the 
messages, we could be able to find the problem.


Regards,
Shankar.


Please help.

Thanks,
Shivam.

-Original Message-
From: Samisa Abeysinghe [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 15, 2008 7:48 PM
To: Apache AXIS C Developers List
Subject: Re: REST support on Axis2/C

Have you enabled GET method in your service?

Samisa...

Gupta, Shivam wrote:
  

Hello,

I have been trying to invoke the echo web service supplied with
Axis2/C using REST based invocation. When I try using the echo_rest
client, the service responds just fine.

   However, when I try to invoke the echo web sercvice using a web
browser, I get no response from the Axis. The browser just hangs in a
wait state. Could you tell me what could possibly be going wrong? I
entered the following query styring in the URL window of the browser:


http://172.31.24.18:2106/axis2c/services/echo/echoString?text='hello'


It would be great if you could help me here.

Thanks,
Shivam.
--
--


No virus found in this incoming message.
Checked by AVG - http://www.avg.com
Version: 8.0.173 / Virus Database: 270.8.0/1724 - Release Date:
10/14/2008 2:02 AM






--
Samisa Abeysinghe
Director, Engineering; WSO2 Inc.

http://www.wso2.com/ - "The Open Source SOA Company"


-
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]



  



--
S.Uthaiyashankar
Software Architect
WSO2 Inc. 
http://wso2.com/ - "The Open Source SOA Company" 



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

Re: Properties in Configuration Context

[Uthaiyashankar]

Damitha Kumarage wrote:

Hi Danushka,
We could easily wrap the  base context functions in conf_ctx, op_ctx, 
svc_ctx, svc_grp_ctx and msg_ctx. But this considerbly increase the 
lines of code. As I remember this was the main reason for not doing it 
previously. However I also agree that it is nice to have these wrapper 
functions in main contexts.


And Danushka's proposal includes internal mutexes as well. i.e. when we 
set/get some property to conf_ctx, only one thread can set/get which is 
very useful. If we get base context and then set the property, we have 
to have an external mutex and manage them, which is always a problem. I 
am +1 to add the methods as Danushka suggested.


Regards,
Shankar.



Thanks,
Damitha

Danushka Menikkumbura wrote:

Hi Devs,
   We have been using the base context of conf_ctx to keep custom 
properties. What we normally do is, get the base context and use its 
(axis2_ctx) API to set/get properties. And we use external mutexes 
for synchronization. Why don't we have get/set calls in conf_ctx API 
itself so that we can set/get properties without any hassle. And that 
way we can use the mutex in conf_ctx to handle synchronization. I 
think that is the cleaner way of accessing the base.


Any thoughts?

Danushka

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








--
S.Uthaiyashankar
Software Architect
WSO2 Inc. 
http://wso2.com/ - "The Open Source SOA Company" 



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

Re: ver 1.6

[Uthaiyashankar]

+1 for Manjula

Regards,
Shankar.


Damitha Kumarage wrote:

+1 for Manjula
thanks
Damitha

Manjula Peiris wrote:

On Mon, 2008-10-13 at 09:10 +0530, Samisa Abeysinghe wrote:
 

Any volunteers to play 1.6 release manager role?



I would like to be the release manager for 1.6

-Manjula.

 

Samisa...

Samisa Abeysinghe wrote:
   

If we can have Xpath and CGI, then we might go for 1.6.

I also had a look into the Jira, and looks like we have 87 open 
issues. We might also want to fix some of these also, before the 
release.


Thanks,
Samisa...

Dumindu Pallewela wrote:
 

Hi,

I have started on the XPath integration. I sent a separate email 
regarding that. It will take some time to get it properly tested.


Regards,
Dumindu.

On Wed, Oct 8, 2008 at 5:24 PM, Samisa Abeysinghe <[EMAIL PROTECTED] 
<mailto:[EMAIL PROTECTED]>> wrote:


Uthaiyashankar wrote:

Nandika Jayawardana wrote:

The code developed under for the two GSOC projects are
also there.


XPath support is still not integrated. We have to integrate
and test it. We are currently working on that. I think, it
will take some time.


The other one was CGI, is that complete as well?

Thanks,
Samisa...


Regards,
Shankar.

 Thanks
Nandika

On Wed, Oct 8, 2008 at 3:25 PM, Manjula Peiris
<[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
<mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>> 
wrote:



   On Wed, 2008-10-08 at 14:11 +0530, Samisa 
Abeysinghe wrote:

   > Subra Aswathanarayanan wrote:
   > > Hello,
   > >
   > > Do you guys know when you are going to release
Axis2/C ver 1.6?
   >
   > We have not got any major features to be released as
1.6 right
   now. In
   > fact, the developer community has not discussed any
plans for
   post 1.5
   > releases as of now. May be it should be 1.5.1.
<http://1.5.1.> <http://1.5.1./>

   We have MTOM caching support. This enhanced the
functionality of
   MTOM to
   send very large attachments with a very low memory 
usage.



   >
   > Devs, any thoughts...
   >
   > Thanks,
   > Samisa...
   >


  
-

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




-- http://nandikajayawardana.blogspot.com/
WSO2 Inc: http://www.wso2.com




 




No virus found in this incoming message.
Checked by AVG - http://www.avg.com Version: 8.0.173 / Virus
Database: 270.7.6/1714 - Release Date: 10/8/2008 7:01 AM

   


-- Samisa Abeysinghe Director, Engineering; WSO2 Inc.

http://www.wso2.com/ - "The Open Source SOA Company"



-

To unsubscribe, e-mail: [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>

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




--
Dumindu Pallewela
Cinergix - "Share, Reuse, Innovate"
cinergix.com <http://cinergix.com>
 




No virus found in this incoming message.
Checked by AVG - http://www.avg.com Version: 8.0.173 / Virus 
Database: 270.7.6/1714 - Release Date: 10/8/2008 7:01 AM


  
 




No virus found in this incoming message.
Checked by AVG - http://www.avg.com Version: 8.0.173 / Virus 
Database: 270.7.6/1714 - Release Date: 10/8/2008 7:01 AM







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


  






--
S.Uthaiyashankar
Software Architect
WSO2 Inc. 
http://wso2.com/ - "The Open Source SOA Company" 



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

Re: ver 1.6

[Uthaiyashankar]

Nandika Jayawardana wrote:

The code developed under for the two GSOC projects are also there.


XPath support is still not integrated. We have to integrate and test it. 
We are currently working on that. I think, it will take some time.


Regards,
Shankar.

 
Thanks

Nandika

On Wed, Oct 8, 2008 at 3:25 PM, Manjula Peiris <[EMAIL PROTECTED] 
> wrote:



On Wed, 2008-10-08 at 14:11 +0530, Samisa Abeysinghe wrote:
> Subra Aswathanarayanan wrote:
> > Hello,
> >
> > Do you guys know when you are going to release Axis2/C ver 1.6?
>
> We have not got any major features to be released as 1.6 right
now. In
> fact, the developer community has not discussed any plans for
post 1.5
> releases as of now. May be it should be 1.5.1. 

We have MTOM caching support. This enhanced the functionality of
MTOM to
send very large attachments with a very low memory usage.


>
> Devs, any thoughts...
>
> Thanks,
> Samisa...
>


-
To unsubscribe, e-mail: [EMAIL PROTECTED]

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





--
http://nandikajayawardana.blogspot.com/
WSO2 Inc: http://www.wso2.com



--
S.Uthaiyashankar
Software Architect
WSO2 Inc. 
http://wso2.com/ - "The Open Source SOA Company" 



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

Re: ver 1.6

[Uthaiyashankar]

Samisa Abeysinghe wrote:

Subra Aswathanarayanan wrote:

Hello,

Do you guys know when you are going to release Axis2/C ver 1.6?


We have not got any major features to be released as 1.6 right now. In 
fact, the developer community has not discussed any plans for post 1.5 
releases as of now. May be it should be 1.5.1.


Yes, we don't have much new features. Only bug fixes.. .So it is better 
to be 1.5.1


Regards,
Shankar



Devs, any thoughts...

Thanks,
Samisa...




--
S.Uthaiyashankar
Software Architect
WSO2 Inc. 
http://wso2.com/ - "The Open Source SOA Company" 



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

Re: Adding XPath GSoC project to svn trunk

[Uthaiyashankar]

I think, it is better to include XPath as part of Axiom, rather than a 
separate project/sub project. Since it is an addition of functionality, 
whether XPath is part of the same library, or separate library, the 
level of unstableness will be same. It will not modify any existing 
functionality. But, later in time, if we want to use some functionlity 
of XPath in our Axiom logic, (for example, methods like 
axiom_element_get_children_with_xpath()), then it is better to include 
XPath as part of axiom.


Regards,
Shankar.

Supun Kamburugamuva wrote:

HI Dumindu,

I think if we can include XPath as a seperate library it will be 
better. If we include this to the Axiom it will make the Axiom much 
heavier. Axiom is a well tested module and adding a large peice of not 
very well tested code can make the Axiom unstable. Also if we make 
XPath a separate sub project under Axiom it will be easier for us to 
maintain.


Supun.

On Mon, Oct 6, 2008 at 11:32 AM, Dumindu Pallewela 
<[EMAIL PROTECTED] > wrote:


Hi All,

I have started on integrating the XPath implementation done by
Varuna for GSoC [1] with our main trunk. I assume that (xpath
being specific to axiom), we can compile it directly into
libaxis2_axiom.so. Thus the source will go to /axiom/src/xpath
directory, and the includes, tests accordingly to relevant
directories relative to that location. You can find the branch I'm
working at [2].

Thanks,
Dumindu.

[1] http://issues.apache.org/jira/browse/AXIS2C-595
[2] 
https://svn.apache.org/repos/asf/webservices/axis2/branches/c/xpath_integration/




--
Software Engineer, WSO2 Inc
http://wso2.org



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

Re: Sending and receiving separate messages from a module

[Uthaiyashankar]

Supun Kamburugamuva wrote:

Hi all,

I have a module which has a handler in the out flow. When a message is 
sent by a client, this module needs to send separate messages prior to 
sending the the original message. What is the best way to send these 
messages? Should I use the service client, operation client or any 
other means of sending a message through axis2/C?


Sandesha and Rampart have similar functionality. We are using 
ServiceClient for that.


Regards,
Shankar



Thanks,
Supun.
Software Engineer, WSO2 Inc



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

Re: Building under windows

[Uthaiyashankar]

Hi,

This error occurs if you declare any variables in the middle of the 
method. You have to declare all the variables at the start of the 
method, before other statements/implementations. In cgi_main.c you have 
declared a variable conf_ctx in line 95, where line 67 - 91 you have 
other statements (implementations). You have to move variable 
declaration to some lines before 67.


Regards,
Shankar

Nikola Tankovć wrote:

Hy all,

I'm trying to build my CGI executable under windows using cl.exe but 
get the following errors


cgi_main.c(95) : error C2275: 'axis2_conf_ctx_t' : illegal use of this 
type as an expression
   C:\axis2c\include\axis2_conf_ctx.h(49) : see declaration of 
'axis2_conf_ctx_t'


... and so on and on (similar errors)

Obviously included locations are fine, maybe the problem is that I'm 
using MS Visual Studio 2008 so syntax is somewhat different for 
typdef? Or did I forget some specific flag?


I'm using the command like this (as I saw in the makefile)

cl.exe /D "_DEBUG" /Od /Z7 /MDd /D "WIN32" /D "_WINDOWS" /D "_MBCS" /D 
"AXIS2_DECLARE_EXPORT" /D "_CRT_SECURE_NO_DEPRECATE" /D 
"_CRT_SECURE_NO_WARNINGS" /D "AXIS2_SVR_MULTI_THREADED" /W3 /wd4100  
/MP10 /nologo /I %AXIS2C_HOME%include /c cgi_main.c



-
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: Using Apache2 global mutex

[Uthaiyashankar]

Hi,

See my comments





Suppose  two requests come to Axis2/C sequentially. Say the first 
request is served by one apache process and the next request is 
served by another process. Then problem is you cannot access the 
previous requests configuration context from your next request 
because each process has it's own configuration context. We recently 
solved this problem using shared memory. But as should be expected 
this is extremely inefficient.


Yes, it is about 10 times slower than non-shared memory implementation.



The other and more effiecient solution is using a database that 
could be shared among your processes. Sandesha2/C uses this approach. 


We have to test the performance of this to decide whether it is worth
doing. I guess the performance will be higher than shared memory
implementation. Only problem is how to solve concurrency issue, without
global mutex.


To solve concurrency issues when using this approach we can use 
Apache2 golbal mutex which could be used when accessing global 
resources like system files and databases. 


Shared memory implementation is very slow because of global mutex :).
Since you implemented it and has good understanding I may ask 
following questions to understand the situation well.


-Did you use apr_shm/apr_rmm or apr_dbm in your implementation?


apr_shm/apr_rmm



-If you used apr_shm/apr_rmm then using apache thread_mutex to protect 
axis2 contexts is not enough?. AFAIK they are less expensive than 
global mutexts.


I am not using the global mutex to protect axis2 contexts. It is used to 
protect apr_rmm structures. You have to use global mutex to protect it.




-Is using apr_dbm more expensive?. I guess the answer is yes.


I think it is more expensive.



-In the database option can't we use mod_dbd which manages a pool of 
database connections efficiently. It is using apr_reslist. Can we use 
apr_reslist directly without mod_dbd?


I am not sure about this. We can try and see..

Regards,
Shankar



thanks,
Damitha

So, if we introduce it here, then again we are going to have same issue
as in shared memory implementation. Can't we have database level
concurrency protection to solve this?

Shall we have a comparision of database implementation Vs shared memory
- with and without global mutex to see whether it is worth doing?

Regards,
Shankar.

But the problem is how we could pass this global mutext from Axis2 
apache module to be accessible from other parts of the code, for 
example from a Axis2/C module. We currently pass Apache2 pools 
through axis2_env_t environment. How about using the same in passing 
this as well?


thanks,
Damitha




-
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: Using Apache2 global mutex

[Uthaiyashankar]

Hi devs,

Suppose  two requests come to Axis2/C sequentially. Say the first 
request is served by one apache process and the next request is served 
by another process. Then problem is you cannot access the previous 
requests configuration context from your next request because each 
process has it's own configuration context. We recently solved this 
problem using shared memory. But as should be expected this is 
extremely inefficient.


Yes, it is about 10 times slower than non-shared memory implementation.



The other and more effiecient solution is using a database that could 
be shared among your processes. Sandesha2/C uses this approach. 


We have to test the performance of this to decide whether it is worth
doing. I guess the performance will be higher than shared memory
implementation. Only problem is how to solve concurrency issue, without
global mutex.


To solve concurrency issues when using this approach we can use 
Apache2 golbal mutex which could be used when accessing global 
resources like system files and databases. 


Shared memory implementation is very slow because of global mutex :).
So, if we introduce it here, then again we are going to have same issue
as in shared memory implementation. Can't we have database level
concurrency protection to solve this?

Shall we have a comparision of database implementation Vs shared memory
- with and without global mutex to see whether it is worth doing?

Regards,
Shankar.

But the problem is how we could pass this global mutext from Axis2 
apache module to be accessible from other parts of the code, for 
example from a Axis2/C module. We currently pass Apache2 pools through 
axis2_env_t environment. How about using the same in passing this as 
well?


thanks,
Damitha




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

Re: [VOTE][Axis2]Apache Axis2/C 1.5.0 Release

[Uthaiyashankar]

I tested on windows. +1 for release

Regards,
Shankar

Dushshantha Chandradasa wrote:

I tested src and bin on windows and it works fine.

Here's my +1 for the release

regards,
Dushshantha

On Mon, Jul 14, 2008 at 11:29 AM, Supun Kamburugamuva 
<[EMAIL PROTECTED] > wrote:


Hi Devs,

I have uploaded the Apache Axis2/C 1.5.0 release artifacts here
http://people.apache.org/~supun/axis2/release_1_5/1.5.0


The key to verify the release artifacts can be found at
http://people.apache.org/~supun/axis2/release_1_5/1.5.0/KEYS


If the released artifacts are fine, please vote for the Apache
Axis2/C 1.5.0 release.
Here is my +1.

Thanks,
Supun





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

Re: [Axis2] VOTE Diluka Moratuwage as Commiter

[Uthaiyashankar]

Here is my +1

Regards,
Shankar

Damitha Kumarage wrote:

Hi devs,

I would like to nominate Diluka Moratuwage to be an Axis2/C commiter.

Diluka has contributed some important patches to Savan/C. He 
implemented XPath filtering support and fault handling for Savan/C. He 
has also contributed patches to Axis2/C and has been active in mailing 
list.


I am confident that Diluka will continue to make his valuable 
contributions to Axis2/C and Savan/C projects.


Please refer to the attached jira report for more information about 
his contributions.


Here is my vote. +1

Thanks,
Damitha




  [AXIS2C-688] Savan fault handling and filter dialect support
   Created:
  05/Sep/07  Updated: 19/Sep/07

*Status:*



Closed

*Project:*



Axis2-C 



*Component/s:*



None

*Affects Version/s:*



None

*Fix Version/s:*



None


*Type:*



Improvement



*Priority:*



Major

*Reporter:*



Diluka Moratuwage 





*Assignee:*



Unassigned

*Resolution:*



Fixed



*Votes:*



0

*Remaining Estimate:*



Not Specified

*Time Spent:*



Not Specified

*Original Estimate:*



Not Specified


*File Attachments:*



Text File savan-filtering-faults.patch



 *Description* 




 


Savan fault handling and filter dialect support implemented.


 *Comments* 




 

Comment by Damitha Kumarage 
 
[ 10/Sep/07 06:21 AM ]


Patch Applied. Thanks Diluka for the important patch. I tested with 
the subscriber sample and it looks OK


Comment by Damitha Kumarage 
 
[ 19/Sep/07 02:51 AM ]


No issues so far. So close it





  [AXIS2C-552] Code formatting for axis2c/axiom
   Created:
  19/Mar/07  Updated: 19/Mar/07

*Status:*



Resolved

*Project:*



Axis2-C 



*Component/s:*



None

*Affects Version/s:*



None

*Fix Version/s:*



1.0.0 
 




*Type:*



Improvement



*Priority:*



Minor

*Reporter:*



Diluka Moratuwage 





*Assignee:*



Dinesh Premalal 
 



*Resolution:*



Fixed



*Votes:*



0

*Remaining Estimate:*



Not Specified

*Time Spent:*



Not Specified

*Original Estimate:*



Not Specified


*File Attachments:*



File patch.axiom



 *Description* 




 


Code formatted in axiom/soap and axiom/attachments


 *Comments* 




 

Comment by Diluka Moratuwage 
 
[ 19/Mar/07 03:02 AM ]


Macros removed, and code formatted in axiom/soap and axiom/attachmens.

Comment by Dinesh Premalal 
 
[ 19/Mar/07 12:25 PM ]


patch applied , thanks Diluka, Keep them coming





  [AXIS2C-652] XPath filtering support for savan
   Created:
  26/Jul/07  Updated: 04/Sep/07

*Status:*



Resolved

*Project:*



Axis2-C 



*Component/s:*



None

*Affects Version/s:*



None

*Fix Version/s:*



None


*Type:*



Improvement



*Priority:*



Major

*Reporter:*



Diluka Moratuwage 





*Assignee:*



Unassigned

*Resolution:*



Fixed



*Votes:*



0

*Remaining Estimate:*



Not Specified

*Time Spent:*



Not Specified

*Original Estimate:*



Not Specified

*Environment:*



Ubuntu 7.04


*File Attachments:*



Text File filtering.patch File template.xsl



 *Description* 




 

XPath, filtering for elements, without a namespace prefix is 
supported. Since, we still don't have XPath f

Re: message id interoperability issue with .net 2.0

[Uthaiyashankar]

Dinesh Premalal wrote:

Hi,

Uthaiyashankar <[EMAIL PROTECTED]> writes:
  

.NET 2.0 client expects "urn:uuid" prefix in the message id.  (i.e
urn:uuid:6b85e6c2-4645-1dd1-2636-000c292fec05
). To be able to interoperate with .NET 2.0 it is better to add
"urn:uuid" prefix to message id. WDYT?



+1 , after adding urn:uuid to message id please make sure that it
won't break other interoperability cases such as Axis2 , Axis etc
  


We have tested interoperability, and everything works fine. I have 
committed it to trunk. If possible, we can include this functionality in 
Axis2/C 1.5.0


Regards,
Shankar

thanks,
Dinesh

  



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

message id interoperability issue with .net 2.0

[Uthaiyashankar]

Hi,

Axis2/C creates wsa:MessageID as a sequence of characters. (E.g:  
6b85e6c2-4645-1dd1-2636-000c292fec05).  
When using with .NET 3.0 clients, above message id works without any 
problem. However, when using with .NET 2.0 clients, this message id 
could not be processed by .NET client.


.NET 2.0 client expects "urn:uuid" prefix in the message id.  (i.e 
urn:uuid:6b85e6c2-4645-1dd1-2636-000c292fec05 
). To be able to interoperate with .NET 2.0 it is better to add 
"urn:uuid" prefix to message id. WDYT?


Regards,
Shankar

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

Re: [Axis2]Axis2/C 1.5.0 RC1

[Uthaiyashankar]

Supun Kamburugamuva wrote:

Hi All,

I have packed and uploaded Apache Axis2/C 1.5.0 RC1 here [1]. Please 
test and send your feedback.


[1] http://people.apache.org/~supun/release_1_5/rc1/ 



Thanks,
Supun.. 

Hi,

I tested windows source version and binary version and they works.

However, there are some documentation issues

(1) In INSTALL file, 3.2 section (Deploying in Apache2 Web Server) - it 
is better to change the libmod_axis2.so.0.3.1 to libmod_axis2.so.0.5.0
(2) INSTALL file mentions about ENABLE_GUTHTHILA option (section 2.3.1). 
It is removed from configure.in, so we can remove it from INSTALL file
(3) ChangeLog and NEWS inside samples\ should be modified (still saying 
1.3.0 release)

(4) docs/archived_news.html does not have version 1.4.0 as previous release

There are some issues in linux binary distribution
(1) version number of libraries and modules are still 0.4.0, it should 
be 0.5.0
(2) there is a folder "share" in linux binary distribution which should 
be removed


Regards,
Shankar


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

Re: [Axis2][Vote] Supun as Release Manager for 1.5.0 Apache Axis2/C Release

[Uthaiyashankar]

+1

Regards,
Shankar

Samisa Abeysinghe wrote:

Hi devs,

I would like to propose Supun Kamburugamuva as the release manager for
Apache Axis2/C 1.5.0 release.
Since he has already volunteered to do so I would like to call a vote
here to confirm his role as RM.

Here is my vote: +1.

Thanks,
Samisa...


-
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: soap action based dispatching with rampart

[Uthaiyashankar]

Hi,

This article [1] written by Samisa explicitly saying we can add user 
defined phases only after pre-defined phases in in-flow. I guess it is 
added purposely. Then we have to consider some other options to invoke 
rampart after soap action based dispatching.


Regards,
Shankar

[1] http://wso2.org/library/777


Kaushalye Kapuruge wrote:

Thanks Manjula for this finding.
Is this a bug or added purposely?
Are there any problems if module defined phases get invoked before the 
default phases?

If not definitely need to fix this phase ordering problem in Axis2/C.
Cheers,
Kaushalye

Manjula Peiris wrote:

Hi,

I debug the code. What is happening here is Security phase always
invokes at last even you put it before Transport phase. Since soap
action based dispatcher is in Dispatch phase in this situation when it
comes to Rampart actual dispatching has occurred. So this means Axis2/C
always invoke module defined phases after invoking its default phases. I
think we need to fix this. I will raise a JIRA.

Thanks,
-Manjula.

 


On Wed, 2008-05-28 at 14:18 +0530, Manjula Peiris wrote:
 

On Wed, 2008-05-28 at 14:15 +0530, Manjula Peiris wrote:
   

Shankar,

I have tested Rampart/C with a soap action(without addressing) and
putting the Security phase even before Transport phase and it 
worked. So

I think what is happening in this case is that actual dispatching does
not happen from soap action phase dispatcher.
  

not happen from soap action based dispatcher.

   
 


-Manjula.

On Wed, 2008-05-28 at 12:21 +0530, Uthaiyashankar wrote:
 

Hi,

Currently rampart in-handler is called in "PreDispatch" phase in 
inflow. Due to that, if a message is having only soap action (no 
operation is specified in url or no wsa:action is given, so only 
possible way of dispatching is based on soap action) and message 
is secured, security cannot be verified. This is because, rampart 
needs operation to be resolved before verifying the security of 
the message. If the message is having only soap action, then when 
message comes to rampart, still the operation is not resolved.


Can somebody confirm soap action based dispatching happening on 
"PreDispatch"? If so, can we introduce another phase "Security" 
between "PreDispatch" and "Dispatch" and install 
rampart-in-handler to "Security" phase? will it cause any 
problem?  Any reason why rampart-in-handler is installed in 
"PreDispatch" phase rather than another phase? (I tried it and it 
worked)


Comments are welcome.

Regards,
Shankar.


-
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]





-
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]

soap action based dispatching with rampart

[Uthaiyashankar]

Hi,

Currently rampart in-handler is called in "PreDispatch" phase in inflow. 
Due to that, if a message is having only soap action (no operation is 
specified in url or no wsa:action is given, so only possible way of 
dispatching is based on soap action) and message is secured, security 
cannot be verified. This is because, rampart needs operation to be 
resolved before verifying the security of the message. If the message is 
having only soap action, then when message comes to rampart, still the 
operation is not resolved.


Can somebody confirm soap action based dispatching happening on 
"PreDispatch"? If so, can we introduce another phase "Security" between 
"PreDispatch" and "Dispatch" and install rampart-in-handler to 
"Security" phase? will it cause any problem?  Any reason why 
rampart-in-handler is installed in "PreDispatch" phase rather than 
another phase? (I tried it and it worked)


Comments are welcome.

Regards,
Shankar.

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

Re: Caching support for MTOM

[Uthaiyashankar]

+1 for branching.

Regards,
Shankar

Dumindu Pallewela wrote:

Yes I too think that a branch is the proper way of handling such a situation.

Regards,
Dumindu.

On Fri, May 9, 2008 at 7:19 PM, Damitha Kumarage <[EMAIL PROTECTED]> wrote:
  

Hi Manjula,
Is n't it better to have branch of Axis2/C to do these improvements?. Then
as soon as you are done we can merge
thanks
Damitha
Manjula Peiris wrote:



Hi devs,

I have implemented a caching technique [1] for MTOM. I had to completely
rewrite the current mime_parser logic. The implementation also has a new
searching technique which efficiently uses memory. There are some bugs
need to be fixed in the new implementation and it also need to be
tested. Some API additions may need to be done in order to put this
implementation to the current Axis2/C trunk. I will discuss those in
this list. Since we now have a stable MTOM implementation I propose we
will put these new stuff in a scratch area and continue with the further
development.
Thoughts please ?

[1] https://issues.apache.org/jira/browse/AXIS2C-672

Thanks,
-Manjula.



-
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]







  



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

Re: [Vote][Rampart-C] Vote for Apache Rampart/C 1.2.0 Release - Take 2

[Uthaiyashankar]

+1

Regards,
Shankar

Kaushalye Kapuruge wrote:

Hi Devs,

I have uploaded the Apache Rampart/C 1.2.0 release artifacts (Take 2) 
here

http://people.apache.org/~kaushalye/release/rampart-c/1.2.0

The key to verify the release artifacts can be found at
http://people.apache.org/~kaushalye/release/KEYS

Please test and review with Apache Axis2/C 1.4.0 artifacts.
http://people.apache.org/~dinesh/release/Axis2C-1.4.0/

If the released artifacts are fine, please vote for the Apache 
Rampart/C 1.2.0 release in [EMAIL PROTECTED] list.

Here is my +1.

Cheers,
Kaushalye




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

Re: [VOTE][Axis2]Apache Axis2/C 1.4.0 Release - Take3

[Uthaiyashankar]

I tested on windows. Here is my +1.

Regards,
Shankar.

Sanjaya Ratnaweera wrote:
I have tested source and binary distributions with Debian GNU/Linux 
testing (lenny) and it works fine.

Here's my +1

Thanks

   ~sanjaya

Dimuthu Gamage wrote:

Tested linux binaries with codegen tests. Everything works fine.

Just one minor issue, I found directory named 'share' in the binary
pack which has readme s related to tcpmon, I think that should be
moved to the bin/tools directory. But it will not effect the release a
lot.

So +1 for the release.

Thanks
Dimuthu

On Sun, May 4, 2008 at 10:36 AM, Samisa Abeysinghe <[EMAIL PROTECTED]> wrote:
  

Tested binary on Windows.

 Here is my +1.

 Thanks,
 Samisa...


 Dinesh Premalal wrote:



Hi Devs,

 I have packaged and uploaded the Apache Axis2/C 1.4.0 release artifacts
  

at


[1].  The key used to sign the release artifacts can be found at [2].
   Please test, review and vote on the release artifacts for Apache
 Axis2/C 1.4.0 release.

 Here is my +1

Thanks,
Dinesh

1. http://people.apache.org/~dinesh/release/Axis2C-1.4.0/
2. http://www.apache.org/dist/ws/axis2/c/KEYS



  

 --
 Samisa Abeysinghe Director, Engineering; WSO2 Inc.

 http://www.wso2.com/ - "The Open Source SOA Company"




 -
 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]


  





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

Re: [VOTE][Axis2]Apache Axis2/C 1.3.1 Release Artifacts - Take 2

[Uthaiyashankar]

I corrected this on windows. Will commit when svn is up.

Hi,

Modification is committed.

Regards,
Shankar.

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

Re: [VOTE][Axis2]Apache Axis2/C 1.3.1 Release Artifacts - Take 2

[Uthaiyashankar]

Dimuthu Gamage wrote:

Hi devs,

I tested the linux axis2/c source package with libxml2 and it fails.

Looks like right now https://svn.apache.org/ is down. So I will commit
the fix  for linux after svn is up again.

Although the guththila is the default parser, we should also support
libxml2. So I think we have to repack the release again.
  


Hi,

I corrected this on windows. Will commit when svn is up.

Regards,
Shankar.


Thanks
Dimuthu


On Fri, Apr 25, 2008 at 3:59 PM, Damitha Kumarage <[EMAIL PROTECTED]> wrote:
  

+1,
 Tested Sandesha2/C and wsclient in debian.
 thanks
 Damitha
 Dinesh Premalal wrote:




Hi Devs,

 I have packaged and uploaded the Apache Axis2/C 1.3.1 release artifacts
  

at [1].  The key used to sign the release artifacts can be found at [2].


   Please test, review and vote on the release artifacts for Apache
  

Axis2/C 1.3.1 release.


 I have tested and reviewed them, here is my +1

Thanks,
Dinesh

1. http://people.apache.org/~dinesh/release/Axis2C-1.3.1/
  




2. http://www.apache.org/dist/ws/axis2/c/KEYS


--
http://nethu.org/

  




 -
 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]



  



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

Re: [VOTE][Axis2]Apache Axis2/C 1.3.1 Release Artifacts - Take 2

[Uthaiyashankar]

Hi,

I tested on windows. Tested with rampart as well and works fine.

Here is my +1.

Regards,
Shankar.

Manjula Peiris wrote:

Hi,

I have tested both the source and binary distributions on ubuntu 7.10
with Apache 2.2.6 and they work fine.
Here is my +1.

Thanks,
-Manjula.


On Wed, 2008-04-23 at 16:19 +0530, lahiru gunathilake wrote:
  

Hi,

I've tested in Ubuntu 7.04, both the source and binary works fine.
Here's my +1,

Regs
lahiru 


On Wed, Apr 23, 2008 at 3:30 PM, Dinesh Premalal <[EMAIL PROTECTED]>
wrote:
Hi Devs,

  I have packaged and uploaded the Apache Axis2/C 1.3.1

release artifacts at [1].  The key used to sign the release
artifacts can be found at [2]. 
   
  Please test, review and vote on the release artifacts for

Apache Axis2/C 1.3.1 release.

  I have tested and reviewed them, here is my +1

Thanks,

Dinesh

1. http://people.apache.org/~dinesh/release/Axis2C-1.3.1/

2. http://www.apache.org/dist/ws/axis2/c/KEYS


-- 
http://nethu.org/




--
East or West 
Mahindians are the 
Best... !




-
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: [Axis2][Vote]Dinesh as Release Manager

[Uthaiyashankar]

here is my +1

Regards,
Shankar

Damitha Kumarage wrote:

Hi devs,

I would like to propose Dinesh Premalal as the release manager for 
Apache Axis2/C 1.3.1 release.
Since he has already volunteered to do so I would like to call a vote 
here to confirm his role as RM.


Since we have identified few problems, it is worth to fix them with a 
patch release, along with any bugs we have fixed since the release of 
1.3.0.


Here is my vote: +1.

Thanks,
Damitha


-
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: build break on windows

[Uthaiyashankar]

-
-typedef struct axiom_mime_output axiom_mime_output_t;
+typedef void axiom_mime_output_t;



Modified it as
typedef char axiom_mime_output_t;


Is there any other options??

Regards,
Shankar.



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

build break on windows

[Uthaiyashankar]

Date: Wed Mar 19 05:19:12 2008
New Revision: 638811

URL: http://svn.apache.org/viewvc?rev=638811&view=rev
Log:
Axis2/C Hackathon: Improving code

Modified:
webservices/axis2/trunk/c/axiom/src/attachments/axiom_mime_output.h
webservices/axis2/trunk/c/axiom/src/attachments/data_handler.c
webservices/axis2/trunk/c/axiom/src/attachments/mime_body_part.c
webservices/axis2/trunk/c/axiom/src/attachments/mime_output.c
webservices/axis2/trunk/c/include/axis2_http_transport.h
webservices/axis2/trunk/c/src/core/transport/http/common/http_worker.c

webservices/axis2/trunk/c/src/core/transport/http/common/simple_http_svr_conn.c
webservices/axis2/trunk/c/src/core/transport/http/sender/http_sender.c

webservices/axis2/trunk/c/src/core/transport/http/sender/libcurl/axis2_libcurl.c

Modified: webservices/axis2/trunk/c/axiom/src/attachments/axiom_mime_output.h
URL: 
http://svn.apache.org/viewvc/webservices/axis2/trunk/c/axiom/src/attachments/axiom_mime_output.h?rev=638811&r1=638810&r2=638811&view=diff
==
--- webservices/axis2/trunk/c/axiom/src/attachments/axiom_mime_output.h 
(original)
+++ webservices/axis2/trunk/c/axiom/src/attachments/axiom_mime_output.h Wed Mar 
19 05:19:12 2008
@@ -1,4 +1,3 @@
-
 /*
  * Licensed to the Apache Software Foundation (ASF) under one or more
  * contributor license agreements.  See the NOTICE file distributed with
@@ -37,10 +36,7 @@
 {
 #endif
 
-/* This should be moved to header file later axutil_utils_defines.h*/

-#define axis2_byte_t char
-
-typedef struct axiom_mime_output axiom_mime_output_t;
+typedef void axiom_mime_output_t;
 



Modified: webservices/axis2/trunk/c/axiom/src/attachments/mime_output.c
URL: 
http://svn.apache.org/viewvc/webservices/axis2/trunk/c/axiom/src/attachments/mime_output.c?rev=638811&r1=638810&r2=638811&view=diff
==
--- webservices/axis2/trunk/c/axiom/src/attachments/mime_output.c (original)
+++ webservices/axis2/trunk/c/axiom/src/attachments/mime_output.c Wed Mar 19 
05:19:12 2008
@@ -1,4 +1,3 @@
-
 /*
  * Licensed to the Apache Software Foundation (ASF) under one or more
  * contributor license agreements.  See the NOTICE file distributed with
@@ -17,69 +16,65 @@
  */
 
 #include "axiom_mime_output.h"

-#include "axiom_data_handler.h"
+#include 
 #include "axiom_mime_body_part.h"
 #include 
 #include 
 #include 
 
-struct axiom_mime_output

-{
-int dummy;
-};
-

 
 AXIS2_EXTERN axiom_mime_output_t *AXIS2_CALL

 axiom_mime_output_create(
-const axutil_env_t * env)
+const axutil_env_t *env)
 {
 axiom_mime_output_t *mime_output = NULL;
 AXIS2_ENV_CHECK(env, NULL);
 mime_output = (axiom_mime_output_t *) AXIS2_MALLOC(env->allocator,
-   sizeof
-   (axiom_mime_output_t));
+sizeof(axiom_mime_output_t));
 
 if (!mime_output)

 {
 AXIS2_ERROR_SET(env->error, AXIS2_ERROR_NO_MEMORY, AXIS2_FAILURE);
+AXIS2_LOG_ERROR(env->log, AXIS2_LOG_SI,
+"No memory. Cannot create MIME output");
 return NULL;
 }
  


Hi Devs,

Because of this modification, sizeof(axiom_mime_output_t) will return 0. 
Hence, malloc will fail. Also, in windows, this gives a compilation 
error (since warnings are treated as error). Can we revert it or is it 
possible to fix it??


Regards,
Shankar.

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

Re: [Axis2] [Vote] Dinesh as Release Manager for Apache Axis2/C 1.3.0 Release

[Uthaiyashankar]

+1

Regards,
Shankar.

Kaushalye Kapuruge wrote:

+1
-Kau

Dumindu Pallewela wrote:

+1.

Regards,
Dumindu.

On Jan 31, 2008 2:23 PM, Samisa Abeysinghe <[EMAIL PROTECTED]> wrote:
 

Hi All,
Looking at the new features we have, it looks like we could do 
1.3.0

release, rather than doing a 1.2.1 patch release. I would like to
propose Dinesh Premalal as the release manager for  Apache Axis2/C 
1.3.0

release.

Here is my vote: +1.

Thanks,
Samisa...



-
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: [Axis2][VOTE]Lahiru Gunathilake as a committer

[Uthaiyashankar]

+1

Regards,
Shankar

Dinesh Premalal wrote:

Hi Devs,

I would like to propose Lahiru Gunathilake as an Axis2/C committer. 
Lahiru hascontributed a lot to improve Guththila parser and test 
many components in Axis2/C. Here [1] is some of the issues that he has 
worked on. I'm sure that he will be a resourceful person for Axis2/C  
project.


Here is my +1 for Lahiru !

thanks,
Dinesh


1. 
http://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&reporterSelect=specificuser&reporter=lahiru 



--
http://nethu.org/ 




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

Re: [Axis2] [Vote] Dinesh as Release Manager for Apache Axis2/C 1.2.1 Release

[Uthaiyashankar]

+1

Regards,
Shankar.

Samisa Abeysinghe wrote:

Hi All,
   I would like to propose Dinesh Premalal as the release manager for 
Apache Axis2/C 1.2.1 release.


   Since we have identified few glitches, it is worth to fix them with 
a patch release, along with any bugs we have fixed since the release 
of 1.2.0.


   Dinesh was volunteered to be the release manager and I would like 
to call this vote confirm his role as RM.


   Here is my vote: +1.

Thanks,
Samisa...

-
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: WS-SecureConversation specific policy assertion support for neethi

[Uthaiyashankar]

Manjula Peiris wrote:

Hi Sankar,

When keeping the BootstrapPolicy  I think it is good to store it as a
(neethi_policy_t *) inside SecureConversationToken. Do you have any
different plans ?
  
Exactly, that is the plan I am having. I guess, it will be the best way 
to implement.


Regards,
Shankar.

-Thnaks,
Manjula. 



On Mon, 2008-01-21 at 10:10 +0530, Uthaiyashankar wrote:
  

Hi devs,

We are implementing WS-SecureConversation support to rampart/C. In order 
to do that, there are some secure conversation specific 
WS-SecurityPolicy assertions which are needed to be implemented in 
neethi. The assertions are,


* SecurityContextToken assertion
* SecureConversationToken assertion
* BootstrapPolicy assertion

The modification of neethi will be introducing support for above 
assertions. Since, it is just an addition (based on Ws-SecurityPolicy 
specification), modification to existing neethi codes will be minimal.


Any comments or suggestions are invited.

Regards,
Shankar.


-
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]



  




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

WS-SecureConversation specific policy assertion support for neethi

[Uthaiyashankar]

Hi devs,

We are implementing WS-SecureConversation support to rampart/C. In order 
to do that, there are some secure conversation specific 
WS-SecurityPolicy assertions which are needed to be implemented in 
neethi. The assertions are,


* SecurityContextToken assertion
* SecureConversationToken assertion
* BootstrapPolicy assertion

The modification of neethi will be introducing support for above 
assertions. Since, it is just an addition (based on Ws-SecurityPolicy 
specification), modification to existing neethi codes will be minimal.


Any comments or suggestions are invited.

Regards,
Shankar.


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

Re: [Axis2][VOTE]Senaka Fernando as a committer

[Uthaiyashankar]

+1.

Regards,
Shankar.

Manjula Peiris wrote:

+1.

Thanks.
-Manjula.

On Wed, 2008-01-16 at 22:29 +0530, Sanjaya Ratnaweera wrote:
  

+1.

Thanks

~sanjaya


Samisa Abeysinghe wrote:


+1.

Samisa...

P.S. Wow, that's too many issues. Dinesh, are you sure about this list ;)

Dinesh Premalal wrote:
  

Hi Devs,

 I would like to propose Senaka Fernando as an Axis2/C 
committer. He has done a great job for the development of Axis2/C. He 
is very much active in the mailing lists and provide numerous amount 
of patches. Here is some of the jiras he has contributed.


AXIS2C-243, AXIS2C-296, AXIS2C-554, AXIS2C-618, AXIS2C-622, AXIS2C-699,
AXIS2C-726, AXIS2C-728, AXIS2C-735, AXIS2C-738, AXIS2C-739, AXIS2C-740,
AXIS2C-741, AXIS2C-742, AXIS2C-743, AXIS2C-751, AXIS2C-752, AXIS2C-757,
AXIS2C-765, AXIS2C-767, AXIS2C-773, AXIS2C-774, AXIS2C-775, AXIS2C-788,
AXIS2C-795, AXIS2C-796, AXIS2C-813, AXIS2C-814, AXIS2C-815, AXIS2C-816,
AXIS2C-817, AXIS2C-819, AXIS2C-820, AXIS2C-821, AXIS2C-822, AXIS2C-823,
AXIS2C-824, AXIS2C-828, AXIS2C-831, AXIS2C-836, AXIS2C-837, AXIS2C-842,
AXIS2C-844, AXIS2C-852, AXIS2C-853, AXIS2C-854, AXIS2C-865, AXIS2C-867,
AXIS2C-868, AXIS2C-870, AXIS2C-871, AXIS2C-872, AXIS2C-873, AXIS2C-874,
AXIS2C-878, AXIS2C-879, AXIS2C-880, AXIS2C-881, AXIS2C-885, AXIS2C-887,
AXIS2C-888, AXIS2C-892, AXIS2C-894

 I'm sure that he will continue his contribution towards the 
development of Axis2/C project in the future as well.


Here is my +1 for Senaka.

thanks,
Dinesh

--
http://nethu.org/


No virus found in this incoming message.
Checked by AVG Free Edition. Version: 7.5.516 / Virus Database: 
269.19.2/1223 - Release Date: 1/13/2008 8:23 PM
  


-
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]





-
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: Invailability of sed command on Windows addressed

[Uthaiyashankar]

Hi,

We have started discussion on rampart-dev list with the same subject. 
Please follow it.


Regards,
Shankar.

Samisa Abeysinghe wrote:

Should we not discuss this on rampart list?

Samisa...

Dumindu Pallewela wrote:

Hi Senaka,

Is this a problem anywhere outside secpolicy samples?

in secpolicy samples, however, this cannot be done without sed like
functionality, because we need to set the paths inside certain files
according to the install path that is defined at the build-time. Do
you see any other way out of this problem?

-Dumindu.

On Jan 15, 2008 6:24 PM, Senaka Fernando <[EMAIL PROTECTED]> wrote:
 

Hi devs,

It is a known fact that we can't use the sed command on windows 
unless you
install an add-on. Under these circumstances we have burdened our 
users to
do appropriate replacements so that the sed command wouldn't be 
necessary.
The Rampart/C secpolicy set of samples is a good example. However, 
there

is a way we could easily overcome this.

We initially do things for windows and during the Linux build 
process we
apply the sed command and covert it to Linux. This way, both Linux 
as well

as the Windows user will have a similar experience.

Regards,
Senaka

-
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]







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

Re: [Vote][Rampart-C] Vote for Apache Rampart/C 1.1.0 Release - Take 1

[Uthaiyashankar]

Hi,

I tested source and binary distribution in windows XP (with openssl 
0.9.8d) and it works fine.


Here is my +1.

Regards,
Shankar.

Kaushalye Kapuruge wrote:

Hi Devs,

I have uploaded the Apache Rampart/C 1.1.0 release artifacts here
http://people.apache.org/~kaushalye/release/rampart-c/1.1.0

The key to verify the release artifacts can be found at
http://people.apache.org/~kaushalye/release/KEYS

Please test and review.
If the released artifacts are fine, please vote for the Apache 
Rampart/C 1.1.0 release.

Here is my +1.

Cheers,
Kaushalye





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

Re: [Vote] [Axis2-C] Vote for Apache Axis2/C 1.2.0 Release - Take 5

[Uthaiyashankar]

Hi,
I tested the source distribution and binary distribution in windows XP, 
and it works fine...


here is my +1.

Regards,
Shankar.

Dimuthu Gamage wrote:

Hi,
I tested the Linux binary in Ubuntu 7.10 and it was working fine..

Here is my +1.

Thanks
Dimuthu

On Jan 10, 2008 11:04 AM, Kaushalye Kapuruge <[EMAIL PROTECTED]> wrote:
  

Dinesh Premalal wrote:


Hi,

Dinesh Premalal <[EMAIL PROTECTED]> writes:


  

  There is a bug in the generated site. It states latest version as
  1.1.0



I think it is kind of minor bug. Since Axis2/C 1.2.0 release already
delayed considerable time, I would suggest to go along with the vote
and do the release.

Here is my +1


  

Here is my +1.
-Kau


thanks,
Dinesh

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



  

--
http://blog.kaushalye.org/
http://wso2.org/



-
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]



  




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

Re: [Axis2][VOTE]Bill Mitchell as a committer

[Uthaiyashankar]

+1

Shankar.

Kaushalye Kapuruge wrote:

+1
-Kau

Milinda Pathirage wrote:

Here's my +1 for Bill.

Milinda

On Jan 8, 2008 12:37 PM, Manjula Peiris <[EMAIL PROTECTED] 
> wrote:


+1

-Manjula.

On Tue, 2008-01-08 at 11:10 +0530, Sanjaya Ratnaweera wrote:
> +1
>
> ~sanjaya
>
> Dushshantha Chandradasa wrote:
> > +1
> >
> > Dushshantha
> >
> > On Jan 8, 2008 10:59 AM, Nandika Jayawardana
<[EMAIL PROTECTED] >
> > wrote:
> > +1
> >
> > -- Nandika
> >
> >
> > On Jan 8, 2008 10:57 AM, Dimuthu Gamage
<[EMAIL PROTECTED] >
> > wrote:
> > Bill gave good suggestions to improve the
WSDL2C as
> > well.
> >
> > Here is my +1 to give him the commitership.
> >
> > Thanks,
> > Dimuthu
> >
> >
> > On Jan 8, 2008 10:47 AM, Supun Kamburugamuva
> > <[EMAIL PROTECTED] >
wrote:
> > > On Jan 8, 2008 10:28 AM, Dinesh Premalal
> > <[EMAIL PROTECTED]
> wrote:
> > > > Hi Devs,
> > > >
> > > > I would like to propose Bill Mitchell
as an
> > Axis2/C
> > > > committer. Bill has reported many
issues and
> > provided many
> > > > patches. He has contributed towards the
> > Axis2/C core, libcurl
> > > > based HTTP transport layer and code
> > generation tool. Here is some
> > > > of the issues that Bill has reported and
> > provided patches [1]. I'm
> > > > sure he will continue his contribution
> > towards the Axis2/C.
> > > >
> > > > Here is my +1 for Bill !
> > > >
> > > There is a great contribution to Guththila
parser
> > from Bill.
> > >
> > > Here is my +1.
> > >
> > > Thanks,
> > > Supun..
> > >
> > >
> > >
> >
-

> > > 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]

> >
> >
> >
> >
> >
> >
> > --
> > http://nandikajayawardana.blogspot.com/
> > WSO2 Inc: http://www.wso2.com
> >
>



-

To unsubscribe, e-mail: [EMAIL PROTECTED]

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





--
http://think2ed.blogspot.com "thinksquared"
http://wsaxc.blogspot.com "Web Services With Axis2/C" 







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

Re: Problem when running axis2c ws client in multiple threads

[Uthaiyashankar]

formatting of modified code is shown as *modified code* in the previous 
listing. so, please use the code listing given here.


Uthaiyashankar wrote:

Hehe Zhou wrote:

Hey,
 
  The following program will crash when the second thread starts up [ 
_beginthread() in main() ]. A unhandled exception error is reported 
and program crashes when 2nd thread starts to run ( 1st thread ends 
already). This test program is just a multi-threaded version from 
Math sample webservice client code of AXIS2. I just excute Math WS 
client twice in different thread. But I don't have this problem if 
Math WS Client is run in the same thread for two times. Any idea 
about this. I checked out the newest AXIS2C code from SVN. Same 
problem happened.
 
Platform: WinXP

Compilor: Visual Studio 2005 Professional
 

Hi Zhou,

The crashing is due to libxml in multi threaded environment. when 
using libxml in multithreaded environment,
(1) you have to call xmlInitParser() in the "main" thread before using 
any of the libxml2 API. (Refer http://xmlsoft.org/threads.html)
(2) should not call xmlCleanupParser() from individual threads. It can 
be called from "main" thread at the end.


By default, when destroying axis2_stub, it will call 
xmlCleanupParser(). To disable it, after creating axis2_stub, the 
option xml_parser_reset should be set to false.


so, the modified code should be as given below.

Regards,
Shankar.


/*
MathWSClient.cpp : Defines the entry point for the console application.
*/

#include "axis2_math_stub.h"
#include 
#include 
#include 
#include 
#include 
/*#include */

/*using namespace std;*/

axiom_node_t *
build_om_programatically(
  const axutil_env_t *env,
  const axis2_char_t *operation,
  const axis2_char_t *param1,
  const axis2_char_t *param2);

void
run(void* param)

{
  axis2_stub_t *stub = NULL;
  axiom_node_t *node = NULL;
  axis2_status_t status = AXIS2_FAILURE;
  const axutil_env_t *env = NULL;
  const axis2_char_t *address = NULL;
  const axis2_char_t *client_home = NULL;
  axiom_node_t *ret_node = NULL;
  const axis2_char_t *operation = "add";
  const axis2_char_t *param1 = "40";
  const axis2_char_t *param2 = "8";
  axis2_options_t* options = NULL;

  env = axutil_env_create_all(
  "math_blocking.log", AXIS2_LOG_LEVEL_TRACE);

  client_home = AXIS2_GETENV(
  "AXIS2C_HOME");

  if (!client_home || !strcmp (client_home, ""))

  client_home =
  "../..";

  address =
  "http://localhost:9090/axis2/services/math";;

  printf(
  "Using endpoint : %s\n", address);

  printf(
  "\nInvoking operation %s with params %s and %s\n", operation, param1, 
param2);

  node = build_om_programatically(env, operation, param1, param2);

  stub =axis2_math_stub_create_with_endpoint_uri_and_client_home(env, 
address, client_home);


  /* create node and invoke math */

  if (stub)
  {
  options = axis2_stub_get_options(stub, env);
  if (options)
  {
  axis2_options_set_xml_parser_reset(options, env, AXIS2_FALSE);
  }
  ret_node = axis2_math_stub_add(stub, env, node);
  }

  if (ret_node)
  {
  if (axiom_node_get_node_type(ret_node, env) == AXIOM_ELEMENT)
  {
  axis2_char_t *result = NULL;
  axiom_element_t *result_ele = 
(axiom_element_t*)axiom_node_get_data_element(ret_node, env);

  result = axiom_element_get_text(result_ele, env, ret_node);
  printf(
  "\nResult = %s\n", result);
  }
  else
  {
  axiom_xml_writer_t *writer = NULL;
  axiom_output_t *om_output = NULL;
  axis2_char_t *buffer = NULL;
  writer = axiom_xml_writer_create_for_memory(env, NULL, 
AXIS2_TRUE, 0,

  AXIS2_XML_PARSER_TYPE_BUFFER);
  om_output = axiom_output_create(env, writer);
  axiom_node_serialize(ret_node, env, om_output);
  buffer = (axis2_char_t*)axiom_xml_writer_get_xml(writer, env);
  printf(
  "\nReceived invalid OM as result : %s\n", buffer);

  if (buffer)
  {
  AXIS2_FREE(env->allocator, buffer);
  buffer = NULL;
  }

  if (om_output)
  {
  axiom_output_free(om_output, env);
  om_output = NULL;
  }

  axiom_xml_writer_free(writer, env);

  }
  }
  else
  {
  AXIS2_LOG_ERROR(env->log, AXIS2_LOG_SI,
  "Stub invoke FAILED: Error code:"
  " %d :: %s", env->error->error_number,
  AXIS2_ERROR_GET_MESSAGE(env->error));
  printf(
  "math stub invoke FAILED!\n");
  }

  if (stub)
  {
  axis2_stub_free(stub, env);
  }

  if (env)
  {
  axutil_env_free((axutil_env_t *) env);
  env = NULL;
  }

  _endthread();
}

int
main(int argc, char* argv[])
{
  axiom_xml_reader_init();
  _beginthread(run, 0, NULL);
  Sleep(5000);
  _beginthread(run, 

Re: Problem when running axis2c ws client in multiple threads

[Uthaiyashankar]

Hehe Zhou wrote:

Hey,
 
  The following program will crash when the second thread starts up [ 
_beginthread() in main() ]. A unhandled exception error is reported 
and program crashes when 2nd thread starts to run ( 1st thread ends 
already). This test program is just a multi-threaded version from Math 
sample webservice client code of AXIS2. I just excute Math WS client 
twice in different thread. But I don't have this problem if Math WS 
Client is run in the same thread for two times. Any idea about this. I 
checked out the newest AXIS2C code from SVN. Same problem happened.
 
Platform: WinXP

Compilor: Visual Studio 2005 Professional
 

Hi Zhou,

The crashing is due to libxml in multi threaded environment. when using 
libxml in multithreaded environment,
(1) you have to call xmlInitParser() in the "main" thread before using 
any of the libxml2 API. (Refer http://xmlsoft.org/threads.html)
(2) should not call xmlCleanupParser() from individual threads. It can 
be called from "main" thread at the end.


By default, when destroying axis2_stub, it will call xmlCleanupParser(). 
To disable it, after creating axis2_stub, the option xml_parser_reset 
should be set to false.


so, the modified code should be as given below.

Regards,
Shankar.

/*
MathWSClient.cpp : Defines the entry point for the console application.
*/

#include "axis2_math_stub.h"
#include 
#include 
#include 
#include 
#include 
/*#include */

/*using namespace std;*/

axiom_node_t *
build_om_programatically(
   const axutil_env_t *env,
   const axis2_char_t *operation,
   const axis2_char_t *param1,
   const axis2_char_t *param2);

void
run(void* param)

{
   axis2_stub_t *stub = NULL;
   axiom_node_t *node = NULL;
   axis2_status_t status = AXIS2_FAILURE;
   const axutil_env_t *env = NULL;
   const axis2_char_t *address = NULL;
   const axis2_char_t *client_home = NULL;
   axiom_node_t *ret_node = NULL;
   const axis2_char_t *operation = "add";
   const axis2_char_t *param1 = "40";
   const axis2_char_t *param2 = "8";
*axis2_options_t* options = NULL;*

   env = axutil_env_create_all(
   "math_blocking.log", AXIS2_LOG_LEVEL_TRACE);

   client_home = AXIS2_GETENV(
   "AXIS2C_HOME");

   if (!client_home || !strcmp (client_home, ""))

   client_home =
   "../..";

   address =
   "http://localhost:9090/axis2/services/math";;

   printf(
   "Using endpoint : %s\n", address);

   printf(
   "\nInvoking operation %s with params %s and %s\n", operation, 
param1, param2);

   node = build_om_programatically(env, operation, param1, param2);

   stub =axis2_math_stub_create_with_endpoint_uri_and_client_home(env, 
address, client_home);


   /* create node and invoke math */

   if (stub)
   {
   *options = axis2_stub_get_options(stub, env);
   if (options)
   {
   axis2_options_set_xml_parser_reset(options, env, AXIS2_FALSE);
   }*
   ret_node = axis2_math_stub_add(stub, env, node);
   }

   if (ret_node)
   {
   if (axiom_node_get_node_type(ret_node, env) == AXIOM_ELEMENT)
   {
   axis2_char_t *result = NULL;
   axiom_element_t *result_ele = 
(axiom_element_t*)axiom_node_get_data_element(ret_node, env);

   result = axiom_element_get_text(result_ele, env, ret_node);
   printf(
   "\nResult = %s\n", result);
   }
   else
   {
   axiom_xml_writer_t *writer = NULL;
   axiom_output_t *om_output = NULL;
   axis2_char_t *buffer = NULL;
   writer = axiom_xml_writer_create_for_memory(env, NULL, 
AXIS2_TRUE, 0,

   AXIS2_XML_PARSER_TYPE_BUFFER);
   om_output = axiom_output_create(env, writer);
   axiom_node_serialize(ret_node, env, om_output);
   buffer = (axis2_char_t*)axiom_xml_writer_get_xml(writer, env);
   printf(
   "\nReceived invalid OM as result : %s\n", buffer);

   if (buffer)
   {
   AXIS2_FREE(env->allocator, buffer);
   buffer = NULL;
   }

   if (om_output)
   {
   axiom_output_free(om_output, env);
   om_output = NULL;
   }

   axiom_xml_writer_free(writer, env);

   }
   }
   else
   {
   AXIS2_LOG_ERROR(env->log, AXIS2_LOG_SI,
   "Stub invoke FAILED: Error code:"
   " %d :: %s", env->error->error_number,
   AXIS2_ERROR_GET_MESSAGE(env->error));
   printf(
   "math stub invoke FAILED!\n");
   }

   if (stub)
   {
   axis2_stub_free(stub, env);
   }

   if (env)
   {
   axutil_env_free((axutil_env_t *) env);
   env = NULL;
   }

   _endthread();
}

int
main(int argc, char* argv[])
{
   *axiom_xml_reader_init();*
   _beginthread(run, 0, NULL);
   Sleep(5000);
   _beginthread(run, 0, NULL);
   Sleep(5000);
   *axiom_xml_reader_cleanup();*
   return 0;
}

axiom_node_t *
build_om_programatically(
const axutil_env_t *env,
const axis2_char_t *operation,
const axis2_char_t *param1,
const axis2_char_t *param2)
{
   axiom_node_t *math_om_

Re: [Axis2] Apache process problems [Was - Re: Urgent: Specifying scope in Axis2c]

[Uthaiyashankar]

Hi,

An implementation is given in 
https://issues.apache.org/jira/browse/AXIS2C-780

please check and apply the patch. comments are welcome.

regards,
Uthaiyashankar.

Uthaiyashankar wrote:

Hi Chris,

Thank you very much for the comment. For the initial phase, as you 
advised, we'll proceed by allocating a large block without resizing. 
Later on, we can implement the resizing logic.


Regards,
Uthaiyashankar



Chris Darroch wrote:

Uthaiyashankar wrote:

 
We can use global mutex to control the access of shared memory. An 
example implementation is given in  
http://people.apache.org/~sctemme/mod_example_ipc.c.
mod_ldap is also using a similar approach to cache and share data 
between child processes.


However, to hide the low level details from service/module 
implementers, we might have to write a wrapper to manage the shared 
memory, growing/shrinking the shared memory according to the demand, 
creating objects in shared memory, etc.



   One caution: growing/shrinking shared memory is likely to be a
pretty complex operation, if it's even possible with certain 
shared-memory

implementations.  APR provides a number of different shared memory
options and chooses between them at compile-time; the only options
to the programmer are named-based vs. anonymous.

   To resize the shared memory block, you'd probably need name-based
shared memory, first of all.  The only way I can see resizing would
work is if all the processes coordinate; suppose, for example, that
process A acquires the global lock, it could then allocate a new
shared-memory block, copy all the data from the old one, and write
the filename associated with the new block into a special location
in the old one or communicate it somehow to all other processes;
they then need to attach to the new block and detach from the old block.
Depending on the underlying implementation, you might, I suppose,
need to also manage a reference count of how many processes are
still attached to the old block, and only destroy it when all had
attached to the new block; this of course gets complicated if a
process dies suddenly, etc.

   This is why httpd, for its scoreboard, simply creates a large
shared memory segment at startup (based on compile-time limits)
and never tries to resize it.

   A number of httpd modules already manage data in shared memory
segments (in one case, by borrowing part of the scoreboard, but
that's not ideal).  I proposed, for httpd 3.0, some ideas about how
to try to abstract the subject of inter-process data sharing, such
that different providers could be plugged into a generic interface
(shared memory, memcache, etc.):

http://svn.apache.org/viewvc/httpd/sandbox/amsterdam/architecture/scoreboard.txt   


   I think Axis2/C might be a good candidate to be another user of
this mechanism ... but, of course, it exists only on paper so far.
With luck I'll get back to this in 2008; time permitting, of course!

Cheers,

Chris.

  



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

Re: [Axis2] Apache process problems [Was - Re: Urgent: Specifying scope in Axis2c]

[Uthaiyashankar]

Hi Chris,

Thank you very much for the comment. For the initial phase, as you 
advised, we'll proceed by allocating a large block without resizing. 
Later on, we can implement the resizing logic.


Regards,
Uthaiyashankar



Chris Darroch wrote:

Uthaiyashankar wrote:

  
We can use global mutex to control the access of shared memory. An 
example implementation is given in  
http://people.apache.org/~sctemme/mod_example_ipc.c.
mod_ldap is also using a similar approach to cache and share data 
between child processes.


However, to hide the low level details from service/module 
implementers, we might have to write a wrapper to manage the shared 
memory, growing/shrinking the shared memory according to the demand, 
creating objects in shared memory, etc.



   One caution: growing/shrinking shared memory is likely to be a
pretty complex operation, if it's even possible with certain shared-memory
implementations.  APR provides a number of different shared memory
options and chooses between them at compile-time; the only options
to the programmer are named-based vs. anonymous.

   To resize the shared memory block, you'd probably need name-based
shared memory, first of all.  The only way I can see resizing would
work is if all the processes coordinate; suppose, for example, that
process A acquires the global lock, it could then allocate a new
shared-memory block, copy all the data from the old one, and write
the filename associated with the new block into a special location
in the old one or communicate it somehow to all other processes;
they then need to attach to the new block and detach from the old block.
Depending on the underlying implementation, you might, I suppose,
need to also manage a reference count of how many processes are
still attached to the old block, and only destroy it when all had
attached to the new block; this of course gets complicated if a
process dies suddenly, etc.

   This is why httpd, for its scoreboard, simply creates a large
shared memory segment at startup (based on compile-time limits)
and never tries to resize it.

   A number of httpd modules already manage data in shared memory
segments (in one case, by borrowing part of the scoreboard, but
that's not ideal).  I proposed, for httpd 3.0, some ideas about how
to try to abstract the subject of inter-process data sharing, such
that different providers could be plugged into a generic interface
(shared memory, memcache, etc.):

http://svn.apache.org/viewvc/httpd/sandbox/amsterdam/architecture/scoreboard.txt   


   I think Axis2/C might be a good candidate to be another user of
this mechanism ... but, of course, it exists only on paper so far.
With luck I'll get back to this in 2008; time permitting, of course!

Cheers,

Chris.

  

Hi Chris,

Thank you very much for the comment. For the initial phase, as you 
advised, we'll proceed by allocating a large block without resizing. 
Later on, we can implement the resizing logic.


Regards,
Uthaiyashankar

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

Re: [Axis2] Apache process problems [Was - Re: Urgent: Specifying scope in Axis2c]

[Uthaiyashankar]

Hi,

Since apache is creating child processes using fork (in linux), only 
possible option to share data between children is using an ipc method. 
For example, creating Axis2_worker, conf_context and global pool in a 
shared memory, and sharing between processes (using apr_shm, apr_rmm). 
We can use global mutex to control the access of shared memory. An 
example implementation is given in  
http://people.apache.org/~sctemme/mod_example_ipc.c.
mod_ldap is also using a similar approach to cache and share data 
between child processes.


However, to hide the low level details from service/module implementers, 
we might have to write a wrapper to manage the shared memory, 
growing/shrinking the shared memory according to the demand, creating 
objects in shared memory, etc.


It is also possible to use apr_dbm/apr_memcache to share data, but those 
are similar to using a database.


Any other thoughts or comments ??

Regards,
Uthaiyashankar.

Samisa Abeysinghe wrote:

FYI: This mail was in the user list.
I think we have to solve this mod_axis2 related problems, specially 
for the benefit of the production users.


At a glance, it looks to me as if we can solve this by using either 
apr_proc_mutex [1] or apr_global_mutex [2].
At a glance, it looks to me as if using apr_global_mutex and locking 
the stuff could be the solution.


Thoughts please...

[1] http://apr.apache.org/docs/apr/0.9/apr__proc__mutex_8h.html
[2] http://apr.apache.org/docs/apr/0.9/apr__global__mutex_8h.html

Thanks,
Samisa...


 Original Message 
Subject: Re: Urgent: Specifying scope in Axis2c
Date: Fri, 12 Oct 2007 08:59:17 +0600
From: Samisa Abeysinghe <[EMAIL PROTECTED]>
Reply-To: Apache AXIS C User List <[EMAIL PROTECTED]>
To: Apache AXIS C User List <[EMAIL PROTECTED]>
References: 
<[EMAIL PROTECTED]>




Subra A Narayanan wrote:

Hello everyone,

I have run in to an issue which I can't seem to figure out. In my 
init method in the service skeleton I call the initialization routine 
of one of the libraries that my web service uses. I notice in my logs 
that the library initialization function is being called 8 times. 
This corresponds to the number of apache processes that are running.
This is a problem yet to be solved in Axis2/C. See 
http://damithakumarage.wordpress.com/2007/09/23/an-axis2-c-design-issue/.

This is a pending issue that needs to be fixed.
The workaround for the time being would be to use some persistent 
storage to keep a flag and call the init routine based on the flag value.


Samisa...


This is causing a lot of issues because I was under the impression 
that my web service init function is called only once when the first 
request comes in. My library sets up some resources which I want to 
share among all processes. Can this be done?


In Axis2/Java there is a way to specify scope for the webservice 
(request, session, application) in the services.xml file? can 
something similar be done in Axis2/c? I took a look at the axis2c 
code and saw that there is an enum called axis2_scope defined. Is it 
used for the same purpose as in Axis2/Java?


Thanks for any help.

Subra









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

Re: [Vote][Rampart-C]Vote for Apache Rampart/C 1.0.0 Release

[Uthaiyashankar]

Hi Kaushalye,

When testing in windows XP, i came across some problems.
(1) In binary version, deploy_rampart.bat reads the samples directory as 
bin/sample. But in the distribution, the sample directory is directly 
under the deployed root.
(2) In source version, group__rampart__util.html and 
group__Rampart__Util.html (in docs/api/html) are having name confilicts.


Regards,
Shankar.


Kaushalye Kapuruge wrote:

Hi Devs,

I have packaged and uploaded the Apache Rampart/C 1.0.0 release 
artifacts at

http://people.apache.org/~kaushalye/release/rampart-c/1.0.0/

The key to verify the release artifacts can be found at
http://people.apache.org/~kaushalye/release/KEYS

Please test and review. If the released artifacts are fine, please 
vote for the Apache Rampart/C 1.0.0 release.

Here is my +1.

Cheers,
Kaushalye




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

Re: [Vote 2] [Axis2] Vote for Apache Axis2/C 1.1.0 Release

[Uthaiyashankar]

Hi,

I tested the binary and source on Ubuntu 7.04.  Also, tested the source 
with  Solaris 10 (intel version).

Here is my +1

Regards,
Uthaiyashankar



Dushshantha Chadradasa wrote:

Hi,

I tested the linux binary and source distributions on Ubuntu 6.04.
Here's my +1

Dushshantha

Manjula Peiris wrote:

Tested the linux source on Debian 4.0 . Also tested Sandesha2/C with the
package. Works fine.
Here is my +1.

-Manjula.



On Mon, 2007-09-24 at 17:04 +0530, Dimuthu Gamage wrote:
 

Tested and reviewed the source and linux binary packages in ubuntu
7.04. Here is my +1

Thanks
Dimuthu

On 9/24/07, Dinesh Premalal <[EMAIL PROTECTED]> wrote:
I test and reviewed packages. Here my +1
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]
   




-
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]





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