You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Amila Suriarachchi <am...@gmail.com> on 2008/08/01 07:17:18 UTC

Re: Axis2 Client side deployment configuration

On Thu, Jul 31, 2008 at 11:18 PM, Shah, Sumit <su...@cgi.com> wrote:

>  Hello,
>
>
>
> I would appreciate if someone could tell me how I can specify configuration
> options for invoking 3rd party web services using Axis2 client side APIs.
> The parameters maybe specified at the global, service or module level.
>

you can create a configuration context at the client side as well pointing
out to a repository

ConfigurationContext configurationContext =

ConfigurationContextFactory.createConfigurationContextFromFileSystem(
                            AXIS2_REPOSITORY_LOCATION,
AXIS2_CLIENT_CONFIG_FILE);
            ServiceClient serviceClient = new
ServiceClient(configurationContext, null);

and add any parameters to Axis2.xml

thanks,
Amila.

> In Axis1.4, I could use the .wsdd file to specify options/parameters at all
> levels even for the client (or consumption) side. I am not sure how to
> achieve that in Axis2.
>
>
>
> Thanks
>
> Sumit
>
>
>
>
>



-- 
Amila Suriarachchi,
WSO2 Inc.

Re: Axis2 Client side deployment configuration

Posted by Amila Suriarachchi <am...@gmail.com>.
On Wed, Aug 6, 2008 at 9:44 PM, Shah, Sumit <su...@cgi.com> wrote:

>  Thanks Amila. So for services, there is no configuration file on the
> client side that can be utilized?
>
yes. client side does not have deployed services.

thanks,
Amila.

>
>
> Sumit
>
>
>  ------------------------------
>
> *From:* Amila Suriarachchi [mailto:amilasuriarachchi@gmail.com]
> *Sent:* Wednesday, August 06, 2008 4:30 AM
>
> *To:* axis-user@ws.apache.org
> *Subject:* Re: Axis2 Client side deployment configuration
>
>
>
>
>
> On Fri, Aug 1, 2008 at 8:19 PM, Shah, Sumit <su...@cgi.com> wrote:
>
> Hi Amila,
>
>
>
> Thanks for the information. If I add parameters to the axis2.xml then won't
> it apply globally? Is there a way to restrict it at the service and the
> module level on the Axis2 client side?
>
> 1. For services
> you can set parameters using the stub or service client
> mobileCommServiceStub._getServiceClient().getAxisService().addParameter(new
> Parameter("name","value"));
>
> 2. for modules.
> you need to edit the module.xml file
>
> thanks,
> Amila.
>
>
>
> Thanks
>
> Sumit
>
>
>  ------------------------------
>
> *From:* Amila Suriarachchi [mailto:amilasuriarachchi@gmail.com]
> *Sent:* Friday, August 01, 2008 1:17 AM
> *To:* axis-user@ws.apache.org
> *Subject:* Re: Axis2 Client side deployment configuration
>
>
>
>
>
> On Thu, Jul 31, 2008 at 11:18 PM, Shah, Sumit <su...@cgi.com> wrote:
>
> Hello,
>
>
>
> I would appreciate if someone could tell me how I can specify configuration
> options for invoking 3rd party web services using Axis2 client side APIs.
> The parameters maybe specified at the global, service or module level.
>
>
> you can create a configuration context at the client side as well pointing
> out to a repository
>
> ConfigurationContext configurationContext =
>
> ConfigurationContextFactory.createConfigurationContextFromFileSystem(
>                             AXIS2_REPOSITORY_LOCATION,
> AXIS2_CLIENT_CONFIG_FILE);
>             ServiceClient serviceClient = new
> ServiceClient(configurationContext, null);
>
> and add any parameters to Axis2.xml
>
> thanks,
> Amila.
>
>  In Axis1.4, I could use the .wsdd file to specify options/parameters at
> all levels even for the client (or consumption) side. I am not sure how to
> achieve that in Axis2.
>
>
>
> Thanks
>
> Sumit
>
>
>
>
>
>
>
>
> --
> Amila Suriarachchi,
> WSO2 Inc.
>
>
>
>
> --
> Amila Suriarachchi,
> WSO2 Inc.
>



-- 
Amila Suriarachchi,
WSO2 Inc.

RE: Axis2 Client side deployment configuration

Posted by "Shah, Sumit" <su...@cgi.com>.
Thanks Amila. So for services, there is no configuration file on the
client side that can be utilized?

 

Sumit

 

________________________________

From: Amila Suriarachchi [mailto:amilasuriarachchi@gmail.com] 
Sent: Wednesday, August 06, 2008 4:30 AM
To: axis-user@ws.apache.org
Subject: Re: Axis2 Client side deployment configuration

 

 

On Fri, Aug 1, 2008 at 8:19 PM, Shah, Sumit <su...@cgi.com> wrote:

Hi Amila,

 

Thanks for the information. If I add parameters to the axis2.xml then
won't it apply globally? Is there a way to restrict it at the service
and the module level on the Axis2 client side?

1. For services
you can set parameters using the stub or service client
mobileCommServiceStub._getServiceClient().getAxisService().addParameter(
new Parameter("name","value"));

2. for modules.
you need to edit the module.xml file 

thanks,
Amila.

	 

	Thanks

	Sumit

	 

	
________________________________


	From: Amila Suriarachchi [mailto:amilasuriarachchi@gmail.com] 
	Sent: Friday, August 01, 2008 1:17 AM
	To: axis-user@ws.apache.org
	Subject: Re: Axis2 Client side deployment configuration

	 

	 

	On Thu, Jul 31, 2008 at 11:18 PM, Shah, Sumit
<su...@cgi.com> wrote:

	Hello,

	 

	I would appreciate if someone could tell me how I can specify
configuration options for invoking 3rd party web services using Axis2
client side APIs. The parameters maybe specified at the global, service
or module level.

	
	you can create a configuration context at the client side as
well pointing out to a repository
	
	ConfigurationContext configurationContext =
	
ConfigurationContextFactory.createConfigurationContextFromFileSystem(
	                            AXIS2_REPOSITORY_LOCATION,
AXIS2_CLIENT_CONFIG_FILE);
	            ServiceClient serviceClient = new
ServiceClient(configurationContext, null);
	
	and add any parameters to Axis2.xml
	
	thanks,
	Amila.

		In Axis1.4, I could use the .wsdd file to specify
options/parameters at all levels even for the client (or consumption)
side. I am not sure how to achieve that in Axis2. 

		 

		Thanks

		Sumit

		 

		 

	
	
	
	-- 
	Amila Suriarachchi,
	WSO2 Inc.




-- 
Amila Suriarachchi,
WSO2 Inc.

Re: Axis2 Client side deployment configuration

Posted by Amila Suriarachchi <am...@gmail.com>.
On Fri, Aug 1, 2008 at 8:19 PM, Shah, Sumit <su...@cgi.com> wrote:

>  Hi Amila,
>
>
>
> Thanks for the information. If I add parameters to the axis2.xml then won't
> it apply globally? Is there a way to restrict it at the service and the
> module level on the Axis2 client side?
>
1. For services
you can set parameters using the stub or service client
mobileCommServiceStub._getServiceClient().getAxisService().addParameter(new
Parameter("name","value"));

2. for modules.
you need to edit the module.xml file

thanks,
Amila.

>
>
> Thanks
>
> Sumit
>
>
>  ------------------------------
>
> *From:* Amila Suriarachchi [mailto:amilasuriarachchi@gmail.com]
> *Sent:* Friday, August 01, 2008 1:17 AM
> *To:* axis-user@ws.apache.org
> *Subject:* Re: Axis2 Client side deployment configuration
>
>
>
>
>
> On Thu, Jul 31, 2008 at 11:18 PM, Shah, Sumit <su...@cgi.com> wrote:
>
> Hello,
>
>
>
> I would appreciate if someone could tell me how I can specify configuration
> options for invoking 3rd party web services using Axis2 client side APIs.
> The parameters maybe specified at the global, service or module level.
>
>
> you can create a configuration context at the client side as well pointing
> out to a repository
>
> ConfigurationContext configurationContext =
>
> ConfigurationContextFactory.createConfigurationContextFromFileSystem(
>                             AXIS2_REPOSITORY_LOCATION,
> AXIS2_CLIENT_CONFIG_FILE);
>             ServiceClient serviceClient = new
> ServiceClient(configurationContext, null);
>
> and add any parameters to Axis2.xml
>
> thanks,
> Amila.
>
>  In Axis1.4, I could use the .wsdd file to specify options/parameters at
> all levels even for the client (or consumption) side. I am not sure how to
> achieve that in Axis2.
>
>
>
> Thanks
>
> Sumit
>
>
>
>
>
>
>
>
> --
> Amila Suriarachchi,
> WSO2 Inc.
>



-- 
Amila Suriarachchi,
WSO2 Inc.

RE: Axis2 Client side deployment configuration

Posted by "Shah, Sumit" <su...@cgi.com>.
Hi Amila,

 

Thanks for the information. If I add parameters to the axis2.xml then
won't it apply globally? Is there a way to restrict it at the service
and the module level on the Axis2 client side?

 

Thanks

Sumit

 

________________________________

From: Amila Suriarachchi [mailto:amilasuriarachchi@gmail.com] 
Sent: Friday, August 01, 2008 1:17 AM
To: axis-user@ws.apache.org
Subject: Re: Axis2 Client side deployment configuration

 

 

On Thu, Jul 31, 2008 at 11:18 PM, Shah, Sumit <su...@cgi.com>
wrote:

Hello,

 

I would appreciate if someone could tell me how I can specify
configuration options for invoking 3rd party web services using Axis2
client side APIs. The parameters maybe specified at the global, service
or module level.


you can create a configuration context at the client side as well
pointing out to a repository

ConfigurationContext configurationContext =
 
ConfigurationContextFactory.createConfigurationContextFromFileSystem(
                            AXIS2_REPOSITORY_LOCATION,
AXIS2_CLIENT_CONFIG_FILE);
            ServiceClient serviceClient = new
ServiceClient(configurationContext, null);

and add any parameters to Axis2.xml

thanks,
Amila.

	In Axis1.4, I could use the .wsdd file to specify
options/parameters at all levels even for the client (or consumption)
side. I am not sure how to achieve that in Axis2. 

	 

	Thanks

	Sumit

	 

	 




-- 
Amila Suriarachchi,
WSO2 Inc.