You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@synapse.apache.org by Hiranya Jayathilaka <hi...@gmail.com> on 2009/07/14 06:21:41 UTC
File Hierarchy Based Configuration Builder for Synapse
Hi Folks,
I have been working on a new configuration builder for Synapse. This new
configuration builder reads the Synapse configuration from a hierarchy of
XML files instead of loading everything from a single flat file. It enables
the user to easily manage large Synapse configurations by breaking it down
to a number of smaller files.
The new functionality is completely optional and the only way to trigger the
new configuration builder is to specify a path to an existing directory
instead of the path to the synapse.xml file at startup. The old
configuration model hasn't changed a bit and therefore all the samples etc
are not effected by the change.
If the community has no objection towards getting this new configuration
builder (and the associated serializer) in I'd be happy to contribute. WDYT?
Thanks,
Hiranya
--
Hiranya Jayathilaka
Software Engineer;
WSO2 Inc.; http://wso2.org
E-mail: hiranya@wso2.com; Mobile: +94 77 633 3491
Blog: http://techfeast-hiranya.blogspot.com
Re: File Hierarchy Based Configuration Builder for Synapse
Posted by Ruwan Linton <ru...@gmail.com>.
Hiranya,
Please update the documentation according to this change... Document the
possible configuration mechanisms and specify the folder structure of the
configuration root.
Thanks,
Ruwan
On Wed, Jul 15, 2009 at 12:13 PM, Hiranya Jayathilaka
<hi...@gmail.com>wrote:
> Hi Folks,
>
> I just committed my workings to the trunk. Now when you pass a path to an
> existing *directory* as the synapse XML path, the new configuration
> builder will spring into action. This is the directory structure accepted by
> the new configuration builder.
>
> CONF_ROOT
> |-- endpoints
> |-- events
> |-- local-entries
> |-- proxy-services
> |-- registry.xml
> |-- sequences
> `-- tasks
>
> I believe the directory and file names in the above diagram explain what
> needs to be done. You can place zero or more XML files baring Synapse
> configuration definitions in the directories mentioned above. Each file
> should define exactly one item and no more. That is each proxy service
> definition should have its own file and it's the same for other artifacts.
> Registry definition will go in the registry.xml file.
>
> Thanks,
> Hiranya
>
>
>
> On Tue, Jul 14, 2009 at 4:36 PM, Ruwan Linton <ru...@gmail.com>wrote:
>
>> We were actually having this idea of separating the configuration into
>> configuration bits and provided that this is optional I would like to get
>> this in to the synapse.
>>
>> Here is my +1.
>>
>> Thanks,
>> Ruwan
>>
>>
>> On Tue, Jul 14, 2009 at 9:51 AM, Hiranya Jayathilaka <
>> hiranya911@gmail.com> wrote:
>>
>>> Hi Folks,
>>>
>>> I have been working on a new configuration builder for Synapse. This new
>>> configuration builder reads the Synapse configuration from a hierarchy of
>>> XML files instead of loading everything from a single flat file. It enables
>>> the user to easily manage large Synapse configurations by breaking it down
>>> to a number of smaller files.
>>>
>>> The new functionality is completely optional and the only way to trigger
>>> the new configuration builder is to specify a path to an existing directory
>>> instead of the path to the synapse.xml file at startup. The old
>>> configuration model hasn't changed a bit and therefore all the samples etc
>>> are not effected by the change.
>>>
>>> If the community has no objection towards getting this new configuration
>>> builder (and the associated serializer) in I'd be happy to contribute. WDYT?
>>>
>>> Thanks,
>>> Hiranya
>>>
>>> --
>>> Hiranya Jayathilaka
>>> Software Engineer;
>>> WSO2 Inc.; http://wso2.org
>>> E-mail: hiranya@wso2.com; Mobile: +94 77 633 3491
>>> Blog: http://techfeast-hiranya.blogspot.com
>>>
>>
>>
>>
>> --
>> Ruwan Linton
>> Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
>> WSO2 Inc.; http://wso2.org
>> email: ruwan@wso2.com; cell: +94 77 341 3097
>> blog: http://ruwansblog.blogspot.com
>>
>
>
>
> --
> Hiranya Jayathilaka
> Software Engineer;
> WSO2 Inc.; http://wso2.org
> E-mail: hiranya@wso2.com; Mobile: +94 77 633 3491
> Blog: http://techfeast-hiranya.blogspot.com
>
--
Ruwan Linton
Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
WSO2 Inc.; http://wso2.org
email: ruwan@wso2.com; cell: +94 77 341 3097
blog: http://ruwansblog.blogspot.com
Re: File Hierarchy Based Configuration Builder for Synapse
Posted by Hiranya Jayathilaka <hi...@gmail.com>.
Hi Folks,
I just committed my workings to the trunk. Now when you pass a path to an
existing *directory* as the synapse XML path, the new configuration builder
will spring into action. This is the directory structure accepted by the new
configuration builder.
CONF_ROOT
|-- endpoints
|-- events
|-- local-entries
|-- proxy-services
|-- registry.xml
|-- sequences
`-- tasks
I believe the directory and file names in the above diagram explain what
needs to be done. You can place zero or more XML files baring Synapse
configuration definitions in the directories mentioned above. Each file
should define exactly one item and no more. That is each proxy service
definition should have its own file and it's the same for other artifacts.
Registry definition will go in the registry.xml file.
Thanks,
Hiranya
On Tue, Jul 14, 2009 at 4:36 PM, Ruwan Linton <ru...@gmail.com>wrote:
> We were actually having this idea of separating the configuration into
> configuration bits and provided that this is optional I would like to get
> this in to the synapse.
>
> Here is my +1.
>
> Thanks,
> Ruwan
>
>
> On Tue, Jul 14, 2009 at 9:51 AM, Hiranya Jayathilaka <hiranya911@gmail.com
> > wrote:
>
>> Hi Folks,
>>
>> I have been working on a new configuration builder for Synapse. This new
>> configuration builder reads the Synapse configuration from a hierarchy of
>> XML files instead of loading everything from a single flat file. It enables
>> the user to easily manage large Synapse configurations by breaking it down
>> to a number of smaller files.
>>
>> The new functionality is completely optional and the only way to trigger
>> the new configuration builder is to specify a path to an existing directory
>> instead of the path to the synapse.xml file at startup. The old
>> configuration model hasn't changed a bit and therefore all the samples etc
>> are not effected by the change.
>>
>> If the community has no objection towards getting this new configuration
>> builder (and the associated serializer) in I'd be happy to contribute. WDYT?
>>
>> Thanks,
>> Hiranya
>>
>> --
>> Hiranya Jayathilaka
>> Software Engineer;
>> WSO2 Inc.; http://wso2.org
>> E-mail: hiranya@wso2.com; Mobile: +94 77 633 3491
>> Blog: http://techfeast-hiranya.blogspot.com
>>
>
>
>
> --
> Ruwan Linton
> Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
> WSO2 Inc.; http://wso2.org
> email: ruwan@wso2.com; cell: +94 77 341 3097
> blog: http://ruwansblog.blogspot.com
>
--
Hiranya Jayathilaka
Software Engineer;
WSO2 Inc.; http://wso2.org
E-mail: hiranya@wso2.com; Mobile: +94 77 633 3491
Blog: http://techfeast-hiranya.blogspot.com
Re: File Hierarchy Based Configuration Builder for Synapse
Posted by Ruwan Linton <ru...@gmail.com>.
We were actually having this idea of separating the configuration into
configuration bits and provided that this is optional I would like to get
this in to the synapse.
Here is my +1.
Thanks,
Ruwan
On Tue, Jul 14, 2009 at 9:51 AM, Hiranya Jayathilaka
<hi...@gmail.com>wrote:
> Hi Folks,
>
> I have been working on a new configuration builder for Synapse. This new
> configuration builder reads the Synapse configuration from a hierarchy of
> XML files instead of loading everything from a single flat file. It enables
> the user to easily manage large Synapse configurations by breaking it down
> to a number of smaller files.
>
> The new functionality is completely optional and the only way to trigger
> the new configuration builder is to specify a path to an existing directory
> instead of the path to the synapse.xml file at startup. The old
> configuration model hasn't changed a bit and therefore all the samples etc
> are not effected by the change.
>
> If the community has no objection towards getting this new configuration
> builder (and the associated serializer) in I'd be happy to contribute. WDYT?
>
> Thanks,
> Hiranya
>
> --
> Hiranya Jayathilaka
> Software Engineer;
> WSO2 Inc.; http://wso2.org
> E-mail: hiranya@wso2.com; Mobile: +94 77 633 3491
> Blog: http://techfeast-hiranya.blogspot.com
>
--
Ruwan Linton
Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
WSO2 Inc.; http://wso2.org
email: ruwan@wso2.com; cell: +94 77 341 3097
blog: http://ruwansblog.blogspot.com