Hi Tharindu, :-)... Anyway, could you briefly outline what you expected, so that Janaka and the others can make sure that the OOTB experience can capture a requirement similar to the one you had. I believe that we might be having 80% of what you want but the last mile is always the toughest part, so your feedback is very useful.
Thanks, Senaka. On Fri, Mar 30, 2012 at 5:21 PM, Tharindu Mathew <[email protected]> wrote: > > > On Fri, Mar 30, 2012 at 1:14 PM, Senaka Fernando <[email protected]> wrote: > >> Hi Tharindu, >> >> This is dead obvious. >> > :O :) i'll figure it out the next time. Thanks. > >> >> 1. Create a new Service with the ServiceLifecycle as its lifecycle. >> 2. Promote the service. >> 3. Go and check inside /_system/governance/branches/.. >> >> Please note that as I mentioned in my e-mail this works only for >> services. If you want this for any type of asset, you have to use your own >> CopyExecutor in releases 4.1.0 and 4.1.1, and there will be a CopyExecutor >> shipped by default from 4.2.0 onwards (this is already on the trunk). >> >> What else are you expecting out of this? >> >> Also, what I meant that you need to reconfigure is if you want this to >> work with the exact same paths (ex:- /environment/design), exact same state >> names etc. >> >> You also can try out the distributedLCM sample in 4.0.0 and compare and >> contrast the two approaches if you are in doubt of anything. >> >> Thanks, >> Senaka. >> >> On Fri, Mar 30, 2012 at 1:04 PM, Tharindu Mathew <[email protected]>wrote: >> >>> Senaka, >>> >>> I don't want to know how to re-configure. Just give me a sample I can >>> run. >>> >>> You say two things. That it works OOTB and then I can easily >>> re-configure. I really did not see my artifact moving around in a >>> distributed manner OOTB! >>> >>> >>> On Fri, Mar 30, 2012 at 12:55 PM, Senaka Fernando <[email protected]>wrote: >>> >>>> Hi Tharindu, Janaka, >>>> >>>> You do not need a new sample (I mean separate code is not required). >>>> You can very easily reconfigure the default lifecycle configuration and do >>>> exactly the same. And, the current service lifecycle configuration that we >>>> ship OOTB does everything (functionality-vise) what the previous >>>> distributed LCM sample did. >>>> >>>> Thanks, >>>> Senaka. >>>> >>>> >>>> On Fri, Mar 30, 2012 at 10:09 AM, Tharindu Mathew <[email protected]>wrote: >>>> >>>>> Oh... that sucks... >>>>> >>>>> It would've been better to replace than to remove... I'll just skip >>>>> this demo... >>>>> >>>>> >>>>> On Fri, Mar 30, 2012 at 10:04 AM, Janaka Ranabahu <[email protected]>wrote: >>>>> >>>>>> Hi Tharindu, >>>>>> >>>>>> The distributed LCM sample was written using older lifecycle >>>>>> configuration model and was not compatible with the new lifecycle model. >>>>>> All of what was doable with the older distributed LCM sample (which >>>>>> involved a more powerful LC than the older Service LC) can now be done >>>>>> OOTB >>>>>> in G-reg 4.1.1. So we decided to remove it from the distribution until we >>>>>> create a new sample using the new lifecycle configuration model. >>>>>> >>>>>> Thanks, >>>>>> Janaka >>>>>> >>>>>> On Fri, Mar 30, 2012 at 9:26 AM, Tharindu Mathew >>>>>> <[email protected]>wrote: >>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> This is an extremely usefu sample for demos. Where is it now?? >>>>>>> >>>>>>> :samples $ ls >>>>>>> custom-ui dotnet filesampleutils handler >>>>>>> jcr-client pom.xml shutterbug ws-client >>>>>>> >>>>>>> -- >>>>>>> Regards, >>>>>>> >>>>>>> Tharindu >>>>>>> >>>>>>> blog: http://mackiemathew.com/ >>>>>>> M: +94777759908 >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Dev mailing list >>>>>>> [email protected] >>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Janaka Ranabahu >>>>>> Software Engineer >>>>>> WSO2 Inc. >>>>>> >>>>>> Mobile +94 718370861 >>>>>> Email : [email protected] >>>>>> Blog : janakaranabahu.blogspot.com >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Regards, >>>>> >>>>> Tharindu >>>>> >>>>> blog: http://mackiemathew.com/ >>>>> M: +94777759908 >>>>> >>>>> >>>>> _______________________________________________ >>>>> Dev mailing list >>>>> [email protected] >>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>> >>>>> >>>> >>>> >>>> -- >>>> *Senaka Fernando* >>>> Product Manager - WSO2 Governance Registry; >>>> Associate Technical Lead; WSO2 Inc.; http://wso2.com* >>>> Member; Apache Software Foundation; http://apache.org >>>> >>>> E-mail: senaka AT wso2.com >>>> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 >>>> Linked-In: http://linkedin.com/in/senakafernando >>>> >>>> *Lean . Enterprise . Middleware >>>> >>>> >>> >>> >>> -- >>> Regards, >>> >>> Tharindu >>> >>> blog: http://mackiemathew.com/ >>> M: +94777759908 >>> >>> >> >> >> -- >> *Senaka Fernando* >> Product Manager - WSO2 Governance Registry; >> Associate Technical Lead; WSO2 Inc.; http://wso2.com* >> Member; Apache Software Foundation; http://apache.org >> >> E-mail: senaka AT wso2.com >> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 >> Linked-In: http://linkedin.com/in/senakafernando >> >> *Lean . Enterprise . Middleware >> >> > > > -- > Regards, > > Tharindu > > blog: http://mackiemathew.com/ > M: +94777759908 > > -- *Senaka Fernando* Product Manager - WSO2 Governance Registry; Associate Technical Lead; WSO2 Inc.; http://wso2.com* Member; Apache Software Foundation; http://apache.org E-mail: senaka AT wso2.com **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 Linked-In: http://linkedin.com/in/senakafernando *Lean . Enterprise . Middleware
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
