Why not "governed workflow" in ES? In case of LCs, people always have use cases to plug-in workflows.
Thanks, Samisa... Samisa Abeysinghe Vice President Developer Evangelism WSO2 Inc. http://wso2.com On Tue, Mar 11, 2014 at 10:51 PM, Senaka Fernando <[email protected]> wrote: > Hi all, > > IMHO, G-Reg will focus on the Governance aspect. The governance of Service > Providers' artefacts will happen through G-Reg, and it will continue to > support "SOA Governance" as first-class. > > But, for use-cases involving Artefacts/Store, it will be ES. ES will also > provide a complete lifecycle. But, without a governed workflow. This is > where I was trying to get to in the AM thread on workflows. If we properly > separate the lifecycle and governed workflow associated with a lifecycle we > can clearly differentiate G-Reg and ES, AFAIU. > > G-Reg will have an embedded store, just like AM, but with limited scope. > > Thanks, > Senaka. > > > On Tue, Mar 11, 2014 at 8:54 AM, Ruchira Wageesha <[email protected]>wrote: > >> Hi Janaka, >> >> Immediate/blocking requirements were fixed in 1.0.1 branch[1] and we will >> do a patch release of 1.0.0. All the features and major improvements will >> go with 1.1.0 and has planed to release at least an Alpha by the end of Q1. >> [2], [3] and [4] issues reported by Chandana have already been fixed in [1]. >> >> /Ruchira >> >> [1] https://github.com/wso2/enterprise-store/tree/es-1.0.1-apm-reg >> [2] https://wso2.org/jira/browse/STORE-391 >> [3] https://wso2.org/jira/browse/STORE-394 >> [4] https://wso2.org/jira/browse/STORE-395 >> >> >> On Tue, Mar 11, 2014 at 7:16 AM, Janaka Ranabahu <[email protected]> wrote: >> >>> Hi Guys, >>> >>> Will these limitations get fixed in the upcoming release? If so do we >>> have a timeline for that? >>> >>> Thanks, >>> Janaka >>> >>> >>> On Sat, Mar 8, 2014 at 10:43 AM, Chandana Napagoda <[email protected]>wrote: >>> >>>> Hi Samisa >>>> >>>> In addition to above issue, ES is still not supporting all the RXT >>>> configuration elements(ex: unbounded table option) which are currently >>>> supported by G-Reg. We have reported JIRAs to get those added to coming up >>>> releases. >>>> >>>> Regards, >>>> Chandana >>>> >>>> >>>> On Mar 8, 2014 7:09 AM, "Janaka Ranabahu" <[email protected]> wrote: >>>> >>>>> Hi Samisa, >>>>> >>>>> IMO, it should be ES. But the current ES architecture does not pick >>>>> new RXT types automatically and some configurations to jaggery config >>>>> files >>>>> are required to show the new asset in both Store and Publisher[1]. Until >>>>> we >>>>> have a more flexible way of generating the Store and Publisher UI, I >>>>> believe we have to stick with G-Reg. >>>>> >>>>> Thanks, >>>>> Janaka >>>>> >>>>> [1] https://docs.wso2.org/display/ES100/Adding+a+New+Asset+Type >>>>> >>>>> >>>>> On Fri, Mar 7, 2014 at 8:08 PM, Samisa Abeysinghe <[email protected]>wrote: >>>>> >>>>>> We used to position G-Reg as a store of anything with RXT. >>>>>> >>>>>> Now what ES is there, and is more capable, do we propose the users >>>>>> use ES or G-Reg RXT like use cases? >>>>>> >>>>>> Thanks, >>>>>> Samisa... >>>>>> >>>>>> >>>>>> Samisa Abeysinghe >>>>>> >>>>>> Vice President Developer Evangelism >>>>>> >>>>>> WSO2 Inc. >>>>>> http://wso2.com >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Architecture mailing list >>>>>> [email protected] >>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> *Janaka Ranabahu* >>>>> Senior Software Engineer; WSO2 Inc.; http://wso2.com >>>>> >>>>> >>>>> * E-mail: [email protected] <http://wso2.com>**M: **+94 718370861 >>>>> <%2B94%20718370861>* >>>>> >>>>> Lean . Enterprise . Middleware >>>>> >>>>> _______________________________________________ >>>>> Architecture mailing list >>>>> [email protected] >>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>> >>>>> >>>> _______________________________________________ >>>> Architecture mailing list >>>> [email protected] >>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>> >>>> >>> >>> >>> -- >>> *Janaka Ranabahu* >>> Senior Software Engineer; WSO2 Inc.; http://wso2.com >>> >>> >>> * E-mail: [email protected] <http://wso2.com>**M: **+94 718370861 >>> <%2B94%20718370861>* >>> >>> Lean . Enterprise . Middleware >>> >>> _______________________________________________ >>> Architecture mailing list >>> [email protected] >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> >> >> >> -- >> >> *Ruchira Wageesha**Associate Technical Lead* >> *WSO2 Inc. - lean . enterprise . middleware | wso2.com <http://wso2.com>* >> >> *email: [email protected] <[email protected]>, blog: >> ruchirawageesha.blogspot.com <http://ruchirawageesha.blogspot.com>, >> mobile: +94 77 5493444 <%2B94%2077%205493444>* >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > > > *[image: http://wso2.com] <http://wso2.com> Senaka Fernando* > Senior Technical Lead; WSO2 Inc.; http://wso2.com > > > > * Member; Apache Software Foundation; http://apache.org > <http://apache.org>E-mail: senaka AT wso2.com <http://wso2.com>**P: +1 > 408 754 7388 <%2B1%20408%20754%207388>; ext: 51736*; > > > *M: +94 77 322 1818 <%2B94%2077%20322%201818> Linked-In: > http://linkedin.com/in/senakafernando > <http://linkedin.com/in/senakafernando>* > Lean . Enterprise . Middleware >
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
