-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
 
The reason for this was we wanted to abstract the loading of
properties in to Axis2 and not to limit to file system. So one has to
create a ConfigurationContext and pass that to the ServiceClient. He
should create the ConfigurationContext through a Configurator, which
can be FileSystemCofigurator or DatabaseConfigurator (yet to be
implemented) or any other configurator which can load the static
parameters. For creating ConfigurationContext via Configurator, please
use ConfigurationContextFactory .

Davanum Srinivas wrote:

> Example from one of the test cases:
>
> ConfigurationContextFactory factory = new
> ConfigurationContextFactory(); ConfigurationContext configContext =
>
>
> factory.createConfigurationContextFromFileSystem("target/test-resources/integrationRepo");
> ServiceClient sender = new ServiceClient(configContext, null);
>
> thanks, dims
>
> On 1/10/06, Liu, Tao <[EMAIL PROTECTED]> wrote:
>
>> Thanks. Is the repository a directory? I couldn't find in the
>> config guide.
>>
>> I can see a ConfigurationContext parameter in ServiceClient's
>> constructor.
>>
>> Thanks, Tao
>>
>> -----Original Message----- From: Davanum Srinivas
>> [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 10, 2006 5:28
>> PM To: [email protected] Subject: Re: search path for
>> axis2.xml on client
>>
>> i believe it checks the repo first, then the classpath. (check
>> the constructor where you can specify a repo). Also please use
>> ServiceClient.
>>
>> thanks, dims
>>
>> On 1/10/06, Liu, Tao <[EMAIL PROTECTED]> wrote:
>>
>>> "Call" seems deprecated in .094 release.
>>>
>>> Does it search the current directory, classpath, and specified
>>> dir with a system property? In what order?
>>>
>>> Thanks, Tao
>>>
>>
>> -- Davanum Srinivas : http://wso2.com/blogs/
>>
>
>
> -- Davanum Srinivas : http://wso2.com/blogs/
>

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (MingW32)
 
iD8DBQFDxGQOjON2uBzUhh8RAjxxAKCj2n9rjUCZTTCPOZZ/oXaQCDSPOwCcDH1u
MDY4bm8uPVyuFYP9dmPP6WY=
=sK8j
-----END PGP SIGNATURE-----

Reply via email to