Re: [Dev] WSO2 Committers += Dilini Muthumala

[Melan Nimesh]

Congratulations Dilini !!!


On Fri, Aug 15, 2014 at 10:14 AM, Aruna Karunarathna  wrote:

> Congratzz Dilini..!!!
>
>
> On Fri, Aug 15, 2014 at 10:12 AM, Sohani Weerasinghe 
> wrote:
>
>> Congratulations 
>>
>> Sohani Weerasinghe
>> Software Engineer
>> WSO2, Inc: http://wso2.com
>>
>> Mobile  : +94 716439774
>> Blog :http://christinetechtips.blogspot.com/
>> Twitter  : https://twitter.com/sohanichristine
>>
>>
>> On Fri, Aug 15, 2014 at 9:50 AM, Susinda Perera  wrote:
>>
>>> Congratulations.. !
>>>
>>>
>>>
>>> On Fri, Aug 15, 2014 at 9:47 AM, Sriskandarajah Suhothayan <
>>> s...@wso2.com> wrote:
>>>

 Hi All,

 It's my pleasure to announce Dilini Muthumala as a WSO2 Committer.
 Dilini has been a valuable contributor for WSO2 CEP product and in
 recognition of her contributions to WSO2, she has been voted as a
 WSO2Committer.

 Dilini, Congratulations and Keep up the good work!

 Thanks and Regards,
 Suho
  --

 *S. Suhothayan*
 Technical Lead & Team Lead of WSO2 Complex Event Processor
  *WSO2 Inc. *http://wso2.com
 * *
 lean . enterprise . middleware


 *cell: (+94) 779 756 757 <%28%2B94%29%20779%20756%20757> | blog:
 http://suhothayan.blogspot.com/  twitter:
 http://twitter.com/suhothayan  | linked-in:
 http://lk.linkedin.com/in/suhothayan 
 *

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev


>>>
>>>
>>> --
>>> *Susinda Perera*
>>> Software Engineer
>>> Mobile:(+94)716049075
>>>
>>> WSO2 Inc. http://wso2.com/
>>> Tel : 94 11 214 5345 Fax :94 11 2145300
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
>
> * Aruna Sujith Karunarathna* | Software Engineer
> WSO2, Inc | lean. enterprise. middleware.
> #20, Palm Grove, Colombo 03, Sri Lanka
> Mobile: +94 71 9040362 | Work: +94 112145345
> Email: ar...@wso2.com | Web: www.wso2.com
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] using the tag in contextualizing the new option for dec_studio projects

[Melan Nimesh]

On Sun, Jul 20, 2014 at 10:46 AM, Awanthika Senarath 
wrote:

> HI
>
> but  extension point "navigatorcontent" does not provide the label we want
> in to the projectrightclick->new-> options does it? we have to use the
> extension point newWizard in order to get it under the new options on
> project right click in project explorer.
>

Yes, you have to define your wizard configurations under newWizard
extension-point, then you can refer it inside navigatorcontent as a
commonWizard, under that you can use enablement tag. for a example if you
right click on a JAX-RS project on DevS, there is a option 'JAX-RS service
class'. Currently DevS list all possible project type under new option of
project's context menu, It was a design decision to simulate nested project
structure.


>
> regards
>
>
> On Sat, Jul 19, 2014 at 9:56 PM, Awanthika Senarath 
> wrote:
>
>> thank you, i was trying the enablement tag with the newWizard and it
>> didnt work either.. will try it with navigatorcontent and let you know!
>>
>> thanks and regards
>>
>> awanthika
>>
>>
>> On Sat, Jul 19, 2014 at 12:16 AM, Melan Nimesh  wrote:
>>
>>> Hi,
>>>
>>>
>>> On Fri, Jul 18, 2014 at 10:57 AM, Awanthika Senarath >> > wrote:
>>>
>>>> Hi,
>>>>
>>>> Im trying to contextualize the eclipse new project option in
>>>>
>>>>  project (in projectExplorer) -> rightclick -> new -> wso2projects
>>>>  (CEP project/ proxy service etc.)
>>>>
>>>>  to make it more meaningful.
>>>>
>>>> I have been trying with the  tag inside the
>>>>   filtering by project nature
>>>> in plugin.xml with no success.
>>>>
>>>
>>> AFAIK, org.eclipse.ui.newWizards extension-point does not supports
>>> visibleWhen or activeWhen attributes. you can use
>>> org.eclipse.ui.navigator.navigatorContent extension point to achieve your
>>> requirements I guess. we are using it in many places inside DevS. please
>>> refer org.wso2.developerstudio.eclipse.artifact.axis2 component's
>>> plugin.xml [1] for a example.
>>>
>>> e.g.
>>>
>>>  
>>> >>
>>> menuGroupId="1org.wso2.developerstudio.eclipse.artifact.webservice1"
>>>
>>> wizardId="org.wso2.developerstudio.eclipse.artifact.axis2.ui.wizard">
>>> 
>>> 
>>> >> type="org.eclipse.core.resources.IProject">
>>> >> property="org.eclipse.core.resources.projectNature"
>>>
>>> value="org.wso2.developerstudio.eclipse.axis2.project.nature" />
>>> 
>>> >> type="org.eclipse.jdt.core.IPackageFragment">
>>> >> property="org.wso2.developerstudio.projectNature"
>>>
>>> value="org.wso2.developerstudio.eclipse.axis2.project.nature" />
>>> 
>>>     
>>> 
>>> 
>>> 
>>>
>>> Thanks,
>>> Melan
>>>
>>> [1]
>>> https://github.com/wso2-dev/developer-studio/blob/master/app-server/org.wso2.developerstudio.eclipse.artifact.axis2/plugin.xml
>>>
>>>
>>>
>>>>
>>>> is there anyone who has previous experience in using this tag? OR any
>>>> other way of getting it done? I also tried with the property-tester in
>>>> eclipse.
>>>>
>>>> thanks and regards
>>>> --
>>>> Awanthika Senarath
>>>> Software Engineer, WSO2 Inc.
>>>> Mobile: +94717681791
>>>>
>>>>
>>>>
>>>> ___
>>>> Dev mailing list
>>>> Dev@wso2.org
>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>
>>>>
>>>
>>>
>>> --
>>> *Melan Nimesh*
>>> Software Engineer;
>>> WSO2 Inc.;  http://wso2.org
>>> E-mail: melan AT wso2.com;
>>> Mobile: +94 77 631 6759
>>>
>>>
>>
>>
>> --
>> Awanthika Senarath
>> Software Engineer, WSO2 Inc.
>> Mobile: +94717681791
>>
>>
>>
>
>
> --
> Awanthika Senarath
> Software Engineer, WSO2 Inc.
> Mobile: +94717681791
>
>
>


-- 
*Melan Nimesh*
Software Engineer;
WSO2 Inc.;  http://wso2.org
E-mail: melan AT wso2.com;
Mobile: +94 77 631 6759
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] using the tag in contextualizing the new option for dec_studio projects

[Melan Nimesh]

Hi,


On Fri, Jul 18, 2014 at 10:57 AM, Awanthika Senarath 
wrote:

> Hi,
>
> Im trying to contextualize the eclipse new project option in
>
>  project (in projectExplorer) -> rightclick -> new -> wso2projects  (CEP
> project/ proxy service etc.)
>
>  to make it more meaningful.
>
> I have been trying with the  tag inside the
>   filtering by project nature
> in plugin.xml with no success.
>

AFAIK, org.eclipse.ui.newWizards extension-point does not supports
visibleWhen or activeWhen attributes. you can use
org.eclipse.ui.navigator.navigatorContent extension point to achieve your
requirements I guess. we are using it in many places inside DevS. please
refer org.wso2.developerstudio.eclipse.artifact.axis2 component's
plugin.xml [1] for a example.

e.g.

 














Thanks,
Melan

[1]
https://github.com/wso2-dev/developer-studio/blob/master/app-server/org.wso2.developerstudio.eclipse.artifact.axis2/plugin.xml



>
> is there anyone who has previous experience in using this tag? OR any
> other way of getting it done? I also tried with the property-tester in
> eclipse.
>
> thanks and regards
> --
> Awanthika Senarath
> Software Engineer, WSO2 Inc.
> Mobile: +94717681791
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Melan Nimesh*
Software Engineer;
WSO2 Inc.;  http://wso2.org
E-mail: melan AT wso2.com;
Mobile: +94 77 631 6759
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Student Introduction, GSoC-2014 project: "UI Testing Framework for Developer Studio"

[Melan Nimesh]

d that each time I run 'mvn clean install' the p2
>>> plugins are redownloaed. But inside the,
>>> .m2/repository/p2/osgi/bundle/org.wso2.developerstudio.eclipse.*.*/3.6.0
>>> nothing is found. But other group ID plugins contains Jar other than
>>> 'org.wso2.developerstudio.eclipse'. And even I add a single dependency the
>>> whole p2 is downloaded (may be due to transitive dependencies). Are these
>>> are normal behaviors?
>>>
>>> Please help. Please leave a hint or clarify what is | may causing |
>>> cause this issue.
>>>
>>> [1] https://github.com/Tharshayene/DevStudioUITestAutomation
>>>
>>> [2] https://github.com/reficio/p2-maven-plugin/issues/10
>>> <https://github.com/reficio/p2-maven-plugin/issues/10>
>>>
>>>
>>> Regards,
>>> Tharshayene Loganathan
>>> Undergraduate,
>>> Dept. of Computer Science & Engineering,
>>> IIT,Sri Lanka.
>>>
>>>
>>>
>>>
>>> On 18 June 2014 01:59, Nila  wrote:
>>>
>>>> SWTBot Kepler build is failing due to hamcrest.org. It's a bug [1]
>>>> [2]  and hope will find a work around sooner (there are other Kepler based
>>>> systems such as EGit still use SWTBot for UI testing).
>>>>
>>>> As the next step I'm trying to integrate Developer Studio dependencies
>>>> so I could test its UI work flows.
>>>>
>>>> Maven build failures occurred during the process.
>>>>
>>>>
>>>> I've tried to place all the pom.xml dependencies from the JIRA project
>>>> but the build failed.
>>>>
>>>> I've tried only to add ESB dependencies but similar error occurred. I'm
>>>> finding it difficult to trace required dependencies and reasons for the
>>>> failures. Thus please help me by suggesting the list of plugins (at least a
>>>> minimal set of plugin to test a single product related cases).
>>>>
>>>> Is it possible to group out minimum plugins that are to be added to the
>>>> pom.xml to test ESB test cases (as a start)?
>>>>
>>>> I've attached both pom.xml files and corresponding build errors. Please
>>>> check them and let me know what I'm missing.
>>>>
>>>> Thanks in advance.
>>>>
>>>>
>>>> [1]
>>>> http://eclipse.1072660.n5.nabble.com/org-junit-4-11-and-backward-compatibility-td159026.html
>>>>
>>>> [2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=405276
>>>>
>>>>
>>>>
>>>>
>>>> Regards,
>>>> Tharshayene Loganathan
>>>> Undergraduate,
>>>> Dept. of Computer Science & Engineering,
>>>> IIT,Sri Lanka.
>>>>
>>>>
>>>>
>>>>
>>>> On 17 June 2014 20:07, Nila  wrote:
>>>>
>>>>> Thanks Melan,
>>>>>
>>>>> I've solved the issue that I've mentioned above by adding org.hamcrest
>>>>> to the Manifest (as Tycho refers to it to resolve certain dependencies).
>>>>> It's a reported buggy behavior of SWTBot [1].
>>>>>
>>>>> Now the Tycho Integration is been successful and the Repository is up
>>>>> to date.
>>>>>
>>>>> Yes, now I need to add Dev Studio bundles and for that I will consider
>>>>> the facts that you've mentioned and refer the Jira [2]. I faced several
>>>>> issues trying to build the Jira project. Then only I decided to try with a
>>>>> minimal pom.xml. Now I'll set the dependencies, build and update by
>>>>> tonight.
>>>>>
>>>>> Thanks.
>>>>>
>>>>> [1] http://permalink.gmane.org/gmane.comp.ide.eclipse.tycho.user/1426
>>>>>
>>>>> [2] https://github.com/Tharshayene/DevStudioUITestAutomation
>>>>>
>>>>> [3] https://wso2.org/jira/browse/TOOLS-1334
>>>>>
>>>>>
>>>>> Regards,
>>>>> Tharshayene Loganathan
>>>>> Undergraduate,
>>>>> Dept. of Computer Science & Engineering,
>>>>> IIT,Sri Lanka.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On 17 June 2014 12:01, Melan Nimesh  wrote:
>>>>>
>>>>>> Hi Nila,
>>>>>>

Re: [Dev] Student Introduction, GSoC-2014 project: "UI Testing Framework for Developer Studio"

[Melan Nimesh]

proposal document.
>>> Lemme know the feedback.
>>>
>>>
>>> Regards,
>>> Tharshayene Loganathan
>>> Undergraduate,
>>> Dept. of Computer Science & Engineering,
>>> IIT,Sri Lanka.
>>>
>>>
>>>
>>>
>>> On 31 May 2014 09:32, Nila  wrote:
>>>
>>> Hi,
>>> As we've already discussed over the phone, I'm preparing my hierarchical
>>> analysis design so far. And I would like to get an overall
>>> mid term evaluation criteria, bench marks,tasks (schedules),objectives
>>> (date by), Also I wish if I can get any reference/samples regarding the
>>> specified module.
>>>
>>>
>>> Regards,
>>> Tharshayene Loganathan
>>> Undergraduate,
>>> Dept. of Computer Science & Engineering,
>>> IIT,Sri Lanka.
>>>
>>>
>>>
>>>
>>> On 23 May 2014 17:32, Nila  wrote:
>>>
>>>
>>
>> --
>> Sent from Gmail Mobile
>>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Melan Nimesh*
Software Engineer;
WSO2 Inc.;  http://wso2.org
E-mail: melan AT wso2.com;
Mobile: +94 77 631 6759
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] cloud-services-desc.xml.erb - why we need this in PPaaS?

[Melan Nimesh]

On Wed, Jun 4, 2014 at 9:49 AM, Nirmal Fernando  wrote:

> I just fixed this issue with init.pp.
>
Thanks Nirmal, I was about to commit the fix


>
>
> On Wed, Jun 4, 2014 at 9:44 AM, Nirmal Fernando  wrote:
>
>> Cool.. +1... Also please fix the IS's init.pp issue.
>> https://github.com/wso2/private-paas/commit/d70b44ef73589b30486aa3072f0812f203d1e218
>>
>>
>> On Wed, Jun 4, 2014 at 9:41 AM, Melan Nimesh  wrote:
>>
>>>
>>>
>>>
>>> On Wed, Jun 4, 2014 at 8:31 AM, Isuru Haththotuwa 
>>> wrote:
>>>
>>>>
>>>> On Wed, Jun 4, 2014 at 8:26 AM, Nirmal Fernando 
>>>> wrote:
>>>>
>>>>> Hi Melan,
>>>>>
>>>>> What's the use of cloud-services-desc.xml ? Can you please give some
>>>>> insight.
>>>>>
>>>> This was from the Stratos 1.6 time period AFAIK. Not sure if this is
>>>> still needed. Will talk with AmilaM regarding this.
>>>>
>>> cloud-services-desc.xml.erb was there from initial commit for IS
>>> templates (I guess it's taken from ESB templates), but it is not included
>>> in init.pp of IS, so I guess we can remove it
>>>
>>>
>>>
>>>>
>>>>> --
>>>>>
>>>>> Thanks & regards,
>>>>> Nirmal
>>>>>
>>>>> Senior Software Engineer- Platform Technologies Team, WSO2 Inc.
>>>>> Mobile: +94715779733
>>>>> Blog: http://nirmalfdo.blogspot.com/
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Thanks and Regards,
>>>>
>>>> Isuru H.
>>>> +94 716 358 048* <http://wso2.com/>*
>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> *Melan Nimesh*
>>> Software Engineer;
>>> WSO2 Inc.;  http://wso2.org
>>> E-mail: melan AT wso2.com;
>>> Mobile: +94 77 631 6759
>>>
>>>
>>
>>
>> --
>>
>> Thanks & regards,
>> Nirmal
>>
>> Senior Software Engineer- Platform Technologies Team, WSO2 Inc.
>> Mobile: +94715779733
>> Blog: http://nirmalfdo.blogspot.com/
>>
>>
>>
>
>
> --
>
> Thanks & regards,
> Nirmal
>
> Senior Software Engineer- Platform Technologies Team, WSO2 Inc.
> Mobile: +94715779733
> Blog: http://nirmalfdo.blogspot.com/
>
>
>


-- 
*Melan Nimesh*
Software Engineer;
WSO2 Inc.;  http://wso2.org
E-mail: melan AT wso2.com;
Mobile: +94 77 631 6759
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += Sohani Weerasinghe

[Melan Nimesh]

Congratulations!


On Fri, May 30, 2014 at 11:17 AM, Aruna Karunarathna  wrote:

> Congratulations...!!!
>
>
> On Fri, May 30, 2014 at 11:14 AM, Susankha Nirmala 
> wrote:
>
>> Congratulations!!!
>>
>>
>>  On Fri, May 30, 2014 at 11:06 AM, Jasintha Dasanayake > > wrote:
>>
>>> Hi All,
>>>
>>> It's my distinct pleasure to welcome Sohani as a WSO2 Committer.
>>>
>>> Sohani has  been a valuable contributor for WSO2 Developer Studio since
>>> she joined WSO2. In recognition of her contributions to WSO2, she has been
>>> voted as a WSO2 Committer.
>>>
>>> Sohani, Congratulations and Keep up the good work!
>>>
>>> Thanks and Regards,
>>> /Jasintha
>>>
>>>
>>> --
>>>
>>> *Jasintha Dasanayake *
>>>
>>> *Senior Software EngineerWSO2 Inc. | http://wso2.com <http://wso2.com/>
>>> lean . enterprise . middleware*
>>>
>>>
>>> *mobile :- 0711368118*
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Susankha Nirmala
>> Software Engineer
>>  WSO2, Inc.: http://wso2.com
>> lean.enterprise.middleware
>> Mobile : +94 77 593 2146
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
>
> * Aruna Sujith Karunarathna* | Software Engineer
> WSO2, Inc | lean. enterprise. middleware.
> #20, Palm Grove, Colombo 03, Sri Lanka
> Mobile: +94 71 9040362 | Work: +94 112145345
> Email: ar...@wso2.com | Web: www.wso2.com
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Melan Nimesh*
Software Engineer;
WSO2 Inc.;  http://wso2.org
E-mail: melan AT wso2.com;
Mobile: +94 77 631 6759
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += Lali Devamanthri

[Melan Nimesh]

Congratulations!


On Fri, May 30, 2014 at 11:17 AM, Nirmal Fernando  wrote:

> Congratulations!
>
>
> On Fri, May 30, 2014 at 11:15 AM, Manoj Kumara  wrote:
>
>> Congratulations !!!
>>
>>
>> *Manoj Kumara*
>> Software Engineer
>> WSO2 Inc. http://wso2.com/
>> *lean.enterprise.middleware*
>> Mobile: +94713448188
>>
>>
>> On Fri, May 30, 2014 at 11:11 AM, Dimuthu De Lanerolle > > wrote:
>>
>>> Congratz ... !!!
>>>
>>>
>>> On Fri, May 30, 2014 at 11:10 AM, Sohani Weerasinghe 
>>> wrote:
>>>
>>>> Congratulations 
>>>>
>>>> Sohani Weerasinghe
>>>> Software Engineer
>>>> WSO2, Inc: http://wso2.com
>>>>
>>>> Mobile  : +94 716439774
>>>> Blog :http://christinetechtips.blogspot.com/
>>>> Twitter  : https://twitter.com/sohanichristine
>>>>
>>>>
>>>> On Fri, May 30, 2014 at 11:08 AM, Jasintha Dasanayake <
>>>> jasin...@wso2.com> wrote:
>>>>
>>>>> Hi All,
>>>>>
>>>>> It's my distinct pleasure to welcome Lali as a WSO2 Committer.
>>>>>
>>>>> Lali has  been a valuable contributor for WSO2 Developer Studio since
>>>>> he joined WSO2. In recognition of his contributions to WSO2, he has been
>>>>> voted as a WSO2 Committer.
>>>>>
>>>>> Lali, Congratulations and Keep up the good work!
>>>>>
>>>>> Thanks and Regards,
>>>>> /Jasintha
>>>>>
>>>>> --
>>>>>
>>>>> *Jasintha Dasanayake *
>>>>>
>>>>> *Senior Software EngineerWSO2 Inc. | http://wso2.com
>>>>> <http://wso2.com/> lean . enterprise . middleware*
>>>>>
>>>>>
>>>>> *mobile :- 0711368118 <0711368118> *
>>>>>
>>>>> ___
>>>>> Dev mailing list
>>>>> Dev@wso2.org
>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>
>>>>>
>>>>
>>>> ___
>>>> Dev mailing list
>>>> Dev@wso2.org
>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>
>>>>
>>>
>>>
>>> --
>>> Dimuthu De Lanerolle
>>> Software Engineer
>>> WSO2 Inc.
>>> lean . enterprise . middlewear.
>>> http://wso2.com/
>>> Tel. : +94 11 2145345  Fax : +94 11 2145300  email : dimut...@wso2.com
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
>
> Thanks & regards,
> Nirmal
>
> Senior Software Engineer- Platform Technologies Team, WSO2 Inc.
> Mobile: +94715779733
> Blog: http://nirmalfdo.blogspot.com/
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Melan Nimesh*
Software Engineer;
WSO2 Inc.;  http://wso2.org
E-mail: melan AT wso2.com;
Mobile: +94 77 631 6759
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Error at SM while tenant is creating

[Melan Nimesh]

 at
> org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:141)
>
> at
> org.wso2.carbon.tomcat.ext.valves.CarbonStuckThreadDetectionValve.invoke(CarbonStuckThreadDetectionValve.java:156)
>
> at
> org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:936)
>
> at
> org.wso2.carbon.tomcat.ext.valves.CarbonContextCreatorValve.invoke(CarbonContextCreatorValve.java:52)
>
> at
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
>
> at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
>
> at
> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1004)
>
> at
> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589)
>
> at
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1653)
>
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
>
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
>
> at java.lang.Thread.run(Thread.java:662)
>
> Caused by: javax.naming.NamingException: This context must be accessed
> through a java: URL
>
> at org.apache.naming.SelectorContext.parseName(SelectorContext.java:751)
>
> at
> org.apache.naming.SelectorContext.createSubcontext(SelectorContext.java:489)
>
> at
> org.wso2.carbon.context.internal.CarbonContextDataHolder$CarbonInitialJNDIContext.getInitialContext(CarbonContextDataHolder.java:900)
>
> ... 51 more
>
> TID: [0] [SCC] [2014-05-13 20:54:52,147]  INFO
> {org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils} -  Loaded tenant
> k.com in 3052 ms {org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils}
>
>
> --
> Dimuthu Leelarathne
> Architect & Product Lead of App Factory
>
> WSO2, Inc. (http://wso2.com)
> email: dimut...@wso2.com
> Mobile : 0773661935
>
> Lean . Enterprise . Middleware
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Melan Nimesh*
Software Engineer;
WSO2 Inc.;  http://wso2.org
E-mail: melan AT wso2.com;
Mobile: +94 77 631 6759
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Private PaaS] Cannot access instances (in tenant mode ) via LB after LB restart

[Melan Nimesh]

This is now fixed!


On Sat, May 10, 2014 at 12:25 AM, Melan Nimesh  wrote:

> Hi,
>
>
> On Fri, May 9, 2014 at 7:10 PM, Nirmal Fernando  wrote:
>
>> Hi Melan,
>>
>> AFAIK there's a complete tenant message too. Isn't LB listens to that at
>> the start-up?
>>
> Yes, there is a listener for CompleteTenantEvent in LB and
> TenantSynzhronizerTask is the publisher for CompleteTenantEvent, I guess
> there's an issue with setting cluster-Id for subscription in
> TenantSynzhronizerTask's code. I did some small changes [1] to that code
> and I will test it
>
>
> [1]
> ---
> a/source/components/org.apache.stratos.manager/src/main/java/org/apache/stratos/manager/publisher/TenantSynzhronizerTask.java
> +++
> b/source/components/org.apache.stratos.manager/src/main/java/org/apache/stratos/manager/publisher/TenantSynzhronizerTask.java
> @@ -75,8 +75,9 @@ public class TenantSynzhronizerTask implements Task {
>  log.debug(String.format("Tenant subscription
> found: [tenant-id] %d [tenant-domain] %s [service] %s",
>  carbonTenant.getId(),
> carbonTenant.getDomain(), cartridgeSubscription.getType()));
>  }
> -Subscription subscription = new
> Subscription(cartridgeSubscription.getType(),
> -new
> HashSet(cartridgeSubscription.getCluster().getId()));
> +HashSet clusterIds = new
> HashSet();
> +
> clusterIds.add(String.valueOf(cartridgeSubscription.getCluster().getId()));
> +Subscription subscription = new
> Subscription(cartridgeSubscription.getType(), clusterIds);
>  for(SubscriptionDomain subscriptionDomain :
> cartridgeSubscription.getSubscriptionDomains()) {
>
> subscription.addSubscriptionDomain(subscriptionDomain.getDomainName(),
> subscriptionDomain.getApplicationContext());
>  }
>
>
>
>>
>>
>> On Fri, May 9, 2014 at 12:07 PM, Melan Nimesh  wrote:
>>
>>> Hi All,
>>>
>>> I noticed the $subject while testing LB for Private PaaS. Any tenant
>>> created and subscribed before restart of LB cannot be access and getting
>>> 404 error *"Active application instances not found"*. This works fine
>>> if existing session found in request (Such as Admin console requests [1])
>>> and any request pass through via 
>>> *requestDelegator.findNextMemberFromHostName().
>>> *I noticed cluster is getting null when calling
>>> LoadBalancerContext.getInstance().getMultiTenantClusterMap().getCluster(hostName,
>>> tenantId) in findNextMemberFromTenantId(). It seems multiTenantClusterMap
>>> not get updated after LB restart. Can we use Complete topology to update
>>> this? what is the best way this fix this?
>>>
>>>
>>> Thanks,
>>> Melan
>>>
>>>
>>> [1]
>>> TID: [0] [LB] [2014-05-09 11:29:43,645] DEBUG
>>> {org.apache.stratos.load.balancer.endpoint.TenantAwareLoadBalanceEndpoint}
>>> -  Existing session found: JSESSIONID=A5E345AEA80006C03F60775E83531DA4
>>> TID: [0] [LB] [2014-05-09 11:29:43,645] DEBUG
>>> {org.apache.stratos.load.balancer.endpoint.TenantAwareLoadBalanceEndpoint}
>>> -  Updating axis2 member port
>>> TID: [0] [LB] [2014-05-09 11:29:43,646] DEBUG
>>> {org.apache.stratos.load.balancer.endpoint.TenantAwareLoadBalanceEndpoint}
>>> -  Outgoing request port found: 9443
>>> TID: [0] [LB] [2014-05-09 11:29:43,646] DEBUG
>>> {org.apache.stratos.load.balancer.endpoint.TenantAwareLoadBalanceEndpoint}
>>> -  Sending request to endpoint:
>>> https://10.144.0.231:9443/t/my.org/carbon/service-mgt/index.jsp?region=region1&item=services_list_menu
>>>
>>>
>>> --
>>> *Melan Nimesh*
>>> Software Engineer;
>>> WSO2 Inc.;  http://wso2.org
>>> E-mail: melan AT wso2.com;
>>> Mobile: +94 77 631 6759
>>>
>>>
>>
>>
>> --
>>
>> Thanks & regards,
>> Nirmal
>>
>> Senior Software Engineer- Platform Technologies Team, WSO2 Inc.
>> Mobile: +94715779733
>> Blog: http://nirmalfdo.blogspot.com/
>>
>>
>>
>
>
> --
> *Melan Nimesh*
> Software Engineer;
> WSO2 Inc.;  http://wso2.org
> E-mail: melan AT wso2.com;
> Mobile: +94 77 631 6759
>
>


-- 
*Melan Nimesh*
Software Engineer;
WSO2 Inc.;  http://wso2.org
E-mail: melan AT wso2.com;
Mobile: +94 77 631 6759
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Private PaaS] Can't Spawn any instances

[Melan Nimesh]

This issue is no longer there in the master branch,  Thanks for the fix

On Sat, May 10, 2014 at 12:06 AM, Melan Nimesh  wrote:

> Hi All,
>
> I noticed the $subject in packs from master branch , I am getting
> following error [1] . Did we made any changes to rule files recenlty?
>
> [1]
>
> TID: [0] [STRATOS] [2014-05-09 23:46:00,093] ERROR
> {org.apache.stratos.autoscaler.monitor.LbClusterMonitor} -  Cluster
> monitor: Monitor failed. LbClusterMonitor [clusterId=lbisuruh.lk.domain,
> serviceId=lb] {org.apache.stratos.autoscaler.monitor.LbClusterMonitor}
> Exception executing consequence for rule "Minimum Rule" in
> org.apache.stratos.autoscaler.rule: [Error: null]
> [Near : {... $delegator.delegateSpawn($ctxt }]
>  ^
> [Line: 1, Column: 1]
> at
> org.drools.runtime.rule.impl.DefaultConsequenceExceptionHandler.handleException(DefaultConsequenceExceptionHandler.java:39)
> at
> org.drools.common.DefaultAgenda.fireActivation(DefaultAgenda.java:1297)
> at
> org.drools.common.DefaultAgenda.fireNextItem(DefaultAgenda.java:1221)
> at
> org.drools.common.DefaultAgenda.fireAllRules(DefaultAgenda.java:1456)
> at
> org.drools.common.AbstractWorkingMemory.fireAllRules(AbstractWorkingMemory.java:710)
> at
> org.drools.common.AbstractWorkingMemory.fireAllRules(AbstractWorkingMemory.java:674)
> at
> org.drools.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:230)
> at
> org.apache.stratos.autoscaler.rule.AutoscalerRuleEvaluator.evaluateMinCheck(AutoscalerRuleEvaluator.java:86)
> at
> org.apache.stratos.autoscaler.monitor.LbClusterMonitor.monitor(LbClusterMonitor.java:91)
> at
> org.apache.stratos.autoscaler.monitor.LbClusterMonitor.run(LbClusterMonitor.java:63)
> at java.lang.Thread.run(Thread.java:744)
> Caused by: [Error: null]
> [Near : {... $delegator.delegateSpawn($ctxt }]
>  ^
> [Line: 1, Column: 1]
> at
> org.mvel2.optimizers.impl.refl.ReflectiveAccessorOptimizer.compileGetChain(ReflectiveAccessorOptimizer.java:435)
> at
> org.mvel2.optimizers.impl.refl.ReflectiveAccessorOptimizer.optimizeAccessor(ReflectiveAccessorOptimizer.java:143)
> at org.mvel2.ast.ASTNode.optimize(ASTNode.java:159)
> at org.mvel2.ast.ASTNode.getReducedValueAccelerated(ASTNode.java:115)
> at org.mvel2.MVELRuntime.execute(MVELRuntime.java:85)
> at
> org.mvel2.compiler.CompiledExpression.getDirectValue(CompiledExpression.java:123)
> at
> org.mvel2.compiler.CompiledExpression.getValue(CompiledExpression.java:119)
> at
> org.mvel2.compiler.CompiledExpression.getValue(CompiledExpression.java:113)
> at org.mvel2.MVEL.executeExpression(MVEL.java:930)
> at
> org.drools.base.mvel.MVELConsequence.evaluate(MVELConsequence.java:104)
> at
> org.drools.common.DefaultAgenda.fireActivation(DefaultAgenda.java:1287)
> ... 9 more
> Caused by: java.lang.IllegalArgumentException
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.mvel2.optimizers.impl.refl.ReflectiveAccessorOptimizer.getMethod(ReflectiveAccessorOptimizer.java:1104)
> at
> org.mvel2.optimizers.impl.refl.ReflectiveAccessorOptimizer.getMethod(ReflectiveAccessorOptimizer.java:987)
> at
> org.mvel2.optimizers.impl.refl.ReflectiveAccessorOptimizer.compileGetChain(ReflectiveAccessorOptimizer.java:377)
> ... 19 more
>
>
> Thanks,
> Melan
>
> --
> *Melan Nimesh*
> Software Engineer;
> WSO2 Inc.;  http://wso2.org
> E-mail: melan AT wso2.com;
> Mobile: +94 77 631 6759
>
>


-- 
*Melan Nimesh*
Software Engineer;
WSO2 Inc.;  http://wso2.org
E-mail: melan AT wso2.com;
Mobile: +94 77 631 6759
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Private PaaS] Cannot access instances (in tenant mode ) via LB after LB restart

[Melan Nimesh]

Hi,


On Fri, May 9, 2014 at 7:10 PM, Nirmal Fernando  wrote:

> Hi Melan,
>
> AFAIK there's a complete tenant message too. Isn't LB listens to that at
> the start-up?
>
Yes, there is a listener for CompleteTenantEvent in LB and
TenantSynzhronizerTask is the publisher for CompleteTenantEvent, I guess
there's an issue with setting cluster-Id for subscription in
TenantSynzhronizerTask's code. I did some small changes [1] to that code
and I will test it


[1]
---
a/source/components/org.apache.stratos.manager/src/main/java/org/apache/stratos/manager/publisher/TenantSynzhronizerTask.java
+++
b/source/components/org.apache.stratos.manager/src/main/java/org/apache/stratos/manager/publisher/TenantSynzhronizerTask.java
@@ -75,8 +75,9 @@ public class TenantSynzhronizerTask implements Task {
 log.debug(String.format("Tenant subscription
found: [tenant-id] %d [tenant-domain] %s [service] %s",
 carbonTenant.getId(),
carbonTenant.getDomain(), cartridgeSubscription.getType()));
 }
-Subscription subscription = new
Subscription(cartridgeSubscription.getType(),
-new
HashSet(cartridgeSubscription.getCluster().getId()));
+HashSet clusterIds = new HashSet();
+
clusterIds.add(String.valueOf(cartridgeSubscription.getCluster().getId()));
+Subscription subscription = new
Subscription(cartridgeSubscription.getType(), clusterIds);
 for(SubscriptionDomain subscriptionDomain :
cartridgeSubscription.getSubscriptionDomains()) {

subscription.addSubscriptionDomain(subscriptionDomain.getDomainName(),
subscriptionDomain.getApplicationContext());
 }



>
>
> On Fri, May 9, 2014 at 12:07 PM, Melan Nimesh  wrote:
>
>> Hi All,
>>
>> I noticed the $subject while testing LB for Private PaaS. Any tenant
>> created and subscribed before restart of LB cannot be access and getting
>> 404 error *"Active application instances not found"*. This works fine if
>> existing session found in request (Such as Admin console requests [1]) and
>> any request pass through via *requestDelegator.findNextMemberFromHostName().
>> *I noticed cluster is getting null when calling
>> LoadBalancerContext.getInstance().getMultiTenantClusterMap().getCluster(hostName,
>> tenantId) in findNextMemberFromTenantId(). It seems multiTenantClusterMap
>> not get updated after LB restart. Can we use Complete topology to update
>> this? what is the best way this fix this?
>>
>>
>> Thanks,
>> Melan
>>
>>
>> [1]
>> TID: [0] [LB] [2014-05-09 11:29:43,645] DEBUG
>> {org.apache.stratos.load.balancer.endpoint.TenantAwareLoadBalanceEndpoint}
>> -  Existing session found: JSESSIONID=A5E345AEA80006C03F60775E83531DA4
>> TID: [0] [LB] [2014-05-09 11:29:43,645] DEBUG
>> {org.apache.stratos.load.balancer.endpoint.TenantAwareLoadBalanceEndpoint}
>> -  Updating axis2 member port
>> TID: [0] [LB] [2014-05-09 11:29:43,646] DEBUG
>> {org.apache.stratos.load.balancer.endpoint.TenantAwareLoadBalanceEndpoint}
>> -  Outgoing request port found: 9443
>> TID: [0] [LB] [2014-05-09 11:29:43,646] DEBUG
>> {org.apache.stratos.load.balancer.endpoint.TenantAwareLoadBalanceEndpoint}
>> -  Sending request to endpoint:
>> https://10.144.0.231:9443/t/my.org/carbon/service-mgt/index.jsp?region=region1&item=services_list_menu
>>
>>
>> --
>> *Melan Nimesh*
>> Software Engineer;
>> WSO2 Inc.;  http://wso2.org
>> E-mail: melan AT wso2.com;
>> Mobile: +94 77 631 6759
>>
>>
>
>
> --
>
> Thanks & regards,
> Nirmal
>
> Senior Software Engineer- Platform Technologies Team, WSO2 Inc.
> Mobile: +94715779733
> Blog: http://nirmalfdo.blogspot.com/
>
>
>


-- 
*Melan Nimesh*
Software Engineer;
WSO2 Inc.;  http://wso2.org
E-mail: melan AT wso2.com;
Mobile: +94 77 631 6759
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Private PaaS] Can't Spawn any instances

[Melan Nimesh]

Hi All,

I noticed the $subject in packs from master branch , I am getting following
error [1] . Did we made any changes to rule files recenlty?

[1]

TID: [0] [STRATOS] [2014-05-09 23:46:00,093] ERROR
{org.apache.stratos.autoscaler.monitor.LbClusterMonitor} -  Cluster
monitor: Monitor failed. LbClusterMonitor [clusterId=lbisuruh.lk.domain,
serviceId=lb] {org.apache.stratos.autoscaler.monitor.LbClusterMonitor}
Exception executing consequence for rule "Minimum Rule" in
org.apache.stratos.autoscaler.rule: [Error: null]
[Near : {... $delegator.delegateSpawn($ctxt }]
 ^
[Line: 1, Column: 1]
at
org.drools.runtime.rule.impl.DefaultConsequenceExceptionHandler.handleException(DefaultConsequenceExceptionHandler.java:39)
at
org.drools.common.DefaultAgenda.fireActivation(DefaultAgenda.java:1297)
at org.drools.common.DefaultAgenda.fireNextItem(DefaultAgenda.java:1221)
at org.drools.common.DefaultAgenda.fireAllRules(DefaultAgenda.java:1456)
at
org.drools.common.AbstractWorkingMemory.fireAllRules(AbstractWorkingMemory.java:710)
at
org.drools.common.AbstractWorkingMemory.fireAllRules(AbstractWorkingMemory.java:674)
at
org.drools.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:230)
at
org.apache.stratos.autoscaler.rule.AutoscalerRuleEvaluator.evaluateMinCheck(AutoscalerRuleEvaluator.java:86)
at
org.apache.stratos.autoscaler.monitor.LbClusterMonitor.monitor(LbClusterMonitor.java:91)
at
org.apache.stratos.autoscaler.monitor.LbClusterMonitor.run(LbClusterMonitor.java:63)
at java.lang.Thread.run(Thread.java:744)
Caused by: [Error: null]
[Near : {... $delegator.delegateSpawn($ctxt }]
 ^
[Line: 1, Column: 1]
at
org.mvel2.optimizers.impl.refl.ReflectiveAccessorOptimizer.compileGetChain(ReflectiveAccessorOptimizer.java:435)
at
org.mvel2.optimizers.impl.refl.ReflectiveAccessorOptimizer.optimizeAccessor(ReflectiveAccessorOptimizer.java:143)
at org.mvel2.ast.ASTNode.optimize(ASTNode.java:159)
at org.mvel2.ast.ASTNode.getReducedValueAccelerated(ASTNode.java:115)
at org.mvel2.MVELRuntime.execute(MVELRuntime.java:85)
at
org.mvel2.compiler.CompiledExpression.getDirectValue(CompiledExpression.java:123)
at
org.mvel2.compiler.CompiledExpression.getValue(CompiledExpression.java:119)
at
org.mvel2.compiler.CompiledExpression.getValue(CompiledExpression.java:113)
at org.mvel2.MVEL.executeExpression(MVEL.java:930)
at
org.drools.base.mvel.MVELConsequence.evaluate(MVELConsequence.java:104)
at
org.drools.common.DefaultAgenda.fireActivation(DefaultAgenda.java:1287)
... 9 more
Caused by: java.lang.IllegalArgumentException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.mvel2.optimizers.impl.refl.ReflectiveAccessorOptimizer.getMethod(ReflectiveAccessorOptimizer.java:1104)
at
org.mvel2.optimizers.impl.refl.ReflectiveAccessorOptimizer.getMethod(ReflectiveAccessorOptimizer.java:987)
at
org.mvel2.optimizers.impl.refl.ReflectiveAccessorOptimizer.compileGetChain(ReflectiveAccessorOptimizer.java:377)
... 19 more


Thanks,
Melan

-- 
*Melan Nimesh*
Software Engineer;
WSO2 Inc.;  http://wso2.org
E-mail: melan AT wso2.com;
Mobile: +94 77 631 6759
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Private PaaS] Cannot access instances (in tenant mode ) via LB after LB restart

[Melan Nimesh]

Hi All,

I noticed the $subject while testing LB for Private PaaS. Any tenant
created and subscribed before restart of LB cannot be access and getting
404 error *"Active application instances not found"*. This works fine if
existing session found in request (Such as Admin console requests [1]) and
any request pass through via *requestDelegator.findNextMemberFromHostName().
*I noticed cluster is getting null when calling
LoadBalancerContext.getInstance().getMultiTenantClusterMap().getCluster(hostName,
tenantId) in findNextMemberFromTenantId(). It seems multiTenantClusterMap
not get updated after LB restart. Can we use Complete topology to update
this? what is the best way this fix this?


Thanks,
Melan


[1]
TID: [0] [LB] [2014-05-09 11:29:43,645] DEBUG
{org.apache.stratos.load.balancer.endpoint.TenantAwareLoadBalanceEndpoint}
-  Existing session found: JSESSIONID=A5E345AEA80006C03F60775E83531DA4
TID: [0] [LB] [2014-05-09 11:29:43,645] DEBUG
{org.apache.stratos.load.balancer.endpoint.TenantAwareLoadBalanceEndpoint}
-  Updating axis2 member port
TID: [0] [LB] [2014-05-09 11:29:43,646] DEBUG
{org.apache.stratos.load.balancer.endpoint.TenantAwareLoadBalanceEndpoint}
-  Outgoing request port found: 9443
TID: [0] [LB] [2014-05-09 11:29:43,646] DEBUG
{org.apache.stratos.load.balancer.endpoint.TenantAwareLoadBalanceEndpoint}
-  Sending request to endpoint:
https://10.144.0.231:9443/t/my.org/carbon/service-mgt/index.jsp?region=region1&item=services_list_menu


-- 
*Melan Nimesh*
Software Engineer;
WSO2 Inc.;  http://wso2.org
E-mail: melan AT wso2.com;
Mobile: +94 77 631 6759




-- 
*Melan Nimesh*
Software Engineer;
WSO2 Inc.;  http://wso2.org
E-mail: melan AT wso2.com;
Mobile: +94 77 631 6759
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Data-mapper] Maintain an avro schema object model

[Melan Nimesh]

On Fri, Apr 18, 2014 at 12:20 PM, Susinda Perera  wrote:

>
>
>
> On Thu, Apr 17, 2014 at 6:23 PM, Gayan Yalpathwala wrote:
>
>> Hi Jasintha,
>>
>>
>> On Thu, Apr 17, 2014 at 6:11 PM, Jasintha Dasanayake 
>> wrote:
>>
>>>
>>> Please have a look in the ESB graphical editor, there we have maintained
>>> the synapse model for a particular mediator, similarly you have to maintain
>>> the Avro schema model here
>>>
>>
>> I have referred TaskTransformer class where it transforms the ecore model
>> to respective synapse model during serialization time. IMO, We can use a
>> similar approach to transform the ecore model to respective avro model when
>> saving the diagram. WDYT?
>>
>>>
>>> Thanks
>>> /Jasintha
>>>
>>>
>>> On Thu, Apr 17, 2014 at 6:05 PM, Lali Devamanthri  wrote:
>>>
>>>> Hi GayanK,
>>>>
>>>>
>>>> On Thu, Apr 17, 2014 at 4:27 PM, Gayan Yalpathwala wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> I am in the process of implementing the tool to build input and output
>>>>> schema of data-mapper visual editor. Here I need to maintain an object
>>>>> model of type "org.apache.avro.Schema" where it should be accessible by an
>>>>> array of action classes which reside in
>>>>> org.wso2.developerstudio.visualdatamapper.diagram package. This model
>>>>> should reflect input and ouptut avro schemas and should be modified by
>>>>> above different action classes. Would it be a better idea to maintain a
>>>>> variable of the above type, local to "DataMapperMultiPageEditor" for this
>>>>> purpose?
>>>>>
>>>>
>>>> No, DataMapperMultiPageEditor is for handle switching between graphical
>>>> editor and source editor in data mapper project. Considering your
>>>> requirements, its not a good idea to use DataMapperMultiPageEditor class
>>>> for keeping object model.
>>>>
>>> Agree with Lali, But i think you can keep that variable within
> Datamapper graphical editor i guess, since IMO that is the best place to
> keep this which suits for the mentioned requirement. You can probably
> implement some interface in Datamapper graphical editor and access the
> required functionalities via the interface members.
>

Better way of serializing EMF model to a domain specific model would be
implement custom resource [1] for your EMF model and do your serialization
inside it. Technically EMF can holds any structured data model you want, by
default EMF uses XMI (XML Metadata Interchange) for serialization, so you
can use avro schema object model instead of XMI

Thanks,
Melan

[1] org.eclipse.emf.ecore.resource.Resource



>
>
>>>> Thanks,
>>>> Lali
>>>>
>>>>>
>>>>> Thanks,
>>>>>
>>>>> --
>>>>> *Gayan Kaushalya Yalpathwala*
>>>>>  Software Engineer
>>>>> WSO2 Inc.; http://wso2.com
>>>>> lean.enterprise.middleware
>>>>>
>>>>> mobile: +94 71 8682704 <http://asia14.wso2con.com/>
>>>>>
>>>>>  <http://asia14.wso2con.com/>
>>>>>
>>>>> ___
>>>>> Dev mailing list
>>>>> Dev@wso2.org
>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> *Lali Sudaththa Devamanthri*
>>>> Software Engineer
>>>> WSO2 Inc.; http://wso2.com
>>>> lean.enterprise.middleware
>>>>
>>>> mobile: +94 71 895 4922
>>>>  <http://www.wso2.com>
>>>>
>>>> ___
>>>> Dev mailing list
>>>> Dev@wso2.org
>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>
>>>>
>>>
>>>
>>> --
>>>
>>> *Jasintha Dasanayake *
>>>
>>>
>>> *Software EngineerWSO2 Inc. | http://wso2.com <http://wso2.com/> lean .
>>> enterprise . middleware*
>>>
>>>
>>> *mobile :- 0711368118*
>>>
>>
>>
>> Thanks,
>>
>> --
>> *Gayan Kaushalya Yalpathwala*
>>  Software Engineer
>> WSO2 Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> mobile: +94 71 8682704 <http://asia14.wso2con.com/>
>>
>>  <http://asia14.wso2con.com/>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Susinda Perera*
> Software Engineer
> Mobile:(+94)716049075
>
> WSO2 Inc. http://wso2.com/
> Tel : 94 11 214 5345 Fax :94 11 2145300
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Melan Nimesh*
Software Engineer;
WSO2 Inc.;  http://wso2.org
E-mail: melan AT wso2.com;
Mobile: +94 77 631 6759
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += GayanK

[Melan Nimesh]

;
>>>>>>>>
>>>>>>>> ___
>>>>>>>> Dev mailing list
>>>>>>>> Dev@wso2.org
>>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> *Asanka Sanjeewa*
>>>>>>> Senior Software Engineer
>>>>>>> Mobile: +94772532924
>>>>>>> WSO2 Inc. http://wso2.com/
>>>>>>> Blog: http://asanka-tech-blog.blogspot.com/
>>>>>>>
>>>>>>>
>>>>>>> ___
>>>>>>> Dev mailing list
>>>>>>> Dev@wso2.org
>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Isuruwan Herath
>>>>>> Technical Lead
>>>>>>
>>>>>> Contact: +94 776 273 296
>>>>>>
>>>>>> ___
>>>>>> Dev mailing list
>>>>>> Dev@wso2.org
>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> *Susinda Perera*
>>>>> Software Engineer
>>>>> Mobile:(+94)716049075
>>>>>
>>>>> WSO2 Inc. http://wso2.com/
>>>>> Tel : 94 11 214 5345 Fax :94 11 2145300
>>>>>
>>>>>
>>>>> ___
>>>>> Dev mailing list
>>>>> Dev@wso2.org
>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Susankha Nirmala
>>>> Software Engineer
>>>> WSO2, Inc.: http://wso2.com
>>>> lean.enterprise.middleware
>>>> Mobile : +94 77 593 2146
>>>>
>>>> ___
>>>> Dev mailing list
>>>> Dev@wso2.org
>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>
>>>>
>>>
>>>
>>> --
>>> *Malintha Adikari*
>>>  Software Engineer
>>> WSO2 Inc.; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> Mobile: +94 71 2312958
>>> Blog:http://malinthas.blogspot.com
>>> Page:   http://about.me/malintha
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Dilini Muthumala*
>> Software Engineer,
>> WSO2 Inc.
>>
>>  *E-mail :* dil...@wso2.com
>> *Mobile: *+94713 400 029
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Thanks and Regards
> *, Shani Ranasinghe*
>
> Software Engineer
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: +94 77 2273555
> linked in: lk.linkedin.com/pub/shani-ranasinghe/34/111/ab
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Melan Nimesh*
Software Engineer;
WSO2 Inc.;  http://wso2.org
E-mail: melan AT wso2.com;
Mobile: +94 77 631 6759
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] JFace dialog does not show on top

[Melan Nimesh]

Hi,


On Mon, Apr 7, 2014 at 11:33 AM, Gayan Yalpathwala  wrote:

> Hi,
>
> I have embedded a JFace dialog for some datamapper related functionality.
> This is a basic dialog that extends org.eclipse.jface.dialogs.Dialog and it
> fails to show on top when default shell is passed as the parent [1]. This
> way, the dialog opens fine but hides behind the eclipse window. I have
> tried options [2] and [3] as well where option [2] does not work either and
> [3] works with a known bug [4]. Have anyone come up with a workaround for
> this?
>
> [1]
> Shell shell = new Shell(Display.getDefault());
> DataMapperConfigurationDialog dataMapperConfigurationDialog = new
> DataMapperConfigurationDialog(shell);
> dataMapperConfigurationDialog.create();
>

try with active shell rather than creating a new shell

eg.

Display.getCurrent().getActiveShell() or
PlatformUI.getWorkbench().getActiveWorkbenchWindow().getShell();


Thanks,
Melan


>
> [2] dataMapperConfigurationDialog.getShell().forceActive();
>
> [3]
> public DataMapperConfigurationDialog(Shell parentShell) {
> super(parentShell);
>  setShellStyle(SWT.ON_TOP | SWT.CLOSE | SWT.TITLE | SWT.BORDER | SWT.OK |
> SWT.APPLICATION_MODAL);
> }
>
> [4] https://bugs.eclipse.org/bugs/show_bug.cgi?id=410810
>
> Thanks,
>
>
> --
> *Gayan Kaushalya Yalpathwala*
>  Software Engineer
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: +94 71 8682704 <http://asia14.wso2con.com/>
>
>  <http://asia14.wso2con.com/>
>
> _______
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Melan Nimesh*
Software Engineer;
WSO2 Inc.;  http://wso2.org
E-mail: melan AT wso2.com;
Mobile: +94 77 631 6759
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Representing Nillables in Avro Schema

[Melan Nimesh]

Hi,


On Thu, Apr 3, 2014 at 6:05 AM, Jasintha Dasanayake wrote:

>
>
>
> On Wed, Apr 2, 2014 at 11:35 PM, Sohani Weerasinghe wrote:
>
>> Hi,
>>
>> If I want to create an Avro Schema from XML or XSD which contains
>> nillable value as shown below how can I represent it in the Avro Schema ?
>>
>> xml :  
>>
>> xsd : 
>>
>> In Avro Schema we can have unions (optional fields) as shown below.
>>
>> {"name": "result", "type": ["int", "null"]} which means  result can be
>> either an int or null.
>>
>
> This says , ["int", "null"] declares a schema which may be either a int or
> null,
> /Jasintha
>

AFAIK, there is no nillable or optional kind of specifier in Avro, using
'unions' is only possible way, I don't see this as an issue since you may
handle this in avro serialization / de-serialization level.


Thanks,
Melan


>
>
>
>>
>> Since this is not the way of representing nillables, Can someone provide
>> a solution to represent nillables in Avro Schema.
>>
>>
>> Thanks,
>> Sohani
>>
>> Sohani Weerasinghe
>> Software Engineer
>> WSO2, Inc: http://wso2.com
>>
>> Mobile  : +94 716439774
>> Blog :http://christinetechtips.blogspot.com/
>> Twitter  : https://twitter.com/sohanichristine
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
>
> *Jasintha Dasanayake *
>
> *Software EngineerWSO2 Inc. | http://wso2.com <http://wso2.com/> lean .
> enterprise . middleware*
>
>
> *mobile :- 0711368118*
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Melan Nimesh*
Software Engineer;
WSO2 Inc.;  http://wso2.org
E-mail: melan AT wso2.com;
Mobile: +94 77 631 6759
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Please merge Developer Studio #8 pull request

[Melan Nimesh]

Hi Jasintha,

Please merge the following pull request.

https://github.com/wso2-dev/developer-studio/pull/8

Related jira

https://wso2.org/jira/browse/TOOLS-2389


Thanks,
Melan

-- 
*Melan Nimesh*
Software Engineer;
WSO2 Inc.;  http://wso2.org
E-mail: melan AT wso2.com;
Mobile: +94 77 631 6759
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Please merge Developer Studio #6 pull request

[Melan Nimesh]

Hi Jasintha,

Please merge the following pull request.

https://github.com/wso2-dev/developer-studio/pull/6

Related jira

https://wso2.org/jira/browse/TOOLS-2384


Thanks,
Melan

-- 
*Melan Nimesh*
Software Engineer;
WSO2 Inc.;  http://wso2.org
E-mail: melan AT wso2.com;
Mobile: +94 77 631 6759
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Getting OperationNotSupportedException when creating the initial context for tenants

[Melan Nimesh]

nvoke(CarbonContextCreatorValve.java:52)
 at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
 at
org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1004)
at
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589)
 at
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1653)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
 at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Caused by: javax.naming.NamingException: This context must be accessed
through a java: URL
at org.apache.naming.SelectorContext.parseName(SelectorContext.java:751)
 at
org.apache.naming.SelectorContext.createSubcontext(SelectorContext.java:489)
at
org.wso2.carbon.context.internal.CarbonContextDataHolder$CarbonInitialJNDIContext.getInitialContext(CarbonContextDataHolder.java:865)
 ... 52 more


On Mon, Jan 27, 2014 at 2:23 PM, Kishanthan Thangarajah  wrote:

> May I know the reason on why do we need to set this property in tenant
> mode?
>
>
>
> On Mon, Jan 27, 2014 at 1:42 PM, Ishara Premadasa  wrote:
>
>> Hi Melan,
>>
>> IIRC we came through a similar issue when testing WSO2 MB 2.1.0 in tenant
>> mode as reported in [1].  The fix suggested by Ajanthan should work in here.
>>
>> [1] https://wso2.org/jira/browse/MB-283
>>
>> Thanks!
>>
>>
>> On Mon, Jan 27, 2014 at 1:26 PM, Ajanthan Balachandran > > wrote:
>>
>>> Hi Melan ,
>>> Can you set "org.wso2.carbon.context.RequestBaseContext" property in
>>> the jndi environment properties  to  get InitialContext.?
>>>
>>> E.g :-
>>>
>>> environment = new Hashtable();
>>> 
>>> 
>>> environment.put(CarbonConstants.REQUEST_BASE_CONTEXT, "true");
>>> context = new InitialDirContext(environment);
>>>
>>> Thanks.
>>>
>>> On Fri, Jan 24, 2014 at 9:33 PM, Isuru Haththotuwa 
>>> wrote:
>>> > [looping in dev list]
>>> >
>>> >
>>> > On Fri, Jan 24, 2014 at 7:04 PM, Melan Nimesh  wrote:
>>> >>
>>> >> Hi,
>>> >>
>>> >> We noticed the error mentioned in $subject when creating tenants on
>>> >> Stratos manager (Carbon 4.2 based),  Any idea why this error
>>> occurring?
>>> >>
>>> >> TID: [0] [SCC] [2014-01-24 13:03:06,436] ERROR
>>> >> {org.apache.stratos.messaging.broker.publish.TopicPublisher} -  Error
>>> while
>>> >> publishing to the topic: tenant
>>> >> {org.apache.stratos.messaging.broker.publish.TopicPublisher}
>>> >> java.lang.RuntimeException: An error occurred while creating the
>>> initial
>>> >> context for tenant: 4
>>> >> at
>>> >>
>>> org.wso2.carbon.context.internal.CarbonContextDataHolder$CarbonInitialJNDIContext.getInitialContext(CarbonContextDataHolder.java:873)
>>> >> at
>>> >>
>>> org.wso2.carbon.context.internal.CarbonContextDataHolder$CarbonInitialJNDIContext.lookup(CarbonContextDataHolder.java:916)
>>> >> at javax.naming.InitialContext.lookup(InitialContext.java:392)
>>> >> at
>>> >>
>>> org.apache.stratos.messaging.broker.connect.TopicConnector.init(TopicConnector.java:60)
>>> >> at
>>> >>
>>> org.apache.stratos.messaging.broker.publish.TopicPublisher.setPublisher(TopicPublisher.java:120)
>>> >> at
>>> >>
>>> org.apache.stratos.messaging.broker.publish.TopicPublisher.doPublish(TopicPublisher.java:95)
>>> >> at
>>> >>
>>> org.apache.stratos.messaging.broker.publish.TopicPublisher.publish(TopicPublisher.java:75)
>>> >> at
>>> >>
>>> org.apache.stratos.messaging.broker.publish.EventPublisher.publish(EventPublisher.java:48)
>>> >> at
>>> >>
>>> org.apache.stratos.manager.subscription.utils.CartridgeSubscriptionUtils.publishTenantSubscribedEvent(CartridgeSubscriptionUtils.java:117)
>>> >> at
>>> >>
>>> org.apache.stratos.manager.manager.CartridgeSubscriptionManager.subscribeToCartridgeWithProperties(CartridgeSubscriptionManager.java:230)
>>> >> at
>>> >>
>>> org.apache.stratos.rest.endpoint.services.ServiceUtils.subscribe(ServiceUtils.java:645)

[Dev] Getting OperationNotSupportedException when creating the initial context for tenants

[Melan Nimesh]

(StandardEngineValve.java:118)
 at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
at
org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1004)
 at
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589)
at
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1653)
 at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
 at java.lang.Thread.run(Thread.java:662)
Caused by: javax.naming.OperationNotSupportedException
at
org.wso2.andes.jndi.ReadOnlyContext.createSubcontext(ReadOnlyContext.java:417)
 at
org.wso2.carbon.context.internal.CarbonContextDataHolder$CarbonInitialJNDIContext.getInitialContext(CarbonContextDataHolder.java:865)
... 55 more

Thanks,
Melan


-- 
*Melan Nimesh*
Software Engineer;
WSO2 Inc.;  http://wso2.org
E-mail: melan AT wso2.com;
Mobile: +94 77 631 6759
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Can we compile DevS with maven3?

[Melan Nimesh]

Hi,

On Tue, Jul 30, 2013 at 8:40 AM, Melan Nimesh  wrote:

> Hi,
>
> We are currently using tycho-maven-plugin version 0.17.0 and seems it's
> not compatible with maven 3.1.0, I have updated tycho-maven-plugin
> to 0.18.1 locally and trigger a build, I will commit the fix, if it
> is success.
>

Updated tycho-version to 0.18.1 with r179305. Now DevS build compatible
with maven 3.1.0.

Thanks,
Melan


>
> Thanks,
> Melan
>
> On Tue, Jul 30, 2013 at 6:05 AM, Samisa Abeysinghe wrote:
>
>> Yes, I am using mvn 3.1.0
>>
>>
>> On Mon, Jul 29, 2013 at 9:39 PM, Mohanadarshan Vivekanandalingam <
>> mo...@wso2.com> wrote:
>>
>>> Hi,
>>>
>>> There are some compatibility issues with the maven 3.1.0 which released
>>> on July... We have mentioned regarding this, in the following Dev mail
>>> thread
>>> "[Dev] Build Failure - kernal/trunk/core/org.wso2.carbon.registry.api"
>>>
>>> It is a known compatibility issue with the "Sonatype Aether"
>>>
>>> Regards,
>>> Mohan
>>>
>>>
>>> On Mon, Jul 29, 2013 at 7:09 PM, Samisa Abeysinghe wrote:
>>>
>>>> I get the following error:
>>>>
>>>> Exception in thread "main" java.lang.NoSuchMethodError:
>>>> org.apache.maven.execution.MavenSession.getRepositorySession()Lorg/sonatype/aether/RepositorySystemSession;
>>>>  at
>>>> org.eclipse.tycho.core.maven.utils.PluginRealmHelper.execute(PluginRealmHelper.java:92)
>>>> at
>>>> org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.getDependencyMetadata(P2TargetPlatformResolver.java:144)
>>>>  at
>>>> org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.setupProjects(P2TargetPlatformResolver.java:126)
>>>> at
>>>> org.eclipse.tycho.core.resolver.DefaultTychoDependencyResolver.setupProject(DefaultTychoDependencyResolver.java:87)
>>>>  at
>>>> org.eclipse.tycho.core.maven.TychoMavenLifecycleParticipant.afterProjectsRead(TychoMavenLifecycleParticipant.java:77)
>>>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:272)
>>>>  at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:153)
>>>> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:555)
>>>>  at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
>>>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
>>>>  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>> at
>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>>>  at
>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>> at java.lang.reflect.Method.invoke(Method.java:606)
>>>>  at
>>>> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
>>>> at
>>>> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
>>>>  at
>>>> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:414)
>>>> at
>>>> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:357)
>>>>
>>>>
>>>>
>>>> On Mon, Jul 29, 2013 at 5:46 PM, Viraj Rajaguru  wrote:
>>>>
>>>>> Yes. We use maven 3 for building DevS.
>>>>>
>>>>>
>>>>> Thanks,
>>>>> Viraj.
>>>>>
>>>>>
>>>>> On Mon, Jul 29, 2013 at 5:33 PM, Samisa Abeysinghe wrote:
>>>>>
>>>>>> $subject?
>>>>>>
>>>>>> --
>>>>>>
>>>>>> Thanks,
>>>>>> Samisa...
>>>>>>
>>>>>> Samisa Abeysinghe
>>>>>> VP Engineering
>>>>>> WSO2 Inc.
>>>>>> http://wso2.com
>>>>>> http://wso2.org
>>>>>>
>>>>>> ___
>>>>>> Dev mailing list
>>>>>> Dev@wso2.org
>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Viraj Rajaguru
>>>>> Software Engineer
>>>>> WSO2 Inc. : http://wso2.com
>>>>>
>>>>> Mobile: +94 77 3683068
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> Thanks,
>>>> Samisa...
>>>>
>>>> Samisa Abeysinghe
>>>> VP Engineering
>>>> WSO2 Inc.
>>>> http://wso2.com
>>>> http://wso2.org
>>>>
>>>> ___
>>>> Dev mailing list
>>>> Dev@wso2.org
>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>
>>>>
>>>
>>>
>>> --
>>> *V. Mohanadarshan*
>>> *Software Engineer,*
>>> *Data Technologies Team,*
>>> *WSO2, Inc. http://wso2.com *
>>> *lean.enterprise.middleware.*
>>> *
>>> *
>>> email: mo...@wso2.com
>>> phone:(+94) 771117673
>>>
>>
>>
>>
>> --
>>
>> Thanks,
>> Samisa...
>>
>> Samisa Abeysinghe
>> VP Engineering
>> WSO2 Inc.
>> http://wso2.com
>> http://wso2.org
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Melan Nimesh Jayasingha
> Software Engineer;
> WSO2 Inc.
> m:  77 631 6759
> PGP: 0x7B42450A
>
>


-- 
Melan Nimesh Jayasingha
Software Engineer;
WSO2 Inc.
m:  77 631 6759
PGP: 0x7B42450A
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Can we compile DevS with maven3?

[Melan Nimesh]

Hi,

We are currently using tycho-maven-plugin version 0.17.0 and seems it's
not compatible with maven 3.1.0, I have updated tycho-maven-plugin
to 0.18.1 locally and trigger a build, I will commit the fix, if it
is success.

Thanks,
Melan

On Tue, Jul 30, 2013 at 6:05 AM, Samisa Abeysinghe  wrote:

> Yes, I am using mvn 3.1.0
>
>
> On Mon, Jul 29, 2013 at 9:39 PM, Mohanadarshan Vivekanandalingam <
> mo...@wso2.com> wrote:
>
>> Hi,
>>
>> There are some compatibility issues with the maven 3.1.0 which released
>> on July... We have mentioned regarding this, in the following Dev mail
>> thread
>> "[Dev] Build Failure - kernal/trunk/core/org.wso2.carbon.registry.api"
>>
>> It is a known compatibility issue with the "Sonatype Aether"
>>
>> Regards,
>> Mohan
>>
>>
>> On Mon, Jul 29, 2013 at 7:09 PM, Samisa Abeysinghe wrote:
>>
>>> I get the following error:
>>>
>>> Exception in thread "main" java.lang.NoSuchMethodError:
>>> org.apache.maven.execution.MavenSession.getRepositorySession()Lorg/sonatype/aether/RepositorySystemSession;
>>>  at
>>> org.eclipse.tycho.core.maven.utils.PluginRealmHelper.execute(PluginRealmHelper.java:92)
>>> at
>>> org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.getDependencyMetadata(P2TargetPlatformResolver.java:144)
>>>  at
>>> org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.setupProjects(P2TargetPlatformResolver.java:126)
>>> at
>>> org.eclipse.tycho.core.resolver.DefaultTychoDependencyResolver.setupProject(DefaultTychoDependencyResolver.java:87)
>>>  at
>>> org.eclipse.tycho.core.maven.TychoMavenLifecycleParticipant.afterProjectsRead(TychoMavenLifecycleParticipant.java:77)
>>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:272)
>>>  at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:153)
>>> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:555)
>>>  at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
>>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
>>>  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> at
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>>  at
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>> at java.lang.reflect.Method.invoke(Method.java:606)
>>>  at
>>> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
>>> at
>>> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
>>>  at
>>> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:414)
>>> at
>>> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:357)
>>>
>>>
>>>
>>> On Mon, Jul 29, 2013 at 5:46 PM, Viraj Rajaguru  wrote:
>>>
>>>> Yes. We use maven 3 for building DevS.
>>>>
>>>>
>>>> Thanks,
>>>> Viraj.
>>>>
>>>>
>>>> On Mon, Jul 29, 2013 at 5:33 PM, Samisa Abeysinghe wrote:
>>>>
>>>>> $subject?
>>>>>
>>>>> --
>>>>>
>>>>> Thanks,
>>>>> Samisa...
>>>>>
>>>>> Samisa Abeysinghe
>>>>> VP Engineering
>>>>> WSO2 Inc.
>>>>> http://wso2.com
>>>>> http://wso2.org
>>>>>
>>>>> ___
>>>>> Dev mailing list
>>>>> Dev@wso2.org
>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Viraj Rajaguru
>>>> Software Engineer
>>>> WSO2 Inc. : http://wso2.com
>>>>
>>>> Mobile: +94 77 3683068
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>>
>>> Thanks,
>>> Samisa...
>>>
>>> Samisa Abeysinghe
>>> VP Engineering
>>> WSO2 Inc.
>>> http://wso2.com
>>> http://wso2.org
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *V. Mohanadarshan*
>> *Software Engineer,*
>> *Data Technologies Team,*
>> *WSO2, Inc. http://wso2.com *
>> *lean.enterprise.middleware.*
>> *
>> *
>> email: mo...@wso2.com
>> phone:(+94) 771117673
>>
>
>
>
> --
>
> Thanks,
> Samisa...
>
> Samisa Abeysinghe
> VP Engineering
> WSO2 Inc.
> http://wso2.com
> http://wso2.org
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Melan Nimesh Jayasingha
Software Engineer;
WSO2 Inc.
m:  77 631 6759
PGP: 0x7B42450A
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Can we compile DevS with maven3?

[Melan Nimesh]

Hi,

Are you using Maven 3.1.0 ? if so, we have not build DevS with maven 3.1.0
yet, but It should work with a clean repo

Thanks,
Melan

On Mon, Jul 29, 2013 at 7:09 PM, Samisa Abeysinghe  wrote:

> I get the following error:
>
> Exception in thread "main" java.lang.NoSuchMethodError:
> org.apache.maven.execution.MavenSession.getRepositorySession()Lorg/sonatype/aether/RepositorySystemSession;
>  at
> org.eclipse.tycho.core.maven.utils.PluginRealmHelper.execute(PluginRealmHelper.java:92)
> at
> org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.getDependencyMetadata(P2TargetPlatformResolver.java:144)
>  at
> org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.setupProjects(P2TargetPlatformResolver.java:126)
> at
> org.eclipse.tycho.core.resolver.DefaultTychoDependencyResolver.setupProject(DefaultTychoDependencyResolver.java:87)
>  at
> org.eclipse.tycho.core.maven.TychoMavenLifecycleParticipant.afterProjectsRead(TychoMavenLifecycleParticipant.java:77)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:272)
>  at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:153)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:555)
>  at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
>  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>  at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
>  at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
>  at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:414)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:357)
>
>
>
> On Mon, Jul 29, 2013 at 5:46 PM, Viraj Rajaguru  wrote:
>
>> Yes. We use maven 3 for building DevS.
>>
>>
>> Thanks,
>> Viraj.
>>
>>
>> On Mon, Jul 29, 2013 at 5:33 PM, Samisa Abeysinghe wrote:
>>
>>> $subject?
>>>
>>> --
>>>
>>> Thanks,
>>> Samisa...
>>>
>>> Samisa Abeysinghe
>>> VP Engineering
>>> WSO2 Inc.
>>> http://wso2.com
>>> http://wso2.org
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Viraj Rajaguru
>> Software Engineer
>> WSO2 Inc. : http://wso2.com
>>
>> Mobile: +94 77 3683068
>>
>>
>>
>>
>
>
> --
>
> Thanks,
> Samisa...
>
> Samisa Abeysinghe
> VP Engineering
> WSO2 Inc.
> http://wso2.com
> http://wso2.org
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Melan Nimesh Jayasingha
Software Engineer;
WSO2 Inc.
m:  77 631 6759
PGP: 0x7B42450A
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] ESB 4.7.0 Scheduled Tasks

[Melan Nimesh]

Hi,

On Thu, Jul 18, 2013 at 2:41 PM, Isuru Udana  wrote:

> Hi Susinda,
>
> In ESB 4.7.0 for Scheduled tasks what we improved is specific to
> MessageInjector which is an implementation of a Schedules task.
> So only MessageInjector specific task properties are introduced in 4.7.0.
>
> What we have in DevStudio is a generic interface for all the
> TaskImplementations.
> In ESB management console also we have a common interface for all task
> implementations.
> In the management console when we define the task implementation and click
> on 'load properties' we list out the available configuration parameters.
> What we are missing in DevStudio is that feature.
>

To provide that feature, I think we have to deal with run-time object
of given task implementation to retrieve properties. It might works for
default task implementations, what about if is a custom
task implementation, which is not available to
Developer studio classpath/runtime. WDYT?

Thanks,
Melan


> Wiki[1] is up to date with all the configuration parameters.
>
> [1] http://docs.wso2.org/wiki/display/ESB470/Adding+and+Scheduling+Tasks
>
> Thanks
>
>
> On Thu, Jul 18, 2013 at 2:19 PM, Susinda Perera  wrote:
>
>> Adding Miyuru and Melan
>>
>>
>> On Thu, Jul 18, 2013 at 12:34 PM, Susinda Perera wrote:
>>
>>> Hi ESB Team
>>>
>>> I'm going to work on $subject in DevStudio. Seems like following
>>> properties be the only properties supported by $subject.  However the
>>> library article @ [1] has used some other properties.
>>> My question is 1. Are these the only properties supported by $subject,
>>> 2. is it ok to implement with only a delete button (Current DevS UI
>>> supports both add and delete )
>>>
>>>
>>> [1] - http://wso2.com/library/2900
>>>
>>>
>>>
>>> rdgs
>>> Susinda
>>>
>>> --
>>> *Susinda Perera*
>>> Software Engineer
>>> Mobile:(+94)716049075
>>>
>>> WSO2 Inc. http://wso2.com/
>>>
>>
>>
>>
>> --
>> *Susinda Perera*
>> Software Engineer
>> Mobile:(+94)716049075
>>
>> WSO2 Inc. http://wso2.com/
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Isuru Udana*
> *
>  *
> Senior *
> Software Engineer
> *
> WSO2 Inc.; http://wso2.com
> email: isu...@wso2.com cell: +94 77 3791887
> blog: http://mytecheye.blogspot.com/
> twitter: http://twitter.com/isudana
>



-- 
Melan Nimesh Jayasingha
Software Engineer;
WSO2 Inc.
m:  77 631 6759
PGP: 0x7B42450A
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Upgrading Synapse dependencies in Developer Studio

[Melan Nimesh]

On Fri, Jul 12, 2013 at 2:30 PM, Melan Nimesh  wrote:

>
>
> On Fri, Jul 12, 2013 at 1:33 PM, Viraj Rajaguru  wrote:
>
>> Hi,
>>
>>
>> On Fri, Jul 12, 2013 at 12:30 PM, Harshana Martin wrote:
>>
>>> Hi Viraj,
>>>
>>> Upgrading Synapse dependencies alone will not work since they might have
>>> dependencies to other core dependencies such as Axiom, Axis2, etc.
>>>
>>> So if you are upgrading the versions, you need to check their
>>> dependencies which are used in our codebase and upgrade them as well.
>>>
>>> Yes. We are upgrading those dependencies as well.
>>
>
> Please refactor
> "org.wso2.developerstudio.libraries.libraryprovider" extension-point and
> use that extension-point to include dependencies to other projects
> with hard-coding there jar file names
>

Sorry about the typos, I meant to say * without hard-coding their jar file
names



>
> e.g. we can define following configuration
>
>identifier="synapse-core"
> categoryId="org.wso2.developerstudio.eclipse.libraries.category.esb"
>   />
>
>  and introduce a method to add particular jar using it's identifier as
> a parameter
>
> Thanks,
> Melan
>
>
>>
>>
>>> Please have a look how we did the 4.0.5 upgrade as well.
>>>
>>
>> Thanks for pointing this. Will refer that.
>>
>>>
>>> Hope this helps!
>>>
>>> Thanks and Regards,
>>> Harshana
>>>
>>>
>>> On Thu, Jul 11, 2013 at 11:06 PM, Viraj Rajaguru  wrote:
>>>
>>>> Hi,
>>>>
>>>> We are upgrading the Synapse jars in Developer Studio to implement new
>>>> features related to ESB 4.7.0 within Developer Studio.
>>>>
>>>>
>>>>
>>>> Thanks,
>>>> Viraj.
>>>>
>>>> --
>>>> Viraj Rajaguru
>>>> Software Engineer
>>>> WSO2 Inc. : http://wso2.com
>>>>
>>>> Mobile: +94 77 3683068
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>>
>>> Harshana Martin
>>> Associate Technical Lead
>>> WSO2 Inc. : http://wso2.com
>>>
>>> Mobile: +94 775 998 115
>>> Profile: https://www.google.com/profiles/harshana05
>>> Blog: http://harshana05.blogspot.com
>>> Twitter: http://twitter.com/harshana05
>>>
>>>
>> Thanks,,
>> Viraj.
>>
>> --
>> Viraj Rajaguru
>> Software Engineer
>> WSO2 Inc. : http://wso2.com
>>
>> Mobile: +94 77 3683068
>>
>>
>>
>>
>
>
> --
> Melan Nimesh Jayasingha
> Software Engineer;
> WSO2 Inc.
> m:  77 631 6759
> PGP: 0x7B42450A
>
>


-- 
Melan Nimesh Jayasingha
Software Engineer;
WSO2 Inc.
m:  77 631 6759
PGP: 0x7B42450A
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Upgrading Synapse dependencies in Developer Studio

[Melan Nimesh]

On Fri, Jul 12, 2013 at 1:33 PM, Viraj Rajaguru  wrote:

> Hi,
>
>
> On Fri, Jul 12, 2013 at 12:30 PM, Harshana Martin wrote:
>
>> Hi Viraj,
>>
>> Upgrading Synapse dependencies alone will not work since they might have
>> dependencies to other core dependencies such as Axiom, Axis2, etc.
>>
>> So if you are upgrading the versions, you need to check their
>> dependencies which are used in our codebase and upgrade them as well.
>>
>> Yes. We are upgrading those dependencies as well.
>

Please refactor
"org.wso2.developerstudio.libraries.libraryprovider" extension-point and
use that extension-point to include dependencies to other projects
with hard-coding there jar file names

e.g. we can define following configuration

  

 and introduce a method to add particular jar using it's identifier as
a parameter

Thanks,
Melan


>
>
>> Please have a look how we did the 4.0.5 upgrade as well.
>>
>
> Thanks for pointing this. Will refer that.
>
>>
>> Hope this helps!
>>
>> Thanks and Regards,
>> Harshana
>>
>>
>> On Thu, Jul 11, 2013 at 11:06 PM, Viraj Rajaguru  wrote:
>>
>>> Hi,
>>>
>>> We are upgrading the Synapse jars in Developer Studio to implement new
>>> features related to ESB 4.7.0 within Developer Studio.
>>>
>>>
>>>
>>> Thanks,
>>> Viraj.
>>>
>>> --
>>> Viraj Rajaguru
>>> Software Engineer
>>> WSO2 Inc. : http://wso2.com
>>>
>>> Mobile: +94 77 3683068
>>>
>>>
>>>
>>>
>>
>>
>> --
>>
>> Harshana Martin
>> Associate Technical Lead
>> WSO2 Inc. : http://wso2.com
>>
>> Mobile: +94 775 998 115
>> Profile: https://www.google.com/profiles/harshana05
>> Blog: http://harshana05.blogspot.com
>> Twitter: http://twitter.com/harshana05
>>
>>
> Thanks,,
> Viraj.
>
> --
> Viraj Rajaguru
> Software Engineer
> WSO2 Inc. : http://wso2.com
>
> Mobile: +94 77 3683068
>
>
>
>


-- 
Melan Nimesh Jayasingha
Software Engineer;
WSO2 Inc.
m:  77 631 6759
PGP: 0x7B42450A
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Developer Studio 3.2.0 Milestone 2 Released !

[Melan Nimesh]

Hi All,

We have WSO2 Developer Studio 3.2.0 Milestone 2  ready to be downloaded at [
1].
Installed eclipse distributions available at
[2
]

This release includes following improvements and bug fixes.

Bug fixes

   - [TOOLS-1152 ] - It's better
   if there's option in property editor to change the value of collector
   attribute of cache mediator
   - [TOOLS-1153 ] - Default value
   of useTransaction attribute (of dbreport mediator) is not removed when the
   user has not specified any value for it
   - [TOOLS-1325 ] - 'Apache Axis2
   Web Service Client Wizard's Text controls fail to function
   - [TOOLS-1382 ] - Regisry
   Remote instance resource addtion: Save button is getting enabled regardless
   of the Non-Optional fields are empty
   - [TOOLS-1544 ] - Null pointer
   exception thrown when output mapping not provided for a CEP bucket
   - [TOOLS-1627 ] - When
   importing a synapse.xml if we request not to open imported files at the
   initial step, graphical files doesn't get created.
   - [TOOLS-1646 ] - Axis2 Client
   Code generation is broken after Jar Update
   - [TOOLS-1653 ] - NPE when
   double click on a non existing sequence in the Graphical Editor
   - [TOOLS-1655 ] - Script
   mediator deserialization doesn't work properly.
   - [TOOLS-1657 ] - Maven
   multi-module project creation does not validate project name with existing
   projects

Improvement

   - [TOOLS-1210 ] - Need a way to
   specify parent project/POM for the artifact projects
   - [TOOLS-1656 ] - [Usability]
   Wizard dialogs needs scrollbars for large wizard pages


Your feedbacks are most welcome !!! Please report all the Jiras at
[3]
and specify the version as 3.0.0.

Thanks and Regards,
The WSO2 Developer Studio Team.

[1] -
http://builder1.us1.wso2.org/~developerstudio/developer-studio/3.2.0/M2/wso2-developer-studio_3.2.0.zip
[2] -
http://builder1.us1.wso2.org/~developerstudio/developer-studio/3.2.0/M2/installed-distributions/
[3] - https://wso2.org/jira/browse/TOOLS
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Developer Studio 3.0.0 RC1 Released !

[Melan Nimesh]

Hi Nirmal,

According to the log messages, It seems that Carbon studio 1.0.14
already installed on your eclipse. Please uninstall any previous version
of Carbon studio/Developer Studio before installing Developer Studio 3.0.0,
It's better to use a fresh copy of eclipse.

Thanks,
Melan

On Wed, Mar 6, 2013 at 10:35 AM, Nirmal Fernando  wrote:

> Hi Melan,
>
> When I try to install this version in my Eclipse 3.7.0, I'm getting
> following error. Any idea why?
>
> Your original request has been modified.
>   "Smooks Tools" will be ignored because it is already installed.
> Cannot complete the install because of a conflicting dependency.
>   Software being installed: WSO2 Carbon Application BPEL Connector Feature
> 3.0.0
> (org.wso2.developerstudio.eclipse.bpel.connector.feature.feature.group
> 3.0.0)
>   Software currently installed: Bussiness Process Server Tools 1.0.14
> (org.wso2.carbonstudio.eclipse.bps.feature.feature.group 1.0.14)
>   Only one of the following can be installed at once:
> Extensionmodel Model 0.5.0.wso2v2 (org.eclipse.bpel.common.model
> 0.5.0.wso2v2)
> Extension Model (Incubation) 0.5.0.wso2v1
> (org.eclipse.bpel.common.model 0.5.0.wso2v1)
>   Cannot satisfy dependency:
> From: Bussiness Process Server Tools 1.0.14
> (org.wso2.carbonstudio.eclipse.bps.feature.feature.group 1.0.14)
> To: org.eclipse.bpel.common.model [0.5.0.wso2v1]
>   Cannot satisfy dependency:
> From: WSO2 Carbon Application BPEL Connector Feature 3.0.0
> (org.wso2.developerstudio.eclipse.bpel.connector.feature.feature.group
> 3.0.0)
> To: org.wso2.developerstudio.eclipse.bps.feature.feature.group
> [3.0.0,3.1.0)
>   Cannot satisfy dependency:
> From: Business Process Server Tools 3.0.0
> (org.wso2.developerstudio.eclipse.bps.feature.feature.group 3.0.0)
> To: org.eclipse.bpel.common.model [0.5.0.wso2v2]
>
>
> On Mon, Mar 4, 2013 at 2:04 PM, Melan Nimesh  wrote:
>
>> Hi All,
>>
>> We have WSO2 Developer Studio 3.0.0 release candidate 1 ready to be
>> downloaded at 
>> [1<http://dist.wso2.org/downloads/developer-studio/3.0.0/rc-1/wso2-developer-studio_3.0.0.zip>].
>> Installed eclipse distributions available at 
>> [2<http://dist.wso2.org/downloads/developer-studio/3.0.0/rc-1/>
>> ]
>>
>> This release includes following improvements and bug fixes.
>>
>> bug fixes
>>
>>- [TOOLS-1322 <https://wso2.org/jira/browse/TOOLS-1322>] - It
>>requires 5 "ctrl+z" to undo a dropped mediator
>>- [TOOLS-1567 <https://wso2.org/jira/browse/TOOLS-1567>] - Migrating
>>CEP Plugin dependency jars from 4.0.1 to 4.0.7
>>- [TOOLS-1568 <https://wso2.org/jira/browse/TOOLS-1568>] - CEP plugin
>>does not have TextOutputMapping as an option in QueryDialog
>>- [TOOLS-1571 <https://wso2.org/jira/browse/TOOLS-1571>] - DevS is
>>extremely slow and unresponsive with multiple projects in workspace
>>- [TOOLS-1572 <https://wso2.org/jira/browse/TOOLS-1572>] - DevS 2.1.0
>>always starts with initial workspace in the users home directory
>>- [TOOLS-1573 <https://wso2.org/jira/browse/TOOLS-1573>] - NPE thrown
>>when trying to save a proxy with one named endpoint and one named endpoint
>>as an inline one
>>- [TOOLS-1575 <https://wso2.org/jira/browse/TOOLS-1575>] - Trying to
>>create a Sequence in the workspace throws OOM
>>- [TOOLS-1134 <https://wso2.org/jira/browse/TOOLS-1134>] - WSO2
>>banking sample JMS issue
>>
>> Improvement
>>
>>- [TOOLS-1566 <https://wso2.org/jira/browse/TOOLS-1566>] - Introduce
>>Class Loader Descriptor for JAX-* artifacts to run with CXF in AS 5.0.2
>>
>>
>> Your feedbacks are most welcome !!! Please report all the Jiras at [3]
>> and specify the version as 3.0.0.
>>
>> Thanks and Regards,
>> The WSO2 Developer Studio Team.
>>
>> [1] -
>> http://dist.wso2.org/downloads/developer-studio/3.0.0/rc-1/wso2-developer-studio_3.0.0.zip
>>  [2] - http://dist.wso2.org/downloads/developer-studio/3.0.0/rc-1/
>> [3] - https://wso2.org/jira/browse/TOOLS
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
>
> Thanks & regards,
> Nirmal
>
> Software Engineer- Platform Technologies Team, WSO2 Inc.
> Mobile: +94715779733
> Blog: http://nirmalfdo.blogspot.com/
>
> <http://nirmalfdo.blogspot.com/>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Developer Studio 3.0.0 RC1 Released !

[Melan Nimesh]

Hi All,

We have WSO2 Developer Studio 3.0.0 release candidate 1 ready to be
downloaded at 
[1].
Installed eclipse distributions available at
[2
]

This release includes following improvements and bug fixes.

bug fixes

   - [TOOLS-1322 ] - It requires 5
   "ctrl+z" to undo a dropped mediator
   - [TOOLS-1567 ] - Migrating CEP
   Plugin dependency jars from 4.0.1 to 4.0.7
   - [TOOLS-1568 ] - CEP plugin
   does not have TextOutputMapping as an option in QueryDialog
   - [TOOLS-1571 ] - DevS is
   extremely slow and unresponsive with multiple projects in workspace
   - [TOOLS-1572 ] - DevS 2.1.0
   always starts with initial workspace in the users home directory
   - [TOOLS-1573 ] - NPE thrown
   when trying to save a proxy with one named endpoint and one named endpoint
   as an inline one
   - [TOOLS-1575 ] - Trying to
   create a Sequence in the workspace throws OOM
   - [TOOLS-1134 ] - WSO2 banking
   sample JMS issue

Improvement

   - [TOOLS-1566 ] - Introduce
   Class Loader Descriptor for JAX-* artifacts to run with CXF in AS 5.0.2


Your feedbacks are most welcome !!! Please report all the Jiras at [3] and
specify the version as 3.0.0.

Thanks and Regards,
The WSO2 Developer Studio Team.

[1] -
http://dist.wso2.org/downloads/developer-studio/3.0.0/rc-1/wso2-developer-studio_3.0.0.zip
[2] - http://dist.wso2.org/downloads/developer-studio/3.0.0/rc-1/
[3] - https://wso2.org/jira/browse/TOOLS
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] DevStudio - Issues with JAX-RS projects

[Melan Nimesh]

Hi,

Please find my comments inline

On Wed, Feb 27, 2013 at 1:29 AM, Kasun Gajasinghe  wrote:

> Hi guys,
>
> I've been testing jax-rs support in dev-studio. It's actually pretty cool.
> Liked the automatic creation of spring bean definitions, and the ability to
> create JAX-RS classes etc. easily. Anyway, while doing testing, I noticed
> some issues that would have been if fixed. I tried this on Dev Studio
> 2.1.0. Couldn't grab the 3.0.0 beta yet, but probably the issue is still
> there as well.
>
> - When we create a new JAX-RS Service Class via UI, the cxf-servlet.xml
> gets updated automatically with relevant details which is great. But there
> is a little issue with the xml element name *jaxrs:serviceBean*. It
> should be *jaxrs:serviceBeans* AFAIK. The war files that were generated
> using the default cxf-servlet.xml fails because this is not consistent with
> the jaxrs schema. [1]
>

This issue[2] is already fixed in more recent versions (3.0.0 alpha2 or
later).

>
> - This isn't really a bug, but would be a enhancement. On the 'JAX
> RESTfull Service Class' dialog box, there is a restriction where the user
> must define a 'Service Interface' class as well. As per the JAX-RS spec, it
> not mandatory to have a service interface, and implementation separately. I
> think it's better if we remove this additional restriction.
>

+1, I've created a Jira[3] for this improvement.


>
> - Just noticed a typo - The dialogbox you get when you click on 'JAX
> RESTfull Service Class' has the title "New *JAX-WS *Class" :)
>
>
> [1] http://cxf.apache.org/schemas/jaxrs.xsd
>
> Thanks,
> KasunG
>
> --
> *Kasun Gajasinghe*
> Software Engineer;
> Development Technologies Team, WSO2 Inc.; http://wso2.com ,
> *email: **kasung AT spamfree wso2.com** cell: **+94 (77) 678-0813*
> *linked-in: *http://lk.linkedin.com/in/gajasinghe*
> *
>  *blog: **http://blog.kasunbg.org* *
> twitter: **http://twitter.com/kasunbg* *
> *
>

[2] https://wso2.org/jira/browse/TOOLS-1522
[3] https://wso2.org/jira/browse/TOOLS-1565
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Developer Studio 3.0.0 Beta Released !

[Melan Nimesh]

Hi All,

We have WSO2 Developer Studio 3.0.0 Beta ready to be downloaded at
[1].
Installed eclipse distributions available at
[2
]

This release includes following improvements, new features and bug fixes.

Bug Fixes

   - [TOOLS-1011 ] - Installation
   on Eclipse Indigo hangs for a long time
   - [TOOLS-1101 ] - Unable to
   checkout registry resources
   - [TOOLS-1135 ] - Error in
   creating proxy services if there's a slight change in proxy creation steps
   - [TOOLS-1228 ] - "This is a
   tech preview" text appears on the text editor
   - [TOOLS-1275 ] - Cannot Create
   Servlets in WSO2 WebApp project
   - [TOOLS-1303 ] - Registry
   resources going blank when imported from registry project path
   - [TOOLS-1308 ] - Change the
   server role ComplexEventProcessingServer to ComplexEventProcessor
   - [TOOLS-1320 ] - Generate a
   default key name for sequences in a proxy, rather than having "" and asking
   user upon double click
   - [TOOLS-1352 ] - Running maven
   on new BRS project gives error: Unable to find resource
   'org.wso2.maven:maven-brs-plugin:pom:1.0.0'
   - [TOOLS-1403 ] - Server Port
   window in Eclipse WSO2 Developer Studio not working properly
   - [TOOLS-1409 ] - While
   deserializing DBLookup mediator throws an exception.
   - [TOOLS-1410 ] - Mediators
   doesn't get connected automatically in between two mediators inside complex
   figures.
   - [TOOLS-1412 ] - Sequences
   doesn't get added to artifacts.xml when they are added by tool palette.
   - [TOOLS-1414 ] - BRS feature
   is missing in pre-installed distributions
   - [TOOLS-1415 ] - While
   implementing service chaining, sequence source cannot be viewed until
   sequence mediator get connected with endpoint inside proxy service.
   - [TOOLS-1417 ] - User should
   be able to connect proxy service input connector to mediators inside
   complex mediators of out sequence.
   - [TOOLS-1419 ] - WSDL
   Resources not available for Proxy
   - [TOOLS-1420 ] - Resources not
   able to add for Validate mediator
   - [TOOLS-1423 ] - Script
   Mediator transformer is incomplete.
   - [TOOLS-1424 ] - After
   deserializing, order of mediators inside complex mediators in out path is
   incorrect.
   - [TOOLS-1425 ] - While
   implementing service chaining, user cannot see the source in sequences
   editor if there is no connection in the endpoint.
   - [TOOLS-1426 ] - Link will be
   deleted from diagram not from emf model, If we delete the link indirectly.
   - [TOOLS-1427 ] - There should
   be a property to change sequence type . (Whether it is a receiving sequence
   or not)
   - [TOOLS-1428 ] - Developer
   studio saves/overwrites call-template mediator configuration with incorrect
   values/elements
   - [TOOLS-1432 ] - endpoints
   doesn't get serialized in sequences editor
   - [TOOLS-1433 ] - Sequences
   editor must have a property to set "onError" attribute in sequence
   - [TOOLS-1434 ] - Sequence has
   2 additional properties as AssociateProxy and ReceivingSequence which are
   wrong to have
   - [TOOLS-1435 ] - Main sequence
   properties view shows proxy service's properties.
   - [TOOLS-1445 ] - Property
   Mediator deserializer having issues when set the property value type,
   expression and scope
   - [TOOLS-1447 ] - Can not add
   properties to endpoints.
   - [TOOLS-1449 ] - Namespaces of
   Call template parameters does not get serialized/de-serialized
   - [TOOLS-1455 ] - Fault code
   value doesn't get serialized properly in the Fault mediator.
   - [TOOLS-1477 

[Dev] WSO2 Developer Studio 2.1.0 Milestone 7 Released!

[Melan Nimesh]

Hi All,

We have WSO2 Developer Studio 2.1.0 Milestone 7 ready to be downloaded
at 
[1].
Installed eclipse distributions available at
[2
]

This release includes following improvements and bug fixes.

 Bug Fixes

   - [TOOLS-1282 ] - "Export
   project as deployable archive" option not available for JAX-RS projects
   - [TOOLS-1287 ] - After
   deleting some figures, undo option doesn't work properly.
   - [TOOLS-1290 ] - ESB editor
   serialize time out action in endpoints with wrong format.
   - [TOOLS-1292 ] - In an ESB
   endpoint configuration, the timeout action should be set as
   .
   - [TOOLS-1294 ] - Double click
   on some mediators, doesn't pop up properties view
   - [TOOLS-1272 ] - Implement
   necessary UI components and serialization of Validate Mediator.
   - [TOOLS-1295 ] - Compartment
   name has been missed in some mediators

Improvements

   - [TOOLS-1284 ] - Implement
   Builder Mediator Serialization.
   - [TOOLS-1285 ] - Implement
   property-view components and serialization of DBLookup mediator.
   - [TOOLS-1286 ] - Implement
   property-view components and serialization of DBReport mediator.


Your feedbacks are most welcome !!! Please report all the jiras at
[3]
and specify the version as 2.1.0.

Thanks and Regards,
The WSO2 Developer Studio Team.

[1] -
http://builder1.us1.wso2.org/~developerstudio/developer-studio/2.1.0/M7/wso2-developer-studio_2.1.0-SNAPSHOT.zip
[2] -
http://builder1.us1.wso2.org/~developerstudio/developer-studio/2.1.0/M7/Dev-Studio-Pre-installed-Eclipse/
[3] - https://wso2.org/jira/browse/TOOLS
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] WSO2 Developer Studio 2.1.0 Milestone 5 Released!

[Melan Nimesh]

Hi All,

We have WSO2 Developer Studio 2.1.0 Milestone 5 ready to be downloaded
at 
[1].
Installed eclipse distributions available at
[2
]

This release includes following new features, improvements and bug fixes.

New Features

   - [TOOLS-1145 ] - Complex Event
   Processing Plugin
   - [TOOLS-1267 ] - Developer
   Studio SoapUI integration
   - [TOOLS-1268 ] - Developer
   Studio TCPMon integration

Bug Fixes

   - [TOOLS-1230 ] - Dialog box
   that is shown when we double click on a sequence is too small
   - [TOOLS-1245 ] - If user add a
   sequence mediator as the first mediator of the Out sequence of a Proxy
   service, It doesn't get serialized properly.
   - [TOOLS-1253 ] - Mediators
   doesn't get connected inside the Fault sequence compartment.
   - [TOOLS-1254 ] - Sequence
   mediator doesn't get serialized if it is in the Fault sequence.
   - [TOOLS-1261 ] - RMSequence
   mediator cannot be saved or serialized
   - [TOOLS-1262 ] - Smooks
   mediator : properties /serialization partially incomplete
   - [TOOLS-1264 ] - user should
   be able to drop the arrow anywhere inside the proxy figure not only in the
   input connector to create a connection.
   - [TOOLS-1265 ] - Store
   mediator : cannot set on store sequence

Improvements

   - [TOOLS-1263 ] - Implement
   call-template mediator serialization
   - [TOOLS-1218 ] - Implement
   command mediator serialization


Your feedbacks are most welcome !!! Please report all the jiras at
[3]
and specify the version as 2.1.0.

Thanks and Regards,
The WSO2 Developer Studio Team.

[1] -
http://builder1.us1.wso2.org/~developerstudio/developer-studio/2.1.0/M5/wso2-developer-studio_2.1.0-SNAPSHOT.zip
[2] -
http://builder1.us1.wso2.org/~developerstudio/developer-studio/2.1.0/M5/Dev-Studio-Pre-installed-Eclipse/
[3] - https://wso2.org/jira/browse/TOOLS
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Improve Carbon Studio features according to JAX-WS/JAX-RS changes.

[Melan Nimesh]

Hi Sagara,

Please find my comments inline.

On Fri, Aug 24, 2012 at 10:01 PM, Sagara Gunathunga  wrote:

> Hi Tooling team,
>
> Since AS 5.0.0 will provide 1st class support for CXF we need to
> improve Carbon Studio features as well.
>
> Following 3 improvements are very important and does not require much
> effort, better if we can include them into next few milestone
> releases.
>
> 1. https://wso2.org/jira/browse/TOOLS-1255

This feature is already available. it
is available as separate class wizard. you can see it by right clicking on
a project with  JAX-WS nature and go to New -> JAX-WS Service Class.  and
it capable of adding multiple service class to a project.



>
> 2. https://wso2.org/jira/browse/TOOLS-1256

This feature is already available.  it is
also available as separate class wizard and same as above.


>
> 3. https://wso2.org/jira/browse/TOOLS-1257

Is it good idea to ship a CXF runtime with DevStudio? it will increase size
of devStudio distribution by 50 MB. and is there any way to generation web
service stub from CXF wsdl2java tool? Seems like it's only support client
stub generation.



>
>
>
> Also following are not urgent as above but we need to add them into
> tooling road map.
>
> 4. https://wso2.org/jira/browse/TOOLS-1259
> 5. https://wso2.org/jira/browse/TOOLS-1260

+1, I am looking into this


>
>
>
>
> Thanks !
>
> --
> Sagara Gunathunga
>
> Technical Lead; WSO2, Inc.;  http://wso2.com
> V.P Apache Web Services ;  http://ws.apache.org/
> Blog ;  http://ssagara.blogspot.com
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev


Thanks,
Melan
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] WSO2 Developer Studio 2.1.0 Milestone 3 Released!

[Melan Nimesh]

Hi All,

We have WSO2 Developer Studio 2.1.0 Milestone 3 ready to be downloaded
at 
[1].
Installed
eclipse distributions available at
[2
]

This release includes following improvements and bug fixes.

Bug Fixes

   - [TOOLS-1194 ] - Mediator and
   Endpoint figures are re-sizable. This behavior should be avoided.
   - [TOOLS-1204 ] - Enrich
   mediator can not be linked from rear side.
   - [TOOLS-1208 ] - Cache
   mediator dose not serialize  and can not configure sequence key
   using UI.
   - [TOOLS-1221 ] - Can not save
   the configuration when Cache mediator include in to the diagram.
   - [TOOLS-1225 ] - Cache
   mediator visual object can not contain other mediators.
   - [TOOLS-1231 ] - double
   clicking endpoint does nothing
   - [TOOLS-1233 ] - Cannot
   connect sequence icon to endpoint
   - [TOOLS-1234 ] - Null pointer
   when I drop log mediator to a sequence
   - [TOOLS-1235 ] - User should
   be able to drop the arrow anywhere inside the target figure not only in to
   the input connector, when we connecting figures.
   - [TOOLS-1237 ] - Dropping the
   mediator connector onto another mediator does not connect
   - [TOOLS-1238 ] - Start point
   of a sequence cannot be connected to the first mediator
   - [TOOLS-1241 ] - When we move
   mouse pointer over output connector, it selects a Link tool and remain
   loaded.

Improvement

   - [TOOLS-1236 ] - Implement the
   ESB sequence graphical editor from the components/codebase created in ESB
   graphical editor

Your feedbacks are most welcome !!! Please report all the jiras at
[3]
and specify the version as 2.1.0.

Thanks and Regards,
The WSO2 Developer Studio Team.

[1] -
http://builder1.us1.wso2.org/~developerstudio/developer-studio/2.1.0/M3/wso2-developer-studio_2.1.0-SNAPSHOT.zip
[2] -
http://builder1.us1.wso2.org/~developerstudio/developer-studio/2.1.0/M3/Dev-Studio-Pre-installed-Eclipse/
[3] - https://wso2.org/jira/browse/TOOLS
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Developer Studio Code Frozen for RC1

[Melan Nimesh]

Hi,

On Mon, May 21, 2012 at 4:51 PM, Sumedha Rubasinghe wrote:

> Melan,
> Does this include the bug I explained the morning?
>

Yes, I have create a Jira [1] for track down this issue.

[1] https://wso2.org/jira/browse/TOOLS-1064


> (which are..
> - having  org.wso2.carbon for Maven artifacts even after specifying a
> custom package
> - Artifact name not being editable).
>
> /sumedha
>
> On Mon, May 21, 2012 at 4:45 PM, Harshana Martin wrote:
>
>> Hi All,
>>
>> Please note that Developer Studio code is frozen for RC1.
>>
>> You are not supposed to commit anything other than L1 and L2 bug fixes to
>> branch and trunk right now and please make sure to commit the fixes to both
>> branch and trunk to keep the trunk in sync with branch.
>>
>> Thanks and Regards,
>> Harshana
>> --
>> Harshana Martin
>> Senior Software Engineer
>> WSO2 Inc. : http://wso2.com ; http://wso2.org
>> Mobile: +94 716 062 650
>> Profile: https://www.google.com/profiles/harshana05
>> Blog: http://harshana05.blogspot.com
>> Twitter: http://twitter.com/harshana05
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> /sumedha
> +94 773017743



Thanks,
Melan
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] WSO2 Developer Studio 2.0.0 Beta Released !

[Melan Nimesh]

Hi All,

We have WSO2 Developer Studio 2.0.0 Beta ready to be downloaded at
[1]
(without dependencies) and
[2]
(with dependencies).

Bug

   - [TOOLS-86 ] - Delete items
   remain in the UI.
   - [TOOLS-148 ] - endpoint name
   that is given by default should change for each artifact created
   - [TOOLS-669 ] - It takes ages
   for Registry Handler UI to load
   - [TOOLS-833 ] - Allocated
   memory for server process is not taken into effect when starting up Carbon
   Server inside Carbon Studio
   - [TOOLS-967 ] - Ctrl+V does not
   paste the contents into the input field
   - [TOOLS-970 ] - Importing .dbs
   as a dependency to a new Carbon project does not allow to create the Carbon
   project
   - [TOOLS-974 ] - Error when
   shutting down a Carbon Server from the Eclipse Console
   - [TOOLS-975 ] - Management
   Console does not show up automatically even when the Carbon server start up
   successfully
   - [TOOLS-977 ] - When we apply
   an 'Ordinal' property on a parameter from the Outline View, it does not
   show up in the DS Editor's Source View
   - [TOOLS-978 ] - All the
   Ordinals automatically turn to 0 when saving the configuration
   - [TOOLS-979 ] - Bug in
   Documentation - ESB Tools
   - [TOOLS-980 ] - Cannot specify
   'localhost' in a Endpoint URL
   - [TOOLS-982 ] - Saving .dbs
   file with serviceNamespace attribute giving an error in data service editor.
   - [TOOLS-983 ] - In proxy
   services editor, Endpoint type is set to Anonymous by default
   - [TOOLS-984 ] - In proxy
   services editor, cannot save configuration if the Endpoint element is
   removed
   - [TOOLS-987 ] - Registry
   resources tree view is not correctly showing the resources to be deployed
   - [TOOLS-988 ] - When deleting
   an ESB Artifact, artifact.xml get corrupted
   - [TOOLS-989 ] - When deleting
   an ESB Artifact, incorrect Warning message is displayed
   - [TOOLS-990 ] - When importing
   a .dbs to a project and if that .dbs already exists in the same project no
   error / warning message is given
   - [TOOLS-991 ] - Add
   "description" to ESB EMF Tree editor
   - [TOOLS-992 ] - While refer a
   WSDL as a registry resource, there should be a way to add external
   resources that are being defined in the WSDL when creating a proxy service
   - [TOOLS-995 ] - When importing
   a Synapse config from file system, it does not generate the separate
   entries for local entries when split the ESB config
   - [TOOLS-996 ] - Registry
   Resource behavior is inconsistent for templates and file system imports
   - [TOOLS-997 ] - Conditional
   Router Mediator serialization error
   - [TOOLS-998 ] - Multiple
   service descriptions can be added when creating a data-service through
   wizard
   - [TOOLS-999 ] - Serialization
   error in the URLRewrite Mediator
   - [TOOLS-1004 ] - Data-source
   listing drop down in query page wont get update with newly added
   data-sources.
   - [TOOLS-1006 ] -
   NullPointerException when adding query properties
   - [TOOLS-1012 ] - When 'Use
   Column Numbers' is set to true in query result, output mappings should use
   'data-source column number' instead of 'data-source column name'.
   - [TOOLS-1015 ] - 'Export Type'
   filed is missing in output mappings.
   - [TOOLS-1019 ] - Error occurs
   when trying to build a library artifact created using a workspace project,
   if the pom already exists
   - [TOOLS-1023 ] - Cannot build
   a CAR p