RE: [jira] Updated: (AXIS2-249) Exessive number & size of filesgenerated from WSDL

[Sanjiva Weerawarana <sa...@opensource.lk>]

On Fri, 2005-09-30 at 12:09 -0400, Tom Jordahl wrote:
> +1 on breaking out the war and binary download and slimming down the
> kit.
> 
> I would like to keep WS-Security support in the primary Axis2 distro.  I
> think it is very valuable to have this support 'out of the box' as a
> selling point for Axis, similar to its support of WS-Addressing.

Keeping it inside the "full and complete" download of Axis2 is fine, but
IMO the actual task of building an Axis2 module for the WS-Sec code
belongs inside the WSS4J tree and not in the Axis2 tree. Why? Because
once we get the module working, the reason to rev it will be because of
WSS4J changes and if we keep it in WSS4J those can (at least have a
chance) of being released in sync with WSS4J.

Sanjiva.

Re: [jira] Updated: (AXIS2-249) Exessive number & size of filesgenerated from WSDL

[Davanum Srinivas <da...@gmail.com>]

+1 from me.

On 9/30/05, Sanjiva Weerawarana <sa...@opensource.lk> wrote:
> On Fri, 2005-09-30 at 12:09 -0400, Tom Jordahl wrote:
> > +1 on breaking out the war and binary download and slimming down the
> > kit.
> >
> > I would like to keep WS-Security support in the primary Axis2 distro.  I
> > think it is very valuable to have this support 'out of the box' as a
> > selling point for Axis, similar to its support of WS-Addressing.
>
> Keeping it inside the "full and complete" download of Axis2 is fine, but
> IMO the actual task of building an Axis2 module for the WS-Sec code
> belongs inside the WSS4J tree and not in the Axis2 tree. Why? Because
> once we get the module working, the reason to rev it will be because of
> WSS4J changes and if we keep it in WSS4J those can (at least have a
> chance) of being released in sync with WSS4J.
>
> Sanjiva.
>
>
>


--
Davanum Srinivas : http://wso2.com/ - Oxygenating The Web Service Platform