[ http://issues.apache.org/jira/browse/AXIS2C-63?page=comments#action_12366193 ]
Samisa Abeysinghe commented on AXIS2C-63: ----------------------------------------- We can make the client live with this situation. I have modified the addr_echo sample to demo how. > server.xml files are processed when running client > -------------------------------------------------- > > Key: AXIS2C-63 > URL: http://issues.apache.org/jira/browse/AXIS2C-63 > Project: Axis2-C > Type: Bug > Components: core/deployment > Reporter: Samisa Abeysinghe > > I see no point client trying to read server.xml files. However, it seems that > when I run a client, server.xml for service groups are processed. > Here is a trace: > bt > #0 0x00475460 in axis2_om_document_build_all (document=0xa03ac78, > env=0xbf84a954) at om_document.c:315 > #1 0x006f617a in axis2_build_OM (desc_builder=0xa02fe48, env=0xbf84a954) at > desc_builder.c:294 > #2 0x006f92a7 in axis2_arch_reader_build_svc_grp (arch_reader=0xa02fa00, > env=0xbf84a954, > svc_xml=0xa02fe08 > "/home/samisa/axis2/c/deploy/services/echo/services.xml", > dep_engine=0xa001948, svc_grp=0xa02fa30) > at arch_reader.c:381 > #3 0x006f8f13 in axis2_arch_reader_process_svc_grp (arch_reader=0xa02fa00, > env=0xbf84a954, file_name=0xa020e70 "echo", > dep_engine=0xa001948, svc_grp=0xa02fa30) at arch_reader.c:339 > #4 0x006fdf21 in axis2_dep_engine_do_deploy (dep_engine=0xa001948, > env=0xbf84a954) at dep_engine.c:1431 > #5 0x00703242 in axis2_ws_info_list_update (info_list=0xa020430, > env=0xbf84a954) at ws_info_list.c:512 > #6 0x0070aa21 in axis2_repos_listener_update (listener=0xa01faa0, > env=0xbf84a954) at repos_listener.c:261 > #7 0x0070abc7 in axis2_repos_listener_init (listener=0xa01faa0, > env=0xbf84a954) at repos_listener.c:289 > #8 0x0070a350 in axis2_repos_listener_create_with_folder_name_and_dep_engine > (env=0xbf84a954, > folder_name=0xa001a70 "/home/samisa/axis2/c/deploy", > dep_engine=0xa001948) at repos_listener.c:170 > #9 0x006fbe12 in axis2_dep_engine_load_client (dep_engine=0xa001948, > env=0xbf84a954, > client_home=0xbf84b7a9 "/home/samisa/axis2/c/deploy") at dep_engine.c:853 > #10 0x0070b392 in build_client_conf_ctx (env=0xbf84a954, > axis2_home=0xbf84b7a9 "/home/samisa/axis2/c/deploy") > at conf_init.c:79 > #11 0x00ddea3d in axis2_call_assume_svc_ctx (call=0xa001910, env=0xbf84a954, > client_home=0xbf84b7a9 "/home/samisa/axis2/c/deploy") at call.c:1194 > #12 0x00ddbdb6 in axis2_call_create (env=0xbf84a954, svc_ctx=0x0, > client_home=0xbf84b7a9 "/home/samisa/axis2/c/deploy") > at call.c:203 > #13 0x00de0574 in axis2_stub_create_with_endpoint_ref_and_client_home > (env=0xbf84a954, endpoint_ref=0xa001690, > client_home=0xbf84b7a9 "/home/samisa/axis2/c/deploy") at stub.c:277 > #14 0x00de0778 in axis2_stub_create_with_endpoint_uri_and_client_home > (env=0xbf84a954, > endpoint_uri=0x80493a0 "http://localhost:9090/axis2/services/echo/echo";, > client_home=0xbf84b7a9 "/home/samisa/axis2/c/deploy") at stub.c:307 > #15 0x08048f88 in main (argc=1, argv=0xbf84aa14) at echo_client.c:64 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
