synapse-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From tsaha <Tanmay.S...@westernasset.com>
Subject Re: Exploded vs Archived deployments of config meta data
Date Tue, 01 Jul 2008 17:15:23 GMT

Hi Ruwan:

I am sorry. I mean it has to be both read-only Registry in the jar or zip
format.

-thanks
tanmay


tsaha wrote:
> 
> Hi Ruwan:
> 
> I mean read-only repository . How do you really differentiate between
> Repository and Registry in Synapse?
> 
> Definitely I can use SVN, but my strategy for deployment is to do a token
> replacement through Ant filtering for evironment related variables ( like
> hostname, port number in endpoint configuration and etc) 
> while moving the config meta data from DEV --> QA --> UAT -->PROD. So I
> prefer shared file system Repository/Registry . For many Proxy Deployment,
> I have decided to use more than one Synapse config file (Synapse1.xml,
> Synapse2.xml , Synapse3.xml .... ) and use case wise I will distribute the
> <proxy> elements among multiple Synapse config files, and the develop a
> startup script (using XQuery )which will aggregate all config elements
> from different synapse config files into a single Synapse.xml file .
> 
> Is it possible for Synapse to specify multiple config files during startup
> like Springframework ( where you can use more than one beans config file
> like
> applicationContext1.xml,applicationContext2.xml,applicationContext3.xml,
> and so on )? This will make maintenance and developers' easy  over a giant
> config file. 
> 
> -Thanks
> tanmay
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Ruwan Linton wrote:
>> 
>> Hi Tanmay,
>> 
>> Good point. I think we should be able to support archived repository and
>> in
>> this case it will be a read only repository. According to your case any
>> way
>> this is going to be read only right?
>> 
>> BTW: One other option would be to use SVN as the repository so that one
>> could easily point to a SVN location as the repository.
>> 
>> Just to make it clear are you referring to the repository or the registry
>> in
>> the archived format here?
>> 
>> Thanks,
>> Ruwan
>> 
>> On Tue, Jul 1, 2008 at 6:57 AM, tsaha <Tanmay.Saha@westernasset.com>
>> wrote:
>> 
>>>
>>> Hi Ruwan:
>>>
>>> For deployment purposes single unit archive is more manageable. We can
>>> just
>>> tell our operation team "Please deploy this jar or zip file to QA or
>>> PROD."
>>>
>>>
>>>
>>> -Thanks
>>> tanmay
>>>
>>>
>>>
>>> Ruwan Linton wrote:
>>> >
>>> > Hi Tanmay,
>>> >
>>> > For the moment we do not support this. You cannot put them in a JAR
>>> and
>>> > refer to it, but just the exploded structure. Can I know the
>>> requirement
>>> > for
>>> > you to put them on an archive?
>>> >
>>> > Thanks,
>>> > Ruwan
>>> >
>>> > On Tue, Jul 1, 2008 at 5:49 AM, tsaha <Tanmay.Saha@westernasset.com>
>>> > wrote:
>>> >
>>> >>
>>> >> Is it possible to  create a jar consisting of all my config meta data
>>> (
>>> >> wsdls, endpoints, sequences and etc ) and then refer from synapse.xml
>>> or
>>> >> only exploded structure is supported?
>>> >> --
>>> >> View this message in context:
>>> >>
>>> http://www.nabble.com/Exploded-vs-Archived-deployments-of-config-meta-data-tp18206910p18206910.html
>>> >> Sent from the Synapse - User mailing list archive at Nabble.com.
>>> >>
>>> >>
>>> >
>>> >
>>> > --
>>> > Ruwan Linton
>>> > http://wso2.org - "Oxygenating the Web Services Platform"
>>> > http://ruwansblog.blogspot.com/
>>> >
>>> >
>>>
>>> --
>>> View this message in context:
>>> http://www.nabble.com/Exploded-vs-Archived-deployments-of-config-meta-data-tp18206910p18207529.html
>>> Sent from the Synapse - User mailing list archive at Nabble.com.
>>>
>>>
>> 
>> 
>> -- 
>> Ruwan Linton
>> http://wso2.org - "Oxygenating the Web Services Platform"
>> http://ruwansblog.blogspot.com/
>> 
>> 
> 
> 

-- 
View this message in context: http://www.nabble.com/Exploded-vs-Archived-deployments-of-config-meta-data-tp18206910p18220974.html
Sent from the Synapse - User mailing list archive at Nabble.com.


Mime
View raw message