On Sat, Apr 21, 2012 at 1:18 PM, Afkham Azeez <[email protected]> wrote:
> > > On Sat, Apr 21, 2012 at 12:13 PM, Hiranya Jayathilaka <[email protected]>wrote: > >> >> >> On Fri, Apr 20, 2012 at 7:34 PM, Afkham Azeez <[email protected]> wrote: >> >>> Some problems. >>> >>> 1. org.wso2.carbon.deployment.synchronizer.subversion bundle is missing >>> 2. svnclient bundle is missing >>> 3. If you configure once using the UI, all your subsequent changes to >>> carbon.xml will be ignored >>> >> >> Right. You should use one way of configuring this feature. We don't sync >> configurations from file system to the registry due to the 2-way sync >> problem.Settings in the registry have priority. >> >> >>> 4. UI configurations are stored in local repository. So, if your cluster >>> has several nodes, you will have to make changes to all nodes one by one.\ >>> >> >> That's right. This is because within a single cluster some nodes will be >> in auto checkout mode and some nodes (usually one) will be in auto commit >> mode. We used to store these settings in config registry about a year ago, >> but with that we cannot use this component to actually configure a useful >> clustered setup. That way either everyone will be in auto commit mode or >> everyone will be in auto checkout mode. So we moved the settings to the >> local repo. It's a per node setting. >> > > On a related note, the way we handle service metadata is, we give > precedence to the metadata stored in the metadata repository (earlier this > was the config registry). But when the original artifact was changed or > re-uploaded, we used to clear out all the data in the metadata repo, and > give precedence to the metadata in the uploaded artifact. If the UI is > going be there, we should have something similar. Yesterday, we had an > issue with the UI based depsync config, then tried to change the settings > in the carbon.xml, and were in for a surprise when it was not picked up. > Then we had to go into the implementation, and figure out that we would > need to go to the registry browser and remove the depsync configuration. > This sort of thing may be too much for an average user. > Ok got the point. Up until now we have been recommending users to use one of the provided ways to set this up. Trying to use a bit of this and bit of that usually leads to conflicts such as the one you have described. Implementing something like service persistence is tricky here, since there is no 'artifact' object involved with this to detect changes from. What we can do is to flip the priority order and give prominence to carbon.xml when the synchronizer seems to be enabled in both fronts. I think that should take care of the situation you have described and might even be useful when somebody first tries out a configuration through UI and then wants to move it to carbon.xml. Thanks, Hiranya > >> Thanks, >> Hiranya >> >> >>> >>> >>> On Fri, Apr 20, 2012 at 6:53 PM, Afkham Azeez <[email protected]> wrote: >>> >>>> Folks, >>>> Has anybody tested this with the new packs? >>>> >>>> -- >>>> *Afkham Azeez* >>>> Director of Architecture; WSO2, Inc.; http://wso2.com >>>> Member; Apache Software Foundation; http://www.apache.org/ >>>> * <http://www.apache.org/>** >>>> email: **[email protected]* <[email protected]>* cell: +94 77 3320919 >>>> blog: **http://blog.afkham.org* <http://blog.afkham.org>* >>>> twitter: >>>> **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> >>>> * >>>> linked-in: **http://lk.linkedin.com/in/afkhamazeez* >>>> * >>>> * >>>> *Lean . Enterprise . Middleware* >>>> >>>> >>> >>> >>> -- >>> *Afkham Azeez* >>> Director of Architecture; WSO2, Inc.; http://wso2.com >>> Member; Apache Software Foundation; http://www.apache.org/ >>> * <http://www.apache.org/>** >>> email: **[email protected]* <[email protected]>* cell: +94 77 3320919 >>> blog: **http://blog.afkham.org* <http://blog.afkham.org>* >>> twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> >>> * >>> linked-in: **http://lk.linkedin.com/in/afkhamazeez* >>> * >>> * >>> *Lean . Enterprise . Middleware* >>> >>> >>> _______________________________________________ >>> Dev mailing list >>> [email protected] >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> Hiranya Jayathilaka >> Associate Technical Lead; >> WSO2 Inc.; http://wso2.org >> E-mail: [email protected]; Mobile: +94 77 633 3491 >> Blog: http://techfeast-hiranya.blogspot.com >> > > > > -- > *Afkham Azeez* > Director of Architecture; WSO2, Inc.; http://wso2.com > Member; Apache Software Foundation; http://www.apache.org/ > * <http://www.apache.org/>** > email: **[email protected]* <[email protected]>* cell: +94 77 3320919 > blog: **http://blog.afkham.org* <http://blog.afkham.org>* > twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> > * > linked-in: **http://lk.linkedin.com/in/afkhamazeez* > * > * > *Lean . Enterprise . Middleware* > > -- Hiranya Jayathilaka Associate Technical Lead; WSO2 Inc.; http://wso2.org E-mail: [email protected]; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
