Hi,
I am using axis2c_1.5.0 release.
When I specify libDir and moduleDir in axis2.xml, axis2c client on Linux
still, axis2c client run time still does not use paths specified in
axis2.xml file and exits with an error. I am attaching my axis2.xml
file. I am specifying
<parameter name="libDir">/usr/local/axis2c/lib</parameter>
<parameter name="moduleDir">/usr/local/axis2c/modules</parameter>
as children of axisconfig root element.
Here is the axis2client log
[Wed Apr 15 10:49:36 2009] [error] class_loader.c(162) Loading shared
library /usr/ops/5.0/config/wsclient/http/lib/libaxis2_http_sender.so
Failed. DLERROR IS
/usr/ops/5.0/config/wsclient/http/lib/libaxis2_http_sender.so: cannot
open shared object file: No such file or directory
[Wed Apr 15 10:49:36 2009] [error] conf_builder.c(898) Transport sender
is NULL for transport http, unable to continue
[Wed Apr 15 10:49:36 2009] [error] conf_builder.c(261) Processing
transport senders failed, unable to continue
[Wed Apr 15 10:49:36 2009] [error] dep_engine.c(939) Populating Axis2
Configuration failed
[Wed Apr 15 10:49:36 2009] [error] conf_init.c(195) Loading deployment
engine failed for client repository /usr/ops/5.0/config/wsclient/http
[Wed Apr 15 10:49:36 2009] [error] class_loader.c(162) Loading shared
library /usr/ops/5.0/config/wsclient/http/lib/libaxis2_http_sender.so
Failed. DLERROR IS
/usr/ops/5.0/config/wsclient/http/lib/libaxis2_http_sender.so: cannot
open shared object file: No such file or directory
[Wed Apr 15 10:49:36 2009] [error] conf_builder.c(898) Transport sender
is NULL for transport http, unable to continue
[Wed Apr 15 10:49:36 2009] [error] conf_builder.c(261) Processing
transport senders failed, unable to continue
[Wed Apr 15 10:49:36 2009] [error] dep_engine.c(939) Populating Axis2
Configuration failed
[Wed Apr 15 10:49:36 2009] [error] conf_init.c(195) Loading deployment
engine failed for client repository /usr/ops/5.0/config/wsclient/http
[Wed Apr 15 10:49:42 2009] [error] class_loader.c(162) Loading shared
library /usr/ops/5.0/config/wsclient/http/lib/libaxis2_http_sender.so
Failed. DLERROR IS
/usr/ops/5.0/config/wsclient/http/lib/libaxis2_http_sender.so: cannot
open shared object file: No such file or directory
[Wed Apr 15 10:49:42 2009] [error] conf_builder.c(898) Transport sender
is NULL for transport http, unable to continue
[Wed Apr 15 10:49:42 2009] [error] conf_builder.c(261) Processing
transport senders failed, unable to continue
I need to have lib and modules located in AXIS2C_HOME directory. I am
setting up soft links to actual lib and module dir. Once lib and modules
links are set up in axis2c_home dir every thing works fine.
Thanks,
Raghu
________________________________
From: Raymond Zhou [mailto:[email protected]]
Sent: Tuesday, March 10, 2009 1:11 PM
To: Apache AXIS C User List
Subject: Re: multiple configurations (multiple axis2.xml with different
names)?
OK, I just tried, it seems that I can only use the name axis2.xml. I can
specify different folds and axis2/c will look for axis2.xml in that
fold. I can also specify a file path ended with axis2.xml. All works
fine. But axis2/c will fail to create a wb service client if I specify a
full file path with a name different from axis2.xml.
I think this needs to be fixed. In my environment, my web service client
needs to connect to several web service providers with different
configurations, it would be convenient if I can create several config
files with different names.
Thanks!
Frank
--- On Mon, 3/2/09, Samisa Abeysinghe <[email protected]> wrote:
From: Samisa Abeysinghe <[email protected]>
Subject: Re: multiple configurations (multiple axis2.xml with
different names)?
To: "Apache AXIS C User List" <[email protected]>
Date: Monday, March 2, 2009, 1:35 AM
Raymond Zhou wrote:
> OK, Thanks Dinesh.
> So it seems that I can create multiple configuration files
all named axis2.xml but put in different folds, and in each axis2.xml,
specify the library and module locations pointing to the single axis2/c
installation.
> It would be nice if I can create multiple configuration files
with different names, so I can put them in a same fold, and then set the
axis2_home programmatically.
>
That should be possible, but we might have to pach the current
implementation of config builder.
Thanks,
Samisa...
> Thanks!
> Frank
>
>
> --- On *Fri, 2/27/09, Dinesh Premalal /<[email protected]
<http://us.mc464.mail.yahoo.com/mc/[email protected]> >/*
wrote:
>
> From: Dinesh Premalal <[email protected]
<http://us.mc464.mail.yahoo.com/mc/[email protected]> >
> Subject: Re: multiple configurations (multiple axis2..xml
with
> different names)?
> To: [email protected]
<http://us.mc464.mail.yahoo.com/mc/[email protected]>
> Cc: [email protected]
<http://us.mc464.mail.yahoo.com/mc/[email protected]> ,
[email protected]
<http://us.mc464.mail.yahoo.com/mc/[email protected]>
> Date: Friday, February 27, 2009, 7:53 PM
>
> Raymond Zhou <[email protected]
<http://us.mc464.mail.yahoo.com/mc/[email protected]> >
writes:
> > I was wondering if I can have multiple configuration
file with different
> name
> > in the same axis2_home fold. What I need is this: in the
same axis2_home
> fold,
> > I would like to have axis2_1.xml, axis2_2.xml,
axis2_3.xml and so on and
> so
> > forth, then when I want to connect to different web
servers, I can use
> these
> > different configuration files.
>
> http://wso2.org/library/3330
>
> thanks,
> Dinesh
>
>
>
------------------------------------------------------------------------
>
>
> Internal Virus Database is out of date.
> Checked by AVG - http://www.avg.com <http://www.avg.com/>
Version: 8.0.176 / Virus Database: 270.10.7/1892 - Release Date:
1/13/2009 8:04 PM
>
>
-- Samisa Abeysinghe Director, Engineering; WSO2 Inc.
http://www.wso2.com/ - "The Open Source SOA Company"
<axisconfig name="Axis2/C">
<!-- ================================================= -->
<!-- Parameters -->
<!-- ================================================= -->
<!-- Uncomment following to enable MTOM support globally -->
<!--parameter name="enableMTOM" locked="false">true</parameter-->
<!-- Set the suitable size for optimum memory usage when sending large attachments -->
<!--parameter name="MTOMChunkBufferSize" locked="false">10</parameter-->
<!--parameter name="MTOMMaxChunkBuffers" locked="false">1000</parameter-->
<!-- Enable REST -->
<parameter name="enableREST" locked="false">true</parameter>
<!-- Uncomment following to persist op_ctx, useful with RM -->
<!--parameter name="persistOperationContext" locked="false">true</parameter-->
<!--if you want to extract the service archive file and work with that please uncomment this-->
<!--else , it wont extract archive file or does not take into consideration if someone drop-->
<!--exploded directory into /service directory-->
<!--<parameter name="extractServiceArchive" locked="false">true</parameter>-->
<parameter name="libDir">/usr/local/axis2c/lib</parameter>
<parameter name="moduleDir">/usr/local/axis2c/modules</parameter>
<!-- ================================================= -->
<!-- Message Receivers -->
<!-- ================================================= -->
<!-- This is the Deafult Message Receiver for the Request Response style Operations -->
<!--messageReceiver mep="INOUT" class="axis2_receivers"/-->
<!-- ================================================= -->
<!-- Transport Ins -->
<!-- ================================================= -->
<transportReceiver name="http" class="axis2_http_receiver">
<parameter name="port" locked="false">6060</parameter>
<parameter name="exposeHeaders" locked="true">false</parameter>
</transportReceiver>
<!--transportReceiver name="https" class="axis2_http_receiver">
<parameter name="port" locked="false">6060</parameter>
<parameter name="exposeHeaders" locked="true">false</parameter>
</transportReceiver-->
<!--transportReceiver name="tcp" class="axis2_tcp_receiver">
<parameter name="port" locked="false">6060</parameter>
</transportReceiver-->
<!-- ================================================= -->
<!-- Transport Outs -->
<!-- ================================================= -->
<transportSender name="http" class="axis2_http_sender">
<parameter name="PROTOCOL" locked="false">HTTP/1.1</parameter>
<parameter name="xml-declaration" insert="false"/>
<!--parameter name="Transfer-Encoding">chunked</parameter-->
<!--parameter name="HTTP-Authentication" username="" password="" locked="true"/-->
<!--parameter name="PROXY" proxy_host="127.0.0.1" proxy_port="8080" proxy_username="" proxy_password="" locked="true"/-->
</transportSender>
<!-- Uncomment the following with appropriate parameters to enable the SSL transport sender.
Also make sure that the appropriate transport receiver is enabled above.-->
<!--transportSender name="https" class="axis2_http_sender">
<parameter name="PROTOCOL" locked="false">HTTP/1.1</parameter>
<parameter name="xml-declaration" insert="false"/>
</transportSender>
<parameter name="SERVER_CERT">/path/to/ca/certificate</parameter>
<parameter name="KEY_FILE">/path/to/client/certificate/chain/file</parameter>
<parameter name="SSL_PASSPHRASE">passphrase</parameter>
-->
<!-- Uncomment this one with the appropriate papameters to enable the TCP transport Sender-->
<!--transportSender name="tcp" class="axis2_tcp_sender">
<parameter name="PROTOCOL" locked="false">TCP</parameter>
<parameter name="xml-declaration" insert="false"/>
</transportSender-->
<!-- ================================================= -->
<!-- Global Modules -->
<!-- ================================================= -->
<!-- Comment this to disable Addressing -->
<module ref="addressing"/>
<!--Configuring module , providing paramters for modules whether they refer or not-->
<!--<moduleConfig name="addressing">-->
<!--<parameter name="addressingPara" locked="false">N/A</parameter>-->
<!--</moduleConfig>-->
<!-- ================================================= -->
<!-- Phases -->
<!-- ================================================= -->
<phaseOrder type="inflow">
<!-- System pre defined phases -->
<phase name="Transport"/>
<phase name="PreDispatch"/>
<phase name="Dispatch"/>
<phase name="PostDispatch"/>
<!-- End system pre defined phases -->
<!-- After PostDispatch phase, module or service author can add any phase as required -->
<!-- User defined phases could be added here -->
<!--phase name="userphase1"/-->
</phaseOrder>
<phaseOrder type="outflow">
<!-- User defined phases could be added here -->
<!--phase name="userphase1"/-->
<!--system predefined phase-->
<phase name="MessageOut"/>
<phase name="Security"/>
<!--phase name="Security"/-->
</phaseOrder>
<phaseOrder type="INfaultflow">
<!-- User defined phases could be added here -->
<!--phase name="userphase1"/-->
</phaseOrder>
<phaseOrder type="Outfaultflow">
<!-- User defined phases could be added here -->
<!--phase name="userphase1"/-->
<phase name="MessageOut"/>
</phaseOrder>
</axisconfig>
