Mailing-List: contact axis-c-user-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache AXIS C User List" <axis-c-user@ws.apache.org>
Received-SPF: neutral (herse.apache.org: local policy)
Message-ID: <46A80E54.3060907@wso2.com>
Date: Thu, 26 Jul 2007 09:00:36 +0600
From: Samisa Abeysinghe <samisa@wso2.com>
User-Agent: Thunderbird 1.5 (X11/20060313)
MIME-Version: 1.0
To: Apache AXIS C User List <axis-c-user@ws.apache.org>
Subject: Re: Services.xml
References: 
 <LE2B97FF053AE489eAE12E36C25D5B2DB.1185285523.dakghar.aylus.com@MHS>
In-Reply-To: 
 <LE2B97FF053AE489eAE12E36C25D5B2DB.1185285523.dakghar.aylus.com@MHS>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Manoj Rao wrote:
> Hi all,
> What are the major differences in the logic of 
> axis2_raw_xml_in_out_msg_recv_invoke_business_logic_sync() function 
> between 0.90 and 1.0. Is it just the nomenclature of API's? I am facing 
> problems in my PostDispatch phase where my response xml from server is 
> not reaching the client. Please help me.
>   
Most probrbaly it is not the 
axis2_raw_xml_in_out_msg_recv_invoke_business_logic_sync()  function 
that is causing the problem. I guess it is the service implementation.

If you look at the service skeleton implementation, as an example, echo 
service, you will find that you have to allocate the ops struct as a 
static variable. e.g.

static const axis2_svc_skeleton_ops_t echo_svc_skeleton_ops_var = {
    echo_init,
    echo_invoke,
    echo_on_fault,
    echo_free
};

And in your service creation you have to assign it to ops

svc_skeleton->ops = &echo_svc_skeleton_ops_var;

Please check your service implementtion.

Samisa...

> Thanks,
> Manoj R
>
> -----Original Message-----
> From: Samisa Abeysinghe [mailto:samisa@wso2.com] 
> Sent: Monday, July 23, 2007 1:34 PM
> To: Apache AXIS C User List
> Subject: Re: Services.xml
>
> Looking at the back trace, the problem is most probably with the service 
>
> library.
> Please try to re-compile the service. Also make sure the old libs form 
> 0.90 are not in the library path, when you compile and run the service 
> and client.
>
> Samisa...
>
> Manoj Rao wrote:
>   
>> Ok Maybe I was not clear in my previous emails, sorry. I am using 
>>     
> 1.0's 
>   
>> axis2.xml and when I send a request from the client my application 
>>     
> dies 
>   
>> after invoking the handler context_handler in PostDispatch phase. 
>> Backtrace from core shows the following.
>>
>>
>>     
> ========================================================================
>   
>> (gdb) bt
>> #0  axis2_msg_recv_make_new_svc_obj (msg_recv=0x8194290, 
>>     
> env=0x81fbe28, 
>   
>> msg_ctx=0x81fc8f0) at msg_recv.c:157
>> #1  0xb7a61b35 in axis2_msg_recv_get_impl_obj (msg_recv=0x8194290, 
>> env=0x81fbe28, msg_ctx=0x81fc8f0) at msg_recv.c:184
>> #2  0xb7a61fc2 in 
>> axis2_raw_xml_in_out_msg_recv_invoke_business_logic_sync 
>> (msg_recv=0x8194290, env=0x81fbe28,
>>     msg_ctx=0x81fc8f0, new_msg_ctx=0x8204e50) at 
>> raw_xml_in_out_msg_recv.c:93
>> #3  0xb7a61694 in axis2_msg_recv_invoke_business_logic 
>> (msg_recv=0x8194290, env=0x81fbe28, in_msg_ctx=0x81fc8f0,
>>     out_msg_ctx=0x8204e50) at msg_recv.c:372
>> #4  0xb7a61c4d in axis2_msg_recv_receive_impl (msg_recv=0x8194290, 
>> env=0x81fbe28, msg_ctx=0x81fc8f0,
>>     callback_recv_param=0x0) at msg_recv.c:304
>> #5  0xb7a61714 in axis2_msg_recv_receive (msg_recv=0x8194290, 
>> env=0x81fbe28, msg_ctx=0x81fc8f0, callback_recv_param=0x0)
>>     at msg_recv.c:407
>> #6  0xb7a59aac in axis2_engine_receive (engine=0x82045b0, 
>>     
> env=0x81fbe28, 
>   
>> msg_ctx=0x81fc8f0) at engine.c:288
>> #7  0xb7a7e144 in axis2_http_transport_utils_process_http_post_request 
>>     
>
>   
>> (env=0x81fbe28, msg_ctx=0x81fc8f0,
>>     in_stream=0x81fbe58, out_stream=0x81fbff0, content_type=0x81fbef8 
>> "text/xml; charset=utf-8", content_length=632,
>>     soap_action_header=0x81fcc30, request_uri=0x81fca78 
>> "http://127.0.0.1:9090/axis2/services/SpsMvnoprofile")
>>     at http_transport_utils.c:485
>> #8  0xb76ad307 in axis2_http_worker_process_request 
>> (http_worker=0x81fa9d8, env=0x81fbe28, svr_conn=0x81fbe48,
>>     simple_request=0x81fbee0) at http_worker.c:299
>> #9  0xb7a8db72 in axis2_svr_thread_worker_func (thd=0x81fbda0, 
>> data=0x81faa10) at http_svr_thread.c:256
>> #10 0xb7aad9fd in dummy_worker () from /opt/aylus/lib/libaxutil.so.0
>> #11 0xb7f510bd in start_thread () from /lib/tls/libpthread.so.0
>> #12 0xb793b9ee in clone () from /lib/tls/libc.so.6
>>
>>     
> ========================================================================
>   
>> I am not quite sure what the problem is, AXIS2_SVC_SKELETON_INIT fails 
>>     
>
>   
>> as impl_class = 0x00
>>
>> -----Original Message-----
>> From: Dinesh Premalal [mailto:xydinesh@gmail.com] 
>> Sent: Monday, July 23, 2007 1:43 PM
>> To: axis-c-user@ws.apache.org
>> Subject: Re: Services.xml
>>
>> Hi Manoj,
>> "Manoj Rao" <rmanoj@aylus.com> writes:
>>
>>   
>>     
>>> Hi Dinesh,
>>> Thanks for the reply. I was using axis2c 0.90 till recently and now 
>>> migrated to 1.0 the same services.xml doesn't work here is there 
>>> anything I need to change in axis2.xml before using it? Sample of my 
>>> working services.xml is the simple math sample.
>>>     
>>>       
>> It is the same services.xml still in math sample. AFAIK there is no
>> special changes required in axis2.xml. What does your axis2.log says ?
>>
>> thanks,
>> Dinesh
>>
>>   
>>     
>
>
>   


-- 
Samisa Abeysinghe : http://www.wso2.org/ (WSO2 Oxygen Tank - Web Services Developers' Portal)


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