Re: [Dev] Problem with Adding Comment lines in WSO2 code
Hi, This is a bug and we need fix this. If there is a "comment" as the first element of any code block(ie. sequence) it will be removed while generating the source. You will be able to put comments after the first mediator successfully. Thanks, Viraj. On Fri, Sep 1, 2017 at 2:07 PM, Malaka Silva <mal...@wso2.com> wrote: > +WSO2 Dev > -- Forwarded message -- > From: Vivek Kumar <vivku...@salmon.com> > Date: Fri, Sep 1, 2017 at 11:44 AM > Subject: Problem with Adding Comment lines in WSO2 code > To: "mal...@wso2.com" <mal...@wso2.com> > > > Hi Malaka, > > I am having problem adding comment lines in WSO2 code.This is what happen: > > When I write some comment lines before some mediator(Filter mediator > here),Then I go to design view and come back to source view,the comment > lines are gone. > > How do we achieve adding comment lines to improve code understandability. > > > > WITH COMMENT LINE: > > > > WITH COMMENT LINE GONE: > > > > *Vivek Kumar* > > *Associate System Analyst* > > *Office: *+91-120-4737401 <+91%20120%20473%207401> > > *Mobile*: +91 8588897434 <+91%2085888%2097434> > > *Email*:vivku...@salmon.com <youraddr...@salmon.com> > > *Skype:* vivekhereatskype > > > > > > Information contained in this e-mail and any attachments is confidential > and intended for the use of the addressee only. Dissemination, > distribution, copying or use of this communication without prior permission > of the addressee is strictly prohibited. If you have received this > transmission in error, please advise the originator by reply e-mail and > delete it. Thank you. Salmon India’s Registered Address is: B-13, Sector > 57, Noida (U.P.) 201301. Registered in India U72200DL2003PTC120356. > > > > > Information contained in this e-mail and any attachments is confidential > and intended for the use of the addressee only. Dissemination, > distribution, copying or use of this communication without prior permission > of the addressee is strictly prohibited. If you have received this > transmission in error, please advise the originator by reply e-mail and > delete it. Thank you. Salmon India’s Registered Address is: B-13, Sector > 57, Noida (U.P.) 201301. Registered in India U72200DL2003PTC120356. > > > > -- > > Best Regards, > > Malaka Silva > Associate Director / Architect > M: +94 777 219 791 <+94%2077%20721%209791> > Tel : 94 11 214 5345 > Fax :94 11 2145300 > Skype : malaka.sampath.silva > LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77 > Blog : http://mrmalakasilva.blogspot.com/ > > WSO2, Inc. > lean . enterprise . middleware > https://wso2.com/signature > http://www.wso2.com/about/team/malaka-silva/ > <http://wso2.com/about/team/malaka-silva/> > https://store.wso2.com/store/ > > Don't make Trees rare, we should keep them with care > -- Viraj Rajaguru Associate Technical Lead WSO2 Inc. : http://wso2.com Mobile: +94 77 3683068 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] WSO2 Committers += Aruna Herath
Hi All, It's my pleasure to announce Aruna Herath as a WSO2 Committer. Congratulations Aruna ! Thanks, Viraj. -- Viraj Rajaguru Associate Technical Lead WSO2 Inc. : http://wso2.com Mobile: +94 77 3683068 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [DEV] MSF4J level support to get resource template of a http request
Hi Ishara,
We can do that. We have a release scheduled by end of this week. Fix will
be available in that release.
Thanks,
Viraj.
On Tue, May 30, 2017 at 12:16 PM, Ishara Cooray <isha...@wso2.com> wrote:
> Hi Thusitha,
>
> I could not observe a property called "method" in my Request object.
>
> I noticed that,
>
> we have *msf4j-core-2.3.0-m2.jar* and *workspace-service-0.8.2.jar *in
> place.
>
> *workspace-service-0.8.2.jar *uses
> * msf4j 2.1.0*
> So at runtime it picks from the *workspace-service-0.8.2.jar *
>
>
>
>
> *@Viraj,*
> Can we please get the msf4j version updated to it's latest version in
> ballerina-parent/*pom.xml*
> <https://github.com/ballerinalang/ballerina-parent/blob/master/pom.xml#L981>
> Currently it is 2.1.0
>
>
> Thanks & Regards,
> Ishara Cooray
> Senior Software Engineer
> Mobile : +9477 262 9512 <+94%2077%20262%209512>
> WSO2, Inc. | http://wso2.com/
> Lean . Enterprise . Middleware
>
> On Mon, May 29, 2017 at 10:06 PM, Thusitha Thilina Dayaratne <
> thusit...@wso2.com> wrote:
>
>> Hi Ishara,
>>
>> You can access the actual method that will get invoke at the Interceptor
>> level
>> e.g. request.getProperty("method");[1] So then you can get the @Path
>> value of the method and compare that with the request.getUri().
>>
>> [1] - https://github.com/wso2/msf4j/blob/v2.3.0-m2/core/src/main
>> /java/org/wso2/msf4j/internal/router/HttpMethodInfo.java#L174
>>
>> Thanks
>> Thusitha
>>
>> On Mon, May 29, 2017 at 1:51 AM, Ishara Cooray <isha...@wso2.com> wrote:
>>
>>> Ths usecase behind this is,
>>>
>>> we have scopes defined in apim product REST APIs for each resource path
>>> as below.
>>>
>>> /apis/{apiId}:
>>>
>>> #-
>>>
>>> # Retrieve the details of an API definition
>>>
>>> #-
>>>
>>> get:
>>>
>>> x-scope: apim:api_view
>>>
>>> x-wso2-curl: "curl -k -H \"Authorization: Bearer
>>> ae4eae22-3f65-387b-a171-d37eaa366fa8\" https://127.0.0.1:9443/api/am/
>>> publisher/v1.0/apis/7a2298c4-c905-403f-8fac-38c73301631f"
>>>
>>> ..
>>>
>>>
>>> We are keeping track of these resource to scope mapping and at the time
>>> of a new request, we need to validate the scope.
>>>
>>> But, the request coming with a value(206e1b0b-a48e-47c9-95d0-3eb85544cf2e)
>>> for the variable(apiId), hence unable to find the resource template to
>>> match unless we do a string manipulation(we are maintaining a map for the
>>> resource to scope mapping).
>>>
>>>
>>> We better avoid string manipulations as much as possible because this
>>> will take place in gateway.
>>>
>>>
>>> Therefore need to check the possibility of supporting this from MSF4J
>>> level so that we can get template info from the Request object itself.
>>>
>>>
>>>
>>>
>>> Thanks & Regards,
>>> Ishara Cooray
>>> Senior Software Engineer
>>> Mobile : +9477 262 9512 <+94%2077%20262%209512>
>>> WSO2, Inc. | http://wso2.com/
>>> Lean . Enterprise . Middleware
>>>
>>> On Mon, May 29, 2017 at 12:40 PM, Ishara Cooray <isha...@wso2.com>
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> We have a requirement to identify the request template for a given http
>>>> request.
>>>>
>>>> For example,
>>>> *Req: *
>>>> /api/am/publisher/v1.0/apis/206e1b0b-a48e-47c9-95d0-3eb85544cf2e
>>>>
>>>> *Req path:*
>>>> /apis/206e1b0b-a48e-47c9-95d0-3eb85544cf2e
>>>>
>>>> *Need *to identify corresponding *template as *
>>>> apis/{apiId}
>>>>
>>>> Is there a way to get this info from the MSF4J level?
>>>>
>>>>
>>>> Thanks & Regards,
>>>> Ishara Cooray
>>>> Senior Software Engineer
>>>> Mobile : +9477 262 9512 <+94%2077%20262%209512>
>>>> WSO2, Inc. | http://wso2.com/
>>>> Lean . Enterprise . Middleware
>>>>
>>>
>>>
>>
>>
>> --
>> Thusitha Dayaratne
>> WSO2 Inc. - lean . enterprise . middleware | wso2.com
>>
>> Mobile +94712756809 <+94%2071%20275%206809>
>> Blog alokayasoya.blogspot.com
>> Abouthttp://about.me/thusithathilina
>> <http://wso2.com/signature>
>>
>>
>
--
Viraj Rajaguru
Associate Technical Lead
WSO2 Inc. : http://wso2.com
Mobile: +94 77 3683068
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Error in API does not got to default fault sequence in ESB 5.0.0
Hi Niranjan, That's how it is being serialised. That is a known thing. But if it's causing issues we have to fix that. Thanks, Viraj. On Tue, Jan 31, 2017 at 1:57 PM, Niranjan Karunanandham <niran...@wso2.com> wrote: > Hi ESB Team, > > In ESB 5.0.0 Dev Studio, when an API is created, an empty fault sequence > is added (**). Even if I go to the source view and remove > this, it gets added when creating the CAR file or when deploying it to ESB > from Dev Studio. Because of this, the default fault sequence is not hit > when an error occurs. In the ESB server UI, if I go and remove the empty > fault sequence from source view for the API then it works as expected. > > Is this a known issue? > > Regards, > Nira > > -- > > > *Niranjan Karunanandham* > Associate Technical Lead - WSO2 Inc. > WSO2 Inc.: http://www.wso2.com > > -- Viraj Rajaguru Associate Technical Lead WSO2 Inc. : http://wso2.com Mobile: +94 77 3683068 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Scatter and Gather Pattern for Dynamic Endpoints
Hi, On Mon, Oct 3, 2016 at 7:43 AM, Isuru Udana <isu...@wso2.com> wrote: > Hi Isuru, > > By looking at the synapse code of RecipientListEndpoint, I can see that > there is an option to pick endpoint list dynamically. I am not sure whether > that is configurable through tooling. You may have a look on that. > ESB Tooling supports RecipientListEndpoint configurations. Thanks, Viraj. > > Please note that I haven't tried it out. > > Thanks. > > > On Sun, Oct 2, 2016 at 11:12 AM, Isuru Haththotuwa <isu...@wso2.com> > wrote: > >> Missed the link: >> >> [1]. https://docs.wso2.com/display/IntegrationPatterns/Scatter-Gather >> >> On Sun, Oct 2, 2016 at 11:12 AM, Isuru Haththotuwa <isu...@wso2.com> >> wrote: >> >>> Hi Devs, >>> >>> Do we support $subject with latest ESB? The use case is as follows: >>> >>>- The endpoints are dynamically picked up during the mediation flow >>>(Ex. via a DB query, etc.). The number of endpoints are not fixed >>>- In the aggregation, need to wait till the all the endpoints to >>>which the request were sent returns a response >>> >>> In the EIP sample [1], we can achieve the same with a fixed number of >>> endpoints. Can we do the same with a dynamic number of endpoints? >>> >>> -- >>> Thanks and Regards, >>> >>> Isuru H. >>> +94 716 358 048* <http://wso2.com/>* >>> >>> >>> >> >> >> -- >> Thanks and Regards, >> >> Isuru H. >> +94 716 358 048* <http://wso2.com/>* >> >> >> > > > -- > *Isuru Udana* > Technical Lead > WSO2 Inc.; http://wso2.com > email: isu...@wso2.com cell: +94 77 3791887 > blog: http://mytecheye.blogspot.com/ > -- Viraj Rajaguru Associate Technical Lead WSO2 Inc. : http://wso2.com Mobile: +94 77 3683068 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [VOTE] Release WSO2 Enterprise Service Bus 5.0.0 RC4
Hi all, I've tested followings. - "ESB Solution project" creation and artifact creation (API, Proxy, Inbound endpoint, Sequence, Endpoint, Message Store, Message Processor, Task) - Creating CAR files with the tool and deploying to ESB server after adding the server as a remote server and starting inside the tool. - Creating CAR files with Maven. - Creating artifacts with Connectors and deploy. - Creating Class mediators with the tool and deploy. - Datamapper feature. - Mediation debugger feature. [+] - Stable, go ahead and release. Thanks, Viraj. On Fri, Aug 19, 2016 at 12:31 PM, Nuwan Wimalasekara <nuw...@wso2.com> wrote: > Hi all. > > Tested and verified following > > >- ESB Mediation Debugging > > > [+] Stable - go ahead and release. > > Thanks, > Nuwnaw > > On Fri, Aug 19, 2016 at 12:21 PM, Prabath Ariyarathna <prabat...@wso2.com> > wrote: > >> Hi All. >> >> Tested and verified following. >> >>- File(VFS) Inbound Endpoint. >>- HTTP/HTTPS Inbound Endpoints. >>- Custom Inbound Endpoint. >>- RabbitMQ Inbound Endpoint. >> >> [+] Stable - go ahead and release. >> >> Thanks. >> >> On Fri, Aug 19, 2016 at 11:30 AM, Nadeeshaan Gunasinghe < >> nadeesh...@wso2.com> wrote: >> >>> Hi all, >>> >>> Tested the following, >>> >>> >>>- Inbound Endpoints >>> VFS, HTTP, HTTPS, WSO2 MB, JMS >>>- JMS scenarios >>> Message Processor, Message Store with ActiveMQ, Rabbit MQ and >>>WSO2 MB >>>- Capp Deployment through tooling >>> >>> [+] Stable - go ahead and release >>> >>> Thanks, >>> >>> *Nadeeshaan Gunasinghe* >>> Software Engineer, WSO2 Inc. http://wso2.com >>> +94770596754 | nadeesh...@wso2.com | Skype: nadeeshaan.gunasinghe >>> <#m_-7683677138807661042_m_7132569658457042904_m_5569028783450022843_> >>> <http://www.facebook.com/nadeeshaan.gunasinghe> >>> <http://lk.linkedin.com/in/nadeeshaan> <http://twitter.com/Nadeeshaan> >>> <http://nadeeshaan.blogspot.com/> >>> Get a signature like this: Click here! >>> <http://ws-promos.appspot.com/r?rdata=eyJydXJsIjogImh0dHA6Ly93d3cud2lzZXN0YW1wLmNvbS9lbWFpbC1pbnN0YWxsP3dzX25jaWQ9NjcyMjk0MDA4JnV0bV9zb3VyY2U9ZXh0ZW5zaW9uJnV0bV9tZWRpdW09ZW1haWwmdXRtX2NhbXBhaWduPXByb21vXzU3MzI1Njg1NDg3Njk3OTIiLCAiZSI6ICI1NzMyNTY4NTQ4NzY5NzkyIn0==155679456732825> >>> >>> On Wed, Aug 17, 2016 at 8:13 AM, Senduran Balasubramaniyam < >>> sendu...@wso2.com> wrote: >>> >>>> Hi All, >>>> >>>> This is the 4th Release Candidate of WSO2 Enterprise Service Bus 5.0.0 >>>> >>>> Please download, test the product and vote. Vote will be open for 72 >>>> hours or as needed. >>>> >>>> Source and distribution >>>> >>>> Run-time: https://github.com/wso2/produc >>>> t-esb/releases/tag/v5.0.0-rc4 >>>> Tooling : https://github.com/wso2/devstu >>>> dio-tooling-esb/releases/tag/v5.0.0-rc4 >>>> Analytics: https://github.com/wso2/analyt >>>> ics-esb/releases/tag/v5.0.0-rc4 >>>> >>>> Please vote as follows. >>>> [+] Stable - go ahead and release >>>> [-] Broken - do not release (explain why) >>>> >>>> Thanks, >>>> - WSO2 ESB Team - >>>> >>>> -- >>>> *Senduran * >>>> Senior Software Engineer, >>>> WSO2, Inc.; http://wso2.com/ <http://wso2.com/> >>>> Mobile: +94 77 952 6548 >>>> >>> >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> >> *Prabath Ariyarathna* >> >> *Associate Technical Lead* >> >> *WSO2, Inc. * >> >> *lean . enterprise . middleware * >> >> >> *Email: prabat...@wso2.com <prabat...@wso2.com>* >> >> *Blog: http://prabu-lk.blogspot.com <http://prabu-lk.blogspot.com>* >> >> *Flicker : https://www.flickr.com/photos/47759189@N08 >> <https://www.flickr.com/photos/47759189@N08>* >> >> *Mobile: +94 77 699 4730 * >> >> >> >> >> >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > Nuwan Wimalasekara > Associate Technical Lead > WSO2, Inc.: http://wso2.com > lean. enterprise. middleware > > phone: +94 71 668 4620 > > > > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Viraj Rajaguru Associate Technical Lead WSO2 Inc. : http://wso2.com Mobile: +94 77 3683068 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Unsupported mediators for custom mediation flows in API Manager
On Thu, Sep 3, 2015 at 9:34 AM, Nuwan Dias <nuw...@wso2.com> wrote: > Here's what I think makes sense to have on the API Manager. > > Call > Drop > Log > Property > Sequence > > ConditionalRouter > Filter > Switch > Validate > > Class > Script > > Enrich > Fault > Header > PayloadFactory > URLRewrite > XQuery > XSLT > FastXSLT > > Cache > DBLookup > DBReport > Enqueue > Transaction > > Aggregate > Callout > Clone > Iterate > ForEach > > Entitlement > > Builder > > BAM > > Thanks, > NuwanD. > > On Thu, Aug 6, 2015 at 12:07 PM, Jasintha Dasanayake <jasin...@wso2.com> > wrote: > >> Hi Nuwan >> >> Did you find any time to list down the valid mediator set for APIM >> >> Thanks & Regards >> /Jasintha >> >> On Wed, Jul 29, 2015 at 11:37 PM, Isabelle Mauny <isabe...@wso2.com> >> wrote: >> >>> All, >>> >>> As discussed today, please sort this out quickly.. Seems you're waiting >>> on each other here :) >>> >>> Isabelle. >>> >>> >>> - >>> *Isabelle Mauny* >>> VP, Product Management - WSO2, Inc. - http://wso2.com/ >>> email: isabe...@wso2.com - mobile (Spain) : +34 616050684 - mobile (Sri >>> Lanka) +94 (0)774777663 >>> Landline: +1 (650) 745 4499 (USA) or +94 (11) 214 534 (SL) Extension >>> : 7302 >>> >>> >>> >>> On Wed, Jul 15, 2015 at 7:59 PM, Nuwan Dias <nuw...@wso2.com> wrote: >>> >>>> Can you list the mediators so we can go through it and see? >>>> >>>> On Wed, Jul 15, 2015 at 6:05 PM, Viraj Rajaguru <vi...@wso2.com> wrote: >>>> >>>>> Hi APIM team, >>>>> >>>>> DevS team is adding the support to add, remove, edit custom mediation >>>>> flows in API Manager by connecting to the remote APIM server using >>>>> Developer Studio. >>>>> >>>>> Since we are reusing the same ESB graphical sequence editor for APIM, >>>>> currently it will list all the available mediators(supported by ESB) in >>>>> the >>>>> tool palette. >>>>> Do we support all the mediators supported by ESB in APIM ? If not can >>>>> we have a list of unsupported mediators so that we can remove them from >>>>> the >>>>> tool palette. >>>>> >>>>> Thanks, >>>>> Viraj. >>>>> >>>>> -- >>>>> Viraj Rajaguru >>>>> Senior Software Engineer >>>>> WSO2 Inc. : http://wso2.com >>>>> >>>>> Mobile: +94 77 3683068 >>>>> >>>>> >>>>> >>>>> >>>> >>>> >>>> -- >>>> Nuwan Dias >>>> >>>> Technical Lead - WSO2, Inc. http://wso2.com >>>> email : nuw...@wso2.com >>>> Phone : +94 777 775 729 >>>> >>> >>> >> >> >> -- >> >> *Jasintha Dasanayake* >> >> *Senior Software EngineerWSO2 Inc. | http://wso2.com >> <http://wso2.com/>lean . enterprise . middleware* >> >> >> *mobile :- 0711368118* >> > > > > -- > Nuwan Dias > > Technical Lead - WSO2, Inc. http://wso2.com > email : nuw...@wso2.com > Phone : +94 777 775 729 > -- Viraj Rajaguru Associate Technical Lead WSO2 Inc. : http://wso2.com Mobile: +94 77 3683068 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Fwd: Releasing an update for DevS kernel 4.1.0
Hi Kavith, I tested the update. It works. We can go ahead and publish it to product dist. Thanks, Viraj. On Thu, Jul 28, 2016 at 10:21 AM, Kavith Lokuhewage <kav...@wso2.com> wrote: > Hi Viraj, > > Update is staged at [1] and available via common staging update URL [2] > for kernel 4.1.0. > Please verify the update, upon verification, we will get it published to > product dist server. > > Thanks, > > [1] > http://builder1.us1.wso2.org/~developerstudio/developer-studio-kernel/4.1.0/platform-bundles/updates/platform-p2-4.1.0-201607270157/ > > [2] > http://builder1.us1.wso2.org/~developerstudio/developer-studio-kernel/4.1.0/updates/ > > *Kavith Lokuhewage* > Senior Software Engineer > WSO2 Inc. - http://wso2.com > lean . enterprise . middleware > Mobile - +94779145123 > Linkedin <http://www.linkedin.com/pub/kavith-lokuhewage/49/473/419> > Twitter <https://twitter.com/KavithThiranga> > > On Tue, Jul 26, 2016 at 8:10 PM, Viraj Rajaguru <vi...@wso2.com> wrote: > >> Thanks Kavith ! >> >> On Tue, Jul 26, 2016 at 8:08 PM, Kavith Lokuhewage <kav...@wso2.com> >> wrote: >> >>> Hi Viraj, >>> >>> I will prepare platform update and let you know once it is published. >>> >>> Thanks, >>> >>> On 26 Jul 2016 8:02 p.m., "Viraj Rajaguru" <vi...@wso2.com> wrote: >>> >>>> Hi Kavith, >>>> >>>> Sent a pull request[1]. >>>> >>>> Thanks, >>>> Viraj. >>>> >>>> [1] - https://github.com/wso2/devstudio-tooling-platform/pull/1 >>>> >>>> On Tue, Jul 26, 2016 at 2:17 PM, Kavith Lokuhewage <kav...@wso2.com> >>>> wrote: >>>> >>>>> Hi Viraj, >>>>> >>>>> Please send the PR with the fix to master branch. We will release the >>>>> update for 4.1.0. >>>>> >>>>> Thanks, >>>>> >>>>> *Kavith Lokuhewage* >>>>> Senior Software Engineer >>>>> WSO2 Inc. - http://wso2.com >>>>> lean . enterprise . middleware >>>>> Mobile - +94779145123 >>>>> Linkedin <http://www.linkedin.com/pub/kavith-lokuhewage/49/473/419> >>>>> Twitter <https://twitter.com/KavithThiranga> >>>>> >>>>> On Fri, Jul 22, 2016 at 3:47 PM, Viraj Rajaguru <vi...@wso2.com> >>>>> wrote: >>>>> >>>>>> >>>>>> -- Forwarded message -- >>>>>> From: Viraj Rajaguru <vi...@wso2.com> >>>>>> Date: Fri, Jul 22, 2016 at 3:46 PM >>>>>> Subject: Releasing an update for DevS kernel 4.1.0 >>>>>> To: Jasintha Dasanayake <jasin...@wso2.com>, Kavith Lokuhewage < >>>>>> kav...@wso2.com>, Susinda Perera <susi...@wso2.com>, Sohani >>>>>> Weerasinghe <soh...@wso2.com>, Nuwan Pallewela <nuw...@wso2.com>, >>>>>> Chanaka Fernando <chana...@wso2.com>, Jagath Sisirakumara >>>>>> Ariyarathne <jaga...@wso2.com> >>>>>> >>>>>> >>>>>> Hi DevS kernel team, >>>>>> >>>>>> We faced an issue while deploying CAR files when webContextRoot is >>>>>> enabled in carbon.xml. See the public Jira[1]. This needs to be fixed in >>>>>> "devstudio-tooling-platform". Can we have this fix as an update for >>>>>> Kernel >>>>>> 4.1.0 since this is a blocker for ESB tolling release. Fix is attached to >>>>>> the jira. >>>>>> >>>>>> BTW, is there any 4.1.0 update branch so that we can send pull >>>>>> requests? >>>>>> >>>>>> Thanks, >>>>>> Viraj. >>>>>> >>>>>> [1] - https://wso2.org/jira/browse/DEVTOOLESB-637 >>>>>> -- >>>>>> Viraj Rajaguru >>>>>> Associate Technical Lead >>>>>> WSO2 Inc. : http://wso2.com >>>>>> >>>>>> Mobile: +94 77 3683068 >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Viraj Rajaguru >>>>>> Associate Technical Lead >>>>>> WSO2 Inc. : http://wso2.com >>>>>> >>>>>> Mobile: +94 77 3683068 >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> ___ >>>>>> Dev mailing list >>>>>> Dev@wso2.org >>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>> >>>>>> >>>>> >>>> >>>> >>>> -- >>>> Viraj Rajaguru >>>> Associate Technical Lead >>>> WSO2 Inc. : http://wso2.com >>>> >>>> Mobile: +94 77 3683068 >>>> >>>> >>>> >>>> >> >> >> -- >> Viraj Rajaguru >> Associate Technical Lead >> WSO2 Inc. : http://wso2.com >> >> Mobile: +94 77 3683068 >> >> >> >> > -- Viraj Rajaguru Associate Technical Lead WSO2 Inc. : http://wso2.com Mobile: +94 77 3683068 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Fwd: Releasing an update for DevS kernel 4.1.0
Thanks Kavith ! On Tue, Jul 26, 2016 at 8:08 PM, Kavith Lokuhewage <kav...@wso2.com> wrote: > Hi Viraj, > > I will prepare platform update and let you know once it is published. > > Thanks, > > On 26 Jul 2016 8:02 p.m., "Viraj Rajaguru" <vi...@wso2.com> wrote: > >> Hi Kavith, >> >> Sent a pull request[1]. >> >> Thanks, >> Viraj. >> >> [1] - https://github.com/wso2/devstudio-tooling-platform/pull/1 >> >> On Tue, Jul 26, 2016 at 2:17 PM, Kavith Lokuhewage <kav...@wso2.com> >> wrote: >> >>> Hi Viraj, >>> >>> Please send the PR with the fix to master branch. We will release the >>> update for 4.1.0. >>> >>> Thanks, >>> >>> *Kavith Lokuhewage* >>> Senior Software Engineer >>> WSO2 Inc. - http://wso2.com >>> lean . enterprise . middleware >>> Mobile - +94779145123 >>> Linkedin <http://www.linkedin.com/pub/kavith-lokuhewage/49/473/419> >>> Twitter <https://twitter.com/KavithThiranga> >>> >>> On Fri, Jul 22, 2016 at 3:47 PM, Viraj Rajaguru <vi...@wso2.com> wrote: >>> >>>> >>>> -- Forwarded message -- >>>> From: Viraj Rajaguru <vi...@wso2.com> >>>> Date: Fri, Jul 22, 2016 at 3:46 PM >>>> Subject: Releasing an update for DevS kernel 4.1.0 >>>> To: Jasintha Dasanayake <jasin...@wso2.com>, Kavith Lokuhewage < >>>> kav...@wso2.com>, Susinda Perera <susi...@wso2.com>, Sohani >>>> Weerasinghe <soh...@wso2.com>, Nuwan Pallewela <nuw...@wso2.com>, >>>> Chanaka Fernando <chana...@wso2.com>, Jagath Sisirakumara Ariyarathne < >>>> jaga...@wso2.com> >>>> >>>> >>>> Hi DevS kernel team, >>>> >>>> We faced an issue while deploying CAR files when webContextRoot is >>>> enabled in carbon.xml. See the public Jira[1]. This needs to be fixed in >>>> "devstudio-tooling-platform". Can we have this fix as an update for Kernel >>>> 4.1.0 since this is a blocker for ESB tolling release. Fix is attached to >>>> the jira. >>>> >>>> BTW, is there any 4.1.0 update branch so that we can send pull requests? >>>> >>>> Thanks, >>>> Viraj. >>>> >>>> [1] - https://wso2.org/jira/browse/DEVTOOLESB-637 >>>> -- >>>> Viraj Rajaguru >>>> Associate Technical Lead >>>> WSO2 Inc. : http://wso2.com >>>> >>>> Mobile: +94 77 3683068 >>>> >>>> >>>> >>>> >>>> >>>> >>>> -- >>>> Viraj Rajaguru >>>> Associate Technical Lead >>>> WSO2 Inc. : http://wso2.com >>>> >>>> Mobile: +94 77 3683068 >>>> >>>> >>>> >>>> >>>> ___ >>>> Dev mailing list >>>> Dev@wso2.org >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >> >> >> -- >> Viraj Rajaguru >> Associate Technical Lead >> WSO2 Inc. : http://wso2.com >> >> Mobile: +94 77 3683068 >> >> >> >> -- Viraj Rajaguru Associate Technical Lead WSO2 Inc. : http://wso2.com Mobile: +94 77 3683068 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Fwd: Releasing an update for DevS kernel 4.1.0
Hi Kavith, Sent a pull request[1]. Thanks, Viraj. [1] - https://github.com/wso2/devstudio-tooling-platform/pull/1 On Tue, Jul 26, 2016 at 2:17 PM, Kavith Lokuhewage <kav...@wso2.com> wrote: > Hi Viraj, > > Please send the PR with the fix to master branch. We will release the > update for 4.1.0. > > Thanks, > > *Kavith Lokuhewage* > Senior Software Engineer > WSO2 Inc. - http://wso2.com > lean . enterprise . middleware > Mobile - +94779145123 > Linkedin <http://www.linkedin.com/pub/kavith-lokuhewage/49/473/419> > Twitter <https://twitter.com/KavithThiranga> > > On Fri, Jul 22, 2016 at 3:47 PM, Viraj Rajaguru <vi...@wso2.com> wrote: > >> >> -- Forwarded message -- >> From: Viraj Rajaguru <vi...@wso2.com> >> Date: Fri, Jul 22, 2016 at 3:46 PM >> Subject: Releasing an update for DevS kernel 4.1.0 >> To: Jasintha Dasanayake <jasin...@wso2.com>, Kavith Lokuhewage < >> kav...@wso2.com>, Susinda Perera <susi...@wso2.com>, Sohani Weerasinghe < >> soh...@wso2.com>, Nuwan Pallewela <nuw...@wso2.com>, Chanaka Fernando < >> chana...@wso2.com>, Jagath Sisirakumara Ariyarathne <jaga...@wso2.com> >> >> >> Hi DevS kernel team, >> >> We faced an issue while deploying CAR files when webContextRoot is >> enabled in carbon.xml. See the public Jira[1]. This needs to be fixed in >> "devstudio-tooling-platform". Can we have this fix as an update for Kernel >> 4.1.0 since this is a blocker for ESB tolling release. Fix is attached to >> the jira. >> >> BTW, is there any 4.1.0 update branch so that we can send pull requests? >> >> Thanks, >> Viraj. >> >> [1] - https://wso2.org/jira/browse/DEVTOOLESB-637 >> -- >> Viraj Rajaguru >> Associate Technical Lead >> WSO2 Inc. : http://wso2.com >> >> Mobile: +94 77 3683068 >> >> >> >> >> >> >> -- >> Viraj Rajaguru >> Associate Technical Lead >> WSO2 Inc. : http://wso2.com >> >> Mobile: +94 77 3683068 >> >> >> >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > -- Viraj Rajaguru Associate Technical Lead WSO2 Inc. : http://wso2.com Mobile: +94 77 3683068 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [ESB] DataMapper issue
Hi Godwin,
We do not have a Jira for this improvement. Please create a Jira.
Thanks,
Viraj.
On Tue, Jul 19, 2016 at 7:28 PM, Godwin Shrimal <god...@wso2.com> wrote:
> Hi Viraj,
>
> This is not a blocking thing and we can move forward by changing it from
> the graphical view. But I think we need to figure out the proper way to fix
> it. Do we have a jira for this already ?
>
>
> Thanks
> Godwin
>
>
> On Mon, Jul 18, 2016 at 11:47 PM, Viraj Rajaguru <vi...@wso2.com> wrote:
>
>> Hi Godwin,
>>
>> In this use case, JSON schema generator will consider all the datatypes,
>> but it will get the datatype of the last value of the array. See the below
>> JSON representation of the XML
>>
>> {
>>"employees":{
>> "firstname":"Demo",
>> "lastname":"Demo",
>> "addresses":{
>> "address":[
>> {
>>"add1":"No 827/B",
>>"add2":"Gemunu Mawatha"
>> },
>> {
>>"add1":321,
>>"add2":"Mount Lavinia"
>> }
>> ]
>> }
>>}
>> }
>>
>> Since the datatype of last "add1" is a NUMBER it will take that for the
>> JSON schema. Hence we see it in the graphical tree.
>>
>> Issue is we have to select one of the datatypes among all the datatypes
>> for the schema. Currently the convention is to get the last datatype. But
>> as a fix, we can set high priority to STRING when we have to select one
>> from multiple datatypes.
>>
>> Until we figure out that conventional issue, you can change the datatype
>> of "add1" from the graphical view. Right click on the "add1" element from
>> the tree --> Click "Edit Field" and then change the Schema type.
>>
>> Thanks,
>> Viraj.
>>
>> On Tue, Jul 19, 2016 at 9:02 AM, Nuwan Pallewela <nuw...@wso2.com> wrote:
>>
>>> Adding Sohani
>>>
>>> On Tue, Jul 19, 2016 at 12:42 AM, Godwin Shrimal <god...@wso2.com>
>>> wrote:
>>>
>>>> Hi All,
>>>>
>>>> When load following xml file in to data mapper (input/output), the add1
>>>> data type takes as NUMBER as in screenshot . It looks when there is at
>>>> least one record in the array with NUMBER it takes as NUMBER. I think It
>>>> should consider all the values in the array.
>>>>
>>>>
>>>> Demo
>>>> Demo
>>>>
>>>>
>>>>
>>>> *No 827/B*
>>>> Gemunu Mawatha
>>>>
>>>>
>>>> *321*
>>>> Mount Lavinia
>>>>
>>>>
>>>>
>>>>
>>>> [image: Inline image 2]
>>>> Thanks
>>>> Godwin
>>>>
>>>> --
>>>> *Godwin Amila Shrimal*
>>>> Senior Software Engineer
>>>> WSO2 Inc.; http://wso2.com
>>>> lean.enterprise.middleware
>>>>
>>>> mobile: *+94772264165*
>>>> linkedin: *http://lnkd.in/KUum6D <http://lnkd.in/KUum6D>*
>>>> twitter: https://twitter.com/godwinamila
>>>> <http://wso2.com/signature>
>>>>
>>>
>>>
>>>
>>> --
>>> --
>>>
>>> *Nuwan Chamara Pallewela*
>>>
>>>
>>> *Software Engineer*
>>>
>>> *WSO2, Inc. *http://wso2.com
>>> *lean . enterprise . middleware*
>>>
>>> Email *nuw...@wso2.com <nuw...@wso2.com>*
>>> Mobile *+94719079739 <%2B94719079739>@*
>>>
>>>
>>>
>>
>>
>> --
>> Viraj Rajaguru
>> Associate Technical Lead
>> WSO2 Inc. : http://wso2.com
>>
>> Mobile: +94 77 3683068
>>
>>
>>
>>
>
>
> --
> *Godwin Amila Shrimal*
> Senior Software Engineer
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: *+94772264165*
> linkedin: *http://lnkd.in/KUum6D <http://lnkd.in/KUum6D>*
> twitter: https://twitter.com/godwinamila
> <http://wso2.com/signature>
>
--
Viraj Rajaguru
Associate Technical Lead
WSO2 Inc. : http://wso2.com
Mobile: +94 77 3683068
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [DEV][ESB Tooling] Improvement on constant operator
Hi Chaturika, We got your point and we will consider this improvement for a next release with a proper graphical representation. BTW, we are encouraging users to write self contained custom functions as much as possible to reduce the complexity. So that its better to define constants within the custom function scope. Without having a proper graphical representation of the connectivity between a custom function and a global constant, facilitating such a feature might lead to a confusion. We had to introduce global variables concept, since there was no other option to achieve some use cases. Thanks, Viraj. On Fri, Jul 22, 2016 at 5:03 PM, Chathurika De Silva <chathuri...@wso2.com> wrote: > Hi ESB Team > > Currently the constant operator provides just a setting of value and > mapping to an output. In the present mapping configuration the constant is > not defined as a constant, rather the defined value is assigned directly to > the relevant output. > > If there is a mechanism to define a global constant, this can be reused > (e.g. in custom functions) and hence will upgrade the usage of the data > mapper as well. I have created [1] for this and hope this will be > considered as this will add a greater value. > > [1] https://wso2.org/jira/browse/DEVTOOLESB-640 > > Thank You > Erandi > > -- > *Chathurika Erandi* > Senior Software Engineer, > WSO2 Inc. > > *E-mail:* chathuri...@wso2.com > *Mobile: *+94714 328 612 > *Blog*: chathurikaerandi.blogspot.com > -- Viraj Rajaguru Associate Technical Lead WSO2 Inc. : http://wso2.com Mobile: +94 77 3683068 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Fwd: Releasing an update for DevS kernel 4.1.0
-- Forwarded message -- From: Viraj Rajaguru <vi...@wso2.com> Date: Fri, Jul 22, 2016 at 3:46 PM Subject: Releasing an update for DevS kernel 4.1.0 To: Jasintha Dasanayake <jasin...@wso2.com>, Kavith Lokuhewage < kav...@wso2.com>, Susinda Perera <susi...@wso2.com>, Sohani Weerasinghe < soh...@wso2.com>, Nuwan Pallewela <nuw...@wso2.com>, Chanaka Fernando < chana...@wso2.com>, Jagath Sisirakumara Ariyarathne <jaga...@wso2.com> Hi DevS kernel team, We faced an issue while deploying CAR files when webContextRoot is enabled in carbon.xml. See the public Jira[1]. This needs to be fixed in "devstudio-tooling-platform". Can we have this fix as an update for Kernel 4.1.0 since this is a blocker for ESB tolling release. Fix is attached to the jira. BTW, is there any 4.1.0 update branch so that we can send pull requests? Thanks, Viraj. [1] - https://wso2.org/jira/browse/DEVTOOLESB-637 -- Viraj Rajaguru Associate Technical Lead WSO2 Inc. : http://wso2.com Mobile: +94 77 3683068 -- Viraj Rajaguru Associate Technical Lead WSO2 Inc. : http://wso2.com Mobile: +94 77 3683068 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [ESB] DataMapper issue
Hi Godwin,
In this use case, JSON schema generator will consider all the datatypes,
but it will get the datatype of the last value of the array. See the below
JSON representation of the XML
{
"employees":{
"firstname":"Demo",
"lastname":"Demo",
"addresses":{
"address":[
{
"add1":"No 827/B",
"add2":"Gemunu Mawatha"
},
{
"add1":321,
"add2":"Mount Lavinia"
}
]
}
}
}
Since the datatype of last "add1" is a NUMBER it will take that for the
JSON schema. Hence we see it in the graphical tree.
Issue is we have to select one of the datatypes among all the datatypes for
the schema. Currently the convention is to get the last datatype. But as a
fix, we can set high priority to STRING when we have to select one from
multiple datatypes.
Until we figure out that conventional issue, you can change the datatype of
"add1" from the graphical view. Right click on the "add1" element from the
tree --> Click "Edit Field" and then change the Schema type.
Thanks,
Viraj.
On Tue, Jul 19, 2016 at 9:02 AM, Nuwan Pallewela <nuw...@wso2.com> wrote:
> Adding Sohani
>
> On Tue, Jul 19, 2016 at 12:42 AM, Godwin Shrimal <god...@wso2.com> wrote:
>
>> Hi All,
>>
>> When load following xml file in to data mapper (input/output), the add1
>> data type takes as NUMBER as in screenshot . It looks when there is at
>> least one record in the array with NUMBER it takes as NUMBER. I think It
>> should consider all the values in the array.
>>
>>
>> Demo
>> Demo
>>
>>
>>
>> *No 827/B*
>> Gemunu Mawatha
>>
>>
>> *321*
>> Mount Lavinia
>>
>>
>>
>>
>> [image: Inline image 2]
>> Thanks
>> Godwin
>>
>> --
>> *Godwin Amila Shrimal*
>> Senior Software Engineer
>> WSO2 Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> mobile: *+94772264165*
>> linkedin: *http://lnkd.in/KUum6D <http://lnkd.in/KUum6D>*
>> twitter: https://twitter.com/godwinamila
>> <http://wso2.com/signature>
>>
>
>
>
> --
> --
>
> *Nuwan Chamara Pallewela*
>
>
> *Software Engineer*
>
> *WSO2, Inc. *http://wso2.com
> *lean . enterprise . middleware*
>
> Email *nuw...@wso2.com <nuw...@wso2.com>*
> Mobile *+94719079739 <%2B94719079739>@*
>
>
>
--
Viraj Rajaguru
Associate Technical Lead
WSO2 Inc. : http://wso2.com
Mobile: +94 77 3683068
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Getting Developer Studio kernel updates for 4.1.0
Thanks Kavith ! On Fri, Jul 15, 2016 at 10:53 AM, Kavith Lokuhewage <kav...@wso2.com> wrote: > Hi Viraj, > > We are currently creating the updates and facing some issues with the > builder. I will update you once the updates are successfully published. > > Thanks, > > *Kavith Lokuhewage* > Senior Software Engineer > WSO2 Inc. - http://wso2.com > lean . enterprise . middleware > Mobile - +94779145123 > Linkedin <http://www.linkedin.com/pub/kavith-lokuhewage/49/473/419> > Twitter <https://twitter.com/KavithThiranga> > > On Fri, Jul 15, 2016 at 10:43 AM, Viraj Rajaguru <vi...@wso2.com> wrote: > >> Hi DevS kernel team, >> >> We are in the process of releasing ESB Tools 5.0.0-BETA-2. Can we have >> updates for DevS Kernel 4.1.0 with the fixes[1][2] for the DEVTOOLESB-57[3] >> ? >> >> Thanks, >> Viraj. >> >> [1] - >> https://github.com/wso2/developer-studio/commit/cd4ffb8ac54845b551136595939bc32879e31b10 >> [2] - >> https://github.com/wso2/developer-studio/commit/24c28ffccaca3ab4019101d778cbd71dc9aaa48a >> [3] - https://wso2.org/jira/browse/DEVTOOLESB-576 >> >> -- >> Viraj Rajaguru >> Associate Technical Lead >> WSO2 Inc. : http://wso2.com >> >> Mobile: +94 77 3683068 >> >> >> >> > -- Viraj Rajaguru Associate Technical Lead WSO2 Inc. : http://wso2.com Mobile: +94 77 3683068 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Getting Developer Studio kernel updates for 4.1.0
Hi, On Fri, Jul 15, 2016 at 10:43 AM, Viraj Rajaguru <vi...@wso2.com> wrote: > Hi DevS kernel team, > > We are in the process of releasing ESB Tools 5.0.0-BETA-2. Can we have > updates for DevS Kernel 4.1.0 with the fixes[1][2] for the DEVTOOLESB-57[3] > ? > Issue should be DEVTOOLESB-441[4] not DEVTOOLESB-576[3] > > Thanks, > Viraj. > > [1] - > https://github.com/wso2/developer-studio/commit/cd4ffb8ac54845b551136595939bc32879e31b10 > [2] - > https://github.com/wso2/developer-studio/commit/24c28ffccaca3ab4019101d778cbd71dc9aaa48a > [3] - https://wso2.org/jira/browse/DEVTOOLESB-576 > [4] - https://wso2.org/jira/browse/DEVTOOLESB-441 > > > -- > Viraj Rajaguru > Associate Technical Lead > WSO2 Inc. : http://wso2.com > > Mobile: +94 77 3683068 > > > > -- Viraj Rajaguru Associate Technical Lead WSO2 Inc. : http://wso2.com Mobile: +94 77 3683068 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Getting Developer Studio kernel updates for 4.1.0
Hi DevS kernel team, We are in the process of releasing ESB Tools 5.0.0-BETA-2. Can we have updates for DevS Kernel 4.1.0 with the fixes[1][2] for the DEVTOOLESB-57[3] ? Thanks, Viraj. [1] - https://github.com/wso2/developer-studio/commit/cd4ffb8ac54845b551136595939bc32879e31b10 [2] - https://github.com/wso2/developer-studio/commit/24c28ffccaca3ab4019101d778cbd71dc9aaa48a [3] - https://wso2.org/jira/browse/DEVTOOLESB-576 -- Viraj Rajaguru Associate Technical Lead WSO2 Inc. : http://wso2.com Mobile: +94 77 3683068 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Smooks editor features are not available in a WSO2 P2 repository
Thanks Jasintha. We have created a new feature[1] from those plugins. Thanks, Viraj. [1] - https://github.com/wso2/devstudio-tooling-esb/tree/master/features/org.wso2.developerstudio.eclipse.smooks.editor.feature On Wed, Jun 29, 2016 at 3:12 PM, Jasintha Dasanayake <jasin...@wso2.com> wrote: > Hi Viraj > > Since Jboss no more sending update for smooks feature there is no value to > keep these two features separately. Lets marge these two and create a > single feature for smooks by adding all 6 plugins .All these plugins are > added into the stage p2 repo[1] so please build feature using that and I > later will move into WSO2 public p2 > > Thanks and Regards > /Jasintha > > [1]- > http://builder1.us1.wso2.org/~developerstudio/developer-studio-kernel/dependencies/other/p2/plugins/ > > On Wed, Jun 29, 2016 at 11:30 AM, Viraj Rajaguru <vi...@wso2.com> wrote: > >> Hi Jasintha, >> >> We need following Smooks editor features for ESB Tooling. Can we have >> them in a WSO2 public P2 repository ? >> >> org.smooks.edi.editor-feature.feature.group:1.0.1.201105031731 >> org.jboss.tools.smooks.feature.feature.group:1.1.0.v20110215-1231-H25-GA >> >> BTW, We can see org.smooks.edi.editor_1.0.1.201105031731.jar >> and org.smooks.edi.editor.model_1.0.1.201105031731.jar plugins are >> available at [1]. We can create >> "org.smooks.edi.editor-feature.feature.group" feature with those. But still >> we need org.jboss.tools.smooks.feature.feature.group feature. >> >> Can we have these features in a public WSO2 P2 repository ? >> >> Thanks, >> Viraj. >> >> [1] - >> http://builder1.us1.wso2.org/~developerstudio/developer-studio-kernel/dependencies/other/p2/plugins/ >> >> -- >> Viraj Rajaguru >> Associate Technical Lead >> WSO2 Inc. : http://wso2.com >> >> Mobile: +94 77 3683068 >> >> >> >> > > > -- > > *Jasintha Dasanayake**Associate Technical Lead* > > *WSO2 Inc. | http://wso2.com <http://wso2.com/>lean . enterprise . > middleware* > > > *mobile :- 0711-368-118* > -- Viraj Rajaguru Associate Technical Lead WSO2 Inc. : http://wso2.com Mobile: +94 77 3683068 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Smooks editor features are not available in a WSO2 P2 repository
Hi Jasintha, We need following Smooks editor features for ESB Tooling. Can we have them in a WSO2 public P2 repository ? org.smooks.edi.editor-feature.feature.group:1.0.1.201105031731 org.jboss.tools.smooks.feature.feature.group:1.1.0.v20110215-1231-H25-GA BTW, We can see org.smooks.edi.editor_1.0.1.201105031731.jar and org.smooks.edi.editor.model_1.0.1.201105031731.jar plugins are available at [1]. We can create "org.smooks.edi.editor-feature.feature.group" feature with those. But still we need org.jboss.tools.smooks.feature.feature.group feature. Can we have these features in a public WSO2 P2 repository ? Thanks, Viraj. [1] - http://builder1.us1.wso2.org/~developerstudio/developer-studio-kernel/dependencies/other/p2/plugins/ -- Viraj Rajaguru Associate Technical Lead WSO2 Inc. : http://wso2.com Mobile: +94 77 3683068 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [ESB Tooling] Can we activate "event statistics" on global level?
Hi Iranga, IIUC, requirement is to setting a global level setting with CAR files to enable event statistics publishing. As per this document[1], we need to set a property in synapse.properties file + relevant config changes in artifact files to enable statistics publishing. With CAR files we are not modifying config files such as synapse.properties. So how can we achieve this? Thanks, Viraj. [1] - https://docs.wso2.com/display/ESB500/Prerequisites+to+Publish+Statistics On Fri, Apr 29, 2016 at 12:12 PM, Iranga Muthuthanthri <ira...@wso2.com> wrote: > > > On Fri, Apr 29, 2016 at 11:35 AM, Malaka Silva <mal...@wso2.com> wrote: > >> +1 and it make sense to do it since we are having the >> a separate analytics server for ESB. >> >> Iranga when you say global do you mean for a CAPP or for the complete >> deployment? I think you are referring to the second option. >> > > Global setting -Having it at complete deployment , having it at the C-App > level would also be a useful option as well IMO > >> >> On Fri, Apr 29, 2016 at 11:20 AM, Iranga Muthuthanthri <ira...@wso2.com> >> wrote: >> >>> Hi All, >>> >>> When creating a C-App to publish event statistics to ESB Analytics we >>> have to enable event statistics for each configuration ( proxy service, >>> API,) , would there be an option to set this at a global level? >>> >>> -- >>> Thanks & Regards >>> >>> Iranga Muthuthanthri >>> (M) -0777-255773 >>> Team Product Management >>> >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> >> Best Regards, >> >> Malaka Silva >> Senior Tech Lead >> M: +94 777 219 791 >> Tel : 94 11 214 5345 >> Fax :94 11 2145300 >> Skype : malaka.sampath.silva >> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77 >> Blog : http://mrmalakasilva.blogspot.com/ >> >> WSO2, Inc. >> lean . enterprise . middleware >> http://www.wso2.com/ >> http://www.wso2.com/about/team/malaka-silva/ >> <http://wso2.com/about/team/malaka-silva/> >> https://store.wso2.com/store/ >> >> Save a tree -Conserve nature & Save the world for your future. Print this >> email only if it is absolutely necessary. >> > > > > -- > Thanks & Regards > > Iranga Muthuthanthri > (M) -0777-255773 > Team Product Management > > -- Viraj Rajaguru Associate Technical Lead WSO2 Inc. : http://wso2.com Mobile: +94 77 3683068 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] ClassCastException when using datamapper
dispatch(Unknown
>>> Source)
>>>
>>> at
>>> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
>>> Source)
>>>
>>> at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>>>
>>> at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>>>
>>> at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
>>>
>>> at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
>>>
>>> at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown
>>> Source)
>>>
>>> at
>>> org.wso2.carbon.mediator.datamapper.engine.input.readers.XMLReader.read(XMLReader.java:95)
>>>
>>> at
>>> org.wso2.carbon.mediator.datamapper.engine.input.InputModelBuilder.buildInputModel(InputModelBuilder.java:52)
>>>
>>> at
>>> org.wso2.carbon.mediator.datamapper.engine.core.mapper.MappingHandler.doMap(MappingHandler.java:59)
>>>
>>> at
>>> org.wso2.carbon.mediator.datamapper.DataMapperMediator.transform(DataMapperMediator.java:245)
>>>
>>> at
>>> org.wso2.carbon.mediator.datamapper.DataMapperMediator.mediate(DataMapperMediator.java:217)
>>>
>>> at
>>> org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:87)
>>>
>>> at
>>> org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:292)
>>>
>>> at
>>> org.apache.synapse.core.axis2.Axis2SynapseEnvironment.mediateFromContinuationStateStack(Axis2SynapseEnvironment.java:774)
>>>
>>> at
>>> org.apache.synapse.core.axis2.Axis2SynapseEnvironment.injectMessage(Axis2SynapseEnvironment.java:282)
>>>
>>> at
>>> org.apache.synapse.core.axis2.SynapseCallbackReceiver.handleMessage(SynapseCallbackReceiver.java:546)
>>>
>>> at
>>> org.apache.synapse.core.axis2.SynapseCallbackReceiver.receive(SynapseCallbackReceiver.java:179)
>>>
>>> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
>>>
>>> at
>>> org.apache.synapse.transport.passthru.ClientWorker.run(ClientWorker.java:255)
>>>
>>> at
>>> org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
>>>
>>> at
>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
>>>
>>> at
>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
>>>
>>> at java.lang.Thread.run(Thread.java:722)
>>>
>>> *Proxy Service:*
>>>
>>>
>>> http://ws.apache.org/ns/synapse;
>>>name="createIssue"
>>>transports="https,http"
>>>statistics="disable"
>>>trace="disable"
>>>startOnLoad="true">
>>>
>>>
>>>
>>> PS9VE7M
>>>
>>> >>
>>> inputSchema="gov:datamapper/pdJiraConfig_inputSchema.json"
>>>
>>> outputSchema="gov:datamapper/pdJiraConfig_outputSchema.json"
>>> inputType="XML"
>>> outputType="XML"/>
>>>
>>> {json-eval($.issueFields)}
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> *pdJiraConfig.dmc:*
>>>
>>> function map_S_root_S_root( ){
>>> var outputroot={};
>>>
>>>
>>> outputroot = {};
>>> outputroot.issueFields = {};
>>> outputroot.issueFields.fields = {};
>>>
>>>
>>> outputroot.issueFields.fields.description = inputroot.html_url;
>>> return outputroot;
>>> }
>>>
>>> Thanks,
>>> Keerthika.
>>> --
>>> <dev-requ...@wso2.org>
>>> Keerthika Mahendralingam
>>> Software Engineer
>>> Mobile :+94 (0) 776 121144
>>> keerth...@wso2.com
>>> WSO2, Inc.
>>> lean . enterprise . middleware
>>>
>>
>>
>>
>> --
>> --
>>
>> *Nuwan Chamara Pallewela*
>>
>>
>> *Software Engineer*
>>
>> *WSO2, Inc. *http://wso2.com
>> *lean . enterprise . middleware*
>>
>> Email *nuw...@wso2.com <nuw...@wso2.com>*
>> Mobile *+94719079739 <%2B94719079739>@*
>>
>>
>>
>
>
> --
> <dev-requ...@wso2.org>
> Keerthika Mahendralingam
> Software Engineer
> Mobile :+94 (0) 776 121144
> keerth...@wso2.com
> WSO2, Inc.
> lean . enterprise . middleware
>
--
Viraj Rajaguru
Associate Technical Lead
WSO2 Inc. : http://wso2.com
Mobile: +94 77 3683068
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [DEV] [VOTE] WSO2 Developer Studio Tooling for Platform RC3
Hi, Did we release WSO2 Developer Studio Tooling for Platform 4.1.0. ? Thanks, Viraj. On Sun, Jun 5, 2016 at 1:24 PM, Jasintha Dasanayake <jasin...@wso2.com> wrote: > Thanks all, > > We are closing this vote with 4 +1's and 0 -1's. > > The RC3 has passed the vote. > > Thanks and Regards > /Jasintha > > On Wed, Jun 1, 2016 at 11:33 AM, Jasintha Dasanayake <jasin...@wso2.com> > wrote: > >> >> >> On Wed, Jun 1, 2016 at 10:25 AM, Susinda Perera <susi...@wso2.com> wrote: >> >>> when i'm installing It asks for me to trust on 2 certificates, one is >>> DeveloperStudio and other is Developer Studio kernel team. But from users >>> POV i think it's good to have only one cert to trust WDYT? >>> >> These because DevStudio kernel and the platform build using Jenkins, but >> ESB has been build manually , by end of this week we will provide Jenkins >> jobs for all product so there won't be two certificate in the future >> releases >> >> Thanks and Regards >> /Jasintha >> >> >> >> >>> >>> On Tue, May 31, 2016 at 11:45 AM, Awanthika Senarath <awanth...@wso2.com >>> > wrote: >>> >>>> Hello all, >>>> >>>> I have tested the Server Additions and removals with ESB product tool. >>>> >>>> >>>> here is my vote : +1 >>>> >>>> >>>> >>>> >>>> Awanthika Senarath >>>> Software Engineer, WSO2 Inc. >>>> Mobile: +94717681791 >>>> >>>> >>>> >>>> On Tue, May 31, 2016 at 11:33 AM, Jasintha Dasanayake < >>>> jasin...@wso2.com> wrote: >>>> >>>>> Hello Devs, >>>>> >>>>> We are pleased to announce the vote for RC-3 of *WSO2 Developer Studio >>>>> Tooling >>>>> for Platform 4.1.0.* >>>>> >>>>> P2 repository of WSO2 developer Studio Tooling for Platform 4.1.0 is >>>>> available here >>>>> <http://builder1.us1.wso2.org/~developerstudio/developer-studio-kernel/4.1.0/platform-bundles/releases/>. >>>>> Source >>>>> and Tag Location to be voted upon is available here >>>>> <https://github.com/wso2/devstudio-tooling-platform/releases/tag/Released-mars-carbon-4.4-platform-4.1.0-RC3-2016-05-30-163759> >>>>> . >>>>> >>>>> Developer Studio 4.1.0 Tooling for Platform is released on Developer >>>>> Studio kernel 4.1.0. >>>>> Developer Studio Kernel contains a single feature which has the >>>>> bundles that are required to implement WSO2 specific product tooling on >>>>> Eclipse. >>>>> >>>>> This release contains; >>>>> >>>>>- Developer Studio migration to Eclipse mars >>>>>- Support Devs kernel 4.1.0 >>>>>- Improvements in the Developer Studio Updater tool for automatic >>>>>updates >>>>>- List down severs in product wise (previously it was carbon >>>>>version) >>>>>- Introduced new extension point to add product natures dynamically >>>>>- Adding support for carbon 4.4.5 based server >>>>> >>>>> >>>>> >>>>>1. [+] Stable - go ahead and release >>>>>2. [-] Broken - do not release (please explain why) >>>>> >>>>> >>>>> The platform could to be tested on top of Developer Studio Kernel with >>>>> compatible tooling SNAPSHOT versions available at [1]. >>>>> >>>>> Thanks go everyone who made this checkpoint possible. >>>>> >>>>> >>>>> [1] >>>>> http://builder1.us1.wso2.org/~developerstudio/developer-studio-kernel/4.1.0/ >>>>> >>>>> >>>>> -- >>>>> >>>>> *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 >>>> >>>> >>> >>> >>> -- >>> *Susinda Perera* >>> Software Engineer >>> B.Sc.(Eng), M.Sc(Computer Science), AMIE(SL) >>> Mobile:(+94)716049075 >>> Blog: susinda.blogspot.com >>> WSO2 Inc. http://wso2.com/ >>> Tel : 94 11 214 5345 Fax :94 11 2145300 >>> >>> >> >> >> -- >> >> *Jasintha Dasanayake* >> >> *Senior Software EngineerWSO2 Inc. | http://wso2.com >> <http://wso2.com/>lean . enterprise . middleware* >> >> >> *mobile :- 0711368118 <0711368118>* >> > > > > -- > > *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 > > -- Viraj Rajaguru Associate Technical Lead WSO2 Inc. : http://wso2.com Mobile: +94 77 3683068 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Issue in processing certain integer values in data mapper
Hi Sohani, +1 for suggestion. This will solve the same issue we are solving with synapse.commons.json.json.output.autoPrimitive and synapse.commons.json.json.output.disableAutoPrimitive.regex in synapse.properties file while XML to JSON conversion in ESB. With Datamapper we will have more flexibility since we can set the 'Type' per attribute. Thanks, Viraj. On Fri, Jun 10, 2016 at 4:59 PM, Sohani Weerasinghe <soh...@wso2.com> wrote: > Hi All, > > Since there is already a feature to edit the properties of a particular > tree node, we can use that to change the data type > > Thanks, > Sohani > > Sohani Weerasinghe > Senior Software Engineer > WSO2, Inc: http://wso2.com > > Mobile : +94 716439774 > Blog :http://christinetechtips.blogspot.com/ > Twitter : https://twitter.com/sohanichristine > > On Fri, Jun 10, 2016 at 11:26 AM, Sohani Weerasinghe <soh...@wso2.com> > wrote: > >> Hi All, >> >> If we consider a payload which has values such as telephone numbers, >> userID, house no etc, when generating the JSON schema they are treated as >> "numbers". >> >> When user tries to map the payload, final generated outcome displays as a >> double value. >> >> eg: If we pass an object as below, the output comes as 1.12655655E8 which >> is wrong. >> >> >> 0112655655 >> 01 >> >> >> AFAIU, before generating the mapping config user should be provided with >> an option to change the data type of that particular field into String. As >> a solution I think we should provide a property so that user can change the >> type. WDYT? >> >> Thanks, >> Sohani >> >> Sohani Weerasinghe >> Senior Software Engineer >> WSO2, Inc: http://wso2.com >> >> Mobile : +94 716439774 >> Blog :http://christinetechtips.blogspot.com/ >> Twitter : https://twitter.com/sohanichristine >> > > -- Viraj Rajaguru Associate Technical Lead WSO2 Inc. : http://wso2.com Mobile: +94 77 3683068 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Developer Studio changes ordering of XML attributes
Hi Rajeevan, I think we have two issues. 1. The way attributes are ordered in generated source is not readable. Eg: Property name should come before the Property expression. This is a valid requirement and we will try to fix in a future release. (not in the next immediate release). We will need to find a correct XML processing library as Nuwan & Susinda mentioned. 2. Changes done in source view such as formatting, commenting, ordering of elements/attributes etc. will be overridden by switching between graphical view and source view. This is a more critical issue which tends users to move from Graphical editor to default XML editor. Currently we are regenerating the whole source according to what we have in graphical view. This will lead to override users's changes such as formatting, commenting. What we should do is to modify the existing source in source view according to the changes we have done is graphical view rather regenerating the whole source so that we will not loose anything we've done in the source view. Thanks for pointing these issues and we will fix these in future releases. Thanks, Viraj. On Sat, Jun 11, 2016 at 9:08 AM, Vimalanathan Rajeevan <rajeev...@wso2.com> wrote: > Thanks Nuwan and Susinda for your prompt responses. > > I would say it is a nice to have thing rather not a blocker for Developer > Studio. Here the issue is user can not keep desired attribute order when > using Graphical Editor(when switching between Design and Source view it is > getting overwritten). IMO, even though attribute order does not matter in > XML programming it is important for better readability as I explained > above. I have seen some users are using Eclipse default XML editor for > programming because of this kind of issues with Graphical Editor. But I > understand the difficulty of fixing this issue with available XML > processing libraries. So if possible we can give a try to fix this[1]. WDYT? > > [1] https://wso2.org/jira/browse/DEVTOOLESB-374 > > Thanks, > Rajeevan > > On Fri, Jun 10, 2016 at 1:00 AM, Susinda Perera <susi...@wso2.com> wrote: > >> Hi Rajeevan >> >> I have google a bit on this issue in general. It seems like normal DOM >> does not care about the attribute order. Also I believe xml schemas would >> also not care about the order[1]. We have to test this whether we have any >> support in axiom level. As this requirement is valid in terms of end user, >> please create a JIRA to track this. Kavith is looking at some other xml >> processing library, may be he can hive some input. >> >> [1] - https://www.w3.org/TR/REC-xml/#sec-starttags >> >> On Fri, Jun 10, 2016 at 10:22 AM, Vimalanathan Rajeevan < >> rajeev...@wso2.com> wrote: >> >>> Hi, >>> >>> I will explain the issue with the help of Property Mediator. When we are >>> adding a property with an expression to a sequence in Graphical Editor, the >>> source view for that mediator is as follows, >>> >>> >> name="TestProperty" xmlns:m0="http://services.samples; >>> xmlns:m1=" http://services.samples/xsd "/> >>> >>> Here 'expression' is positioned before 'name' of the mediator. IMHO, >>> 'name' should be positioned before 'expression'(for better readability) and >>> we should try to keep the order as below(from ESB Doc), >>> >>> >> "literal" | expression="xpath") [scope=default|transport|axis2|axis2-client] >>> [pattern="regex" [group="integer"]]> >>> ? >>> >>> >>> So I tried to change it from source view but when I switching between >>> graphical and source views my changes are removed and ordered by >>> alphabetically. It is giving difficulties when we are using Graphical >>> Editor and trying to keep some conventions. >>> It should be a known issue. Will we be able to fix this? >>> >>> Appreciate your thoughts on this. >>> >>> -- >>> Vimalanathan Rajeevan >>> Software Engineer, >>> WSO2, Inc. *http://wso2.com* <http://wso2.com> >>> Lean.Enterprise.Middleware >>> >>> Mobile: >>> *+94 773090875 <%2B94%20773090875>* >>> LinkedIn: >>> *https://www.linkedin.com/in/RajeevanVimalanathan >>> <https://www.linkedin.com/in/rajeevanvimalanathan>* >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> *Susinda Perera* >> Software Engineer &g
[Dev] Fixing ESBJAVA-4225
Hi,
I'm working on Jira[1] and was able to find the root cause for the issue.
While the endpoint is being used, we are redeploying the car file which
contains the endpoint to reproduce the issue. See below stacktrace for
endpoint invocation.
org.apache.synapse.config.SynapseConfiguration.getEntryDefinition(SynapseConfiguration.java:869)
org.apache.synapse.endpoints.IndirectEndpoint.reLoadAndInitEndpoint(IndirectEndpoint.java:155)
org.apache.synapse.endpoints.IndirectEndpoint.send(IndirectEndpoint.java:51)
org.apache.synapse.mediators.builtin.SendMediator.mediate(SendMediator.java:115)
org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:83)
org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:49)
org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:160)
org.apache.synapse.core.axis2.ProxyServiceMessageReceiver.receive(ProxyServiceMessageReceiver.java:197)
org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:395)
org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:142)
org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
java.lang.Thread.run(Thread.java:745)
As you can see in the stacktrace, while the endpoint invocation,
org.apache.synapse.config.SynapseConfiguration.getEntryDefinition(String
key) method is being invoked and it is adding a new "Entry" if
the localRegistry.get(key) evaluates to null. See below code snippet.
public Entry getEntryDefinition(String key) {
Object o = localRegistry.get(key);
if (o == null || o instanceof Entry) {
if (o == null) {
// this is not a local definition
synchronized (this) {
o = localRegistry.get(key);
if (o == null) {
Entry entry = new Entry(key);
entry.setType(Entry.REMOTE_ENTRY);
addEntry(key, entry);
return entry;
}
}
}
return (Entry) o;
} else {
if (log.isDebugEnabled()) {
log.debug("There is no local registry entry for key : " +
key);
}
return null;
}
}
Since we are undeploying the CAR file, there is a possibility to get null
value for localRegistry.get(key). So that, when we get a null value for
localRegistry.get(key) it will create a new Entry with the key value
according to the above code snippet and while the actual endpoint
deployment it is failing because there is a entry added with the same key.
Thanks,
Viraj.
[1] - https://wso2.org/jira/browse/ESBJAVA-4225
--
Viraj Rajaguru
Senior Software Engineer
WSO2 Inc. : http://wso2.com
Mobile: +94 77 3683068
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Releasing maven-tools 5.0.1
Hi Susinda, I think we need to add relevant credentials of Nexus to settings.xml Thanks, Viraj. On Fri, Apr 22, 2016 at 2:16 PM, Susinda Perera <susi...@wso2.com> wrote: > Hi Kasun > > For the $subject I followed [1]. It gives me following error when mvn > release:perform. Any idea, How to proceed from here? > > Failed to execute goal > org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) > on project maven-tools: Failed to deploy artifacts: Could not transfer > artifact org.wso2.maven:maven-tools:pom:5.0.1 from/to nexus-releases ( > http://maven.wso2.org/nexus/service/local/staging/deploy/maven2/ > <http://www.google.com/url?q=http%3A%2F%2Fmaven.wso2.org%2Fnexus%2Fservice%2Flocal%2Fstaging%2Fdeploy%2Fmaven2%2F=D=1=AFQjCNGs47JpckjQELI6m5zdgSg80sTjZA>): > Failed to transfer file: > http://maven.wso2.org/nexus/service/local/staging/deploy/maven2/org/wso2/maven/maven-tools/5.0.1/maven-tools-5.0.1.pom > <http://www.google.com/url?q=http%3A%2F%2Fmaven.wso2.org%2Fnexus%2Fservice%2Flocal%2Fstaging%2Fdeploy%2Fmaven2%2Forg%2Fwso2%2Fmaven%2Fmaven-tools%2F5.0.1%2Fmaven-tools-5.0.1.pom=D=1=AFQjCNGoZxSC_5j8DqM-uJAxptFtLljY3w>. > Return code is: 401, ReasonPhrase: Unauthorized > > [1] - https://docs.wso2.com/display/Carbon441/Releasing+a+Git+Repository > > Thanks > Susinda > > -- > *Susinda Perera* > Software Engineer > B.Sc.(Eng), M.Sc(Computer Science), AMIE(SL) > Mobile:(+94)716049075 > Blog: susinda.blogspot.com > WSO2 Inc. http://wso2.com/ > Tel : 94 11 214 5345 Fax :94 11 2145300 > > -- Viraj Rajaguru Senior Software Engineer WSO2 Inc. : http://wso2.com Mobile: +94 77 3683068 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Issues with JSON Schema in representing data types and in representing an array which contains non identical elements
Hi Sohani,
Yes. we will have "value" attribute to represent the data type as mentioned
above.
And also we are working on adding xsi:type support as well.
Thanks,
Viraj.
On Mon, Apr 11, 2016 at 11:14 AM, Sohani Weerasinghe <soh...@wso2.com>
wrote:
> Ok. For an xml like below, let's have the value field as follows
>
>
>
>xyz
>
>071655339
>
>0112655333
>
>
> {
>
> "$schema": "http://json-schema.org/draft-04/schema#;,
>
> "title": "person",
>
> "id": "http://wso2jsonschema.org;,
>
> "type": "object",
>
> "properties": {
>
> "firstName": {
>
> "id": "http://wso2jsonschema.org/firstName;,
>
> "type": "string"
>
> },
>
> "phone": {
>
> "id": "http://wso2jsonschema.org/phone;,
>
> "type": "array",
>
> "items": [{
>
> * “value”:{*
>
> * "id": "http://wso2jsonschema.org/phone/phone
> <http://wso2jsonschema.org/phone/phone>",*
>
> * "type": "number"*
>
> * },*
>
> "attributes": {
>
> "primary": {
>
> "id": "http://wso2jsonschema.org/phone/primary;,
>
> "type": "boolean"
>
> }
>
> }
>
> }]
>
> }
>
> }
>
> }
>
>
>
> Sohani Weerasinghe
> Software Engineer
> WSO2, Inc: http://wso2.com
>
> Mobile : +94 716439774
> Blog :http://christinetechtips.blogspot.com/
> Twitter : https://twitter.com/sohanichristine
>
> On Mon, Apr 11, 2016 at 11:05 AM, Nuwan Pallewela <nuw...@wso2.com> wrote:
>
>> Hi Sohani,
>>
>> +1 for the above approaches.
>>
>> We have to decide on how to represent non identical elements with same
>> name. Viraj is working on it.
>>
>> Thanks,
>> Nuwan
>>
>> On Mon, Apr 11, 2016 at 10:44 AM, Sohani Weerasinghe <soh...@wso2.com>
>> wrote:
>>
>>> Hi Viraj/Nuwan,
>>>
>>> Really appreciate your input on this
>>>
>>> Thanks,
>>> Sohani
>>>
>>> Sohani Weerasinghe
>>> Software Engineer
>>> WSO2, Inc: http://wso2.com
>>>
>>> Mobile : +94 716439774
>>> Blog :http://christinetechtips.blogspot.com/
>>> Twitter : https://twitter.com/sohanichristine
>>>
>>> On Tue, Apr 5, 2016 at 12:06 PM, Sohani Weerasinghe <soh...@wso2.com>
>>> wrote:
>>>
>>>> Hi All,
>>>>
>>>> This is regarding clarifying the $subject.
>>>>
>>>> If we consider an xml as below, we are currently generating the below
>>>> json schema
>>>>
>>>> http://www.w3.org/TR/html4/;>
>>>> susinda
>>>> 07177101
>>>> 011265565501
>>>>
>>>>
>>>>
>>>> {
>>>> "$schema": "http://json-schema.org/draft-04/schema#;,
>>>> "title": "h:person",
>>>> "id": "http://wso2jsonschema.org;,
>>>> "type": "object",
>>>> "properties": {
>>>> "firstName": {
>>>> "id": "http://wso2jsonschema.org/firstName;,
>>>> "type": "string"
>>>> },
>>>> "phone": {
>>>> "id": "http://wso2jsonschema.org/phone;,
>>>> "type": "array",
>>>> "items": [{
>>>> "id": "http://wso2jsonschema.org/phone/0;,
>>>> "type": "object",
>>>> "properties": {
>>>> "ext": {
>>>> "id": "http://wso2jsonschema.org/phone/0/ext;,
>>>> "type": "number"
>>>> }
>>>> },
>>>> "attributes": {
>>>> "primary": {
>>>> "id": "http://wso2jsonschema.org/phone/0/primary;,
>>>> "type": "boolean"
>>>> }
>>>> }
>>>> }]
>>>> }
>>>> }
>>>> }
>>>>
>>>> But the issue is, we don't have any field to define the data type for
>>>> phone ( eg: number). So are we going to introduce a new field as below to
>>>> define the type?
>>>>
>>>> "phone": {
>>>> "id": "http://wso2jsonschema.org/phone;,
>>>> "type": "array",
>>>> "items": [{
>>>> "id": "http://wso2jsonschema.org/phone/0;,
>>>> "type": "object",
>>>> "value":{
>>>> type: "number",
>>>>
>>>>
>>>> } ,
>>>> "properties": {
>>>> "ext": {
>>>> "id": "http://wso2jsonschema.org/phone/0/ext;,
>>>> "type": "number"
>>>> }
>>>> },
>>>> "attributes": {
>>>> "primary": {
>>>> "id": "http://wso2jsonschema.org/phone/0/primary;,
>>>> "type": "boolean"
>>>> }
>>>> }
>>>> }]
>>>> }
>>>>
>>>> Please advice.
>>>>
>>>> Also, how are we going to represent an array which contains non
>>>> identical elements. Are we going to introduce xsi:type?
>>>>
>>>> Really appreciate your input in proceeding with this.
>>>>
>>>> Thanks,
>>>> Sohani
>>>>
>>>> Sohani Weerasinghe
>>>> Software Engineer
>>>> WSO2, Inc: http://wso2.com
>>>>
>>>> Mobile : +94 716439774
>>>> Blog :http://christinetechtips.blogspot.com/
>>>> Twitter : https://twitter.com/sohanichristine
>>>>
>>>
>>>
>>
>>
>> --
>> --
>>
>> *Nuwan Chamara Pallewela*
>>
>>
>> *Software Engineer*
>>
>> *WSO2, Inc. *http://wso2.com
>> *lean . enterprise . middleware*
>>
>> Email *nuw...@wso2.com <nuw...@wso2.com>*
>> Mobile *+94719079739 <%2B94719079739>@*
>>
>>
>>
>
--
Viraj Rajaguru
Senior Software Engineer
WSO2 Inc. : http://wso2.com
Mobile: +94 77 3683068
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [ESB/Tooling] Support JSON, CSV, Java, Excel and Web services formats in Data Mapper tool
Hi Tchuenkam, Please find more information about JSON schema[1] using following references[2][3]. And also there are few open source JSON serialize/deserialize libraries available[4][5] which can be used to build JSON schema. Thanks, Viraj. [1] - http://json-schema.org/latest/json-schema-core.html [2] - http://json-schema.org/ [3] - http://json-schema.org/examples.html [4] - https://github.com/FasterXML/jackson [5] - https://code.google.com/archive/p/json-simple/ On Wed, Mar 16, 2016 at 6:11 PM, Nuwan Pallewela <nuw...@wso2.com> wrote: > Hi , > > We are sorry that we could not give the necessary information before. > > Data mapper design has been changed in the previous week after several > technical discussions regarding using AVRO. Now we are moving towards JSON > schema to define input and output message formats. > > So the project will mainly aim towards generating JSON schema from xsd, > xml, json, and etc. > > Data Mapper Engine will not be depend on any other WSO2 product. Data > mapper engine functionality will be used through WSO2 ESB as a mediator as > the first step. Proxy service can be deployed in WSO2 ESB which will > contain data mapper mediator in it. So the messages received for deployed > proxy will go through the data mapper mediator and message will transform > as specified in the data mapper configuration. > > Thanks, > Nuwan > > On Wed, Mar 16, 2016 at 5:50 PM, tchuenkam ulrich <ulrichmo...@gmail.com> > wrote: > >> >> Hi developer, >> >> 3 days ago i sent a message requesting for more information on what is >> required to build the necessary components to produce Avro Schema from the >> various format specified in this project. >> >> From my understanding of the problem is that we need to design components >> that will extend the actual functionalities of the Data Mapper tool to >> convert JSON, JAVA, Web services, Excel and CSV format to Avro Schema that >> can be used by your Data mapper tool to output data model. >> >> I Know that Avro is a language neutral and schema based tool and whose >> schema is definced with JSON. >> >> >> I have a question is it that the project aims only at generating the Avro >> Schema or Is that the project needs to generate the Schema, serialize data, >> deserialise the data and then send the JSON formatted result of the >> deserialisation to the data mapper tool ? >> >> The Data mapper tool is the framework behind WS02 Data Service Server >> [1] ? >> >> [1]http://wso2.com/project/data-services/2.6.3/docs/quickstart_guide.html >> >> >> >> >> Thanks, >> -- >> ulrich tchuenkam >> > > > > -- > ------ > > *Nuwan Chamara Pallewela* > > > *Software Engineer* > > *WSO2, Inc. *http://wso2.com > *lean . enterprise . middleware* > > Email *nuw...@wso2.com <nuw...@wso2.com>* > Mobile *+94719079739 <%2B94719079739>@* > > > -- Viraj Rajaguru Senior Software Engineer WSO2 Inc. : http://wso2.com Mobile: +94 77 3683068 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Deciding a file type for Json Schema
Hi all, We can define an extension for JSON schema for our reference. But we shouldn't restrict users from importing JSON schema files which has an extension other than "*.jschema". Since we are claiming that "WSO2 Data mapper" supports JSON schema, we should support JSON schema irrespective of the extension. Reason is there is no official extension defined for JSON schema and there are some other commonly using extensions(Eg: *.json etc.) for JSON schema. >From the implementation perspective, we can change the name "JSCHEMA" from the drop down list of "Open Input Schema" dialog to "JSON Schema" and allow user to import JSON schema irrespective of the extension. Since we are building the tree using the provided JSON schema pro-grammatically, we can validate the schema and provide an error to user if it's not a JSON schema. So no need to consider the extension while the importing. [image: Inline image 1] Thanks, Viraj. On Thu, Mar 10, 2016 at 3:04 PM, Awanthika Senarath <awanth...@wso2.com> wrote: > > > .jsc is commonly used for javascript configuration files [1] and .jsd is > also in use according to [2], therefore IMO it is not suitable to use it > for our purpose as it may introduce conflicts. > > [1] http://www.file-extensions.org/jsc-file-extension > [2] http://filext.com/file-extension/JSD > > Regards > Awanthika > > Awanthika Senarath > Software Engineer, WSO2 Inc. > Mobile: +94717681791 > > > > On Thu, Mar 10, 2016 at 2:48 PM, Susinda Perera <susi...@wso2.com> wrote: > >> >> >> On Thu, Mar 10, 2016 at 2:41 PM, Sohani Weerasinghe <soh...@wso2.com> >> wrote: >> >>> How about using something like .jsc ? >>> >>> When we were using avro schema we have used .avsc as the extension hence >>> shall we use .jsc ? >>> >>> Thanks, >>> Sohani >>> >>> Sohani Weerasinghe >>> Software Engineer >>> WSO2, Inc: http://wso2.com >>> >>> Mobile : +94 716439774 >>> Blog :http://christinetechtips.blogspot.com/ >>> Twitter : https://twitter.com/sohanichristine >>> >>> On Thu, Mar 10, 2016 at 2:38 PM, Awanthika Senarath <awanth...@wso2.com> >>> wrote: >>> >>>> Hi, >>>> >>>> In migrating the Data mapper tool for ESB we need to $subject in order >>>> to differentiate between json schema and json files on loading from file >>>> system and registry. >>>> >>> How about introducing mediatype (if not available) from the registry. >> and file extension something like (.jsd similar to .xsd). >> >>> >>>> according to [1] the official mime type for json schema is " >>>> application/schema+json" and we can go ahead with that as the media >>>> type for json schema registry resources. >>>> >>>> For local file system files we can use .jschema to identify json-schema >>>> files. >>>> >>>> WDYT? >>>> >>>> >>>> [1] >>>> http://stackoverflow.com/questions/9391370/json-schema-file-extension >>>> >>>> Regards >>>> Awanthika Senarath >>>> Software Engineer, WSO2 Inc. >>>> Mobile: +94717681791 >>>> >>>> >>>> >>> >> >> >> -- >> *Susinda Perera* >> Software Engineer >> B.Sc.(Eng), M.Sc(Computer Science), AMIE(SL) >> Mobile:(+94)716049075 >> Blog: susinda.blogspot.com >> 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 > > -- Viraj Rajaguru Senior Software Engineer WSO2 Inc. : http://wso2.com Mobile: +94 77 3683068 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] GSOC 2016-support xml, cvs, json, excel and web services formats in data mapper
Hi Jayamine, For an example, Let's consider "Salesforce" web service[1]. Imagine, we need to a map a payload from Salesforce web service's operation to another payload format using Datamapper tool. Idea is to use metadata about the web service operation(it might be a WSDL, Swagger definition etc.) and build the input tree model automatically in the datamapper tool. This will facilitates Datamapper users to point a WSDL of a web service to build the input/output model automatically. Thanks, Viraj. [1] - https://developer.salesforce.com/docs/atlas.en-us.200.0.api.meta/api/ On Sun, Feb 21, 2016 at 8:35 PM, Jayamine A. <jayamine.alupo...@gmail.com> wrote: > > Hi, > > I have a question about the web services format. > I did not get the idea of web services format.. > > What kind of web services ? > please help me to understand it. > > > Thanks > Jayamine :-) > > > > >>> On Thu, Feb 18, 2016 at 10:04 AM, Nuwan Pallewela <nuw...@wso2.com> >>> wrote: >>> >>>> Hi Jayamine, >>>> >>>> Thank you for showing interest on this project. >>>> >>>> We have not created a proper documentation of the design yet. It will >>>> be completed in next week and we will share it with you. Until that you can >>>> go through data mapper engine source and understand how the current >>>> implementation have been done to convert message formats (Input adapters , >>>> Output adapters ). These implementations were done as a POC before, so we >>>> need to improve these implementations to be done in proper way. >>>> >>>> If you could research and suggest us on the proper and efficient way to >>>> convert different message formats to AVRO and vise versa it will be great. >>>> And if you could find a different and better way to support conversion >>>> of the message types rather than using AVRO, feel free to share your >>>> findings. >>>> >>>> Thanks, >>>> Nuwan >>>> >>>> On Wed, Feb 17, 2016 at 5:55 PM, Jayamine A. < >>>> jayamine.alupo...@gmail.com> wrote: >>>> >>>>> Hi, >>>>> >>>>> Thanks for the suggestions. >>>>> I looked in to Data Mapper engine folder. >>>>> I feel awesome. :-). >>>>> This project is related to the area that i have planned to do in my >>>>> higher studies. >>>>> Also I think this is a good start to contribute to the opensource >>>>> world. >>>>> >>>>> I really want to contribute this whether it get accepted or not in >>>>> gsoc. >>>>> Can I do it? >>>>> >>>>> Also I have a question. >>>>> Even it is in implementation level , Is there a way to get a rough >>>>> idea about the design overview of Data mapper? >>>>> >>>>> Thanks >>>>> Jayamine. >>>>> >>>>> >Hi, >>>>> >>>>> >Glad to hear it. >>>>> >>>>> >You can always contact me or vi...@wso2.com for more details. If you >>>>> want to >observe the current implementation you can refer developer studio >>>>> repository [1]. >There you have Data Mapper >Engine folder which contains >>>>> message format >conversions related sources done for the POC >(proof of >>>>> concept). What we need >is to implement them up-to the required level to >>>>> release this >feature. >>>>> >>>>> >[1] >>>>> https://github.com/wso2/developer-studio/tree/developer-studio-product-plugins >>>>> >>>>> >Thanks, >>>>> >Nuwan >>>>> >>>> >>>> >>>> >>>> -- >>>> -- >>>> >>>> *Nuwan Chamara Pallewela* >>>> >>>> >>>> *Software Engineer* >>>> >>>> *WSO2, Inc. *http://wso2.com >>>> *lean . enterprise . middleware* >>>> >>>> Email *nuw...@wso2.com <nuw...@wso2.com>* >>>> Mobile *+94719079739 <%2B94719079739>@* >>>> >>>> >>>> >>> >> > -- Viraj Rajaguru Senior Software Engineer WSO2 Inc. : http://wso2.com Mobile: +94 77 3683068 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] GSoC 2016 - Proposal 14 Inquiry
[+dev] Hi Zhang, Thanks for your interest on above project proposal. We will get back to you soon with further information on this proposal. Thanks, Viraj. On Thu, Mar 10, 2016 at 6:35 PM, <zhangyi0...@gmail.com> wrote: > Dear Viraj and Nuwan, > > My name is Yi Zhang, a graduate student in Beijing University of Posts and > Telecommunications in China, majored in Information and Communication > Engineering. I have already applied for a master program in computer > science in the U.S. this fall. > > I am really interested in proposal on the WSO2 webpage. *Proposal > 14: [ESB/Tooling] Support JSON, CSV, Java, Excel and Web services formats > in Data Mapper tool* seems quite interesting. I am familiar with Java, > JSON etc. and I would like to take part in this project in GSoC2016. What’s > more, as I have already finished my graduate study in BUPT, I have plenty > of time to participate in the program. > > Now I am working on Apache Avro instructions and trying to get familiar > with the ESB. Please kindly give me some advices and further information on > how I could proceed. Looking forward to your reply. > > Best regards, > > Yi Zhang > Wireless Theories and Technologies Lab/WT > == > Beijing University of Posts and Telecommunications > 10 XiTuCheng Road, HaiDian District > Beijing, CHINA (100876) > Tel:+86-13121927568 > -- Viraj Rajaguru Senior Software Engineer WSO2 Inc. : http://wso2.com Mobile: +94 77 3683068 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Improvements to the Data Services Editor in Developer Studio
+1 for new improvements. Thanks, Viraj. On Fri, Feb 5, 2016 at 8:20 AM, Sohani Weerasinghe <soh...@wso2.com> wrote: > Hi All, > > With the current level of implementation, DS Editor of the Developer > studio has few issues in creating a data service and I have fixed those > issues and implemented some improvements as listed below > > 1. With the initial implementation, when user clicks on the tree view the > design view gets dirty even user didn't change any value. This is fixed > where user will only need to save the content when he/she edits the design > view ( via setting properties) or edits the source view. > > 2. After user creates a data service and closes the editor, once he/she > opens the editor and after traversing through the tree view the added > initial values have not persisted correctly in the source view. This is > fixed with the new improvement so that user will not lose any data. > > 3. With the initial implementation, user didn't get a chance to, > >- Select preferred values for a data source when adding a query >- Select parameter type, sql type, in/out type when adding a query >param >- Select a query ID when adding a call-query for an operation etc > > and this is fixed as shown in the attached image. > > 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 > > -- Viraj Rajaguru Senior Software Engineer WSO2 Inc. : http://wso2.com Mobile: +94 77 3683068 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Cannot import some connectors to Developer studio.
Hi File connector is working properly now. Thanks, Viraj. On Wed, Sep 9, 2015 at 2:46 PM, Vivekananthan Sivanayagam < vivekanant...@wso2.com> wrote: > Hi Malaka, > > It has been uploaded. > > > > > > > *Thank youVivekananthan Sivanayagam* > > *Associate Software Engineer | WSO2* > > *E:vivekanant...@wso2.com <e%3avivekanant...@wso2.com>* > *M:+94752786138 <%2B94752786138>* > > On Wed, Sep 9, 2015 at 12:43 PM, Malaka Silva <mal...@wso2.com> wrote: > >> Hi Viraj, >> >> As we discussed this has not followed the proper structure as other >> connectors. However we can't fix this properly since there are existing >> integration done using the connector. >> >> Will be fixing this in next version. Will discuss more on version aspect >> on architecture mail. [1] will fix the current issue. >> >> @Vivekananthan - pls talk to kathees and build a new version of the >> connector and upload to the store. >> >> [1] >> https://github.com/wso2/esb-connectors/commit/0928fea83c8fa08fa2a3c8a1582b13869e429109 >> >> On Wed, Sep 9, 2015 at 10:33 AM, Viraj Rajaguru <vi...@wso2.com> wrote: >> >>> Hi Malaka/Elimantha, >>> >>> Issue is with deserialization. To reproduce this issue, we can add a >>> File connector operation in to a sequence or proxy. Then go to the source >>> view and do any change in the source view and switch back to the graphical >>> view. We can see it's not allowing us to switch to the graphical view. >>> >>> Is there any possibility to introduce a new attribute called 'version' >>> into 'component' element in the component.xml to handle multiple version of >>> connectors scenarios without adding the version into name attribute ? >>> >>> We can have a hangout to discuss this. >>> >>> Thanks, >>> Viraj. >>> >>> On Wed, Sep 9, 2015 at 9:03 AM, Elilmatha Sivanesan <elilma...@wso2.com> >>> wrote: >>> >>>> Hi Malaka >>>> >>>> Yes I have tested file connector, There are no issues now. >>>> >>>> Thank you. >>>> >>>> >>>> >>>> On Wed, Sep 9, 2015 at 7:05 AM, Malaka Silva <mal...@wso2.com> wrote: >>>> >>>>> Hi Viraj, >>>>> >>>>> I tried to reproduce the issue with the latest devs, and it does seems >>>>> to be working fine. May be I missed something. >>>>> >>>>> Can we have a hangout to discuss this in the morning? >>>>> >>>>> However we should only focus on component.xml. Reason for that is we >>>>> need to start with multiple version of the connectors. >>>>> >>>>> eg:- >>>>> linkedin-connector-1.0.0.zip -> >>>>> >>>>> linkedin-connector-2.0.0.zip -> >>>> ="org.wso2.carbon.connector" > >>>>> >>>>> @Elilmatha I think we tested one by one in [1] with devs? There can't >>>>> be any issues? >>>>> [1] https://wso2.org/jira/browse/ESBCONNECT-63 >>>>> >>>>> On Wed, Sep 9, 2015 at 12:05 AM, Viraj Rajaguru <vi...@wso2.com> >>>>> wrote: >>>>> >>>>>> Hi Connector team, >>>>>> >>>>>> There is a trivial issue in File connector. >>>>>> >>>>>> According to the current implementation in DevS, connector needs a >>>>>> file name which comply with the 'component name' in the connector.xml. >>>>>> For >>>>>> an example "googlecalendar-connector-1.0.0.zip" connector's component >>>>>> name >>>>>> should be "googlecalendar" & "linkedin-connector-1.0.0.zip" >>>>>> connector's component name should be "linkedin". Almost all the >>>>>> connectors >>>>>> follow this rule. But "file-connector-1.0.0.zip" connector's 'component >>>>>> name' is "fileconnector". Due to this issue DevS is having issues after >>>>>> importing File connector. Can we fix this ? >>>>>> >>>>>> Thanks, >>>>>> Viraj. >>>>>> >>>>>> On Mon, Jun 1, 2015 at 12:15 PM, Viraj Rajaguru <vi...@wso2.com> >>>>>> wrote: >>>>>> >>>>>>> Hi Keerthika, >
Re: [Dev] Cannot import some connectors to Developer studio.
Hi Connector team, There is a trivial issue in File connector. According to the current implementation in DevS, connector needs a file name which comply with the 'component name' in the connector.xml. For an example "googlecalendar-connector-1.0.0.zip" connector's component name should be "googlecalendar" & "linkedin-connector-1.0.0.zip" connector's component name should be "linkedin". Almost all the connectors follow this rule. But "file-connector-1.0.0.zip" connector's 'component name' is "fileconnector". Due to this issue DevS is having issues after importing File connector. Can we fix this ? Thanks, Viraj. On Mon, Jun 1, 2015 at 12:15 PM, Viraj Rajaguru <vi...@wso2.com> wrote: > Hi Keerthika, > > Wordpress connector is working properly now. > > Thanks, > Viraj. > > > > On Sun, May 31, 2015 at 10:01 AM, Keerthika Mahendralingam < > keerth...@wso2.com> wrote: > >> Hi Viraj, >> Wordpress connector is updated with the correct icons in Connector store. >> Please check now. >> >> >> Thanks, >> >> On Thu, May 28, 2015 at 2:40 PM, Keerthika Mahendralingam < >> keerth...@wso2.com> wrote: >> >>> Will check and let you know. >>> >>> On Thu, May 28, 2015 at 2:34 PM, Malaka Silva <mal...@wso2.com> wrote: >>> >>>> Connector team, >>>> >>>> Please check this. >>>> >>>> On Thu, May 28, 2015 at 2:32 PM, Viraj Rajaguru <vi...@wso2.com> wrote: >>>> >>>>> Hi connector team, >>>>> >>>>> Following two connectors cannot be imported to Developer Studio due to >>>>> missing/corrupted icons inside the connector[1]. Can you please have a >>>>> look >>>>> ? >>>>> >>>>> 1. You tube connector >>>>> 2. Wordpress connector >>>>> >>>>> Thanks, >>>>> Viraj. >>>>> >>>>> [1] - https://wso2.org/jira/browse/ESBCONNECT-47 >>>>> >>>>> -- >>>>> Viraj Rajaguru >>>>> Senior Software Engineer >>>>> WSO2 Inc. : http://wso2.com >>>>> >>>>> Mobile: +94 77 3683068 >>>>> >>>>> >>>>> >>>>> >>>>> ___ >>>>> Dev mailing list >>>>> Dev@wso2.org >>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>> >>>>> >>>> >>>> >>>> -- >>>> >>>> Best Regards, >>>> >>>> Malaka Silva >>>> Senior Tech Lead >>>> M: +94 777 219 791 >>>> Tel : 94 11 214 5345 >>>> Fax :94 11 2145300 >>>> Skype : malaka.sampath.silva >>>> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77 >>>> Blog : http://mrmalakasilva.blogspot.com/ >>>> >>>> WSO2, Inc. >>>> lean . enterprise . middleware >>>> http://www.wso2.com/ >>>> http://www.wso2.com/about/team/malaka-silva/ >>>> <http://wso2.com/about/team/malaka-silva/> >>>> >>>> Save a tree -Conserve nature & Save the world for your future. Print >>>> this email only if it is absolutely necessary. >>>> >>> >>> >>> >>> -- >>> <dev-requ...@wso2.org> >>> Keerthika Mahendralingam >>> Associate Software Engineer >>> Mobile :+94 (0) 776 121144 >>> keerth...@wso2.com >>> WSO2, Inc. >>> lean . enterprise . middleware >>> >> >> >> >> -- >> <dev-requ...@wso2.org> >> Keerthika Mahendralingam >> Associate Software Engineer >> Mobile :+94 (0) 776 121144 >> keerth...@wso2.com >> WSO2, Inc. >> lean . enterprise . middleware >> > > > > -- > Viraj Rajaguru > Senior Software Engineer > WSO2 Inc. : http://wso2.com > > Mobile: +94 77 3683068 > > > > -- Viraj Rajaguru Senior Software Engineer WSO2 Inc. : http://wso2.com Mobile: +94 77 3683068 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Cannot import some connectors to Developer studio.
Hi Malaka/Elimantha, Issue is with deserialization. To reproduce this issue, we can add a File connector operation in to a sequence or proxy. Then go to the source view and do any change in the source view and switch back to the graphical view. We can see it's not allowing us to switch to the graphical view. Is there any possibility to introduce a new attribute called 'version' into 'component' element in the component.xml to handle multiple version of connectors scenarios without adding the version into name attribute ? We can have a hangout to discuss this. Thanks, Viraj. On Wed, Sep 9, 2015 at 9:03 AM, Elilmatha Sivanesan <elilma...@wso2.com> wrote: > Hi Malaka > > Yes I have tested file connector, There are no issues now. > > Thank you. > > > > On Wed, Sep 9, 2015 at 7:05 AM, Malaka Silva <mal...@wso2.com> wrote: > >> Hi Viraj, >> >> I tried to reproduce the issue with the latest devs, and it does seems to >> be working fine. May be I missed something. >> >> Can we have a hangout to discuss this in the morning? >> >> However we should only focus on component.xml. Reason for that is we need >> to start with multiple version of the connectors. >> >> eg:- >> linkedin-connector-1.0.0.zip -> >> >> linkedin-connector-2.0.0.zip -> >> >> @Elilmatha I think we tested one by one in [1] with devs? There can't be >> any issues? >> [1] https://wso2.org/jira/browse/ESBCONNECT-63 >> >> On Wed, Sep 9, 2015 at 12:05 AM, Viraj Rajaguru <vi...@wso2.com> wrote: >> >>> Hi Connector team, >>> >>> There is a trivial issue in File connector. >>> >>> According to the current implementation in DevS, connector needs a file >>> name which comply with the 'component name' in the connector.xml. For an >>> example "googlecalendar-connector-1.0.0.zip" connector's component name >>> should be "googlecalendar" & "linkedin-connector-1.0.0.zip" >>> connector's component name should be "linkedin". Almost all the connectors >>> follow this rule. But "file-connector-1.0.0.zip" connector's 'component >>> name' is "fileconnector". Due to this issue DevS is having issues after >>> importing File connector. Can we fix this ? >>> >>> Thanks, >>> Viraj. >>> >>> On Mon, Jun 1, 2015 at 12:15 PM, Viraj Rajaguru <vi...@wso2.com> wrote: >>> >>>> Hi Keerthika, >>>> >>>> Wordpress connector is working properly now. >>>> >>>> Thanks, >>>> Viraj. >>>> >>>> >>>> >>>> On Sun, May 31, 2015 at 10:01 AM, Keerthika Mahendralingam < >>>> keerth...@wso2.com> wrote: >>>> >>>>> Hi Viraj, >>>>> Wordpress connector is updated with the correct icons in Connector >>>>> store. Please check now. >>>>> >>>>> >>>>> Thanks, >>>>> >>>>> On Thu, May 28, 2015 at 2:40 PM, Keerthika Mahendralingam < >>>>> keerth...@wso2.com> wrote: >>>>> >>>>>> Will check and let you know. >>>>>> >>>>>> On Thu, May 28, 2015 at 2:34 PM, Malaka Silva <mal...@wso2.com> >>>>>> wrote: >>>>>> >>>>>>> Connector team, >>>>>>> >>>>>>> Please check this. >>>>>>> >>>>>>> On Thu, May 28, 2015 at 2:32 PM, Viraj Rajaguru <vi...@wso2.com> >>>>>>> wrote: >>>>>>> >>>>>>>> Hi connector team, >>>>>>>> >>>>>>>> Following two connectors cannot be imported to Developer Studio due >>>>>>>> to missing/corrupted icons inside the connector[1]. Can you please >>>>>>>> have a >>>>>>>> look ? >>>>>>>> >>>>>>>> 1. You tube connector >>>>>>>> 2. Wordpress connector >>>>>>>> >>>>>>>> Thanks, >>>>>>>> Viraj. >>>>>>>> >>>>>>>> [1] - https://wso2.org/jira/browse/ESBCONNECT-47 >>>>>>>> >>>>>>>> -- >>>>>>>> Viraj Rajaguru >>>>>>>> Senior Software Engineer >>>>>>>> WSO2 Inc. : http://wso2.com >>&g
Re: [Dev] https://wso2.org/jira/browse/TOOLS-3005
Hi John, Please find attached patched jars in https://wso2.org/jira/browse/TOOLS-3005 Jira ticket. org.wso2.developerstudio.eclipse.gmf.esb.diagram_2.0.1.jar org.wso2.developerstudio.eclipse.gmf.esb.edit_2.0.1.jar org.wso2.developerstudio.eclipse.gmf.esb.persistence_2.0.1.jar org.wso2.developerstudio.eclipse.gmf.esb_2.0.1.jar Use following steps to apply patches. (i)Close eclipse if it is already started. (ii) Copy all the 4 bundles that are attached in the Jira to eclipse-home-directory/plugins directory. (iii) Restart Eclipse with -clean option from command line windows - eclipse.exe -clean linux - ./eclipse -clean (there after, you can start eclipse in the normal way) Please note that I couldn't test this patch on a MacOS. So let me know whether issue got resolved or not after applying the patch. Thanks, Viraj. On Wed, Aug 26, 2015 at 9:40 PM, John Hawkins jo...@wso2.com wrote: Hi all, Has anyone created this patch at all? If so - where would it be please ? many thanks ! John. John Hawkins Director: Solutions Architecture On Wed, Aug 19, 2015 at 4:43 PM, John Hawkins jo...@wso2.com wrote: Awesome response guys ! Will this patch be available to customers/opensource too ? John Hawkins Director: Solutions Architecture On Wed, Aug 19, 2015 at 1:58 PM, Rajeevan Vimalanathan rajeev...@wso2.com wrote: Hi Harshana, Thanks for pointing out this. You can find Oracle JDK bug report at [1]. [1] http://bugs.java.com/view_bug.do?bug_id=8027686 Thanks, Rajeevan On Wed, Aug 19, 2015 at 6:22 PM, Viraj Rajaguru vi...@wso2.com wrote: Hi John, Since you are having difficulties while installing Java 7u51 on your Mac, we have to patch DevS 3.7.1 to overcome this issue. Since we have already fixed this issue in master branch we will be able to provide a patched jar. Thanks, Viraj. On Wed, Aug 19, 2015 at 6:09 PM, Rajeevan Vimalanathan rajeev...@wso2.com wrote: Hi John, We just tried to install JDK 7u51 (.dmg) on Mac OS X 10.10.5 but getting the same error as you got. We initially checked this issue (switching between source and design view issue) with Mac OS X 10.9.x and found out that is solved with 7u51. That's why we recommended you to use 7u51 as a workaround. But now JDK installation fails on Mac OS X 10.10.x because of a known issue with JDK installer[1] and it has been fixed with 8u20. [1] https://bugs.openjdk.java.net/browse/JDK-8027686 Thanks, Rajeevan On Mon, Aug 17, 2015 at 6:30 PM, John Hawkins jo...@wso2.com wrote: I just tried to install 7u51 and it comes up with the following error - Your system has Mac OS X Version 10.10.3. This product can be installed on Version 10.7.3 or later. then dumps me out of the install :-( I'm guessing their installer has a problem with parsing the number '10' :-( I can't see a way to install other than through the .dmg (I'm new to mac but nothing comes back in google or the oracle site). Do you have any experience of this sort of thing ? many thanks, john. John Hawkins Director: Solutions Architecture On Sat, Aug 15, 2015 at 7:24 PM, Viraj Rajaguru vi...@wso2.com wrote: Hi John, Looking at the stack trace you provided in issue TOOLS-3005, I suspect that the same class loading issue described in TOOLS-2958[1] caused this issue. This class loading issue exists on MacOS with Java 7 update 55(7u55) and later updates. As a workaround we can use Java 7 update 51(7u51) with DevS 3.7.1 on Mac OS to avoid this issue. Can you please attach the full log($workspace/.metadata/.log) so that I can confirm the workaround. Thanks, Viraj. [1] - https://wso2.org/jira/browse/TOOLS-2958 On Fri, Aug 7, 2015 at 1:31 PM, John Hawkins jo...@wso2.com wrote: Hi Folks, re $subject. I've had this problem for ages now and it takes hours of my day to work around it. I've spoken about it before on this mailing list but the conversation kinda trailed off. This bug is now hitting me hard again - can anyone give me some of there time to fix? I know other users have had this in the past so it's not just me I suspect :-( many thanks, John. John Hawkins Director: Solutions Architecture ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Viraj Rajaguru Senior Software Engineer WSO2 Inc. : http://wso2.com Mobile: +94 77 3683068 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Vimalanathan Rajeevan Software Engineer, WSO2, Inc. *http://wso2.com* http://wso2.com Lean.Enterprise.Middleware Mobile: *+94 773090875 %2B94%20773090875* LinkedIn: *https://www.linkedin.com/in/RajeevanVimalanathan https://www.linkedin.com/in/rajeevanvimalanathan* -- Viraj Rajaguru Senior Software Engineer WSO2 Inc. : http://wso2.com Mobile: +94 77 3683068 -- Vimalanathan Rajeevan Software
Re: [Dev] https://wso2.org/jira/browse/TOOLS-3005
Hi John, Since you are having difficulties while installing Java 7u51 on your Mac, we have to patch DevS 3.7.1 to overcome this issue. Since we have already fixed this issue in master branch we will be able to provide a patched jar. Thanks, Viraj. On Wed, Aug 19, 2015 at 6:09 PM, Rajeevan Vimalanathan rajeev...@wso2.com wrote: Hi John, We just tried to install JDK 7u51 (.dmg) on Mac OS X 10.10.5 but getting the same error as you got. We initially checked this issue (switching between source and design view issue) with Mac OS X 10.9.x and found out that is solved with 7u51. That's why we recommended you to use 7u51 as a workaround. But now JDK installation fails on Mac OS X 10.10.x because of a known issue with JDK installer[1] and it has been fixed with 8u20. [1] https://bugs.openjdk.java.net/browse/JDK-8027686 Thanks, Rajeevan On Mon, Aug 17, 2015 at 6:30 PM, John Hawkins jo...@wso2.com wrote: I just tried to install 7u51 and it comes up with the following error - Your system has Mac OS X Version 10.10.3. This product can be installed on Version 10.7.3 or later. then dumps me out of the install :-( I'm guessing their installer has a problem with parsing the number '10' :-( I can't see a way to install other than through the .dmg (I'm new to mac but nothing comes back in google or the oracle site). Do you have any experience of this sort of thing ? many thanks, john. John Hawkins Director: Solutions Architecture On Sat, Aug 15, 2015 at 7:24 PM, Viraj Rajaguru vi...@wso2.com wrote: Hi John, Looking at the stack trace you provided in issue TOOLS-3005, I suspect that the same class loading issue described in TOOLS-2958[1] caused this issue. This class loading issue exists on MacOS with Java 7 update 55(7u55) and later updates. As a workaround we can use Java 7 update 51(7u51) with DevS 3.7.1 on Mac OS to avoid this issue. Can you please attach the full log($workspace/.metadata/.log) so that I can confirm the workaround. Thanks, Viraj. [1] - https://wso2.org/jira/browse/TOOLS-2958 On Fri, Aug 7, 2015 at 1:31 PM, John Hawkins jo...@wso2.com wrote: Hi Folks, re $subject. I've had this problem for ages now and it takes hours of my day to work around it. I've spoken about it before on this mailing list but the conversation kinda trailed off. This bug is now hitting me hard again - can anyone give me some of there time to fix? I know other users have had this in the past so it's not just me I suspect :-( many thanks, John. John Hawkins Director: Solutions Architecture ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Viraj Rajaguru Senior Software Engineer WSO2 Inc. : http://wso2.com Mobile: +94 77 3683068 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Vimalanathan Rajeevan Software Engineer, WSO2, Inc. *http://wso2.com* http://wso2.com Lean.Enterprise.Middleware Mobile: *+94 773090875 %2B94%20773090875* LinkedIn: *https://www.linkedin.com/in/RajeevanVimalanathan https://www.linkedin.com/in/rajeevanvimalanathan* -- Viraj Rajaguru Senior Software Engineer WSO2 Inc. : http://wso2.com Mobile: +94 77 3683068 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] https://wso2.org/jira/browse/TOOLS-3005
Hi John, Looking at the stack trace you provided in issue TOOLS-3005, I suspect that the same class loading issue described in TOOLS-2958[1] caused this issue. This class loading issue exists on MacOS with Java 7 update 55(7u55) and later updates. As a workaround we can use Java 7 update 51(7u51) with DevS 3.7.1 on Mac OS to avoid this issue. Can you please attach the full log($workspace/.metadata/.log) so that I can confirm the workaround. Thanks, Viraj. [1] - https://wso2.org/jira/browse/TOOLS-2958 On Fri, Aug 7, 2015 at 1:31 PM, John Hawkins jo...@wso2.com wrote: Hi Folks, re $subject. I've had this problem for ages now and it takes hours of my day to work around it. I've spoken about it before on this mailing list but the conversation kinda trailed off. This bug is now hitting me hard again - can anyone give me some of there time to fix? I know other users have had this in the past so it's not just me I suspect :-( many thanks, John. John Hawkins Director: Solutions Architecture ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Viraj Rajaguru Senior Software Engineer WSO2 Inc. : http://wso2.com Mobile: +94 77 3683068 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Script Mediator Error in Developer Studio 3.7.1
)
at org.mozilla.javascript.Context.compileReader(Context.java:1310)
at org.mozilla.javascript.Context.compileReader(Context.java:1282)
at
com.sun.phobos.script.javascript.RhinoScriptEngine.compile(RhinoScriptEngine.java:337)
It seems this is because of using CDATA notations and it seems it is not
a bug according to [1]. Please confirm.
[1] https://wso2.org/jira/browse/TOOLS-1543
Thanks,
Sohani
Sohani Weerasinghe
Software Engineer
WSO2, Inc: http://wso2.com
Mobile : +94 716439774
Blog :http://christinetechtips.blogspot.com/
Twitter : https://twitter.com/sohanichristine
On Tue, Jul 28, 2015 at 7:28 AM, Jasintha Dasanayake jasin...@wso2.com
wrote:
On Tue, Jul 28, 2015 at 7:07 AM, Sohani Weerasinghe soh...@wso2.com
wrote:
Hi Nuwan,
It seems this exception occurs in ScriptMediator.java (at
org.apache.synapse.mediators.bsf - line 354) when trying to compile the
script.
*compiledScript = ((Compilable)
scriptEngine).compile(scriptSourceCode);*
if this line give an error that mean script has some issue , @Sohani
what is the error thrown by bsf ?
/Jasintha
@Jasintha/ Viraj : This can be reproduced even in linux and any idea
about this error?
@Nuwan: The error log can be found at the workspace of the project at
/.metadata/.log
Thanks,
Sohani
Sohani Weerasinghe
Software Engineer
WSO2, Inc: http://wso2.com
Mobile : +94 716439774
Blog :http://christinetechtips.blogspot.com/
Twitter : https://twitter.com/sohanichristine
On Tue, Jul 28, 2015 at 5:43 AM, Nuwan Dias nuw...@wso2.com wrote:
Hi,
I'm using Developer Studio version 3.7.1 on MacOS. When I try to use
the Script Mediator within an API Resource's in-sequence, it doesn't allow
me to save the API and gives an error. The following is the error message
*Save failed. Following error(s) have been detected. Please see the
error log for more details.*
*Reason:*
*Exception initializing inline script*
And following is the content of the javascript
*![CDATA[*
*var doctorId =
mc.getPayloadJSON().createChannelRecord.doctorId.toString();*
*var patientName =
mc.getPayloadJSON().createChannelRecord.patientName.toString();*
*var date =
mc.getPayloadJSON().createChannelRecord.date.toString();*
*var time =
mc.getPayloadJSON().createChannelRecord.time.toString();*
*mc.setPayloadXML(*
*ser:createChannelRecord
xmlns:ser=http://com.example.service/ http://com.example.service/*
* doctorId{doctorId}/doctorId*
* patientName{patientName}/patientName*
* date{date}/date*
* time{time}/time*
*/ser:createChannelRecord*
* );*
*]]*
Any ideas about this error? Where can I find additional logs? The same
script works fine if I create an API using the management console of the
ESB.
Thanks,
NuwanD.
--
Nuwan Dias
Technical Lead - WSO2, Inc. http://wso2.com
email : nuw...@wso2.com
Phone : +94 777 775 729
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
--
*Jasintha Dasanayake*
*Senior Software EngineerWSO2 Inc. | http://wso2.com
http://wso2.com/lean . enterprise . middleware*
*mobile :- 0711368118 0711368118*
--
Nuwan Dias
Technical Lead - WSO2, Inc. http://wso2.com
email : nuw...@wso2.com
Phone : +94 777 775 729
--
Viraj Rajaguru
Senior Software Engineer
WSO2 Inc. : http://wso2.com
Mobile: +94 77 3683068
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Script Mediator Error in Developer Studio 3.7.1
[Correction] On Tue, Jul 28, 2015 at 11:52 AM, Viraj Rajaguru vi...@wso2.com wrote: Hi Nuwan, There is a class loading issue in DevS 3.7.1 on MacOS with Java 7 update 55(7u55) and later updates. That's because you are getting the same issue irrespective of having CDATA tags or not in the payload.(There shouldn't be any issue if you enter the JS script without CDATA tag as Sohani mentioned.) Please use Java 7 update 55(7u55) with DevS 3.7.1 on Mac OS to avoid this issue.(This issue[1] has been fixed in the DevS master branch) Please use Java 7 update 51(7u51) with DevS 3.7.1 on Mac OS to avoid this issue And also we have done an improvement to Script mediator to persist the CDATA tag in the source view.[2] This fix is also available in the DevS master branch. Thanks, Viraj. [1] - https://wso2.org/jira/browse/TOOLS-2958 [2] - https://wso2.org/jira/browse/TOOLS-2730 On Tue, Jul 28, 2015 at 8:39 AM, Nuwan Dias nuw...@wso2.com wrote: I doubt its due to the CDATA tags. I tried both with and without CDATA tags, but it throws the same error always. I even tried providing the content through the source editor, but saving from the source editor also gives the same error. Please note that an API with the exact configuration can be deployed on ESB 4.8.1 without any issues. However, for the script to execute correctly the CDATA tags are required. If the CDATA tags were missing, it would throw the following exception at runtime (only). *org.mozilla.javascript.EvaluatorException: Can't find method org.apache.synapse.mediators.bsf.ScriptMessageContext.setPayloadXML().* Thanks, NuwanD. On Tue, Jul 28, 2015 at 7:45 AM, Sohani Weerasinghe soh...@wso2.com wrote: Hi Jasintha, This is the error I am getting org.apache.synapse.SynapseException: Exception initializing inline script at org.apache.synapse.mediators.bsf.ScriptMediator.initInlineScript(ScriptMediator.java:365) at org.apache.synapse.mediators.bsf.ScriptMediator.init(ScriptMediator.java:152) at org.wso2.developerstudio.eclipse.gmf.esb.internal.persistence.ScriptMediatorTransformer.createScriptMediator(ScriptMediatorTransformer.java:58) at org.wso2.developerstudio.eclipse.gmf.esb.internal.persistence.ScriptMediatorTransformer.transformWithinSequence(ScriptMediatorTransformer.java:45) at org.wso2.developerstudio.eclipse.gmf.esb.internal.persistence.AbstractEsbNodeTransformer.doTransformWithinSequence(AbstractEsbNodeTransformer.java:118) at org.wso2.developerstudio.eclipse.gmf.esb.internal.persistence.SequenceTransformer.transformWithinSequence(SequenceTransformer.java:88) at org.wso2.developerstudio.eclipse.gmf.esb.internal.persistence.DefaultEsbModelExporter.transformSequence(DefaultEsbModelExporter.java:193) at org.wso2.developerstudio.eclipse.gmf.esb.internal.persistence.DefaultEsbModelExporter.designToSource(DefaultEsbModelExporter.java:349) at org.wso2.developerstudio.eclipse.gmf.esb.diagram.part.EsbMultiPageEditor.updateAssociatedXMLFile(EsbMultiPageEditor.java:593) at org.wso2.developerstudio.eclipse.gmf.esb.diagram.part.EsbMultiPageEditor.doSave(EsbMultiPageEditor.java:676) at org.eclipse.ui.internal.SaveableHelper$2.run(SaveableHelper.java:154) at org.eclipse.ui.internal.SaveableHelper$5.run(SaveableHelper.java:283) at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:466) at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:374) at org.eclipse.ui.internal.WorkbenchWindow$13.run(WorkbenchWindow.java:2157) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.ui.internal.WorkbenchWindow.run(WorkbenchWindow.java:2153) at org.eclipse.ui.internal.SaveableHelper.runProgressMonitorOperation(SaveableHelper.java:291) at org.eclipse.ui.internal.SaveableHelper.runProgressMonitorOperation(SaveableHelper.java:269) at org.eclipse.ui.internal.SaveableHelper.savePart(SaveableHelper.java:159) at org.eclipse.ui.internal.WorkbenchPage.saveSaveable(WorkbenchPage.java:3915) at org.eclipse.ui.internal.WorkbenchPage.saveEditor(WorkbenchPage.java:3929) at org.eclipse.ui.internal.handlers.SaveHandler.execute(SaveHandler.java:54) at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:294) at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90) 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.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:55) at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:247) at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:229) at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke
Re: [Dev] Unsupported mediators for custom mediation flows in API Manager
Hi Nuwan, These are the mediators that are available in ESB graphical sequence editor. Call CallTemplate Drop Log Loopback Property Respond Send Sequence Store ConditionalRouter Filter Switch Validate Bean Class Command EJB Script Spring Enrich Fault Header PayloadFactory Smooks URLRewrite XQuery XSLT FastXSLT Cache DBLookup DBReport Enqueue Event RMSequence Throttle Transaction Aggregate Callout Clone Iterate ForEach Entitlement OAuth Builder Rule BAM PublishEvent On Wed, Jul 15, 2015 at 7:59 PM, Nuwan Dias nuw...@wso2.com wrote: Can you list the mediators so we can go through it and see? On Wed, Jul 15, 2015 at 6:05 PM, Viraj Rajaguru vi...@wso2.com wrote: Hi APIM team, DevS team is adding the support to add, remove, edit custom mediation flows in API Manager by connecting to the remote APIM server using Developer Studio. Since we are reusing the same ESB graphical sequence editor for APIM, currently it will list all the available mediators(supported by ESB) in the tool palette. Do we support all the mediators supported by ESB in APIM ? If not can we have a list of unsupported mediators so that we can remove them from the tool palette. Thanks, Viraj. -- Viraj Rajaguru Senior Software Engineer WSO2 Inc. : http://wso2.com Mobile: +94 77 3683068 -- Nuwan Dias Technical Lead - WSO2, Inc. http://wso2.com email : nuw...@wso2.com Phone : +94 777 775 729 -- Viraj Rajaguru Senior Software Engineer WSO2 Inc. : http://wso2.com Mobile: +94 77 3683068 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Unsupported mediators for custom mediation flows in API Manager
Hi APIM team, DevS team is adding the support to add, remove, edit custom mediation flows in API Manager by connecting to the remote APIM server using Developer Studio. Since we are reusing the same ESB graphical sequence editor for APIM, currently it will list all the available mediators(supported by ESB) in the tool palette. Do we support all the mediators supported by ESB in APIM ? If not can we have a list of unsupported mediators so that we can remove them from the tool palette. Thanks, Viraj. -- Viraj Rajaguru Senior Software Engineer WSO2 Inc. : http://wso2.com Mobile: +94 77 3683068 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Architecture] Deploying an ESB Connector with a cApp?
-deployers/org.wso2.carbon.application.deployer.synapse/src/main/java/org/wso2/carbon/application/deployer/synapse/SynapseAppDeployer.java Thank you. On Tue, Jul 7, 2015 at 4:22 PM, Kasun Indrasiri ka...@wso2.com wrote: Any progress on this task? On Thu, Jul 2, 2015 at 11:09 PM, Malaka Silva mal...@wso2.com wrote: Hi All, Shakila will be starting to implement this functionality from ESB side. @Shakila - Any blockers user this mail thread to discuss. On Tue, Jun 30, 2015 at 5:57 PM, Jasintha Dasanayake jasin...@wso2.com wrote: From tooling perspective, this is similar to class mediator deployment using Capp , Since Capp class mediator deployment now working fine with Capp so this can be done , However this is also kind of sever extension so we have to educate the users to use this properly. Thanks and Regards /Jasintha On Tue, Jun 30, 2015 at 5:11 PM, Kasun Indrasiri ka...@wso2.com wrote: Hi, AFAIR, this was discussed several times. But in the context of ESB as a service, I think this will be quite useful. I don't think we have any technical difficulty in doing this. Use case : - We want to invoke a twitter operation. - Import the twitter connector from connector-store( into DevS) and use the twitter connector operation in our mediation logic. - Now we want to deploy the artifact into ESB but it is required to deploy/enable the connector beforehand. (If the connector is not deployed in the ESB instance, this config deployment will fail.) - If we can include the connector as part of the cApp, then the connector deployment is completely transparent to the users. WDYT? -- Kasun Indrasiri Software Architect WSO2, Inc.; http://wso2.com lean.enterprise.middleware cell: +94 77 556 5206 Blog : http://kasunpanorama.blogspot.com/ -- *Jasintha Dasanayake* *Senior Software EngineerWSO2 Inc. | http://wso2.com http://wso2.com/lean . enterprise . middleware* *mobile :- 0711368118 0711368118* -- Best Regards, Malaka Silva Senior Tech Lead M: +94 777 219 791 Tel : 94 11 214 5345 Fax :94 11 2145300 Skype : malaka.sampath.silva LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77 Blog : http://mrmalakasilva.blogspot.com/ WSO2, Inc. lean . enterprise . middleware http://www.wso2.com/ http://www.wso2.com/about/team/malaka-silva/ http://wso2.com/about/team/malaka-silva/ Save a tree -Conserve nature Save the world for your future. Print this email only if it is absolutely necessary. -- Kasun Indrasiri Software Architect WSO2, Inc.; http://wso2.com lean.enterprise.middleware cell: +94 77 556 5206 Blog : http://kasunpanorama.blogspot.com/ -- Shakila Sivagnanarajah Associate Software Engineer Mobile :+94 (0) 770 760240 shak...@wso2.com -- *Jasintha Dasanayake* *Senior Software EngineerWSO2 Inc. | http://wso2.com http://wso2.com/lean . enterprise . middleware* *mobile :- 0711368118 0711368118* ___ Architecture mailing list architect...@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture -- Dushan Abeyruwan | Technical Lead Technical Support-Bloomington US PMC Member Apache Synpase WSO2 Inc. http://wso2.com/ Blog:*http://www.dushantech.com/ http://www.dushantech.com/* Mobile:(001)812-391-7441 -- Shakila Sivagnanarajah Associate Software Engineer Mobile :+94 (0) 770 760240 shak...@wso2.com -- Shakila Sivagnanarajah Associate Software Engineer Mobile :+94 (0) 770 760240 shak...@wso2.com -- Best Regards, Malaka Silva Senior Tech Lead M: +94 777 219 791 Tel : 94 11 214 5345 Fax :94 11 2145300 Skype : malaka.sampath.silva LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77 Blog : http://mrmalakasilva.blogspot.com/ WSO2, Inc. lean . enterprise . middleware http://www.wso2.com/ http://www.wso2.com/about/team/malaka-silva/ http://wso2.com/about/team/malaka-silva/ Save a tree -Conserve nature Save the world for your future. Print this email only if it is absolutely necessary. -- Shakila Sivagnanarajah Associate Software Engineer Mobile :+94 (0) 770 760240 shak...@wso2.com -- Shakila Sivagnanarajah Associate Software Engineer Mobile :+94 (0) 770 760240 shak...@wso2.com -- Kasun Indrasiri Software Architect WSO2, Inc.; http://wso2.com lean.enterprise.middleware cell: +94 77 556 5206 Blog : http://kasunpanorama.blogspot.com/ -- Viraj Rajaguru Senior Software Engineer WSO2 Inc. : http://wso2.com Mobile: +94 77 3683068 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Fwd: Governance registry Endpoint collection not created by default
Hi John, On Wed, Jul 8, 2015 at 4:10 PM, John Hawkins jo...@wso2.com wrote: I'm following our ESB lab and in lab 14 (embedded registry) it tells me to 1) create a new registry resource project 2) create a new address endpoint 3) make it a dynamic endpoint 4) select the registry project I just created 5) target to the governance registry/endpoints path However - when i follow those steps, there is no endpoints path. So I'm wondering how to get that endpoints path. You seem to say that it's created automatically - but how does that work in this case? I would split your step 5 into two steps. 5.1 - Target to the governance registry and click OK(See attached selectParent.png). Still there is no endpoints collection under governance registry and there will be only event, permission, repository and trunk collections. Once you select the governance registry and click OK, content of Registry Path text box will be gov: 5.2 Then add /endpoints string part at the end of gov: manually and click finish. When you click finish, the content of Registry Path text box should be gov:/endpoints. Please note that still there is no collection called endpoints in the governance registry. As Kishanthan mentioned in his previous comment, while the deployment of this endpoint(registry resource), a collection called endpoints will be created inside the governance registry and this endpoint will be deployed to gov:/endpoints path. (Additionally, if you set gov:/foo/bar as the registry path from Developer Studio, while the deployment foo bar collections will be created) Thanks, Viraj. many thanks, John. John Hawkins Director: Solutions Architecture On Wed, Jul 8, 2015 at 10:42 AM, Kishanthan Thangarajah kishant...@wso2.com wrote: Hi John, Are you trying out the registry resource project from dev-studio? If there are endpoints added under a specific registry path, then it should be created automatically at ESB when you deploy registry resource project from dev-studio. But by default - event, permission, repository and trunk collections are found under the governance collection. And any newly added collections from dev-studio will be added to ESB registry space by deploying the registry resource project. Let me also add some dev-studio team members to this thread to get some better responses, if the above does not provide information on what you seek. Thanks, On Wed, Jul 8, 2015 at 2:42 PM, John Hawkins jo...@wso2.com wrote: Hi Folks, any thoughts on this - is it a bug or expected behaviour ? many thanks, John, John Hawkins Director: Solutions Architecture On Mon, Jul 6, 2015 at 10:59 AM, John Hawkins jo...@wso2.com wrote: Hi Folks, Using the ESB v4.8.1; I've just created a new governance registry using dev studio v3.7.1 and I see that it's created the collections: event, permission, repository and trunk collections under the governance context. But, it hasn't created the endpoint collection though. Should it have done? And, if I have to create it manually, are there any instructions on what has to go under the governance/endpoints/ collection? many thanks, John. John Hawkins Director: Solutions Architecture ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Kishanthan Thangarajah* Associate Technical Lead, Platform Technologies Team, WSO2, Inc. lean.enterprise.middleware Mobile - +94773426635 Blog - *http://kishanthan.wordpress.com http://kishanthan.wordpress.com* Twitter - *http://twitter.com/kishanthan http://twitter.com/kishanthan* -- Viraj Rajaguru Senior Software Engineer WSO2 Inc. : http://wso2.com Mobile: +94 77 3683068 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] DevStudio errors
Hi John, Currently there are two types of ESB editors in DevS 3.7.1. 1. Tree structured ESB editor (deprecated) 2. Drag and drop ESB diagram editor (recommended) Deprecated tree structured ESB editor is outdated and we are not maintaining it.(We are removing this deprecated editor in next DevS 3.8.0 release). You are getting saving issues/design to source switching issues with old editor because it's outdated. So the solution here is to open ESB config files using recommended ESB editor by just double clicking on the config file. (Double click event will trigger config file to open in the recommended ESB diagram editor.) Using other options such as Right click on config file -- Open With -- ESB Editor, use Ctrl + Shift + R to open config files, will result to open config files in deprecated ESB editor. It seems mentioned *java.lang.NullPointerException *exception is not the root cause for the issues. Please attach the full error log($workspace/.metadata/.log) to check the actual error. Thanks, Viraj. On Thu, Jul 2, 2015 at 5:47 PM, John Hawkins jo...@wso2.com wrote: Sorry- I meant to put that in the original message !! Here is the data section of the error in eclipse eclipse.buildId=4.3.2.M20140221-1700 java.version=1.7.0_79 java.vendor=Oracle Corporation BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=en_US Framework arguments: -product org.eclipse.epp.package.jee.product -keyring /Users/wso2/.eclipse_keyring -showlocation Command-line arguments: -os macosx -ws cocoa -arch x86_64 -product org.eclipse.epp.package.jee.product -keyring /Users/wso2/.eclipse_keyring -showlocation And I downloaded devstudio (3.7.1) right of the wso2.com pages (two days ago) - as a single, eclipse included, bundle - *not* installed into a pre-existing eclipse. thanks, John. John Hawkins Director: Solutions Architecture On Thu, Jul 2, 2015 at 12:39 PM, Harshana Eranga Martin harshan...@gmail.com wrote: Hi John, What is the Dev Studio version you are using? Did you download it from the Products listing in wso2.com? What is the JDK version you are using? Thanks and Regards, Harshana -- Harshana Eranga Martin Committer - Eclipse ECF: http://www.eclipse.org/ecf/ Blog: http://harshana05.blogspot.com Profile: https://www.google.com/profiles/harshana05 On 2 July 2015 at 19:29, John Hawkins jo...@wso2.com wrote: Hi Folks, I'm getting a few errors with DevStudio which are really beginning to bug me. I can't see anyone else having these errors so I'll put it out there so you folks may be able to guide me as to what to do ( or you may have seen them before but google has let me down :-) Key problem is that eclipse/dev studio is struggling to save files e.g. an api.xml file or a proxy-service.xml file. This shows itself when I try to save a diagram or when I try to move from the diagram to the source view. The first error in the chain is... *Problems occurred when invoking code from plug-in: org.eclipse.ui.workbench. which has the stacktrace of * *java.lang.NullPointerException* * at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.selectionChanged(CompatibilityPart.java:435)* * at org.eclipse.ui.part.MultiPageSelectionProvider$1.run(MultiPageSelectionProvider.java:110)* * at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)* * at org.eclipse.ui.part.MultiPageSelectionProvider.fireEventChange(MultiPageSelectionProvider.java:108)* * etc.etc.* It then has three other errors along those lines. This may or may not be related but.What also happens is that files also don't look right in the esb editor.. They come out as a tree structure and not the nice diagram editor. In order to get around this (and get it opening in the nice diagram editor) I have to close the WSO2 ESB Graphical perspective and then re-open the Dev Studio (by going Dev Studio-Open Dashboard. That solves the problem of the editor not showing the graphical view and also seems to solve the problem of file saving. However, it's not long before both problems come back - but I have no idea what sequence of events makes them come back ! I realise this is a bit of a random problem - but it's really making editing a very long winded process so any help would be much appreciated !! many thanks John. John Hawkins Director: Solutions Architecture ___ 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 -- Viraj Rajaguru Senior Software Engineer WSO2 Inc. : http://wso2.com Mobile: +94 77 3683068 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] XML Comments support in ESB configurations - Dev Studio update
Hi Jagath, Currenlty org.apache.synapse.mediators.AbstractMediator.getCommentsList() and org.apache.synapse.mediators.AbstractMediator.setCommentsList(ListString) methods haven't been defined in org.apache.synapse.Mediator interface. Did we do this intentionally ? It will be more convenient for us to have these two methods in org.apache.synapse.Mediator interface because we are relying on org.apache.synapse.Mediator interface to manipulate generic attributes such as shortDescription in our code. Is it possible to define these methods in the org.apache.synapse.Mediator interface ? Thanks, Viraj. On Sun, May 10, 2015 at 10:01 PM, Viraj Rajaguru vi...@wso2.com wrote: Hi Jagath, Thanks for informing us. We will use latest Synapse and Carbon libraries which contain this fix and do the relevant changes in DevS side to incorporate this feature. Thanks, Viraj. On Sun, May 10, 2015 at 6:47 PM, Jagath Sisirakumara Ariyarathne jaga...@wso2.com wrote: Hi DS Team, XML comments support in ESB configurations has been implemented to fix the Jira [1] with related documentation in [2]. [1] - https://wso2.org/jira/browse/ESBJAVA-3673 [2] - https://docs.google.com/document/d/1SRHBiCdXsZvvTDeX0qONzag8qbBRzh7ks9xNywyNrXA/edit#heading=h.6a7z1ncf8cph Could you please do the needful to incorporate changes required in Dev Studio editors for the $subject. Related PRs for synapse and carbon-mediation sources can be found in [3],[4]; [3] - https://github.com/wso2/wso2-synapse/pull/137 [4] - https://github.com/wso2/carbon-mediation/pull/105 Thanks. -- Jagath Ariyarathne Technical Lead WSO2 Inc. http://wso2.com/ Email: jaga...@wso2.com Mob : +94 77 386 7048 -- Viraj Rajaguru Senior Software Engineer WSO2 Inc. : http://wso2.com Mobile: +94 77 3683068 -- Viraj Rajaguru Senior Software Engineer WSO2 Inc. : http://wso2.com Mobile: +94 77 3683068 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [DevStudio] [ESB] Including ForEach mediator in Developer Studio
Hi Maheeka, We have started implementing ForEach mediator targeting DevS 3.8.0. This mediator will be available in future milestone releases of DevS 3.8.0. Thanks, Viraj. On Wed, Jun 3, 2015 at 2:57 PM, Maheeka Jayasuriya mahe...@wso2.com wrote: Hi DevS Team, With ESB 4.9.0 we are introducing a new mediator - ForEach mediator. Please find the documentation at [1]. Please let know how to proceed on $subject. [1] https://docs.wso2.com/display/ESB490/ForEach+Mediator Thanks, Maheeka Jayasuriya Software Engineer Mobile : +9450661 -- Viraj Rajaguru Senior Software Engineer WSO2 Inc. : http://wso2.com Mobile: +94 77 3683068 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Cannot import some connectors to Developer studio.
Hi Keerthika, Wordpress connector is working properly now. Thanks, Viraj. On Sun, May 31, 2015 at 10:01 AM, Keerthika Mahendralingam keerth...@wso2.com wrote: Hi Viraj, Wordpress connector is updated with the correct icons in Connector store. Please check now. Thanks, On Thu, May 28, 2015 at 2:40 PM, Keerthika Mahendralingam keerth...@wso2.com wrote: Will check and let you know. On Thu, May 28, 2015 at 2:34 PM, Malaka Silva mal...@wso2.com wrote: Connector team, Please check this. On Thu, May 28, 2015 at 2:32 PM, Viraj Rajaguru vi...@wso2.com wrote: Hi connector team, Following two connectors cannot be imported to Developer Studio due to missing/corrupted icons inside the connector[1]. Can you please have a look ? 1. You tube connector 2. Wordpress connector Thanks, Viraj. [1] - https://wso2.org/jira/browse/ESBCONNECT-47 -- Viraj Rajaguru Senior Software Engineer WSO2 Inc. : http://wso2.com Mobile: +94 77 3683068 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Best Regards, Malaka Silva Senior Tech Lead M: +94 777 219 791 Tel : 94 11 214 5345 Fax :94 11 2145300 Skype : malaka.sampath.silva LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77 Blog : http://mrmalakasilva.blogspot.com/ WSO2, Inc. lean . enterprise . middleware http://www.wso2.com/ http://www.wso2.com/about/team/malaka-silva/ http://wso2.com/about/team/malaka-silva/ Save a tree -Conserve nature Save the world for your future. Print this email only if it is absolutely necessary. -- dev-requ...@wso2.org Keerthika Mahendralingam Associate Software Engineer Mobile :+94 (0) 776 121144 keerth...@wso2.com WSO2, Inc. lean . enterprise . middleware -- dev-requ...@wso2.org Keerthika Mahendralingam Associate Software Engineer Mobile :+94 (0) 776 121144 keerth...@wso2.com WSO2, Inc. lean . enterprise . middleware -- Viraj Rajaguru Senior Software Engineer WSO2 Inc. : http://wso2.com Mobile: +94 77 3683068 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Cannot import some connectors to Developer studio.
Hi connector team, Following two connectors cannot be imported to Developer Studio due to missing/corrupted icons inside the connector[1]. Can you please have a look ? 1. You tube connector 2. Wordpress connector Thanks, Viraj. [1] - https://wso2.org/jira/browse/ESBCONNECT-47 -- Viraj Rajaguru Senior Software Engineer WSO2 Inc. : http://wso2.com Mobile: +94 77 3683068 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] XML Comments support in ESB configurations - Dev Studio update
Hi Jagath, Thanks for informing us. We will use latest Synapse and Carbon libraries which contain this fix and do the relevant changes in DevS side to incorporate this feature. Thanks, Viraj. On Sun, May 10, 2015 at 6:47 PM, Jagath Sisirakumara Ariyarathne jaga...@wso2.com wrote: Hi DS Team, XML comments support in ESB configurations has been implemented to fix the Jira [1] with related documentation in [2]. [1] - https://wso2.org/jira/browse/ESBJAVA-3673 [2] - https://docs.google.com/document/d/1SRHBiCdXsZvvTDeX0qONzag8qbBRzh7ks9xNywyNrXA/edit#heading=h.6a7z1ncf8cph Could you please do the needful to incorporate changes required in Dev Studio editors for the $subject. Related PRs for synapse and carbon-mediation sources can be found in [3],[4]; [3] - https://github.com/wso2/wso2-synapse/pull/137 [4] - https://github.com/wso2/carbon-mediation/pull/105 Thanks. -- Jagath Ariyarathne Technical Lead WSO2 Inc. http://wso2.com/ Email: jaga...@wso2.com Mob : +94 77 386 7048 -- Viraj Rajaguru Senior Software Engineer WSO2 Inc. : http://wso2.com Mobile: +94 77 3683068 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [DevStudio] Please review and merge the pull request : TOOLS-2723
Merged. Thanks, Viraj. On Mon, Mar 2, 2015 at 3:35 PM, Rajeevan Vimalanathan rajeev...@wso2.com wrote: Hi, Please review and merge the pull request[1] that includes fix for JIRA[2]. [1] https://github.com/wso2/cloud-dev-studio/pull/4 [2] https://wso2.org/jira/browse/TOOLS-2723 Thanks, Rajeevan -- Best Regards, V.Rajeevan Software Engineer, WSO2 Inc. :http://wso2.com Mobile : +94 773090875 Email : rajeev...@wso2.com -- Viraj Rajaguru Senior Software Engineer WSO2 Inc. : http://wso2.com Mobile: +94 77 3683068 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [DevStudio] Please review and merge the pull request : TOOLS-2726
Merged. Thanks, Viraj. On Thu, Feb 26, 2015 at 9:43 PM, Rajeevan Vimalanathan rajeev...@wso2.com wrote: Hi, Please review and merge the pull request[1] that includes fix for JIRA[2]. [1] https://github.com/wso2/cloud-dev-studio/pull/3 [2] https://wso2.org/jira/browse/TOOLS-2726 Thanks, Rajeevan -- Best Regards, V.Rajeevan Software Engineer, WSO2 Inc. :http://wso2.com Mobile : +94 773090875 Email : rajeev...@wso2.com -- Viraj Rajaguru Senior Software Engineer WSO2 Inc. : http://wso2.com Mobile: +94 77 3683068 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [DevStudio] Please review and merge the pull request : TOOLS-2721
Merged. Thanks, Viraj. On Thu, Feb 26, 2015 at 12:52 PM, Rajeevan Vimalanathan rajeev...@wso2.com wrote: Hi, Please review and merge the pull request[1] that includes fix for JIRA[2]. [1] https://github.com/wso2/cloud-dev-studio/pull/2 [2] https://wso2.org/jira/browse/TOOLS-2721 Thanks, Rajeevan -- Best Regards, V.Rajeevan Software Engineer, WSO2 Inc. :http://wso2.com Mobile : +94 773090875 Email : rajeev...@wso2.com -- Viraj Rajaguru Senior Software Engineer WSO2 Inc. : http://wso2.com Mobile: +94 77 3683068 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [DevStudio] Please review and merge the pull request : TOOLS-2722
Merged. Thanks, Viraj. On Wed, Feb 25, 2015 at 6:21 PM, Rajeevan Vimalanathan rajeev...@wso2.com wrote: Hi, Please review and merge the pull request[1] that includes fix for JIRA[2]. [1] https://github.com/wso2/cloud-dev-studio/pull/1 [2] https://wso2.org/jira/browse/TOOLS-2722 Thanks, Rajeevan -- Best Regards, V.Rajeevan Software Engineer, WSO2 Inc. :http://wso2.com Mobile : +94 773090875 Email : rajeev...@wso2.com -- Viraj Rajaguru Senior Software Engineer WSO2 Inc. : http://wso2.com Mobile: +94 77 3683068 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [DevStudio] Please review and merge the pull request : TOOLS-2715
Merged. Thanks, Viraj. On Wed, Feb 25, 2015 at 12:05 PM, Rajeevan Vimalanathan rajeev...@wso2.com wrote: Hi, Please review and merge the pull request[1] that includes fix for JIRA[2]. [1] https://github.com/wso2/developer-studio/pull/45 [2] https://wso2.org/jira/browse/TOOLS-2715 Thanks, Rajeevan -- Best Regards, V.Rajeevan Software Engineer, WSO2 Inc. :http://wso2.com Mobile : +94 773090875 Email : rajeev...@wso2.com -- Viraj Rajaguru Senior Software Engineer WSO2 Inc. : http://wso2.com Mobile: +94 77 3683068 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [DevStudio] Please review and merge the pull request : TOOLS-2308
Merged. Thanks, Viraj. On Wed, Feb 25, 2015 at 11:06 AM, Rajeevan Vimalanathan rajeev...@wso2.com wrote: Hi, Please review and merge the pull request[1] that includes fix for JIRA[2]. [1] https://github.com/wso2/developer-studio/pull/44 [2] https://wso2.org/jira/browse/TOOLS-2308 Thanks, Rajeevan -- Best Regards, V.Rajeevan Software Engineer, WSO2 Inc. :http://wso2.com Mobile : +94 773090875 Email : rajeev...@wso2.com -- Viraj Rajaguru Senior Software Engineer WSO2 Inc. : http://wso2.com Mobile: +94 77 3683068 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [DevStudio] Please review and merge the pull request : TOOLS-2694
Merged. Thanks, Viraj. On Thu, Feb 12, 2015 at 1:56 PM, Rajeevan Vimalanathan rajeev...@wso2.com wrote: Hi, Please review and merge the pull request[1] that contains fix for JIRA[2]. [1] https://github.com/wso2/developer-studio/pull/40 [2] https://wso2.org/jira/browse/TOOLS-2694 Thanks, Rajeevan -- Best Regards, V.Rajeevan Software Engineer, WSO2 Inc. :http://wso2.com Mobile : +94 773090875 Email : rajeev...@wso2.com -- Viraj Rajaguru Senior Software Engineer WSO2 Inc. : http://wso2.com Mobile: +94 77 3683068 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Implementing eclipse che AppServer plugin
Hi, Since Eclipse Che currently does not support for creating JAX-RS and JAX-WS projects and we are going to implement project types for JAX-RS and JAX-WS for Eclipse Che, I think its better to categorize them under Java -- Maven category not under the WSO2 category.(Following the convention for existing webapps creation in Eclipse Che) Thanks, Viraj. On Thu, Feb 5, 2015 at 9:35 PM, Susinda Perera susi...@wso2.com wrote: Hi All We are in the process of $subject. One of the decision point we faced is how to implement the 3 level project hierarchy as i have discussed in the below mail. (added below[1] is the mail discussion i had with codenvy team). According to them there is no such option in 3.5.0 release but will be there in 3.7.0. However the plugin we already being developing is handled this issue by having a wizard page. But according to the training we had it seems that better way to do this is by having project generator for each project. Therefore i think till we got that thing implemented by codenvy we could go in a project structure as one of the options(1, 2) below. [opt1] WSO2 ESB -- ESB config project WSO2 AppServer -- webapp project -- JAX-WS project -- JAX-RS project [opt2] WSO2 -- ESB project -- AppServer JAX-WS projet -- AppServer JAX-RS projet -- AppServer webapp projet I prefer option one since, when we get 3 level support implemented we can easily move 'WSO2' as the top level. Please give your suggestions. Thanks [1] -- Forwarded message -- From: Vitalii Parfonov vparfo...@codenvy.com Date: Thu, Feb 5, 2015 at 7:30 PM Subject: Re: 3 level hierarchy of projects and pom creation To: Tyler Jewell tjew...@codenvy.com Cc: wso2-engagement wso2-engagem...@codenvy.com, Gennady Azarenkov gazaren...@codenvy.com, Susinda Perera susi...@wso2.com, Evgen Vidolob evido...@codenvy.com, Andrii Plotnikov aplotni...@codenvy.com Vitaly Parfonov -- codenvy On Thu, Feb 5, 2015 at 2:57 PM, Tyler Jewell tjew...@codenvy.com wrote: Adding Gennady. He should have some suggestions. In 3.7, we are introducing an improved project type abstraction. It supports sub project types, project modules, and authorship in a single class. We will use this to create the deployment abstractions as a type of project. It should also simplify what you need for this structure. _ From: Susinda Perera susi...@wso2.com Sent: Wednesday, February 4, 2015 9:58 PM Subject: 3 level hierarchy of projects and pom creation To: wso2-engagement wso2-engagem...@codenvy.com, Andrii Plotnikov aplotni...@codenvy.com, Evgen Vidolob evido...@codenvy.com Hi Andrii/Evgin This is to get some advices and best-practises for following 2 items. 1.We are thinking of developing a project based on following structure WSO2 -- ESB Project -- AppServer Project -- JAX-WS Project -- Webapp Project Is this structure is supported from codenvy.? Do you recomend to go in this approach Alternative approach that we are thinking of is giving a single wizard for AppServer Project and there we give another wizard page to select the project type and depending on project type execute a project generator. But i feel like having a separate project generator for each project type would be good, however to implement that way might need to have above 3 level support. Yes, no reason do something until we ship 3.7.0 2. We want to add repositories and pluginRepositories for the pom, however i could not find a method in com .codenvy.ide.maven.tools.Model to do this. As an alternative we can write to the pom file directly (or can we use model .setPomFile() to do the same). We will add this method to our model. I have created issue on it. Appreciate your inputs and thoughts. Thanks -- *Susinda Perera* Software Engineer Mobile: (+94)716049075 WSO2 Inc. http://wso2.com/ Tel : 94 11 214 5345 Fax :94 11 11%C2%A0%2021453002145300 11%C2%A0%202145300 -- *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 -- Viraj Rajaguru Senior Software Engineer WSO2 Inc. : http://wso2.com Mobile: +94 77 3683068 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Create a OSGi bundle in Dev Studio
Hi Eranda, We are using org.apache.felix.maven-bundle-plugin[1] maven plugin in Java Library Project to create OSGI bundle from the existing jar or java project. Using maven-bundle-plugin we can define parameter such as 'Export-Packages', 'Bundle-Activator' etc. for the OSGI bundle. For an example, see the following plugin definition in the pom.xml of a Java Library Project plugin groupIdorg.apache.felix/groupId artifactIdmaven-bundle-plugin/artifactId version2.3.4/version extensionstrue/extensions configuration instructions Bundle-SymbolicNamemyBundle/Bundle-SymbolicName Bundle-NamemyBundle/Bundle-Name Export-Packageorg.wso2.myBundle,x.y.z/Export-Package DynamicImport-Package*/DynamicImport-Package Bundle-Activatororg.wso2.myBundle.Activator/Bundle-Activator /instructions /configuration /plugin Thanks, Viraj. [1] - http://felix.apache.org/site/apache-felix-maven-bundle-plugin-bnd.html On Wed, Jan 7, 2015 at 5:33 PM, Eranda Sooriyabandara era...@wso2.com wrote: That means we can't restrict the exports, can't use the bundle activators or can't use the declarative service in these bundles. Isn't it? Thanks Eranda On Wednesday, January 7, 2015, Viraj Rajaguru vi...@wso2.com wrote: Hi Eranda, We have Java Library Project[1] in devS to create a OSGI bundle from a existing jar file or java project in the workspace. Thanks, Viraj. [1] - https://docs.wso2.com/display/DVS371/Creating+Carbon+Projects#CreatingCarbonProjects-JavaLibraryProject On Wed, Jan 7, 2015 at 3:33 AM, Eranda Sooriyabandara era...@wso2.com wrote: Hi Dev-Stidio team, Is there a way to do the $subject? I know how to create the OSGi using the eclipse but its bit different when it comes to the conventions we follow when we create Carbon bundles. Carbon UI bundle project is there but nothing for carbon bundles. thanks Eranda -- *Eranda Sooriyabandara*Senior Software Engineer; Integration Technologies Team; WSO2 Inc.; http://wso2.com Lean . Enterprise . Middleware E-mail: eranda AT wso2.com Mobile: (812) 964-9032 Linked-In: http://www.linkedin.com/in/erandasooriyabandara Blog: http://emsooriyabandara.blogspot.com/ -- Viraj Rajaguru Senior Software Engineer WSO2 Inc. : http://wso2.com Mobile: +94 77 3683068 -- *Eranda Sooriyabandara*Senior Software Engineer; Integration Technologies Team; WSO2 Inc.; http://wso2.com Lean . Enterprise . Middleware E-mail: eranda AT wso2.com Mobile: (812) 964-9032 Linked-In: http://www.linkedin.com/in/erandasooriyabandara Blog: http://emsooriyabandara.blogspot.com/ -- Viraj Rajaguru Senior Software Engineer WSO2 Inc. : http://wso2.com Mobile: +94 77 3683068 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Create a OSGi bundle in Dev Studio
Hi, On Fri, Jan 9, 2015 at 10:28 PM, Eranda Sooriyabandara era...@wso2.com wrote: Hi Viraj, Yes, we can use the felix bundle plugin which is what we used in the all the carbon bundles. But can't we automate this in dev-studio? No. There is no dedicated project creation option available to automate carbon/OSGI bundle creation in dev-studio. We have to do tasks such as edit pom.xml, add Activator class etc. manually when we use Java Library Project which is the available option. Thanks, Viraj. thanks Eranda On Fri, Jan 9, 2015 at 11:53 AM, Viraj Rajaguru vi...@wso2.com wrote: Hi Eranda, We are using org.apache.felix.maven-bundle-plugin[1] maven plugin in Java Library Project to create OSGI bundle from the existing jar or java project. Using maven-bundle-plugin we can define parameter such as 'Export-Packages', 'Bundle-Activator' etc. for the OSGI bundle. For an example, see the following plugin definition in the pom.xml of a Java Library Project plugin groupIdorg.apache.felix/groupId artifactIdmaven-bundle-plugin/artifactId version2.3.4/version extensionstrue/extensions configuration instructions Bundle-SymbolicNamemyBundle/Bundle-SymbolicName Bundle-NamemyBundle/Bundle-Name Export-Packageorg.wso2.myBundle,x.y.z/Export-Package DynamicImport-Package*/DynamicImport-Package Bundle-Activatororg.wso2.myBundle.Activator/Bundle-Activator /instructions /configuration /plugin Thanks, Viraj. [1] - http://felix.apache.org/site/apache-felix-maven-bundle-plugin-bnd.html On Wed, Jan 7, 2015 at 5:33 PM, Eranda Sooriyabandara era...@wso2.com wrote: That means we can't restrict the exports, can't use the bundle activators or can't use the declarative service in these bundles. Isn't it? Thanks Eranda On Wednesday, January 7, 2015, Viraj Rajaguru vi...@wso2.com wrote: Hi Eranda, We have Java Library Project[1] in devS to create a OSGI bundle from a existing jar file or java project in the workspace. Thanks, Viraj. [1] - https://docs.wso2.com/display/DVS371/Creating+Carbon+Projects#CreatingCarbonProjects-JavaLibraryProject On Wed, Jan 7, 2015 at 3:33 AM, Eranda Sooriyabandara era...@wso2.com wrote: Hi Dev-Stidio team, Is there a way to do the $subject? I know how to create the OSGi using the eclipse but its bit different when it comes to the conventions we follow when we create Carbon bundles. Carbon UI bundle project is there but nothing for carbon bundles. thanks Eranda -- *Eranda Sooriyabandara*Senior Software Engineer; Integration Technologies Team; WSO2 Inc.; http://wso2.com Lean . Enterprise . Middleware E-mail: eranda AT wso2.com Mobile: (812) 964-9032 Linked-In: http://www.linkedin.com/in/erandasooriyabandara Blog: http://emsooriyabandara.blogspot.com/ -- Viraj Rajaguru Senior Software Engineer WSO2 Inc. : http://wso2.com Mobile: +94 77 3683068 -- *Eranda Sooriyabandara*Senior Software Engineer; Integration Technologies Team; WSO2 Inc.; http://wso2.com Lean . Enterprise . Middleware E-mail: eranda AT wso2.com Mobile: (812) 964-9032 Linked-In: http://www.linkedin.com/in/erandasooriyabandara Blog: http://emsooriyabandara.blogspot.com/ -- Viraj Rajaguru Senior Software Engineer WSO2 Inc. : http://wso2.com Mobile: +94 77 3683068 -- *Eranda Sooriyabandara*Senior Software Engineer; Integration Technologies Team; WSO2 Inc.; http://wso2.com Lean . Enterprise . Middleware E-mail: eranda AT wso2.com Mobile: (812) 964-9032 Linked-In: http://www.linkedin.com/in/erandasooriyabandara Blog: http://emsooriyabandara.blogspot.com/ -- Viraj Rajaguru Senior Software Engineer WSO2 Inc. : http://wso2.com Mobile: +94 77 3683068 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Create a OSGi bundle in Dev Studio
Hi Eranda, We have Java Library Project[1] in devS to create a OSGI bundle from a existing jar file or java project in the workspace. Thanks, Viraj. [1] - https://docs.wso2.com/display/DVS371/Creating+Carbon+Projects#CreatingCarbonProjects-JavaLibraryProject On Wed, Jan 7, 2015 at 3:33 AM, Eranda Sooriyabandara era...@wso2.com wrote: Hi Dev-Stidio team, Is there a way to do the $subject? I know how to create the OSGi using the eclipse but its bit different when it comes to the conventions we follow when we create Carbon bundles. Carbon UI bundle project is there but nothing for carbon bundles. thanks Eranda -- *Eranda Sooriyabandara*Senior Software Engineer; Integration Technologies Team; WSO2 Inc.; http://wso2.com Lean . Enterprise . Middleware E-mail: eranda AT wso2.com Mobile: (812) 964-9032 Linked-In: http://www.linkedin.com/in/erandasooriyabandara Blog: http://emsooriyabandara.blogspot.com/ -- Viraj Rajaguru Senior Software Engineer WSO2 Inc. : http://wso2.com Mobile: +94 77 3683068 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Dev Studio] Adding In Out mediators within a sequence doesn't get saved
Hi Ishara, Developer Studio does not allow you to put In/Out mediators inside any arbitrary Sequence or any Proxy service. But if you create the main sequence using DevS, it will contain In/Out mediators because we definitely need In/Out mediators inside the main sequence. This limitation was introduced because it is almost impossible to represent the meaning of In/Out mediators inside a Sequence graphically. In/Out mediators represent in path and out path and we may need to divide sequence diagram into two parts to represent this forward and reverse message flow if we allow In/Out mediators. After discussing with ESB team, we decided not to support In/Out mediators for sequences except main sequence since users have alternatives to accomplish this. But I understand that there is a limitation in DevS according to the ESB config specification. You can use service chaining for your use case instead of In/Out mediators. Thanks, Viraj. On Fri, Jul 18, 2014 at 9:57 AM, Ishara Premadasa ish...@wso2.com wrote: Hi, When i add the below config inside a sequence.xml file in Developer Studio 3.7.0, once the file is saved and open the source view back, all the configs are wiped out. sequence xmlns=http://ws.apache.org/ns/synapse; name=TestSequence in log level=custom property name=seq in value=msg came to seq in/property /log send endpoint http method=post uri-template= http://localhost:9764/jaxrs_starbucks_service/services/Starbucks_Outlet_Service/orders/ /http /endpoint /send /in out log level=full property name=seq_out value=response came seq out mediator/property /log /out /sequence However when use ESB UI editor to create this config it is supported there. May i please know how to create In,Out mediators from Dev studio, as i have several sequences which invokes external API endpoints at the In and need to get the response into Out. Thanks! Ishara -- Ishara Premasada Software Engineer, WSO2 Inc. http://wso2.com/ *Blog : http://isharapremadasa.blogspot.com/ http://isharapremadasa.blogspot.com/Twitter : https://twitter.com/ishadil https://twitter.com/ishadil Mobile : +94 714445832 %2B94%20714445832* -- Viraj Rajaguru Software Engineer WSO2 Inc. : http://wso2.com Mobile: +94 77 3683068 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] XPATH expression throws an exception
___ 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 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Exception thrown when close the eclipse after run as eclipse application
Hi Lali,
Can you try following code snippet for getEditingDomain() method ?
/**
* @generated NOT
*/
public TransactionalEditingDomain getEditingDomain() {
IDocument document = null;
if (getDocumentProvider() != null) {
document = getEditorInput() != null ? getDocumentProvider().getDocument(
getEditorInput()) : null;
} else {
document = getEditorInput() != null ? getDocumentProvider(getEditorInput())
.getDocument(getEditorInput()) : null;
}
if (document instanceof IDiagramDocument) {
return ((IDiagramDocument) document).getEditingDomain();
}
return super.getEditingDomain();
}
Thanks,
Viraj.
On Tue, Apr 22, 2014 at 11:59 PM, Lali Devamanthri l...@wso2.com wrote:
Hi,
Following exception throw when close the eclipse after run as eclipse
application.
org.eclipse.swt.SWTException: Failed to execute runnable
(java.lang.NullPointerException)
at org.eclipse.swt.SWT.error(SWT.java:4397)
at org.eclipse.swt.SWT.error(SWT.java:4312)
...
Caused by: java.lang.NullPointerException
at
dataMapper.diagram.part.DataMapperDiagramEditor.getEditingDomain(DataMapperDiagramEditor.java:144)
at
org.eclipse.gmf.runtime.diagram.ui.parts.DiagramEditor$1.getEditingDomain(DiagramEditor.java:396)
at
org.eclipse.gmf.runtime.diagram.ui.actions.AbstractDeleteFromAction.getEditingDomain(AbstractDeleteFromAction.java:117)
at
org.eclipse.gmf.runtime.diagram.ui.actions.AbstractDeleteFromAction.updateTargetRequest(AbstractDeleteFromAction.java:85)
at
org.eclipse.gmf.runtime.diagram.ui.actions.DiagramAction.refresh(DiagramAction.java:113)
But DataMapperDiagramEditor class is generated.
/**
* @generated
*/
public TransactionalEditingDomain getEditingDomain() {
IDocument document = getEditorInput() != null ?
getDocumentProvider().getDocument( //line 144
getEditorInput()) : null;
if (document instanceof IDiagramDocument) {
return ((IDiagramDocument) document).getEditingDomain();
}
return super.getEditingDomain();
}
Is this exception occurs due to modified methods of generated class ?
Thanks,
Lali
--
*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
--
Viraj Rajaguru
Software Engineer
WSO2 Inc. : http://wso2.com
Mobile: +94 77 3683068
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Generic implementation for DataMapper config generator
Hi Lali, +1 for the approach. Most of the use cases involved in 'ESB Graphical editor' and 'Datamapper Editor' are almost identical. For an example, there are mediator sequences (Eg: Log -- Property -- Send) in ESB editor and Operator sequences (Eg: Split -- toLowerCase -- Concat) in Datamapper editor. And also there should be a way to add a new mediator into the ESB editor with minimal effort and Datamapper editor has the same requirement when we want to add a new Operator to editor. So its a good idea to use the same pattern which we used in ESB Graphical Editor for Datamapper editor(in terms of config generator for Operators). Thanks, Viraj. On Wed, Apr 16, 2014 at 9:33 PM, Lali Devamanthri l...@wso2.com wrote: Hi, In ESB graphical model serialization, DevS have used 'EsbTransformerRegistry' class for register each mediator specific serialization classes. This allow to add new mediator serialization without a pain. We can use same pattern to add data mapper operators config generation classes. Are there any other best practises or suggestion for do $subject? Thanks, Lali -- *Lali Sudaththa Devamanthri* Software Engineer WSO2 Inc.; http://wso2.com lean.enterprise.middleware mobile: +94 71 895 4922 http://www.wso2.com -- Viraj Rajaguru Software Engineer WSO2 Inc. : http://wso2.com Mobile: +94 77 3683068 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [DevS] Version of the source tree (branch) differs from the real version
Hi, Created 3.5.0 branch [1]. Thanks, Viraj. [1] - https://svn.wso2.org/repos/wso2/branches/tools/eclipse/developer-studio/3.5.0/ On Thu, Jan 16, 2014 at 9:14 AM, Asanka Sanjeewa asan...@wso2.com wrote: Hi Prabath, Initially we named the next version of developer studio as 3.3.0 (since the last released version was 3.2.0). Therefore the 3.3.0 svn branch was created. But while we were working with 3.3.0 version number was changed since there are considerable number of new features and improvements includes in this release. So the finalized release version number is 3.5.0. But still we couldn't rename the svn branch. We'll rename svn branch as 3.5.0 as it sink with release version number. Thanks and Regards, AsankaS. On Thu, Jan 16, 2014 at 3:40 AM, Prabath Abeysekera praba...@wso2.comwrote: Hi DevS team, Noticed the $subject. Eventhough the source tree of the branch [1] carries the version v3.3.0, the contents seem to refer to v3.5.0. Am I missing something? [1] https://svn.wso2.org/repos/wso2/branches/tools/eclipse/developer-studio/3.3.0/ Cheers, Prabath -- Prabath Abeysekara Associate Technical Lead, Data TG. WSO2 Inc. Email: praba...@wso2.com Mobile: +94774171471 ___ 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 -- Viraj Rajaguru Software Engineer WSO2 Inc. : http://wso2.com Mobile: +94 77 3683068 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Shall we remove the WS-AddressingEndpoint from Endpoint Tool Pallet in DevStudio?
Hi, +1 WS-Addresing Endpoint is no longer needed. So we can remove it from tool palette. Created a public Jira [1] to track this. [1] - https://wso2.org/jira/browse/TOOLS-2274 Thanks, Viraj. On Sun, Jan 5, 2014 at 2:23 PM, Harshana Martin harsh...@wso2.com wrote: Hi All, I think we $Subject because now that Send mediator is embedding the endpoint, we no longer need the WS-AddressingEndpoint. Keeping the empty Send mediator indicates the WS-Addressing scenario just like in the Mgt Console. So I'm proposing $Subject. WDYT? Thanks and Regards, Harshana -- 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 -- Viraj Rajaguru Software Engineer WSO2 Inc. : http://wso2.com Mobile: +94 77 3683068 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] How do I get connectors to work with DevS?
Hi Jackie, AFAIK, pack in [1] has latest fixes related to connectors. And also we will use Connectors instead of Cloud connectors. Thanks, Viraj. [1] http://builder1.us1.wso2.org/~developerstudio/developer-studio/3.3.0/Pre-Alpha4/ On Tue, Dec 3, 2013 at 5:35 PM, Jackie Wheeler jac...@wso2.com wrote: Actually, I'm seeing Cloud in many different places, not just the menu command. We need to fix that, as we are not calling them Cloud connectors anymore. Can someone point me to the latest tested version of Dev Studio that you are certain works with the connectors? I've gone back and installed a few different versions, but they all give errors when I import a connector or when I create ESB artifacts (graphical editor won't load), so I am unable to test how connectors are supposed to work. Thanks, Jackie On Tue, Dec 3, 2013 at 11:43 AM, Jackie Wheeler jac...@wso2.com wrote: FYI: In Dev Studio, we need to change the menu command Import Cloud Connector to Import Connector. On Tue, Dec 3, 2013 at 12:45 AM, Samisa Abeysinghe sam...@wso2.comwrote: I do not think I completely understand. May be it is implementation specific and designed that way. Thanks, Samisa... Samisa Abeysinghe Vice President Training WSO2 Inc. http://wso2.com On Tue, Dec 3, 2013 at 2:08 PM, Asanka Sanjeewa asan...@wso2.comwrote: Hi, According to the current implementation imported connectors are specific to the particular ESB Config project. So for the moment it doesn't support for global imports (such that imported connectors are visible to all ESB Config projects within the workspace). In the current model it allows to import only necessary connectors for the particular project. Thanks and Regards, AsanakS. On Tue, Dec 3, 2013 at 1:50 PM, Susinda Perera susi...@wso2.comwrote: There is a brief description on Using connectors in Developer Studio @[1] , but needs to be updated http://docs.wso2.org/display/ESB480/Using+a+Connector On Tue, Dec 3, 2013 at 1:31 PM, Samisa Abeysinghe sam...@wso2.comwrote: Created a Jira https://wso2.org/jira/browse/DOCUMENTATION-495 Thanks, Samisa... Samisa Abeysinghe Vice President Training WSO2 Inc. http://wso2.com On Tue, Dec 3, 2013 at 12:59 PM, Asanka Sanjeewa asan...@wso2.comwrote: Hi, Seems like Developer Studio 3.3.0 Documentations has not been updated with tooling aspect in connectors. Viraj's blog at [1] will helpful in creating connector contents in Developer Studio 3.3.0 document. [1] http://sumuditha-viraj.blogspot.com/2013/10/how-to-use-wso2-developer-studio-cloud.html Thanks and Regards, AsankaS. On Tue, Dec 3, 2013 at 12:56 PM, Isuru Udana isu...@wso2.comwrote: Hi Samisa, You can right-click on the ESB project and then select Import Cloud Connector. There is a blog post[1] written by Viraj on this but I am not sure whether this is documented in the wiki. [1] http://sumuditha-viraj.blogspot.com/2013/10/how-to-use-wso2-developer-studio-cloud.html Thanks. On Tue, Dec 3, 2013 at 12:42 PM, Samisa Abeysinghe sam...@wso2.com wrote: For $subject, do I have to drop connectors to DevS? If yes, where is the doc on that? Thanks, Samisa... Samisa Abeysinghe Vice President Training 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 -- *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 -- *Susinda Perera* Software Engineer Mobile:(+94)716049075 WSO2 Inc. http://wso2.com/ Tel : 94 11 214 5345 Fax :94 11 2145300 -- *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 -- *Jackie Wheeler* VP, Technical Content WSO2, Inc. Mobile: +1 510 725-2876 http://wso2.com/ -- *Jackie Wheeler* VP, Technical Content WSO2, Inc. Mobile: +1 510 725-2876 http://wso2.com/ ___ 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 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Architecture] Developer Studio 3.3.0 Alpha 3 Released!
/ ___ 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 -- 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 -- 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 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Chintana Wilamuna Architect - Solution Architecture WSO2, Inc.; http://wso2.com lean.enterprise.middleware phone: +94 72 145 4545 blog: http://engwar.com/ photos: http://flickr.com/photos/chintana linkedin: http://www.linkedin.com/in/engwar twitter: twitter.com/std_err -- 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 ___ Architecture mailing list architect...@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture -- Viraj Rajaguru Software Engineer WSO2 Inc. : http://wso2.com Mobile: +94 77 3683068 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Dev Studio 3.3.0 Alpha 2 testing
I'll test G-Reg features. Thanks, viraj. On Wed, Oct 23, 2013 at 9:46 AM, Harshana Martin harsh...@wso2.com wrote: Hi All, Please start testing the 3.3.0 Alpha 2 today. Testing cycle should be from creating the artifact to deploying and using the developed artifact in the Server. If you come across any issues report in the Jira and move on to testing. Once the testing is complete we can start fixing the issues we uncovered. Do not spend time on fixing new Jira Tickets did not go to the Alpha 2 release. Only on going development should be Jaggery and App Factory. Thanks and Regards, Harshana -- 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 -- Viraj Rajaguru Software Engineer WSO2 Inc. : http://wso2.com Mobile: +94 77 3683068 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Does CApps support jar services
Hi Manoj, AFAIK Developer Studio does not support for creating jar services. Inside the .car file in [1] there is only an osgi bundle which has been created using Java Library Project in Developer Studio. Thanks, Viraj. [1] https://wso2.org/jira/browse/CARBON-14353 On Wed, Aug 14, 2013 at 11:54 AM, Manoj Kumara ma...@wso2.com wrote: Hi, I'm looking in to Jira issue [1]. Does Developer Studio support jar artifacts on CApp and Is this a valid scenario. Appreciate your guidance. [1] https://wso2.org/jira/browse/CARBON-14353 Thanks, Best Regards.. Manoj Kumara Software Engineer WSO2, Inc.; http://wso2.com Twitter: http://twitter.com/ManKuma Mobile: +94713448188 ___ 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 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Changing the Developer Studio 3.2.1 milestone plan
Will update the RM. Thanks, Viraj. On Fri, Aug 9, 2013 at 8:06 AM, Samisa Abeysinghe sam...@wso2.com wrote: I have done the version changes in Jira. Can someone please update RM? On Tue, Aug 6, 2013 at 5:54 PM, Samisa Abeysinghe sam...@wso2.com wrote: +1 for version change, as we will change the look and feel. It is not a mere bug fix any more. We had to change the look and feel, in the process of addressing some usability issues. Though the number changes, we still can stick to the milestone plan. One concern is the connector POC is lagging. We might have to release Viraj a bit to get cracking on that too, after this week. On Tue, Aug 6, 2013 at 3:03 PM, Jasintha Dasanayake jasin...@wso2.comwrote: HI Well, IMO Once We complete the ESB graphical editor look and feel(new milestone 2.and 3 ) DevS 3.3.0 should be released instead of 3.2.1, after that we can do a 3.3.1 bug fixes release and rest of the fixes(which have been scheduled for milestone 4 and 5) can be include into 3.3.1 BTW 3.2.1 has been scheduled on 8 th of Aug this also impossible WDYT ? Thanks and Regards /Jasintha On Tue, Aug 6, 2013 at 11:19 AM, Asanka Sanjeewa asan...@wso2.comwrote: Hi, We have changed the Developer Studio milestone plan for 3.2.1 bit. We are going to give high priority for the issues related to usability of the ESB graphical editor and look and feel of the editor. So those issues will be fixed in milestone 2 and 3 although they were scheduled to milestone 4 and 5 earlier. Thanks and Regards, AsankaS. -- *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 -- *Jasintha Dasanayake **Software Engineer WSO2 Inc. | http://wso2.com lean . enterprise . middleware* * * *mobile :- 077 291 6596* -- Thanks, Samisa... Samisa Abeysinghe VP Engineering WSO2 Inc. http://wso2.com http://wso2.org -- 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 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Can we compile DevS with maven3?
Yes. We use maven 3 for building DevS. Thanks, Viraj. On Mon, Jul 29, 2013 at 5:33 PM, Samisa Abeysinghe sam...@wso2.com 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 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Upgrading Synapse dependencies in Developer Studio
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 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Upgrading Synapse dependencies in Developer Studio
Hi, On Fri, Jul 12, 2013 at 12:30 PM, Harshana Martin harsh...@wso2.com 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 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 vi...@wso2.com 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 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Dev Studio ESB Mediators in Palette should be in alphabatical order in each catgory
Hi Dushan, Yes there is an issue with palette to find relevant mediator quickly. There is a public jira at [1] which describes the same issue. Fix will be available in next releases. Thanks, Viraj. [1] - https://wso2.org/jira/browse/TOOLS-1323 On Sat, May 25, 2013 at 8:32 AM, Dushan Abeyruwan dus...@wso2.com wrote: Hi Dev Folks, $subject, it really difficult to find mediators by scrolling here and there should be ordered..please make this as note cheers Dushan Abeyruwan Associate Tech Lead *Integration Technologies Team* *WSO2 Inc. http://wso2.com/* *Mobile:(+94)714408632* ___ 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 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Developer Studio 3.0.0 Milestone 2 Released !
Hi All, We have WSO2 Developer Studio 3.0.0 Milestone 2 ready to be downloaded at [1]. Installed eclipse distributions available at [2] Bug - [TOOLS-1360 https://wso2.org/jira/browse/TOOLS-1360] - API's InSequence, OutSequence FaultSequence can be named sequences. Improvement - [TOOLS-1364 https://wso2.org/jira/browse/TOOLS-1364] - Implement main sequence and fault sequence. New Feature - [TOOLS-1171 https://wso2.org/jira/browse/TOOLS-1171] - Enabled Content Assist support for ESB editor Source view - [TOOLS-1192 https://wso2.org/jira/browse/TOOLS-1192] - Implement Failover and Loadbalance endpoints Sub-task - [TOOLS-1384 https://wso2.org/jira/browse/TOOLS-1384] - Complete mediators : Round 1 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/milestone/devstd/3.0.0/M2/wso2-developer-studio_3.0.0-SNAPSHOT.zip [2] - http://dist.wso2.org/milestone/devstd/3.0.0/M2/pre-installed-distributions/ [3] - https://wso2.org/jira/browse/TOOLS -- *Viraj Rajaguru* email: vi...@wso2.com email%3avi...@wso2.com cell: +94 77 3683068 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] WSO2 Developer Studio 2.2.0 Milestone 1 Released !
Hi All, We have WSO2 Developer Studio 2.2.0 Milestone 1 ready to be downloaded at [1]. Installed eclipse distributions available at [2] This release includes following new features, improvements and bug fixes. Bug fixes - [TOOLS-1318 https://wso2.org/jira/browse/TOOLS-1318] - Graphical editor need to save synapse confg into distributed artifacts - [TOOLS-1339 https://wso2.org/jira/browse/TOOLS-1339] - Can not select existing endpoints within the Esb Configuration project. - [TOOLS-1340 https://wso2.org/jira/browse/TOOLS-1340] - Can not create custom proxy templates to extend the existing templates. - [TOOLS-1344 https://wso2.org/jira/browse/TOOLS-1344] - Sequence name doesn't get serialized in sequence editor Improvement - [TOOLS-1345 https://wso2.org/jira/browse/TOOLS-1345] - Adding a new folder structure for ESB Graphical editor - [TOOLS-1346 https://wso2.org/jira/browse/TOOLS-1346] - Changing the figures of elements. (Mediators, Endpoints etc) New Feature - [TOOLS-1342 https://wso2.org/jira/browse/TOOLS-1342] - Support for named endpoints to be opened in a separate editor page. - [TOOLS-1343 https://wso2.org/jira/browse/TOOLS-1343] - Support Task and Local Entry to be opened in separate editor pages. Your feedbacks are most welcome !!! Please report all the jiras at [3] and specify the version as 2.2.0. Thanks and Regards, The WSO2 Developer Studio Team. [1] - http://builder1.us1.wso2.org/~developerstudio/developer-studio/2.2.0/M1/wso2-developer-studio_2.2.0-SNAPSHOT.zip [2] - http://builder1.us1.wso2.org/~developerstudio/developer-studio/2.2.0/M1/Dev-Studio-Pre-installed-Eclipse/ [3] - https://wso2.org/jira/browse/TOOLS -- *Viraj Rajaguru* email: vi...@wso2.com email%3avi...@wso2.com cell: +94 77 3683068 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] WSO2 Developer Studio 2.1.0 Milestone 4 Released!
Hi All, We have WSO2 Developer Studio 2.1.0 Milestone 4 ready to be downloaded at [1]. Installed eclipse distributions available at [2] This release includes following improvements and bug fixes. Bug - [TOOLS-1193 https://wso2.org/jira/browse/TOOLS-1193] - Save button doesn't work correctly. - [TOOLS-1240 https://wso2.org/jira/browse/TOOLS-1240] - Dropping a mediator in between two mediators already connected does not connect the new one - [TOOLS-1244 https://wso2.org/jira/browse/TOOLS-1244] - Service chaining doesn't work properly when there is a sequence mediator in the In sequence of the Proxy service. - [TOOLS-1251 https://wso2.org/jira/browse/TOOLS-1251] - If user put a sequence mediator as the first mediator of the out sequence of the proxy service, synapse configuration doesn't get generated. - [TOOLS-1252 https://wso2.org/jira/browse/TOOLS-1252] - Endpoints doesn't get connected automatically to other figures when we drop them to compartment. Improvement - [TOOLS-1205 https://wso2.org/jira/browse/TOOLS-1205] - Can not create sequence flow for onHitCatch in the Cache mediator. - [TOOLS-1242 https://wso2.org/jira/browse/TOOLS-1242] - Generate synapse mediator project's pom to use the maven-bundle-plugin - [TOOLS-1250 https://wso2.org/jira/browse/TOOLS-1250] - Bending points should be smooth in connections. New Feature - [TOOLS-1170 https://wso2.org/jira/browse/TOOLS-1170] - Implement Fault Sequence in the Proxy Service - [TOOLS-1248 https://wso2.org/jira/browse/TOOLS-1248] - Adding maven build support for CEP artifacts in CApp projects 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/M4/wso2-developer-studio_2.1.0-SNAPSHOT.zip [2] - http://builder1.us1.wso2.org/~developerstudio/developer-studio/2.1.0/M4/Dev-Studio-Pre-installed-Eclipse/ [3] - https://wso2.org/jira/browse/TOOLS -- *Viraj Rajaguru* email: vi...@wso2.com email%3avi...@wso2.com cell: +94 77 3683068 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Developer Studio] ESB Graphical Editor - Proxy Service Fault Sequence.
Hi, We had a discussion on ESB Graphical Editor with Hiranya. In this discussion, followings were proposed. - We have to add a new area for Fault Sequence for Proxy Service figure. - And also it is very convenient for user to have shortcuts for property editors in the Proxy Service figure itself. So that we have to add shortcuts for property editors (Transport, Service Parameters, QoS, WSDL), into the Proxy Service figure. These shortcuts will pop up Dialog Boxes to set the relevant properties. Following figure depicts the new Proxy Service figure including above mentioned changes. ** Thanks Regards, Viraj. On Thu, Mar 15, 2012 at 12:12 PM, Viraj Rajaguru vi...@wso2.com wrote: Hi, Proxy Service figure has been changed in the ESB Graphical Editor in order to have 'In Sequence', 'Out Sequence' and 'Endpoints' inside the Proxy Service figure. (See attached screenshot.) But Proxy Service can have Fault Sequence also. How do we represent Fault Sequence graphically for a particular Proxy Service? Thoughts are welcome.. Thanks Regards, Viraj. -- *Viraj Rajaguru* email: vi...@wso2.com email%3avi...@wso2.com cell: +94 77 3683068 -- *Viraj Rajaguru* email: vi...@wso2.com email%3avi...@wso2.com cell: +94 77 3683068 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Carbon-dev] [Carbon Studio] ESB Graphical editor - Mediator Grouping
Hi Harshana, On Fri, Feb 3, 2012 at 1:17 PM, Harshana Martin harsh...@wso2.com wrote: Hi Viraj, On Thu, Feb 2, 2012 at 5:16 AM, Viraj Rajaguru vi...@wso2.com wrote: Hi, In Carbon Studio - ESB Graphical Editor there are some mediators and endpoints that are having more than one output branch.(Aggregate mediator, Clone Mediator, Switch Mediator etc.). So it will be very convenient to apply a grouping mechanism for these mediators to distinguish the output branches. For an example, previously we had two output connectors for Aggregate Mediator. One is for onComplete attribute and the another output connector is for continue the flow.(See attached Aggregate_Mediator(Previous).png). Now the aggregate mediator has a group box and we can wrap onComplete branch with it. Then we can continue the flow with single output connector.(See attached Aggregate_Mediator(Current).png). So this means now, onComplete has become an property we can set from property view? Assuming the answer is Yes to above, how do I set it? Do I select the group and set it? or Do I select the Aggregate mediator inside this group and set it? onComplete attribute is not a property and it will not appear in the property view. We can drag and drop an Aggregate mediator to the compartment, and then we can drag and drop the mediators relevant to the onComplete branch, on to the Aggregate mediator's compartment. Aggregate mediator has become a group box. So that there is no separation between group box and Aggregate mediator. Thank you for the feedback ! Look and Feel is good now! Thanks and Regards, Harshana We are going to implement this type of grouping mechanism for Clone Mediator, Switch Mediator also. Please comment on this approach. -- *Viraj Rajaguru* email: vi...@wso2.com email%3avi...@wso2.com cell: +94 77 3683068 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Harshana Martin Software Engineer WSO2 Inc. Web:http://wso2.com http://wso2.org Mobile: +94 716062650 Blog: http://harshana05.blogspot.com Profile: https://www.google.com/profiles/harshana05 Twitter: http://twitter.com/harshana05 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- *Viraj Rajaguru* email: vi...@wso2.com email%3avi...@wso2.com cell: +94 77 3683068 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
[Carbon-dev] Review on Carbon Studio - ESB Graphical Editor
Hi, We had a review on Carbon Studio - ESB Graphical Editor with Paul Srinath. In this review we discussed current status of the editor the drawbacks of it. Following facts were discussed. - If we have number of proxy services in the Synapse configuration, editor does not provide a clear separation between proxy services graphically. As a solution it was suggested to group the Proxy services. For an example, if we have three Proxy Services in the Synapse Configuration, the diagram basically would have been divided to three separate groups. And also this groups should be collapsible. - Still we cannot generate the diagram using a xml file. It is not an unsolvable issue but it would get some time to implement this. So ESB graphical editor will go as a separate feature with Carbon Studio. - Value for the XSLT mediator's key attribute should be able to browse from the existing resources. - Suitable extensions for ESB graphical editor and Sequence editor should be suggested. Thanks, -- *Viraj Rajaguru* email: vi...@wso2.com email%3avi...@wso2.com cell: +94 77 3683068 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] [Carbon Studio] ESB Graphical editor - Example 1
Hi, Fixes for the above mentioned issues will be available in Overall Milestone Plan CS 2.0.0 [1]. Some fixes are already done. We do not have the reverse engineering support yet. We are supporting following mediators. - Log Mediator - Drop Mediator - Property Mediator - Enrich Mediator - Send Mediator - Filter Mediator - Switch Mediator - XSLT Mediator - Fault Mediator - Header Mediator - DBLookup Mediator - DBReport Mediator - Clone Mediator - Iterate Mediator - Aggregate Mediator - Callout Mediator - Transaction Mediator - RMSequence Mediator And also graphical implementation of around 12 new mediators have been done. Only serialization logic has to be implemented for them. Thanks, [1] https://docs.google.com/a/wso2.com/document/d/1gTLfLBuEphtHesJf_eSyHNLcisrogEW8Aw4v-2R-iFQ/edit?hl=en_US On Sun, Jan 29, 2012 at 7:22 AM, Samisa Abeysinghe sam...@wso2.com wrote: What is the ETA for these fixes? In other words, in which milestone would these fixes be available? Do we have reverse engineering support now? Meaning, can I edit the source and it will reflect the changes in the graphical view. How many meadiators are supported? What is the plan for testing? On mediators, Jan 25, 2012 at 9:53 AM, Viraj Rajaguru vi...@wso2.comwrote: Hi, We had a discussion on ESB Graphical Editor with Hiranya. In this discussion we figured out how to overcome existing issues in the editor. Followings are the proposed solutions. - We are not going to represent Local Entries graphically inside the editor, Instead we put them on the tool palette.Then user can add them to relevant mediators using the context menu. - And also we can add defined sequences to receive attribute in the Send Mediator using the context menu as above. It is not necessary to represent this relationship in graphically. And also following issues were recognized in this discussion. - When we add a new Sequence, a dialog box should not be appeared to request a name for sequence. - In Failover endpoint, Loadbalance endpoint, Switch mediator and Clone mediator, there should not be an option to add output connectors manually.It should be automated. - File name should be appeared in the editor header. - Defined endpoints should also go to the pallet as re-usable components. - Endpoints in the border should be handled in a better way. - When open the sequence editor diagram, area for the diagram should be auto generated. - Name of the sequence should be displayed in the top of the page as well as in the sequence. - Name of the mediators and endpoints should be appeared in their figure. - Mediator grouping should be added. - A suitable extensions should be used for ESB Graphical editor files and for Sequence editor files. Thanks, On Tue, Jan 24, 2012 at 12:18 PM, Viraj Rajaguru vi...@wso2.com wrote: Hi , I tried to generate a Sample Synapse Configuration (See attached file Synapse Configuration - Example 1.txt) using the ESB Graphical editor. There were some issues while design the diagram. - How can we represent the Local Entry graphically ? - Send mediator has only input connector and output connector (See attached Send_Mediator.png). How can we represent the value of the receive attribute in Send mediator.(For a example, send receive=geoResponseSeq .In this case geoResponseSeq is a defined sequence.How can we represent this relationship between sequence and Send mediator inside the graphical editor.) ? Please comment on these issues if you have any idea. Screen shots for Relevant Diagram for the Synapse Configuration - Example 1 and the generated Synapse configuration are attached with this. Thanks, -- *Viraj Rajaguru* email: vi...@wso2.com email%3avi...@wso2.com cell: +94 77 3683068 -- *Viraj Rajaguru* email: vi...@wso2.com email%3avi...@wso2.com cell: +94 77 3683068 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev Thanks, Samisa... Samisa Abeysinghe VP Engineering WSO2 Inc. http://wso2.com http://wso2.org ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- *Viraj Rajaguru* email: vi...@wso2.com email%3avi...@wso2.com cell: +94 77 3683068 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] [Carbon Studio] ESB Graphical editor - Example 1
Hi, We had a discussion on ESB Graphical Editor with Hiranya. In this discussion we figured out how to overcome existing issues in the editor. Followings are the proposed solutions. - We are not going to represent Local Entries graphically inside the editor, Instead we put them on the tool palette.Then user can add them to relevant mediators using the context menu. - And also we can add defined sequences to receive attribute in the Send Mediator using the context menu as above. It is not necessary to represent this relationship in graphically. And also following issues were recognized in this discussion. - When we add a new Sequence, a dialog box should not be appeared to request a name for sequence. - In Failover endpoint, Loadbalance endpoint, Switch mediator and Clone mediator, there should not be an option to add output connectors manually.It should be automated. - File name should be appeared in the editor header. - Defined endpoints should also go to the pallet as re-usable components. - Endpoints in the border should be handled in a better way. - When open the sequence editor diagram, area for the diagram should be auto generated. - Name of the sequence should be displayed in the top of the page as well as in the sequence. - Name of the mediators and endpoints should be appeared in their figure. - Mediator grouping should be added. - A suitable extensions should be used for ESB Graphical editor files and for Sequence editor files. Thanks, On Tue, Jan 24, 2012 at 12:18 PM, Viraj Rajaguru vi...@wso2.com wrote: Hi , I tried to generate a Sample Synapse Configuration (See attached file Synapse Configuration - Example 1.txt) using the ESB Graphical editor. There were some issues while design the diagram. - How can we represent the Local Entry graphically ? - Send mediator has only input connector and output connector (See attached Send_Mediator.png). How can we represent the value of the receive attribute in Send mediator.(For a example, send receive=geoResponseSeq .In this case geoResponseSeq is a defined sequence.How can we represent this relationship between sequence and Send mediator inside the graphical editor.) ? Please comment on these issues if you have any idea. Screen shots for Relevant Diagram for the Synapse Configuration - Example 1 and the generated Synapse configuration are attached with this. Thanks, -- *Viraj Rajaguru* email: vi...@wso2.com email%3avi...@wso2.com cell: +94 77 3683068 -- *Viraj Rajaguru* email: vi...@wso2.com email%3avi...@wso2.com cell: +94 77 3683068 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
