Question to AF team:
At the moment, there is a runtime associated with each lifecycle stage.
i.e. Dev for Dev, Test for Test etc. This is not going to change, right? My
concern is, when a user adds a new stage, how are we going to provide the
runtime for it? In the public cloud scenario, we have
In the current impl, the engine and the UI seems to be bit disconnected.
(config parameter name=transport.vfs.FileURI
key=conf:/repository/esb/esb-configurations/test/ translates to
key:conf:/repository/esb/esb-configurations/test in the UI (This will be
complicated when it comes to dev studio
Hi Bimali,
In AF, we have roles for the particular stage/stages right? For example
Application Owner/Developer/QA/DevOp etc. How do we handle that if the user
uses custom staging?
Thanks,
-Ayash
On Mon, Jun 22, 2015 at 3:01 PM, Dimuthu Leelarathne dimut...@wso2.com
wrote:
Hi,
IMO, we need
Hi All,
We have WSO2 Developer Studio 3.8.0 Alpha ready to be downloaded at [1] and
installed eclipse distributions available at [2].
This release includes following features, tasks and bug fixes.
Features:
- [TOOLS-2893 https://wso2.org/jira/browse/TOOLS-2893] - Support for
the exploded
Hi,
I have tested the Alpha pack and found 2 issues. Might be worth looking to
fix them for Beta,
[1]. https://wso2.org/jira/browse/TOOLS-2918
[2]. https://wso2.org/jira/browse/TOOLS-2919
Thanks and Regards,
Harshana
--
Harshana Eranga Martin
Committer - Eclipse ECF:
Hi Harshana,
Thanks for reporting the issues. We have already reported the issue
regarding ESB graphical editor is getting dirty when opening artifacts at
[1]. We''ll fix these issues for Beta.
[1] https://wso2.org/jira/browse/TOOLS-2908
Thanks,
Sohani
Sohani Weerasinghe
Software Engineer
