Return-Path: Delivered-To: apmail-ws-axis-c-dev-archive@www.apache.org Received: (qmail 14580 invoked from network); 15 Feb 2010 18:36:56 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 15 Feb 2010 18:36:56 -0000 Received: (qmail 72634 invoked by uid 500); 15 Feb 2010 16:50:15 -0000 Delivered-To: apmail-ws-axis-c-dev-archive@ws.apache.org Received: (qmail 72565 invoked by uid 500); 15 Feb 2010 16:50:15 -0000 Mailing-List: contact axis-c-dev-help@ws.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: "Apache AXIS C Developers List" Reply-To: "Apache AXIS C Developers List" Delivered-To: mailing list axis-c-dev@ws.apache.org Received: (qmail 72556 invoked by uid 99); 15 Feb 2010 16:50:15 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 15 Feb 2010 16:50:15 +0000 X-ASF-Spam-Status: No, hits=3.4 required=10.0 tests=HTML_MESSAGE,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [98.136.167.132] (HELO web113912.mail.gq1.yahoo.com) (98.136.167.132) by apache.org (qpsmtpd/0.29) with SMTP; Mon, 15 Feb 2010 16:50:05 +0000 Received: (qmail 317 invoked by uid 60001); 15 Feb 2010 16:49:44 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ymail.com; s=s1024; t=1266252584; bh=JGVnIUNzrhbzh4XbJ+dj21+H6ZoG4/Sz0cgAnvj9HbE=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=buZ8uyZq0e+XiVms7DjTYQRvxjMrAzLD0aT1w1yF0Lam8s2Y7s5Y3pjFgZ4JyUVtfD1z0wlHKhD0b067rAdEVLry+tgQOBcbFiX/PbDZk35FVPSLe13coQrvjyoiG7htMz5wx5GlteK12Fpoecw7NUvKcwvbZfGzurpLHwv4eEI= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=ymail.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=4nbMk6cgiRlYXPE65TxjyfnJWQCJX36GC0oX/UvuwhwSpz278KTXTHisEtbpBp/CteQk2vMXO/NEmHiCjUebxStjAeC3bBw16sC+zgl22FTMU56bhCvdT/SPcdJ41CUP0spICZ8yPpjhZIo92qREBRTke+Yn5P0qYvhF9w8Yyzo=; Message-ID: <480811.98428.qm@web113912.mail.gq1.yahoo.com> X-YMail-OSG: ATUifOcVM1mGXUmWgRVtT_HBLEEm_6QeIh0h6ccGoNTVC3nf5kYHiMRzDAKFHnNa65ecy2xcSwpRRpA74ylF9CsWgYlwnVbBf7mCye8c32d.FrvkP0em1oKLBjgFUCrKhSEGw3pwIL0Rkm3EsRn8ZgmqK2bUNxNSDBT2PaVoBrYXvp1pi6ToN.K2XtYX5JnV0_6b.WoiuYgpsAmdAWPWIvwdcbZLcRrXoNqcDzxja91RpQG1_xwKkyZxjWGrxuY0Q38acGFlcz8r9lz6P6TcPckfYxynnyCkG0SKZioY Received: from [130.214.17.1] by web113912.mail.gq1.yahoo.com via HTTP; Mon, 15 Feb 2010 08:49:44 PST X-Mailer: YahooMailRC/300.3 YahooMailWebService/0.8.100.260964 References: <349018.35394.qm@web113913.mail.gq1.yahoo.com> <5e8118f31002142221l46e6470ge4c8875651ea35e4@mail.gmail.com> Date: Mon, 15 Feb 2010 08:49:44 -0800 (PST) From: Satish Bvs Subject: Re: NULL: axiom_node_t: node: Any side effects To: Nandika Jayawardana Cc: Apache AXIS C Developers List In-Reply-To: <5e8118f31002142221l46e6470ge4c8875651ea35e4@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-1012440159-1266252584=:98428" --0-1012440159-1266252584=:98428 Content-Type: text/plain; charset=us-ascii Nandika, Thank you for the response. I did try the alternative of using axiom_node_create, but was unsuccessful. Framework is generating coredump upon the return of Web Service operation that return's an node create by above function. Here is the back trace, ================= #0 0x0000002a9719c545 in free () from /lib64/tls/libc.so.6 #1 0x0000002a95d1232d in axis2_http_status_line_free (status_line=0x55bb80, env=0x55cd50) at http_status_line.c:149 #2 0x0000002a95d117cb in axis2_http_simple_response_free (simple_response=0x55bb60, env=0x55cd50) at http_simple_response.c:114 #3 0x0000002a95d10535 in axis2_http_out_transport_info_impl_free (http_out_transport_info=0x558cf0, env=0x55cd50) at http_out_transport_info.c:156 #4 0x0000002a95e61433 in axis2_msg_ctx_free (msg_ctx=0x55bd60, env=0x55cd50) at msg_ctx.c:443 #5 0x0000002a95d14a3d in axis2_http_worker_process_request (http_worker=0x5ef630, env=0x55cd50, svr_conn=0x55a8e0, simple_request=0x55c600) at http_worker.c:2008 #6 0x0000002a960aa9fc in axis2_svr_thread_worker_func (thd=0x55a890, data=0x55a860) at http_svr_thread.c:263 #7 0x0000002a97372137 in start_thread () from /lib64/tls/libpthread.so.0 #8 0x0000002a971fc883 in clone () from /lib64/tls/libc.so.6 No, there is no requirement for empty axiom element. We are using it as a work around to mimic empty response. So does the approach of creating and empty axiom_element has any side effects? Thanks, Satish. ________________________________ From: Nandika Jayawardana To: Apache AXIS C Developers List Sent: Mon, February 15, 2010 1:21:52 AM Subject: Re: NULL: axiom_node_t: node: Any side effects In order to create an empty axiom_node_t you can just use axiom_node_create method. Or is your requirement to create an empty axiom element ? Regards Nandika On Sat, Feb 13, 2010 at 4:02 AM, Satish Bvs wrote: Hi, > > >> Inline with our implementation needs, > to construct an NULL(empty) axiom_node_t, > i have made few canges to AxisC code base. > > > Specifically, the modification were to allow localname for axiom_element creation to be NULL. > > Can anyone help with Insight of possible side effects with this approach. > A prompt comments are very helpful. > >Thanks, >>Satish. > > > > -- http://nandikajayawardana.blogspot.com/ WSO2 Inc: http://www.wso2.com --0-1012440159-1266252584=:98428 Content-Type: text/html; charset=us-ascii
Nandika,

     Thank you for the response.

     I did try the alternative of using axiom_node_create, but was unsuccessful.
     Framework is generating coredump upon the return of Web Service operation that return's an node create by above function.

     Here is the back trace,
     =================
#0  0x0000002a9719c545 in free () from /lib64/tls/libc.so.6
#1  0x0000002a95d1232d in axis2_http_status_line_free (status_line=0x55bb80, env=0x55cd50) at http_status_line.c:149
#2  0x0000002a95d117cb in axis2_http_simple_response_free (simple_response=0x55bb60, env=0x55cd50) at http_simple_response.c:114
#3  0x0000002a95d10535 in axis2_http_out_transport_info_impl_free (http_out_transport_info=0x558cf0, env=0x55cd50) at http_out_transport_info.c:156
#4  0x0000002a95e61433 in axis2_msg_ctx_free (msg_ctx=0x55bd60, env=0x55cd50) at msg_ctx.c:443
#5  0x0000002a95d14a3d in axis2_http_worker_process_request (http_worker=0x5ef630, env=0x55cd50, svr_conn=0x55a8e0, simple_request=0x55c600) at http_worker.c:2008
#6  0x0000002a960aa9fc in axis2_svr_thread_worker_func (thd=0x55a890, data=0x55a860) at http_svr_thread.c:263
#7  0x0000002a97372137 in start_thread () from /lib64/tls/libpthread.so.0
#8  0x0000002a971fc883 in clone () from /lib64/tls/libc.so.6

    No, there is no requirement for empty axiom element.
    We are using it as a work around to mimic empty response.

    So does the approach of creating and empty axiom_element has any side effects?
 
Thanks,
Satish.


From: Nandika Jayawardana <jayawark@gmail.com>
To: Apache AXIS C Developers List <axis-c-dev@ws.apache.org>
Sent: Mon, February 15, 2010 1:21:52 AM
Subject: Re: NULL: axiom_node_t: node: Any side effects

In order to create an empty axiom_node_t you can just use axiom_node_create method. Or is your requirement to create an empty axiom element ?

Regards
Nandika

On Sat, Feb 13, 2010 at 4:02 AM, Satish Bvs <bvs.satish@ymail.com> wrote:
Hi,

     Inline with our implementation needs,
           to construct an NULL(empty) axiom_node_t,
           i have made few canges to AxisC code base.

     Specifically, the modification were to allow localname for axiom_element creation to be NULL.
   
     Can anyone help with Insight of possible side effects with this approach.
     A prompt comments are very helpful. 

Thanks,
Satish.





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

--0-1012440159-1266252584=:98428--