Re: [Carbon-dev] Possible improvements to CS
Hi Chathuri, setting the default version to the latest supported version will solve our issue. Thanks, Ishan. On Sun, Mar 4, 2012 at 4:49 PM, Chathuri Wimalasena wrote: > Hi Ishan, > > On Sat, Mar 3, 2012 at 5:17 PM, Ishan Jayawardena wrote: > >> Hi Chathuri, >> I would like to elaborate on this issue[1]. I think we have to support >> defining/editing namespaces separately because namespaces do not >> belong to the "Properties" view of an element(because they are neither >> attributes nor child nodes) but they are common to all XML elements. >> Therefore it would be useful if you can add a new item to the context >> menu of all XML elements called "Edit Namespaces..." which will bring >> out a namespace editor. This is already available in the XML design >> view of eclipse. >> > > +1 for the suggestion. We can add that improvement. Even now, users can > add namespaces at the global level with source view. This is not a straight > forward feature in the sequence editor in WSO2 ESB as well. But as you > suggested, this will be a useful feature for an end user. > > >> >> In your comment on this issue [2] you say that the target version of >> the ESB can be adjusted within eclipse but the user might not be aware >> of this feature. I believe it would be more meaningful to make that >> feature available in the dashboard or in each wizard (as well). >> Please give your opinions on these suggestions. >> > > I agree that you have a point. But at the development time, if the user is > a newbie, he may not know anything about a ESB versions. IMO, we should not > show information regarding ESB versions in the dashboard. We can show that > information in each and every wizard pages related to ESB features as a > checkbox and set the default ESB version as 4.0.0. Problem with this method > is, that information will be redundant in all the wizard pages. Since the > ESB version is a global setting, users should be able to set it one time > and use it until he wants to change it to something else. We have > documented regarding that preference option in our documentation. We add > this to Eclipse preference page, since this is a global setting and only > advanced users may need to set this feature. IMO, we should keep this as it > is and change the default version to ESB 4.0.0 (which was 3.0.1 previously > ). WDYT ? > > Thanks and Regards, > Chathuri > > >> >> [1] https://wso2.org/jira/browse/TOOLS-946 >> [2] https://wso2.org/jira/browse/TOOLS-943 >> >> Thank you. >> Ishan. >> >> On 3/2/12, Chathuri Wimalasena wrote: >> > Hi Ishan, >> > >> > Thanks alot for the feedback. I believe you change the ESB version in >> the >> > preference page to 4.0.0 [1]. By default, it is set as 3.0.1. After >> setting >> > that preference, you will see, ESB 4.0.0 related mediators being >> activated. >> > Support for defining API [2] is in our roadmap and this feature will be >> > available in the future. >> > >> > We will go through them and try to resolve them. >> > >> > Thanks and Regards, >> > Chathuri >> > >> > [1] >> > >> http://wso2.org/project/carbon-studio/1.0.14/docs/esb_category.html#SupportDifferentESBVersions >> > [2] https://wso2.org/jira/browse/TOOLSROADMAP-26 >> > >> > >> > On Thu, Mar 1, 2012 at 11:34 PM, Ishan Jayawardena >> wrote: >> > >> >> Hi, >> >> I have been using Carbon Studio (M9) to develop the Starbucks sample >> which >> >> Hiranya originally developed [1]. While working with CS, I found >> several >> >> places where we can improve CS editor's support for develping ESB >> >> configurations. I have created JIRA issues addressing them [2 - 5]. >> Please >> >> give your feedback on them. >> >> >> >> [1] https://svn.wso2.com/wso2/repos/client/docs/starbucks-sample/ >> >> [2] https://wso2.org/jira/browse/TOOLS-943 >> >> [3] https://wso2.org/jira/browse/TOOLS-944 >> >> [4] https://wso2.org/jira/browse/TOOLS-945 >> >> [5] https://wso2.org/jira/browse/TOOLS-946 >> >> >> >> Thanks, >> >> Ishan. >> >> >> >> -- >> >> Ishan Jayawardena >> >> Software Engineer >> >> Integration Technologies Team >> >> WSO2 Inc. http://wso2.com/ >> >> *Mobile: +94-774-082-330* >> >> >> >> >> > >> > >> > -- >> > Chathuri Wimalasena >> > Senior Software Engineer; WSO2, Inc.; http://wso2.com/ >> > email: chath...@wso2.com; phone: +94 772 608 596 >> > blog: http://chathuriwimalasena.blogspot.com/ >> > >> >> >> -- >> Ishan Jayawardena >> Software Engineer >> Integration Technologies Team >> WSO2 Inc. http://wso2.com/ >> *Mobile: +94-774-082-330* >> > > > > -- > Chathuri Wimalasena > Senior Software Engineer; WSO2, Inc.; http://wso2.com/ > email: chath...@wso2.com; phone: +94 772 608 596 > blog: http://chathuriwimalasena.blogspot.com/ > -- Ishan Jayawardena Software Engineer Integration Technologies Team WSO2 Inc. http://wso2.com/ *Mobile: +94-774-082-330* ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Possible improvements to CS
Hi Chathuri, I would like to elaborate on this issue[1]. I think we have to support defining/editing namespaces separately because namespaces do not belong to the "Properties" view of an element(because they are neither attributes nor child nodes) but they are common to all XML elements. Therefore it would be useful if you can add a new item to the context menu of all XML elements called "Edit Namespaces..." which will bring out a namespace editor. This is already available in the XML design view of eclipse. In your comment on this issue [2] you say that the target version of the ESB can be adjusted within eclipse but the user might not be aware of this feature. I believe it would be more meaningful to make that feature available in the dashboard or in each wizard (as well). Please give your opinions on these suggestions. [1] https://wso2.org/jira/browse/TOOLS-946 [2] https://wso2.org/jira/browse/TOOLS-943 Thank you. Ishan. On 3/2/12, Chathuri Wimalasena wrote: > Hi Ishan, > > Thanks alot for the feedback. I believe you change the ESB version in the > preference page to 4.0.0 [1]. By default, it is set as 3.0.1. After setting > that preference, you will see, ESB 4.0.0 related mediators being activated. > Support for defining API [2] is in our roadmap and this feature will be > available in the future. > > We will go through them and try to resolve them. > > Thanks and Regards, > Chathuri > > [1] > http://wso2.org/project/carbon-studio/1.0.14/docs/esb_category.html#SupportDifferentESBVersions > [2] https://wso2.org/jira/browse/TOOLSROADMAP-26 > > > On Thu, Mar 1, 2012 at 11:34 PM, Ishan Jayawardena wrote: > >> Hi, >> I have been using Carbon Studio (M9) to develop the Starbucks sample which >> Hiranya originally developed [1]. While working with CS, I found several >> places where we can improve CS editor's support for develping ESB >> configurations. I have created JIRA issues addressing them [2 - 5]. Please >> give your feedback on them. >> >> [1] https://svn.wso2.com/wso2/repos/client/docs/starbucks-sample/ >> [2] https://wso2.org/jira/browse/TOOLS-943 >> [3] https://wso2.org/jira/browse/TOOLS-944 >> [4] https://wso2.org/jira/browse/TOOLS-945 >> [5] https://wso2.org/jira/browse/TOOLS-946 >> >> Thanks, >> Ishan. >> >> -- >> Ishan Jayawardena >> Software Engineer >> Integration Technologies Team >> WSO2 Inc. http://wso2.com/ >> *Mobile: +94-774-082-330* >> >> > > > -- > Chathuri Wimalasena > Senior Software Engineer; WSO2, Inc.; http://wso2.com/ > email: chath...@wso2.com; phone: +94 772 608 596 > blog: http://chathuriwimalasena.blogspot.com/ > -- Ishan Jayawardena Software Engineer Integration Technologies Team WSO2 Inc. http://wso2.com/ *Mobile: +94-774-082-330* ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
[Carbon-dev] Possible improvements to CS
Hi, I have been using Carbon Studio (M9) to develop the Starbucks sample which Hiranya originally developed [1]. While working with CS, I found several places where we can improve CS editor's support for develping ESB configurations. I have created JIRA issues addressing them [2 - 5]. Please give your feedback on them. [1] https://svn.wso2.com/wso2/repos/client/docs/starbucks-sample/ [2] https://wso2.org/jira/browse/TOOLS-943 [3] https://wso2.org/jira/browse/TOOLS-944 [4] https://wso2.org/jira/browse/TOOLS-945 [5] https://wso2.org/jira/browse/TOOLS-946 Thanks, Ishan. -- Ishan Jayawardena Software Engineer Integration Technologies Team WSO2 Inc. http://wso2.com/ *Mobile: +94-774-082-330* ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] WSO2 Committers += Ishan Jayawardena
Hi Hiranya, Thank you very much for giving me the privilege. Hoping to do a valuable contribution to the team. Thanks, Ishan. On Thu, Feb 16, 2012 at 11:18 AM, Hiranya Jayathilaka wrote: > Hi Folks, > > The integration PMC has voted in Ishan Jayawardena as a WSO2 committer. He > has been an excellent contributor for Carbon and other related projects > over the last few months. We sincerely believe that he will continue to > develop our platform with his contributions. > > Ishan, welcome aboard and keep up the good work. > > Thanks > -- > Hiranya Jayathilaka > Associate Technical Lead; > WSO2 Inc.; http://wso2.org > E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 > Blog: http://techfeast-hiranya.blogspot.com > -- Ishan Jayawardena Software Engineer Integration Technologies Team WSO2 Inc. http://wso2.com/ ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
[Carbon-dev] BPMN2BPEL
Hi, Our requirement is to create a tool for Eclipse that can directly deploy a business process modeled in BPMN 2, into BPS. Eclipse already has a BPMN editor but it supports only BPMN 1.0. Initially, the plan was to convert a BPMN diagram into BPEL and then deploy that process in BPS, but this editor is not capable of the converting BPMN into BPEL. The lateset BPMN specification is BPMN 2 which is not still finalized. It has new characteristics like, - concerns direct execution after modeling, without conversion - consists of all BPEL semantics (i.e BPMN2 does everything that BPEL does) - does not use WSDL Therefore, I think we have two options, 1. we will have to wait until the spec gets finalized and use the model it suggests for executing processes 2. we can still try to implement the convesion part (which is going to be lengthy and so difficult) The development for a BPMN2 editor for eclipse is under way and I am trying to work on that. But still I do not have any idea as to with which option to continue. If you have any suggestions please let me know. Thanks. ___ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
