Hi all,
Sorry, lost this thread somehow, :).
Hi Samisa,
With regards to governed workflow, I don't think its mandatory for ES,
because most of the artefacts you'd find in ES, will simply have state.
But, of course there can be some that need a governed workflow. For this
we can either extend ES
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
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 sen...@wso2.com wrote:
Hi all,
IMHO,
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 chand...@wso2.comwrote:
Hi Samisa
In addition to above issue, ES is still not supporting all the RXT
configuration
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
