+1 Ruwan
On Thu, Sep 23, 2010 at 10:10 AM, Supun Kamburugamuva <[email protected]>wrote: > How about extending from the pirority executors in commons and create > synapse internal versions of it? Then we can use the synapse artificat. > > Thanks, > Supun.. > > > On Wed, Sep 22, 2010 at 4:47 AM, Ruwan Linton <[email protected]>wrote: > >> Moving Synapse Artifact into the commons is not a good solution as that >> will result in core API being moved to commons. We need to think through and >> come to a conclusion. >> >> Thanks, >> Ruwan >> >> >> On Tue, Sep 21, 2010 at 11:47 PM, Charith Wickramarachchi < >> [email protected]> wrote: >> >>> Hi, >>> >>> In the current trunk the PriorityExecutor is not a SynapseArtifact. but >>> IMHO since its a synapse configuration element it need to be a synapse >>> artifact. But to make it a Synapse Artifact we need to make the commons >>> module depend on synapse-core which will introduce a cyclic dependency. >>> >>> So i was wondering how to solve this issue ? >>> >>> One simple way to solve this is to move the SynapseArtifact to commons. >>> but i m not sure is it correct way since i m not sure about the duty scope >>> of the commons module in synapse. >>> >>> any thoughts ? >>> >>> >>> >>> -- >>> Charith Dhanushka Wickramarachchi >>> http://charithwiki.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: [email protected]; 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 >> > > > > -- > Tech Lead, 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: [email protected]; 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
