You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by Srinath Perera <he...@gmail.com> on 2006/03/02 23:11:34 UTC
[Axis2][Security]Looking up Secuirty Configuration from AxisModule
Hi All;
Currently SecuirtyModule engageNotifyMethod() does the following
1) create InFlow/OutFlow Configurations from Policy
2) Load the InFlow/OutFlow Configuration from the AxisDiscription
3) Merge the configurations and set them to the AxisDiscrption
I like to purpose a slight modification, Can we load the configuration
from the module as well and merge the InFlow/OutFlow Configurations.
This allow the user to put the configuration that are specific to the
module inside module deployment descriptor. (e.g. Passoword callback
and the security property files have one value for most of the use
cases and use would like to configure them in the module)
Srinath
--
============================
Srinath Perera:
http://www.cs.indiana.edu/~hperera/
http://www.bloglines.com/blog/hemapani
Re: [Axis2][Security]Looking up Secuirty Configuration from AxisModule
Posted by Ruchith Fernando <ru...@gmail.com>.
Hi Srinath,
Yes, I agree that we have to get the parameters from the module.xml
into account as well, I think it will be useful.
BTW I didn't expect a user will repackage the mar with a new
module.xml (with the new properties) but I think its useful to allow
that.
Thanks,
Ruchith
On 3/3/06, Sanjiva Weerawarana <sa...@opensource.lk> wrote:
> Definitely +1! I guess Ruchith should reply too though since I don't
> know the security stuff .. seems logical however ;-).
>
> Sanjiva.
>
> On Thu, 2006-03-02 at 17:11 -0500, Srinath Perera wrote:
> > Hi All;
> >
> >
> > Currently SecuirtyModule engageNotifyMethod() does the following
> >
> > 1) create InFlow/OutFlow Configurations from Policy
> > 2) Load the InFlow/OutFlow Configuration from the AxisDiscription
> > 3) Merge the configurations and set them to the AxisDiscrption
> >
> > I like to purpose a slight modification, Can we load the configuration
> > from the module as well and merge the InFlow/OutFlow Configurations.
> > This allow the user to put the configuration that are specific to the
> > module inside module deployment descriptor. (e.g. Passoword callback
> > and the security property files have one value for most of the use
> > cases and use would like to configure them in the module)
> >
> > Srinath
> >
> >
> >
> > --
> > ============================
> > Srinath Perera:
> > http://www.cs.indiana.edu/~hperera/
> > http://www.bloglines.com/blog/hemapani
>
>
Re: [Axis2][Security]Looking up Secuirty Configuration from
AxisModule
Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
Definitely +1! I guess Ruchith should reply too though since I don't
know the security stuff .. seems logical however ;-).
Sanjiva.
On Thu, 2006-03-02 at 17:11 -0500, Srinath Perera wrote:
> Hi All;
>
>
> Currently SecuirtyModule engageNotifyMethod() does the following
>
> 1) create InFlow/OutFlow Configurations from Policy
> 2) Load the InFlow/OutFlow Configuration from the AxisDiscription
> 3) Merge the configurations and set them to the AxisDiscrption
>
> I like to purpose a slight modification, Can we load the configuration
> from the module as well and merge the InFlow/OutFlow Configurations.
> This allow the user to put the configuration that are specific to the
> module inside module deployment descriptor. (e.g. Passoword callback
> and the security property files have one value for most of the use
> cases and use would like to configure them in the module)
>
> Srinath
>
>
>
> --
> ============================
> Srinath Perera:
> http://www.cs.indiana.edu/~hperera/
> http://www.bloglines.com/blog/hemapani