Re: [Carbon-dev] Refactoring Carbon Transport Configuration Model
On 28 January 2010 11:40, Hiranya Jayathilaka wrote: > > > On Thu, Jan 28, 2010 at 4:37 PM, Paul Fremantle wrote: > >> I think that in general its dangerous to have things that "cannot" be >> stored in the Registry. For a distributed setup we need to be able to >> support as much (everything?) stored in the registry. So I like the idea of >> having a file for the standalone case, but I think we should make sure that >> we do all our config file management in a consistent way. >> > > Well that's another option. In fact we have taken a similar approach with > Synapse configuration in the Carbon trunk. We can save to the file system, > to the registry or both if necessary. But still we'll have to introduce a > new config file to store these transport settings in the file system. > +1 Paul -- Paul Fremantle CTO and Co-Founder, WSO2 OASIS WS-RX TC Co-chair, VP, Apache Synapse Office: +44 844 484 8143 Cell: +44 798 447 4618 blog: http://pzf.fremantle.org twitter.com/pzfreo p...@wso2.com wso2.com Lean Enterprise Middleware ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Refactoring Carbon Transport Configuration Model
On Thu, Jan 28, 2010 at 4:37 PM, Paul Fremantle wrote: > I think that in general its dangerous to have things that "cannot" be > stored in the Registry. For a distributed setup we need to be able to > support as much (everything?) stored in the registry. So I like the idea of > having a file for the standalone case, but I think we should make sure that > we do all our config file management in a consistent way. > Well that's another option. In fact we have taken a similar approach with Synapse configuration in the Carbon trunk. We can save to the file system, to the registry or both if necessary. But still we'll have to introduce a new config file to store these transport settings in the file system. Thanks, Hiranya > Paul > > On 28 January 2010 10:58, Hiranya Jayathilaka wrote: > >> Hi Devs, >> >> Currently we keep the servlet transport configuration in the >> transports.xml file and the other transport configurations in the axis2.xml. >> We also persist transport configurations to the registry which makes it very >> confusing and tedious for an average user to understand and manipulate >> transport settings. We can reduce the complexity by putting service >> transport configurations in a separate file and not persisting any transport >> configurations to the registry. Any changes made via the UI will be >> serialized back to the file. I think it makes sense to have transport >> configs in a place where it is easy to manually inspect and modify. >> >> May be to keep things clean we can put the servlet transport config in a >> file named console.xml and put service transport configs in the >> transports.xml. This will require some changes to the Carbon core. This is >> just an idea I got while looking at how Carbon is presently organized. WDYT? >> >> Thanks >> -- >> Hiranya Jayathilaka >> Software Engineer; >> WSO2 Inc.; http://wso2.org >> E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 >> Blog: http://techfeast-hiranya.blogspot.com >> >> ___ >> Carbon-dev mailing list >> Carbon-dev@wso2.org >> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> >> > > > -- > Paul Fremantle > CTO and Co-Founder, WSO2 > OASIS WS-RX TC Co-chair, VP, Apache Synapse > > Office: +44 844 484 8143 > Cell: +44 798 447 4618 > > blog: http://pzf.fremantle.org > twitter.com/pzfreo > p...@wso2.com > > wso2.com Lean Enterprise Middleware > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > -- Hiranya Jayathilaka Software Engineer; WSO2 Inc.; http://wso2.org E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Refactoring Carbon Transport Configuration Model
I think that in general its dangerous to have things that "cannot" be stored in the Registry. For a distributed setup we need to be able to support as much (everything?) stored in the registry. So I like the idea of having a file for the standalone case, but I think we should make sure that we do all our config file management in a consistent way. Paul On 28 January 2010 10:58, Hiranya Jayathilaka wrote: > Hi Devs, > > Currently we keep the servlet transport configuration in the transports.xml > file and the other transport configurations in the axis2.xml. We also > persist transport configurations to the registry which makes it very > confusing and tedious for an average user to understand and manipulate > transport settings. We can reduce the complexity by putting service > transport configurations in a separate file and not persisting any transport > configurations to the registry. Any changes made via the UI will be > serialized back to the file. I think it makes sense to have transport > configs in a place where it is easy to manually inspect and modify. > > May be to keep things clean we can put the servlet transport config in a > file named console.xml and put service transport configs in the > transports.xml. This will require some changes to the Carbon core. This is > just an idea I got while looking at how Carbon is presently organized. WDYT? > > Thanks > -- > Hiranya Jayathilaka > Software Engineer; > WSO2 Inc.; http://wso2.org > E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 > Blog: http://techfeast-hiranya.blogspot.com > > ___ > Carbon-dev mailing list > Carbon-dev@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > -- Paul Fremantle CTO and Co-Founder, WSO2 OASIS WS-RX TC Co-chair, VP, Apache Synapse Office: +44 844 484 8143 Cell: +44 798 447 4618 blog: http://pzf.fremantle.org twitter.com/pzfreo p...@wso2.com wso2.com Lean Enterprise Middleware ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
