Frankly I'm completely confused by this discussion. I already added
support for this in July 2007:
see http://issues.apache.org/jira/browse/SYNAPSE-111

You can already add an alternative configuration builder based on the
namespace of the XML document without any further code changes.

Admittedly this only works for XML, but I'm guessing you want XML for
the Spring model?

I also completely disagree with Asankha's point that no-one has ever
asked for it since there is a blooming JIRA and I've also blogged a
number of times about adding DSL support to Synapse!

Paul



On Sun, Feb 22, 2009 at 11:40 AM, Sanjiva Weerawarana
<[email protected]> wrote:
> On 2/22/09, Asankha C. Perera <[email protected]> wrote:
>> Charith's email (nor the patch) did not indicate any of this, not even
>> the word 'Spring' :-)
>
> Right, probably because the changes are generic and not specific to
> Spring. Spring is only one potentially interesting alternative DSL for
> how to wire up a Synapse configuration.
>
>> Charith I still stand by what I wrote below. Also please refer to [1]
>> for the Synapse development guidelines for code contributions
>
> Totally +1 for making contributions compliant to the guidelines.
>
> Sanjiva.
> --
> Sanjiva Weerawarana, Ph.D.
> Founder & Director; Lanka Software Foundation; http://www.opensource.lk/
> Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
> Member; Apache Software Foundation; http://www.apache.org/
> Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/
>
> Blog: http://sanjiva.weerawarana.org/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>



-- 
Paul Fremantle
Co-Founder and CTO, WSO2
Apache Synapse PMC Chair
OASIS WS-RX TC Co-chair

blog: http://pzf.fremantle.org
[email protected]

"Oxygenating the Web Service Platform", www.wso2.com

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to