Re: [Axis2] Rampart configuration

2007-02-02 Thread Ruchith Fernando 

Hi Brecht,

you can still use the same property in options and set the callback
handler instance and you can omit the class name value from
RampartConfig assertion.

Thanks,
Ruchith

On 2/1/07, Brecht Yperman <[EMAIL PROTECTED]> wrote:





Hi,



I'm trying to migrate security from Axis2 1.0 / Rampart 1.0 to Axis2
1.1/Rampart1.1.



I used to use the following construction to hand a reference to a
PWCallBack-class to Rampart:



client.getOptions().setProperty("passwordCallbackRef",

new
PasswordCallback(password));



This was, I think, undocumented, but I found this out browsing the
sourcecode.

Unfortunately the RampartConfig-class only allows you to set a classname
(and this is required, according to the XMLSchema), not an instance.



Can I still use this way, is there another way around, or should I think of
another way of handing the password to the callback?



Thanks,

Brecht



--
www.ruchith.org
www.wso2.org

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[Axis2] Rampart configuration

2007-02-01 Thread Brecht Yperman 
Hi,

 

I'm trying to migrate security from Axis2 1.0 / Rampart 1.0 to Axis2
1.1/Rampart1.1.

 

I used to use the following construction to hand a reference to a
PWCallBack-class to Rampart:

 

client.getOptions().setProperty("passwordCallbackRef",

new PasswordCallback(password));

 

This was, I think, undocumented, but I found this out browsing the
sourcecode.

Unfortunately the RampartConfig-class only allows you to set a classname
(and this is required, according to the XMLSchema), not an instance.

 

Can I still use this way, is there another way around, or should I think
of another way of handing the password to the callback?

 

Thanks,

Brecht