You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@synapse.apache.org by indika kumara <in...@gmail.com> on 2010/05/11 12:34:28 UTC

Dependency to transport-base in synapse commons

Hi Devs

I want to add support for securing passwords in configuration files – axis2,
synapse, transports, WSO2 product, etc … The code is in synapse commons, and
the axis2 kernel and transports have to depend on it.

Synapse Commons -> axis2 kernel – (transports)

Currently, there is a dependency to transport-base in synapse commons … and
I believe (did not check) there should be a dependency to axis2 kernel in
the transport-base … This can be an issue to make axis2-kernal depends on
the synapse commons

What should the solution be? … Remove dependency; make a new module for
security code, move security code into axis2 module or somewhere, or any
other solution…

I highly appreciate a proper solution.  Please do not misunderstand me, more
fast solution is more better as now, my time for development is very low.

Thanks

Indika

Re: Dependency to transport-base in synapse commons

Posted by indika kumara <in...@gmail.com>.
Ok .. I will go with securevault ....

Thanks

Indika

On Thu, May 13, 2010 at 7:11 PM, Ruwan Linton <ru...@gmail.com>wrote:

> Isn't security more generic? I prefer securevault.
>
> Thanks,
> Ruwan
>
>
> On Thu, May 13, 2010 at 4:07 PM, indika kumara <in...@gmail.com>wrote:
>
>> Thanks ruwan ... what should be the name of the module ? security (if at
>> future , more security code will  be added ) or securevault or some other
>> ?
>>
>> Thanks
>>
>> Indika
>>
>> On Thu, May 13, 2010 at 11:49 AM, Ruwan Linton <ru...@gmail.com>wrote:
>>
>>> +1, For the moment lets do that and to get rid of the building issues we
>>> could set an svn:external to the axis2 where this security module is
>>> required to be built.
>>>
>>> Thanks,
>>> Ruwan
>>>
>>>
>>> On Wed, May 12, 2010 at 1:36 PM, indika kumara <in...@gmail.com>wrote:
>>>
>>>> Thanks for quick suggestions..
>>>>
>>>> Ruwan ...as you said.. it will be better to make a subproject which may
>>>> be go into ws-commons or under the synapse TL... But It will take some time.
>>>> So I would like a create a new module in synapse so that at later , we can
>>>> move easily it into somewhere mostly appropriate.
>>>>
>>>> Thanks
>>>>
>>>> Indika
>>>>
>>>>
>>>> On Wed, May 12, 2010 at 5:12 AM, Ruwan Linton <ru...@gmail.com>wrote:
>>>>
>>>>> Even if we extract this into a new module we will have a practical
>>>>> issue of building if we add this as a dependency to axis2.
>>>>>
>>>>> Build order will be to build synapse-security module first and then,
>>>>> build axis2 and come back to synapse :-(
>>>>>
>>>>> Can we extract this as a subproject to go into ws-commons or may be
>>>>> even under the synapse TLP??
>>>>>
>>>>> Thanks,
>>>>> Ruwan
>>>>>
>>>>>
>>>>> On Tue, May 11, 2010 at 5:12 PM, Supun Kamburugamuva <
>>>>> supun06@gmail.com> wrote:
>>>>>
>>>>>>
>>>>>>
>>>>>> On Tue, May 11, 2010 at 4:04 PM, indika kumara <indika.kuma@gmail.com
>>>>>> > wrote:
>>>>>>
>>>>>>> Hi Devs
>>>>>>>
>>>>>>> I want to add support for securing passwords in configuration files –
>>>>>>> axis2, synapse, transports, WSO2 product, etc … The code is in synapse
>>>>>>> commons, and the axis2 kernel and transports have to depend on it.
>>>>>>>
>>>>>>> Synapse Commons -> axis2 kernel – (transports)
>>>>>>>
>>>>>>> Currently, there is a dependency to transport-base in synapse commons
>>>>>>> … and I believe (did not check) there should be a dependency to axis2 kernel
>>>>>>> in the transport-base … This can be an issue to make axis2-kernal depends on
>>>>>>> the synapse commons
>>>>>>>
>>>>>>> I've checked the transport code. There is a dependency to
>>>>>> axis2-kernel from transport base.
>>>>>>
>>>>>>
>>>>>>> What should the solution be? … Remove dependency; make a new module
>>>>>>> for security code, move security code into axis2 module or somewhere, or any
>>>>>>> other solution…
>>>>>>>
>>>>>>> Since security code is going to be used by multiple projects, it may
>>>>>> be a good idea to move it to a new module?
>>>>>>
>>>>>> Thanks,
>>>>>> Supun..
>>>>>>
>>>>>>
>>>>>>> I highly appreciate a proper solution.  Please do not misunderstand
>>>>>>> me, more fast solution is more better as now, my time for development is
>>>>>>> very low.
>>>>>>>
>>>>>>> Thanks
>>>>>>>
>>>>>>> Indika
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Software Engineer, WSO2 Inc
>>>>>> http://wso2.org
>>>>>> supunk.blogspot.com
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Ruwan Linton
>>>>> Software Architect & Product Manager, WSO2 ESB; http://wso2.org/esb
>>>>>
>>>>> WSO2 Inc.; http://wso2.org
>>>>>
>>>>> Lean . Enterprise . Middleware
>>>>>
>>>>> phone: +1 408 754 7388 ext 51789
>>>>> email: ruwan@wso2.com; cell: +94 77 341 3097
>>>>> blog: http://blog.ruwan.org
>>>>> linkedin: http://www.linkedin.com/in/ruwanlinton
>>>>> tweet: http://twitter.com/ruwanlinton
>>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> Ruwan Linton
>>> Software Architect & Product Manager, WSO2 ESB; http://wso2.org/esb
>>> WSO2 Inc.; http://wso2.org
>>>
>>> Lean . Enterprise . Middleware
>>>
>>> phone: +1 408 754 7388 ext 51789
>>> email: ruwan@wso2.com; cell: +94 77 341 3097
>>> blog: http://blog.ruwan.org
>>> linkedin: http://www.linkedin.com/in/ruwanlinton
>>> google: http://www.google.com/profiles/ruwan.linton
>>>
>>> tweet: http://twitter.com/ruwanlinton
>>>
>>
>>
>
>
> --
> Ruwan Linton
> Software Architect & Product Manager, WSO2 ESB; http://wso2.org/esb
> WSO2 Inc.; http://wso2.org
>
> Lean . Enterprise . Middleware
>
> phone: +1 408 754 7388 ext 51789
> email: ruwan@wso2.com; cell: +94 77 341 3097
> blog: http://blog.ruwan.org
> linkedin: http://www.linkedin.com/in/ruwanlinton
> google: http://www.google.com/profiles/ruwan.linton
> tweet: http://twitter.com/ruwanlinton
>

Re: Dependency to transport-base in synapse commons

Posted by Ruwan Linton <ru...@gmail.com>.
Isn't security more generic? I prefer securevault.

Thanks,
Ruwan

On Thu, May 13, 2010 at 4:07 PM, indika kumara <in...@gmail.com>wrote:

> Thanks ruwan ... what should be the name of the module ? security (if at
> future , more security code will  be added ) or securevault or some other
> ?
>
> Thanks
>
> Indika
>
> On Thu, May 13, 2010 at 11:49 AM, Ruwan Linton <ru...@gmail.com>wrote:
>
>> +1, For the moment lets do that and to get rid of the building issues we
>> could set an svn:external to the axis2 where this security module is
>> required to be built.
>>
>> Thanks,
>> Ruwan
>>
>>
>> On Wed, May 12, 2010 at 1:36 PM, indika kumara <in...@gmail.com>wrote:
>>
>>> Thanks for quick suggestions..
>>>
>>> Ruwan ...as you said.. it will be better to make a subproject which may
>>> be go into ws-commons or under the synapse TL... But It will take some time.
>>> So I would like a create a new module in synapse so that at later , we can
>>> move easily it into somewhere mostly appropriate.
>>>
>>> Thanks
>>>
>>> Indika
>>>
>>>
>>> On Wed, May 12, 2010 at 5:12 AM, Ruwan Linton <ru...@gmail.com>wrote:
>>>
>>>> Even if we extract this into a new module we will have a practical issue
>>>> of building if we add this as a dependency to axis2.
>>>>
>>>> Build order will be to build synapse-security module first and then,
>>>> build axis2 and come back to synapse :-(
>>>>
>>>> Can we extract this as a subproject to go into ws-commons or may be even
>>>> under the synapse TLP??
>>>>
>>>> Thanks,
>>>> Ruwan
>>>>
>>>>
>>>> On Tue, May 11, 2010 at 5:12 PM, Supun Kamburugamuva <supun06@gmail.com
>>>> > wrote:
>>>>
>>>>>
>>>>>
>>>>> On Tue, May 11, 2010 at 4:04 PM, indika kumara <in...@gmail.com>wrote:
>>>>>
>>>>>> Hi Devs
>>>>>>
>>>>>> I want to add support for securing passwords in configuration files –
>>>>>> axis2, synapse, transports, WSO2 product, etc … The code is in synapse
>>>>>> commons, and the axis2 kernel and transports have to depend on it.
>>>>>>
>>>>>> Synapse Commons -> axis2 kernel – (transports)
>>>>>>
>>>>>> Currently, there is a dependency to transport-base in synapse commons
>>>>>> … and I believe (did not check) there should be a dependency to axis2 kernel
>>>>>> in the transport-base … This can be an issue to make axis2-kernal depends on
>>>>>> the synapse commons
>>>>>>
>>>>>> I've checked the transport code. There is a dependency to axis2-kernel
>>>>> from transport base.
>>>>>
>>>>>
>>>>>> What should the solution be? … Remove dependency; make a new module
>>>>>> for security code, move security code into axis2 module or somewhere, or any
>>>>>> other solution…
>>>>>>
>>>>>> Since security code is going to be used by multiple projects, it may
>>>>> be a good idea to move it to a new module?
>>>>>
>>>>> Thanks,
>>>>> Supun..
>>>>>
>>>>>
>>>>>> I highly appreciate a proper solution.  Please do not misunderstand
>>>>>> me, more fast solution is more better as now, my time for development is
>>>>>> very low.
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>> Indika
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Software Engineer, WSO2 Inc
>>>>> http://wso2.org
>>>>> supunk.blogspot.com
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Ruwan Linton
>>>> Software Architect & Product Manager, WSO2 ESB; http://wso2.org/esb
>>>>
>>>> WSO2 Inc.; http://wso2.org
>>>>
>>>> Lean . Enterprise . Middleware
>>>>
>>>> phone: +1 408 754 7388 ext 51789
>>>> email: ruwan@wso2.com; cell: +94 77 341 3097
>>>> blog: http://blog.ruwan.org
>>>> linkedin: http://www.linkedin.com/in/ruwanlinton
>>>> tweet: http://twitter.com/ruwanlinton
>>>>
>>>
>>>
>>
>>
>> --
>> Ruwan Linton
>> Software Architect & Product Manager, WSO2 ESB; http://wso2.org/esb
>> WSO2 Inc.; http://wso2.org
>>
>> Lean . Enterprise . Middleware
>>
>> phone: +1 408 754 7388 ext 51789
>> email: ruwan@wso2.com; cell: +94 77 341 3097
>> blog: http://blog.ruwan.org
>> linkedin: http://www.linkedin.com/in/ruwanlinton
>> google: http://www.google.com/profiles/ruwan.linton
>>
>> tweet: http://twitter.com/ruwanlinton
>>
>
>


-- 
Ruwan Linton
Software Architect & Product Manager, WSO2 ESB; http://wso2.org/esb
WSO2 Inc.; http://wso2.org

Lean . Enterprise . Middleware

phone: +1 408 754 7388 ext 51789
email: ruwan@wso2.com; cell: +94 77 341 3097
blog: http://blog.ruwan.org
linkedin: http://www.linkedin.com/in/ruwanlinton
google: http://www.google.com/profiles/ruwan.linton
tweet: http://twitter.com/ruwanlinton

Re: Dependency to transport-base in synapse commons

Posted by indika kumara <in...@gmail.com>.
Thanks ruwan ... what should be the name of the module ? security (if at
future , more security code will  be added ) or securevault or some other ?

Thanks

Indika

On Thu, May 13, 2010 at 11:49 AM, Ruwan Linton <ru...@gmail.com>wrote:

> +1, For the moment lets do that and to get rid of the building issues we
> could set an svn:external to the axis2 where this security module is
> required to be built.
>
> Thanks,
> Ruwan
>
>
> On Wed, May 12, 2010 at 1:36 PM, indika kumara <in...@gmail.com>wrote:
>
>> Thanks for quick suggestions..
>>
>> Ruwan ...as you said.. it will be better to make a subproject which may be
>> go into ws-commons or under the synapse TL... But It will take some time. So
>> I would like a create a new module in synapse so that at later , we can move
>> easily it into somewhere mostly appropriate.
>>
>> Thanks
>>
>> Indika
>>
>>
>> On Wed, May 12, 2010 at 5:12 AM, Ruwan Linton <ru...@gmail.com>wrote:
>>
>>> Even if we extract this into a new module we will have a practical issue
>>> of building if we add this as a dependency to axis2.
>>>
>>> Build order will be to build synapse-security module first and then,
>>> build axis2 and come back to synapse :-(
>>>
>>> Can we extract this as a subproject to go into ws-commons or may be even
>>> under the synapse TLP??
>>>
>>> Thanks,
>>> Ruwan
>>>
>>>
>>> On Tue, May 11, 2010 at 5:12 PM, Supun Kamburugamuva <su...@gmail.com>wrote:
>>>
>>>>
>>>>
>>>> On Tue, May 11, 2010 at 4:04 PM, indika kumara <in...@gmail.com>wrote:
>>>>
>>>>> Hi Devs
>>>>>
>>>>> I want to add support for securing passwords in configuration files –
>>>>> axis2, synapse, transports, WSO2 product, etc … The code is in synapse
>>>>> commons, and the axis2 kernel and transports have to depend on it.
>>>>>
>>>>> Synapse Commons -> axis2 kernel – (transports)
>>>>>
>>>>> Currently, there is a dependency to transport-base in synapse commons …
>>>>> and I believe (did not check) there should be a dependency to axis2 kernel
>>>>> in the transport-base … This can be an issue to make axis2-kernal depends on
>>>>> the synapse commons
>>>>>
>>>>> I've checked the transport code. There is a dependency to axis2-kernel
>>>> from transport base.
>>>>
>>>>
>>>>> What should the solution be? … Remove dependency; make a new module for
>>>>> security code, move security code into axis2 module or somewhere, or any
>>>>> other solution…
>>>>>
>>>>> Since security code is going to be used by multiple projects, it may be
>>>> a good idea to move it to a new module?
>>>>
>>>> Thanks,
>>>> Supun..
>>>>
>>>>
>>>>> I highly appreciate a proper solution.  Please do not misunderstand me,
>>>>> more fast solution is more better as now, my time for development is very
>>>>> low.
>>>>>
>>>>> Thanks
>>>>>
>>>>> Indika
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Software Engineer, WSO2 Inc
>>>> http://wso2.org
>>>> supunk.blogspot.com
>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> Ruwan Linton
>>> Software Architect & Product Manager, WSO2 ESB; http://wso2.org/esb
>>>
>>> WSO2 Inc.; http://wso2.org
>>>
>>> Lean . Enterprise . Middleware
>>>
>>> phone: +1 408 754 7388 ext 51789
>>> email: ruwan@wso2.com; cell: +94 77 341 3097
>>> blog: http://blog.ruwan.org
>>> linkedin: http://www.linkedin.com/in/ruwanlinton
>>> tweet: http://twitter.com/ruwanlinton
>>>
>>
>>
>
>
> --
> Ruwan Linton
> Software Architect & Product Manager, WSO2 ESB; http://wso2.org/esb
> WSO2 Inc.; http://wso2.org
>
> Lean . Enterprise . Middleware
>
> phone: +1 408 754 7388 ext 51789
> email: ruwan@wso2.com; cell: +94 77 341 3097
> blog: http://blog.ruwan.org
> linkedin: http://www.linkedin.com/in/ruwanlinton
> google: http://www.google.com/profiles/ruwan.linton
>
> tweet: http://twitter.com/ruwanlinton
>

Re: Dependency to transport-base in synapse commons

Posted by Ruwan Linton <ru...@gmail.com>.
+1, For the moment lets do that and to get rid of the building issues we
could set an svn:external to the axis2 where this security module is
required to be built.

Thanks,
Ruwan

On Wed, May 12, 2010 at 1:36 PM, indika kumara <in...@gmail.com>wrote:

> Thanks for quick suggestions..
>
> Ruwan ...as you said.. it will be better to make a subproject which may be
> go into ws-commons or under the synapse TL... But It will take some time. So
> I would like a create a new module in synapse so that at later , we can move
> easily it into somewhere mostly appropriate.
>
> Thanks
>
> Indika
>
>
> On Wed, May 12, 2010 at 5:12 AM, Ruwan Linton <ru...@gmail.com>wrote:
>
>> Even if we extract this into a new module we will have a practical issue
>> of building if we add this as a dependency to axis2.
>>
>> Build order will be to build synapse-security module first and then, build
>> axis2 and come back to synapse :-(
>>
>> Can we extract this as a subproject to go into ws-commons or may be even
>> under the synapse TLP??
>>
>> Thanks,
>> Ruwan
>>
>>
>> On Tue, May 11, 2010 at 5:12 PM, Supun Kamburugamuva <su...@gmail.com>wrote:
>>
>>>
>>>
>>> On Tue, May 11, 2010 at 4:04 PM, indika kumara <in...@gmail.com>wrote:
>>>
>>>> Hi Devs
>>>>
>>>> I want to add support for securing passwords in configuration files –
>>>> axis2, synapse, transports, WSO2 product, etc … The code is in synapse
>>>> commons, and the axis2 kernel and transports have to depend on it.
>>>>
>>>> Synapse Commons -> axis2 kernel – (transports)
>>>>
>>>> Currently, there is a dependency to transport-base in synapse commons …
>>>> and I believe (did not check) there should be a dependency to axis2 kernel
>>>> in the transport-base … This can be an issue to make axis2-kernal depends on
>>>> the synapse commons
>>>>
>>>> I've checked the transport code. There is a dependency to axis2-kernel
>>> from transport base.
>>>
>>>
>>>> What should the solution be? … Remove dependency; make a new module for
>>>> security code, move security code into axis2 module or somewhere, or any
>>>> other solution…
>>>>
>>>> Since security code is going to be used by multiple projects, it may be
>>> a good idea to move it to a new module?
>>>
>>> Thanks,
>>> Supun..
>>>
>>>
>>>> I highly appreciate a proper solution.  Please do not misunderstand me,
>>>> more fast solution is more better as now, my time for development is very
>>>> low.
>>>>
>>>> Thanks
>>>>
>>>> Indika
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>> --
>>> Software Engineer, WSO2 Inc
>>> http://wso2.org
>>> supunk.blogspot.com
>>>
>>>
>>>
>>
>>
>> --
>> Ruwan Linton
>> Software Architect & Product Manager, WSO2 ESB; http://wso2.org/esb
>>
>> WSO2 Inc.; http://wso2.org
>>
>> Lean . Enterprise . Middleware
>>
>> phone: +1 408 754 7388 ext 51789
>> email: ruwan@wso2.com; cell: +94 77 341 3097
>> blog: http://blog.ruwan.org
>> linkedin: http://www.linkedin.com/in/ruwanlinton
>> tweet: http://twitter.com/ruwanlinton
>>
>
>


-- 
Ruwan Linton
Software Architect & Product Manager, WSO2 ESB; http://wso2.org/esb
WSO2 Inc.; http://wso2.org

Lean . Enterprise . Middleware

phone: +1 408 754 7388 ext 51789
email: ruwan@wso2.com; cell: +94 77 341 3097
blog: http://blog.ruwan.org
linkedin: http://www.linkedin.com/in/ruwanlinton
google: http://www.google.com/profiles/ruwan.linton
tweet: http://twitter.com/ruwanlinton

Re: Dependency to transport-base in synapse commons

Posted by indika kumara <in...@gmail.com>.
Thanks for quick suggestions..

Ruwan ...as you said.. it will be better to make a subproject which may be
go into ws-commons or under the synapse TL... But It will take some time. So
I would like a create a new module in synapse so that at later , we can move
easily it into somewhere mostly appropriate.

Thanks

Indika


On Wed, May 12, 2010 at 5:12 AM, Ruwan Linton <ru...@gmail.com>wrote:

> Even if we extract this into a new module we will have a practical issue of
> building if we add this as a dependency to axis2.
>
> Build order will be to build synapse-security module first and then, build
> axis2 and come back to synapse :-(
>
> Can we extract this as a subproject to go into ws-commons or may be even
> under the synapse TLP??
>
> Thanks,
> Ruwan
>
>
> On Tue, May 11, 2010 at 5:12 PM, Supun Kamburugamuva <su...@gmail.com>wrote:
>
>>
>>
>> On Tue, May 11, 2010 at 4:04 PM, indika kumara <in...@gmail.com>wrote:
>>
>>> Hi Devs
>>>
>>> I want to add support for securing passwords in configuration files –
>>> axis2, synapse, transports, WSO2 product, etc … The code is in synapse
>>> commons, and the axis2 kernel and transports have to depend on it.
>>>
>>> Synapse Commons -> axis2 kernel – (transports)
>>>
>>> Currently, there is a dependency to transport-base in synapse commons …
>>> and I believe (did not check) there should be a dependency to axis2 kernel
>>> in the transport-base … This can be an issue to make axis2-kernal depends on
>>> the synapse commons
>>>
>>> I've checked the transport code. There is a dependency to axis2-kernel
>> from transport base.
>>
>>
>>> What should the solution be? … Remove dependency; make a new module for
>>> security code, move security code into axis2 module or somewhere, or any
>>> other solution…
>>>
>>> Since security code is going to be used by multiple projects, it may be a
>> good idea to move it to a new module?
>>
>> Thanks,
>> Supun..
>>
>>
>>> I highly appreciate a proper solution.  Please do not misunderstand me,
>>> more fast solution is more better as now, my time for development is very
>>> low.
>>>
>>> Thanks
>>>
>>> Indika
>>>
>>>
>>>
>>
>>
>>
>> --
>> Software Engineer, WSO2 Inc
>> http://wso2.org
>> supunk.blogspot.com
>>
>>
>>
>
>
> --
> Ruwan Linton
> Software Architect & Product Manager, WSO2 ESB; http://wso2.org/esb
>
> WSO2 Inc.; http://wso2.org
>
> Lean . Enterprise . Middleware
>
> phone: +1 408 754 7388 ext 51789
> email: ruwan@wso2.com; cell: +94 77 341 3097
> blog: http://blog.ruwan.org
> linkedin: http://www.linkedin.com/in/ruwanlinton
> tweet: http://twitter.com/ruwanlinton
>

Re: Dependency to transport-base in synapse commons

Posted by Ruwan Linton <ru...@gmail.com>.
Even if we extract this into a new module we will have a practical issue of
building if we add this as a dependency to axis2.

Build order will be to build synapse-security module first and then, build
axis2 and come back to synapse :-(

Can we extract this as a subproject to go into ws-commons or may be even
under the synapse TLP??

Thanks,
Ruwan

On Tue, May 11, 2010 at 5:12 PM, Supun Kamburugamuva <su...@gmail.com>wrote:

>
>
> On Tue, May 11, 2010 at 4:04 PM, indika kumara <in...@gmail.com>wrote:
>
>> Hi Devs
>>
>> I want to add support for securing passwords in configuration files –
>> axis2, synapse, transports, WSO2 product, etc … The code is in synapse
>> commons, and the axis2 kernel and transports have to depend on it.
>>
>> Synapse Commons -> axis2 kernel – (transports)
>>
>> Currently, there is a dependency to transport-base in synapse commons …
>> and I believe (did not check) there should be a dependency to axis2 kernel
>> in the transport-base … This can be an issue to make axis2-kernal depends on
>> the synapse commons
>>
>> I've checked the transport code. There is a dependency to axis2-kernel
> from transport base.
>
>
>> What should the solution be? … Remove dependency; make a new module for
>> security code, move security code into axis2 module or somewhere, or any
>> other solution…
>>
>> Since security code is going to be used by multiple projects, it may be a
> good idea to move it to a new module?
>
> Thanks,
> Supun..
>
>
>> I highly appreciate a proper solution.  Please do not misunderstand me,
>> more fast solution is more better as now, my time for development is very
>> low.
>>
>> Thanks
>>
>> Indika
>>
>>
>>
>
>
>
> --
> Software Engineer, WSO2 Inc
> http://wso2.org
> supunk.blogspot.com
>
>
>


-- 
Ruwan Linton
Software Architect & Product Manager, WSO2 ESB; http://wso2.org/esb
WSO2 Inc.; http://wso2.org

Lean . Enterprise . Middleware

phone: +1 408 754 7388 ext 51789
email: ruwan@wso2.com; cell: +94 77 341 3097
blog: http://blog.ruwan.org
linkedin: http://www.linkedin.com/in/ruwanlinton
tweet: http://twitter.com/ruwanlinton

Re: Dependency to transport-base in synapse commons

Posted by Supun Kamburugamuva <su...@gmail.com>.
On Tue, May 11, 2010 at 4:04 PM, indika kumara <in...@gmail.com>wrote:

> Hi Devs
>
> I want to add support for securing passwords in configuration files –
> axis2, synapse, transports, WSO2 product, etc … The code is in synapse
> commons, and the axis2 kernel and transports have to depend on it.
>
> Synapse Commons -> axis2 kernel – (transports)
>
> Currently, there is a dependency to transport-base in synapse commons … and
> I believe (did not check) there should be a dependency to axis2 kernel in
> the transport-base … This can be an issue to make axis2-kernal depends on
> the synapse commons
>
> I've checked the transport code. There is a dependency to axis2-kernel from
transport base.


> What should the solution be? … Remove dependency; make a new module for
> security code, move security code into axis2 module or somewhere, or any
> other solution…
>
> Since security code is going to be used by multiple projects, it may be a
good idea to move it to a new module?

Thanks,
Supun..


> I highly appreciate a proper solution.  Please do not misunderstand me,
> more fast solution is more better as now, my time for development is very
> low.
>
> Thanks
>
> Indika
>
>
>



-- 
Software Engineer, WSO2 Inc
http://wso2.org
supunk.blogspot.com