from:"Nuwan Pallewela"

[Dev] [DevStudio] Please review and merged the PR

2015-06-23 Thread Nuwan Pallewela

Hi,

Please review and merge PR[1] - Fixing TOOLS-2837 Server role is not
clickable until the particular artifact is selected in CAPP editor

[1] https://github.com/wso2/developer-studio/pull/53

Thanks,
Nuwan.

-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739*
*+94767100087*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] How OSGi Bundle Activation Policy Works in Runtime

2015-06-26 Thread Nuwan Pallewela

If a plug-in's Bundle Activation Policy is configured as "lazy", will
another plug-in which depends on it can use it if the current state of the
first plug-in is in RESOLVED state? Will it come to ACTIVE state because of
the second plug-In's invocation?

-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739*
*+94767100087*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [DevStudio] Please review and merge the PR

2015-06-29 Thread Nuwan Pallewela

Hi,

Please review and merge PR [1] and [2] - Fixing TOOLS-2928
 When adding a proxy service using
the wizard, even when all fields are filled 'Give a name for the proxy
service' is shown.


[1] https://github.com/wso2/developer-studio/pull/54
[2] https://github.com/wso2/developer-studio/pull/55

Thanks,
-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739*
*+94767100087*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DevStudio] Please review and merge the PR

2015-06-30 Thread Nuwan Pallewela

Hi,

Please don't merge the above PR.Review and merge  the following PR [1] and
[2] - Fixing TOOLS-2928 <https://wso2.org/jira/browse/TOOLS-2928> When
adding a proxy service using the wizard, even when all fields are filled
'Give a name for the proxy service' is shown.

[1] *https://github.com/wso2/developer-studio/pull/54
<https://github.com/wso2/developer-studio/pull/54>*
[2] *https://github.com/wso2/developer-studio/pull/55
<https://github.com/wso2/developer-studio/pull/55>*

Thanks,

On Mon, Jun 29, 2015 at 6:16 PM, Nuwan Pallewela  wrote:

> Hi,
>
> Please review and merge PR [1] and [2] - Fixing TOOLS-2928
> <https://wso2.org/jira/browse/TOOLS-2928> When adding a proxy service
> using the wizard, even when all fields are filled 'Give a name for the
> proxy service' is shown.
>
>
> [1] https://github.com/wso2/developer-studio/pull/54
> [2] https://github.com/wso2/developer-studio/pull/55
>
> Thanks,
> --
> --
>
> *Nuwan Chamara Pallewela*
>
>
> *Software Engineer*
>
> *WSO2, Inc. *
> *lean . enterprise . middleware*
>
> Email   *nuw...@wso2.com *
> Mobile  *+94719079739 <%2B94719079739>*
> *+94767100087 <%2B94767100087>*
>
>



-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739*
*+94767100087*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [DEV][DevStudio] Please review and merge the PR

2015-07-06 Thread Nuwan Pallewela

Hi,

Please review and merge PR [1] and [2] -
Fixing Tools-2900 -'Advanced Configuration' option does not list any
advanced options for HTTP/HTTPS Inbound Endpoints
Fixing Tools-2673-Typo in XPath

[1] https://github.com/wso2/developer-studio/pull/57
[2] https://github.com/wso2/developer-studio/pull/56

Thanks,
-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739*
*+94767100087*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [DEV][DevStudio] Please review and merge the PR

2015-07-07 Thread Nuwan Pallewela

Hi,
Please review and merge PR [1] and [2]-
   Fixing Tools-2916 - Error message to user for BAM errors is too generic.

Following are the changes done in this PR.

   - Property name is changed from "Server Profile" to "Server Profile
   Name", because property name was little bit misleading.


   - Default values are added to the BAM mediator when first inserted to
   the ESB Graphical Editor.


   - Descriptive error messages are now shown when errors occurs when
   configuring the Proxy Service.
   - Validations are included when modifications done in the source (xml)
   file of the Proxy Service.


[1] https://github.com/wso2/developer-studio/pull/58
[2] https://github.com/wso2/developer-studio/pull/59

-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739*
*+94767100087*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [DEV][DevStudio] Please review and merge the PR

2015-07-13 Thread Nuwan Pallewela

Hi,
Please review and merge PR [1] and [2]-
  Tools-2961 : Restrict switching from source view to design view when
source view has errors

[1] https://github.com/wso2/developer-studio/pull/67
[2] https://github.com/wso2/developer-studio/pull/66

-- 

Thanks,
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739*
*+94767100087*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV][DevStudio] Please review and merge the PR

2015-07-14 Thread Nuwan Pallewela

Hi Rajeevan,

Thank you for your comments and I have done some changes.

Thanks,

On Tue, Jul 14, 2015 at 1:17 PM, Rajeevan Vimalanathan 
wrote:

> Hi Nuwan,
>
> I have added few comments to the PR. Please have a look.
>
> Thanks,
> Rajeevan
>
> On Tue, Jul 14, 2015 at 12:02 PM, Nuwan Pallewela  wrote:
>
>> Hi,
>> Please review and merge PR [1] and [2]-
>>   Tools-2961 : Restrict switching from source view to design view when
>> source view has errors
>>
>> [1] https://github.com/wso2/developer-studio/pull/67
>> [2] https://github.com/wso2/developer-studio/pull/66
>>
>> --
>>
>> Thanks,
>> --
>>
>> *Nuwan Chamara Pallewela*
>>
>>
>> *Software Engineer*
>>
>> *WSO2, Inc. *
>> *lean . enterprise . middleware*
>>
>> Email   *nuw...@wso2.com *
>> Mobile  *+94719079739 <%2B94719079739>*
>> *+94767100087 <%2B94767100087>*
>>
>>
>> ___
>> 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>*
>



-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739*
*+94767100087*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV][DevStudio] Please review and merge the PR

2015-07-15 Thread Nuwan Pallewela

Thanks,
Nuwan

On Wed, Jul 15, 2015 at 1:26 PM, Rajeevan Vimalanathan 
wrote:

> Merged!
>
> Thanks,
> Rajeevan
>
> On Tue, Jul 14, 2015 at 2:41 PM, Nuwan Pallewela  wrote:
>
>> Hi Rajeevan,
>>
>> Thank you for your comments and I have done some changes.
>>
>> Thanks,
>>
>> On Tue, Jul 14, 2015 at 1:17 PM, Rajeevan Vimalanathan <
>> rajeev...@wso2.com> wrote:
>>
>>> Hi Nuwan,
>>>
>>> I have added few comments to the PR. Please have a look.
>>>
>>> Thanks,
>>> Rajeevan
>>>
>>> On Tue, Jul 14, 2015 at 12:02 PM, Nuwan Pallewela 
>>> wrote:
>>>
>>>> Hi,
>>>> Please review and merge PR [1] and [2]-
>>>>   Tools-2961 : Restrict switching from source view to design view when
>>>> source view has errors
>>>>
>>>> [1] https://github.com/wso2/developer-studio/pull/67
>>>> [2] https://github.com/wso2/developer-studio/pull/66
>>>>
>>>> --
>>>>
>>>> Thanks,
>>>> --
>>>>
>>>> *Nuwan Chamara Pallewela*
>>>>
>>>>
>>>> *Software Engineer*
>>>>
>>>> *WSO2, Inc. *
>>>> *lean . enterprise . middleware*
>>>>
>>>> Email   *nuw...@wso2.com *
>>>> Mobile  *+94719079739 <%2B94719079739>*
>>>> *+94767100087 <%2B94767100087>*
>>>>
>>>>
>>>> ___
>>>> 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>*
>>>
>>
>>
>>
>> --
>> --
>>
>> *Nuwan Chamara Pallewela*
>>
>>
>> *Software Engineer*
>>
>> *WSO2, Inc. *
>> *lean . enterprise . middleware*
>>
>> Email   *nuw...@wso2.com *
>> Mobile  *+94719079739 <%2B94719079739>*
>> *+94767100087 <%2B94767100087>*
>>
>>
>
>
>
> --
> 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>*
>



-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739*
*+94767100087*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [DEV][DevStudio] Please review and merge the PR

2015-07-15 Thread Nuwan Pallewela

Hi,
Please review and merge PR [1] and [2] -
 Tools-2932 : Importing existing registry project throws an exception

[1] https://github.com/wso2/developer-studio/pull/70
[2] https://github.com/wso2/developer-studio/pull/71
-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739*
*+94767100087*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV][DevStudio] Please review and merge the PR

2015-07-15 Thread Nuwan Pallewela

Thanks,
Nuwan

On Wed, Jul 15, 2015 at 5:05 PM, Rajeevan Vimalanathan 
wrote:

> Merged!
>
> Thanks,
> Rajeevan
>
> On Wed, Jul 15, 2015 at 2:30 PM, Nuwan Pallewela  wrote:
>
>>
>> Hi,
>> Please review and merge PR [1] and [2] -
>>  Tools-2932 : Importing existing registry project throws an exception
>>
>> [1] https://github.com/wso2/developer-studio/pull/70
>> [2] https://github.com/wso2/developer-studio/pull/71
>> --
>> --
>>
>> *Nuwan Chamara Pallewela*
>>
>>
>> *Software Engineer*
>>
>> *WSO2, Inc. *
>> *lean . enterprise . middleware*
>>
>> Email   *nuw...@wso2.com *
>> Mobile  *+94719079739 <%2B94719079739>*
>> *+94767100087 <%2B94767100087>*
>>
>>
>> ___
>> 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>*
>



-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739*
*+94767100087*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [DEV][DevStudio] Please review and merge the PR for Fixing Tools-2899

2015-07-16 Thread Nuwan Pallewela

Hi,
Please review and merge PR [1] and [2]-
 Tools-2899 : When artifact name already exists, meaningless error given in
UI for Inbound endpints.

[1] https://github.com/wso2/developer-studio/pull/72
[2] https://github.com/wso2/developer-studio/pull/73

Thanks,
Nuwan
-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739*
*+94767100087*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV][DevStudio] Please review and merge the PR for Fixing Tools-2899

2015-07-16 Thread Nuwan Pallewela

Thanks,
Nuwan

On Thu, Jul 16, 2015 at 5:28 PM, Kavith Lokuhewage  wrote:

> Hi Nuwan,
>
> Merged the pull request.
>
> Thanks,
>
> On Thu, Jul 16, 2015 at 5:03 PM, Nuwan Pallewela  wrote:
>
>> Hi,
>> Please review and merge PR [1] and [2]-
>>  Tools-2899 : When artifact name already exists, meaningless error given
>> in UI for Inbound endpints.
>>
>> [1] https://github.com/wso2/developer-studio/pull/72
>> [2] https://github.com/wso2/developer-studio/pull/73
>>
>> Thanks,
>> Nuwan
>> --
>> --
>>
>> *Nuwan Chamara Pallewela*
>>
>>
>> *Software Engineer*
>>
>> *WSO2, Inc. *
>> *lean . enterprise . middleware*
>>
>> Email   *nuw...@wso2.com *
>> Mobile  *+94719079739 <%2B94719079739>*
>> *+94767100087 <%2B94767100087>*
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Kavith Lokuhewage*
> Software Engineer
> WSO2 Inc. - http://wso2.com
> lean . enterprise . middleware
> Mobile - +9477-9-145-123 | +9471-455-6-401
> Linkedin <http://www.linkedin.com/pub/kavith-lokuhewage/49/473/419>
> Twitter <https://twitter.com/KavithThiranga>
>



-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739*
*+94767100087*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [DEV][DevStudio] Please review and merge the PR for Fixing Tools-2869

2015-07-20 Thread Nuwan Pallewela

Hi ,
Please review and merge PR [1] and [2]-
 Tools-2869-When a CAR file is generated, artifacts with dependencies comes
up in order than its dependancies
[1] https://github.com/wso2/developer-studio/pull/75
[2] https://github.com/wso2/developer-studio/pull/74

-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739*
*+94767100087*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV][DevStudio] Please review and merge the PR for Fixing Tools-2869

2015-07-20 Thread Nuwan Pallewela

Thanks,
Nuwan

On Mon, Jul 20, 2015 at 4:26 PM, Rajeevan Vimalanathan 
wrote:

> Merged!
>
> Thanks,
> Rajeevan
>
> On Mon, Jul 20, 2015 at 3:08 PM, Nuwan Pallewela  wrote:
>
>> Hi ,
>> Please review and merge PR [1] and [2]-
>>  Tools-2869-When a CAR file is generated, artifacts with dependencies
>> comes up in order than its dependancies
>> [1] https://github.com/wso2/developer-studio/pull/75
>> [2] https://github.com/wso2/developer-studio/pull/74
>>
>> --
>> --
>>
>> *Nuwan Chamara Pallewela*
>>
>>
>> *Software Engineer*
>>
>> *WSO2, Inc. *
>> *lean . enterprise . middleware*
>>
>> Email   *nuw...@wso2.com *
>> Mobile  *+94719079739 <%2B94719079739>*
>> *+94767100087 <%2B94767100087>*
>>
>>
>> ___
>> 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>*
>



-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739*
*+94767100087*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [DEV][DevStudio] Please review and merge the PR for Fixing Tools-2981

2015-07-20 Thread Nuwan Pallewela

Hi ,
Please review and merge PR [1] and [2]-
 Tools-2981 : Inbound Endpoints folder in ESB Config project, doesn't
contain new Inbound End point option in it's menu
[1] https://github.com/wso2/developer-studio/pull/76
[2] https://github.com/wso2/developer-studio/pull/77

Thanks,
Nuwan

-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739*
*+94767100087*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [DEV][DevStudio] Please review and merge the PR for Fixing Tools-2926

2015-07-21 Thread Nuwan Pallewela

Hi ,
Please review and merge PR [1] and [2]-
 Tools-2926 : Cannot browse security policies from workspace for BPEL
"Apply security" wizard.
[1] https://github.com/wso2/developer-studio/pull/79
[2] https://github.com/wso2/developer-studio/pull/78

Following are the major changes done in this pull request.

   - Created a new package as
   "org.wso2.developerstudio.eclipse.artifact.bpel.dialogs" in
   "org.wso2.developerstudio.eclipse.artifact.bpel/src"
   - New class file named RegistryResourseFileProviderDialog was created
   which extends "DeveloperStudioElementProviderDialog" class in package
   "org.wso2.developerstudio.eclipse.general.project.dialogs" at
   "org.wso2.developerstudio.eclipse.general.project/src"
   - New method was created in DeveloperStudioElementProviderDialog class
   which sub classes must override.


Thanks,
Nuwan

-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739*
*+94767100087*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV][DevStudio] Please review and merge the PR for Fixing Tools-2926

2015-07-21 Thread Nuwan Pallewela

Hi,

Please consider the following [3] and [4] pull requests for the above issue
and don't merge above [1] and [2] pull requests.

[3] https://github.com/wso2/developer-studio/pull/80
[4] https://github.com/wso2/developer-studio/pull/81

Thanks,
Nuwan

On Tue, Jul 21, 2015 at 6:26 PM, Nuwan Pallewela  wrote:

> Hi ,
> Please review and merge PR [1] and [2]-
>  Tools-2926 : Cannot browse security policies from workspace for BPEL
> "Apply security" wizard.
> [1] https://github.com/wso2/developer-studio/pull/79
> [2] https://github.com/wso2/developer-studio/pull/78
>
> Following are the major changes done in this pull request.
>
>- Created a new package as
>"org.wso2.developerstudio.eclipse.artifact.bpel.dialogs" in
>"org.wso2.developerstudio.eclipse.artifact.bpel/src"
>- New class file named RegistryResourseFileProviderDialog was created
>which extends "DeveloperStudioElementProviderDialog" class in package
>"org.wso2.developerstudio.eclipse.general.project.dialogs" at
>"org.wso2.developerstudio.eclipse.general.project/src"
>- New method was created in DeveloperStudioElementProviderDialog class
>which sub classes must override.
>
>
> Thanks,
> Nuwan
>
> --
> --
>
> *Nuwan Chamara Pallewela*
>
>
> *Software Engineer*
>
> *WSO2, Inc. *
> *lean . enterprise . middleware*
>
> Email   *nuw...@wso2.com *
> Mobile  *+94719079739 <%2B94719079739>*
> *+94767100087 <%2B94767100087>*
>
>



-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739*
*+94767100087*
___
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

2016-03-18 Thread Nuwan Pallewela

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 
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 *
Mobile  *+94719079739@*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Deciding a file type for Json Schema

2016-03-19 Thread Nuwan Pallewela

Hi All,

I also think that it is not required to introduce a new extension for json
schema files.
The common method to differentiate JSON files from JSON Schema files is the
"$schema" field in the json.

Eg:

{
  "$schema": "http://json-schema.org/draft-04/schema#";,
  "id": "http://jsonschema.net";,
  "title" : "employees",
  "type": "object",
  .
}

Thanks,
Nuwan

On Sat, Mar 19, 2016 at 3:13 PM, Viraj Rajaguru  wrote:

> 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 
> 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  wrote:
>>
>>>
>>>
>>> On Thu, Mar 10, 2016 at 2:41 PM, Sohani Weerasinghe 
>>> 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 >>> > 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
>
>


-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *http://wso2.com
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739@*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Namespaces and Attributes in JSON Schema

2016-03-21 Thread Nuwan Pallewela

; "properties": {
> "city": {
> "id": "http://jsonschema.net/employee/0/address/city";,
> "type": "string"
> },
>"road": {
> "id": "http://jsonschema.net/employee/0/address/road";,
> "type": "string"
> }
> }
> }
>
> Two reasons to suggest this :
>
> 1. We do not have to use a prefix to define attributes and they can be
> easily distinguished from other fields since they are defined separate from
> other fields (properties)
> 2. In the case of a primitive type with attributes, we can still preserve
> the type as string and have attributes instead of using properties (since
> properties are only valid in json schema for object type)
>
>
> WDYT?
>
> Thanks,
> Maheeka
>
> Maheeka Jayasuriya
> Software Engineer
> Mobile : +9450661
>
> On Wed, Mar 16, 2016 at 10:54 AM, Sohani Weerasinghe 
> wrote:
>
>> Hi,
>>
>> Please find the schema and the visual representation for representing the
>> attributes.
>>
>>   {
>>   "$schema": "http://json-schema.org/draft-04/schema#";,
>>   "id": "http://jsonschema.net";,
>>   "title" : "employees",
>>   "type": "object",
>>   "properties": {
>> "employee": {
>>   "id": "http://jsonschema.net/employee";,
>>   "type": "array",
>>   "items": {
>> "id": "http://jsonschema.net/employee/0";,
>> "type": "object",
>> "properties": {
>>   "firstname": {
>> "id": "http://jsonschema.net/employee/0/firstname";,
>> "type": "string"
>>   },
>>   "lastname": {
>> "id": "http://jsonschema.net/employee/0/lastname";,
>> "type": "string"
>>   },
>>   "address": {
>> "id": "http://jsonschema.net/employee/0/address";,
>> "type": "object",
>> "properties": {
>>   "city": {
>> "id": "http://jsonschema.net/employee/0/address/city";,
>> "type": "string"
>>   },
>>  * "@no": {*
>> "id": "http://jsonschema.net/employee/0/address/no";,
>> "type": "string"
>>   },
>>   "road": {
>> "id": "http://jsonschema.net/employee/0/address/road";,
>> "type": "string"
>>   }
>> }
>>   }
>> },
>> "required": [
>>   "firstname",
>>   "lastname",
>>   "address"
>> ]
>>   },
>>   "required": [
>> "0"
>>   ]
>> }
>>   },
>>   "required": [
>> "employee"
>>   ]
>> }
>>
>> 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 Wed, Mar 16, 2016 at 10:35 AM, Sohani Weerasinghe 
>> wrote:
>>
>>> Thanks Nuwan. Shall we go with '@' then?
>>>
>>> Sohani Weerasinghe
>>> Software Engineer
>>> WSO2, Inc: http://wso2.com
>>>
>>> Mobile  : +94 716439774
>>> Blog :http://christinetechtips.blogspot.com/
>>> Twitter  : https://twitter.com/sohanichristine
>>>
>>> On Wed, Mar 16, 2016 at 10:23 AM, Nuwan Pallewela 
>>> wrote:
>>>
>>>> Hi sohani,
>>>>
>>>> I think we do not need to include new type called "attr" to define it
>>>> as a attribute. We can name the field with a prefix like "@" or "attr_".
>>>>
>>>> Eg:
>>>> "@firstname": {
>>>> "id": "http://jsonschema.net/employee/0/firstname";,
>>>> "type": "string"
>>>>   },
>>>>
>>>> or
>>>>
>>>> "attr_firstname": {
>>>> "id": "http://jsonschema.net/employee/0/firstname";,
>>>> "type": "string"
>>>>   },
>>>>
>>>> Thanks,
>>>> Nuwan
>>>>
>>>> On Wed, Mar 16, 2016 at 10:15 AM, Sohani Weerasinghe 
>>>> wrote:
>>>>
>>>>> Hi Nuwan/ Viraj,
>>>>>
>>>>> Can you please mention how are we going to handle $subject?
>>>>>
>>>>> Can we have a new field as attr as below to handle the attributes?
>>>>>
>>>>> "firstname": {
>>>>> "id": "http://jsonschema.net/employee/0/firstname";,
>>>>> "type": "string",
>>>>> *"attr" : "xyz"*
>>>>>   },
>>>>>
>>>>> 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 *
>>>> Mobile  *+94719079739 <%2B94719079739>@*
>>>>
>>>>
>>>>
>>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>


-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *http://wso2.com
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739@*
___
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

2016-04-10 Thread Nuwan Pallewela

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 
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 
> 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 *
Mobile  *+94719079739@*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV] [ESB] Change payload response (LDAP Connector)

2016-04-25 Thread Nuwan Pallewela

Hi Willian,

Do you want to change the message structure?

If you don't need to change the message structure, you can change the axis2
messageType property to "json/application" and esb formatters will convert
it to JSON.
Eg:



If you want to change the message structure you can use FastXSLT
mediator [1] and then formatter to convert it to JSON as mention
above.
Performance of FastXSLT mediator in transforming messages is also
better as you can see in the [2].

You can find more information abount JSON support in [3].

[1] https://docs.wso2.com/display/ESB481/FastXSLT+Mediator
[2] 
http://soatutorials.blogspot.com/2016/01/wso2-esb-performance-tuning-for-xslt.html
[3] 
https://docs.wso2.com/display/ESB481/JSON+Support#JSONSupport-ConvertingapayloadbetweenXMLandJSON

Thanks,
Nuwan

On Tue, Apr 26, 2016 at 2:47 AM, Willian Antunes <
willian.lima.antu...@gmail.com> wrote:

> Hello everyone,
>
> One I consult my internal LDAP using LDAP Connector to retrieve the
> details regarding some user I receive a huge response. For example (I'm
> omitting anothers groups contained in memberOf):
>
> http://www.w3.org/2003/05/soap-envelope";>
> http://org.wso2.esbconnectors.ldap";>
> 
> CN=Willian Lima Antunes,OU=Users,OU=Online,OU=DU
> Editorial,DC=aqlbras,DC=com,DC=br
> Willian Lima Antunes - Tecnologia Digital - Editora
> Globo
> Willian
> wantu...@willianantunes.com.br
> Lima Antunes
>
> CN=grupoedgfuncionarios,CN=Users,DC=aqlbras,DC=com,DC=br
>
> CN=EgspPRINT_6A1-new,CN=Users,DC=aqlbras,DC=com,DC=br
>
> CN=EgspPRINT_9A3,CN=Users,DC=aqlbras,DC=com,DC=br
>
> CN=EgspPRINT_8A1,CN=Users,DC=aqlbras,DC=com,DC=br
> CN=aws,OU=Groups,OU=Online,OU=DU
> Editorial,DC=aqlbras,DC=com,DC=br
> CN=Ecommerce,OU=Groups,OU=Online,OU=DU
> Editorial,DC=aqlbras,DC=com,DC=br
> CN=Grupo E-commerce -
> TI,CN=Users,DC=aqlbras,DC=com,DC=br
>
> CN=EgspUTLFILE_TRN02CP,CN=Users,DC=aqlbras,DC=com,DC=br
> 
> 
> 
>
> What is the fastest way to change it to JSON? I know a way to do it
> through Payload Factory mediator, but the work to map each value in a
> variable is hard-working and the response may vary.
>
> Can I configure to receive a JSON instead of SOAP at the LDAP Connector
> side?
>
> Any suggestions would be appreciated.
>
> Thanks.
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *http://wso2.com
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739 <%2B94719079739>@*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Data Mapper - xsi:type representation in JSON schema

2016-04-30 Thread Nuwan Pallewela

On Sat, Apr 30, 2016 at 9:48 PM, Sohani Weerasinghe  wrote:

> Hi Viraj,
>
> Thanks for the input. Please find the comments inline
>
> Sohani Weerasinghe
> Software Engineer
> WSO2, Inc: http://wso2.com
>
> Mobile  : +94 716439774
> Blog :http://christinetechtips.blogspot.com/
> Twitter  : https://twitter.com/sohanichristine
>
> On Sat, Apr 30, 2016 at 1:51 PM, Viraj Rajaguru  wrote:
>
>> Hi Sohani,
>>
>> Few suggestions,
>>
>> 1. Lets change value of "type" from "array" to "object" in "urn:sObjects,
>> xsi:type=urn1:Contact" and "urn:sObjects, xsi:type=urn1:Account" as we are
>> not considering this as an array of "urn:sObjects" but two different
>> elements.
>>
>> Eg:
>>
>> "urn:sObjects, xsi:type=urn1:Contact":{
>>"id":"
>> http://wso2jsonschema.org/soapenv:Body/urn:create/urn:sObjects";,
>> "type":"object",
>> ...
>>
> Yes. This should represent as Objects.


> +1 Let's do like that. But if this is inside an array, then this should be
> serialized inside the properties block of the items block
>
 Yes. It should be represent as object elements of array of create elements.

@Sohani: How we are going to handle following kind of message?


http://schemas.xmlsoap.org/soap/envelope/";
xmlns:urn="urn:enterprise.soap.sforce.com" xmlns:urn1="urn:
sobject.enterprise.soap.sforce.com" xmlns:xsi="
http://www.w3.org/2001/XMLSchema-instance";>
   
  
 QwWsHJyTPW.1pd0_jXlNKOSU
  
   
   
  
   *  *
*001D00HRzKD*
*Jane*
*Doe*

* ** *
*001D00HRzKD*
*Pattric*
*Warne*
* *

* *
*Acme Rockets, Inc.*
* *
  
   


Do we consider *urn1:Contact elements* as an array of elements?


>
>>
>> 2. Remove the space in "urn:sObjects, xsi:type=urn1:Contact" field name.
>> Lets change it to "urn:sObjects,xsi:type=urn1:Contact"
>>
>
> A space has been added to clearly identify the name and the element
> identifier, but let's remove it and I also think it's better
>
>>
>> 3. Change "id" value from "id":"
>> http://wso2jsonschema.org/soapenv:Body/urn:create/urn:sObjects"; to "id":"
>> http://wso2jsonschema.org/soapenv:Body/urn:create/urn:sObjects,xsi:type=urn1:Contact";
>> and "id":"
>> http://wso2jsonschema.org/soapenv:Body/urn:create/urn:sObjects,xsi:type=urn1:Account";
>> accordingly as now "urn:sObjects,xsi:type=urn1:Contact" and
>> "urn:sObjects,xsi:type=urn1:Account" are the unique identifiers not the
>> "urn:sObjects"
>>
>> 4. In the graphical representation users are not suppose to map value of
>> xsi:type attribute to another. It's kind of a metadata. So that I think
>> it's better hide xsi:type attribute from input/output tree.
>>
>
> I have added this to the tree view as an attribute since as I remember we
> discussed that there can be use cases. @nuwan can you please confirm?  If
> we don't have such use cases we can simply remove this when generating the
> schema so that it will not represent in the tree
>
Yes, I think it may required to map the value of the xsi:type in some
cases.
I Agree that it is a constant value in this case. So user can also use a
constant operator instead of it. But there can be occasions like user may
need to get two representations of same kind of elements to one common
format as shown below.

Different representation of contact elements in US and UK
**
*001D00HRzKD*
*Jane*
*Doe*
**


**
*001D00HRzKD*
*Jane **Doe*
**

Need to convert to a common format
**
*001D00HRzKD*
*Jane*
*Doe*
**



>> Thanks.
>> Viraj.
>>
>>
>>
>> On Thu, Apr 28, 2016 at 3:07 PM, Sohani Weerasinghe 
>> wrote:
>>
>>> Hi All,
>>>
>>> We are in a process of supporting the xsi:type in JSON Schema and please
>>> find the below implementation details.
>>>
>>> *Input*:
>>>
>>> 
>>> http://schemas.xmlsoap.org/soap/envelope/"; xmlns:urn="urn:
>>> enterprise.soap.sforce.com" xmlns:urn1="urn:
>>> sobject.enterprise.soap.sforce.com" xmlns:xsi="
>>> http://www.w3.org/2001/XMLSchema-instance";>
>>>
>>>   
>>>  QwWsHJyTPW.1pd0_jXlNKOSU
>>>   
>>>
>>>
>>>   
>>>*  *
>>> **
>>> **
>>> *001D00HRzKD*
>>> *Jane*
>>> *Doe*
>>> * *
>>> * *
>>> *Acme Rockets, Inc.*
>>> * *
>>>   
>>>
>>> 
>>>
>>>
>>> *Generated JSON schema via the Data Mapper editor :*
>>>
>>> {
>>>"$schema":"http://json-schema.org/draft-04/schema#";,
>>>"id":"http://wso2jsonschema.org";,
>>>"title":"soapenv:Envelope",
>>>"type":"object",
>>>   * "elementIdentifiers":[  *
>>> *  {  *
>>> * "type":"xsi:type"*
>>> *  }*
>>> *   ],*
>>>"properties":{
>>>   "soapenv:Body":{
>>>  "id":"http://wso2jsonschema.org/soapenv:Body";,
>>>  "type":"object",
>>>  "properties":{
>>>

Re: [Dev] [ESB Tooling][Mediation Debugger] Does not debug APIs

2016-05-03 Thread Nuwan Pallewela

Hi Dilshani,

Can you send me the api configuration file and the breakpoints you marked?

Thanks,
Nuwan

On Tue, May 3, 2016 at 2:22 PM, Dilshani Subasinghe 
wrote:

> Hi ESB Team,
>
> As I found, mediation debugging feature does not work for APIs. I didn't
> even see any functional test cases related to APIs.
>
> Did you not developed that feature to cover APIs or missed covering APIs ?
>
> Any clarifications will be really helpful.
>
> Thank you.
>
> --
> Best Regards,
>
> Dilshani Subasinghe
> Software Engineer - QA
> WSO2, Inc.;http://wso2.com/
> 
> lean.enterprise.middleware
>
> Mobile: +94773375185
>
> Blog: dilshanilive.blogspot.com
>



-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *http://wso2.com
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739@*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB Tooling][Mediation Debugger] Does not debug APIs

2016-05-03 Thread Nuwan Pallewela

Hi Dilshani,

Can you try it with only specifying one method type as "GET" or "POST" and
try?

Thanks,
Nuwan

On Tue, May 3, 2016 at 2:38 PM, Dilshani Subasinghe 
wrote:

> Hi Nuwan,
>
> Please find the attachment of API configuration file and I added few
> breakpoints as follows:
>
> API in sequence - Log mediator, payload mediator, send mediator
>
> API out sequence - Property, payload and send mediators
>
> Regards,
> Dilshani
>
>
> On Tue, May 3, 2016 at 2:27 PM, Nuwan Pallewela  wrote:
>
>> Hi Dilshani,
>>
>> Can you send me the api configuration file and the breakpoints you marked?
>>
>> Thanks,
>> Nuwan
>>
>> On Tue, May 3, 2016 at 2:22 PM, Dilshani Subasinghe 
>> wrote:
>>
>>> Hi ESB Team,
>>>
>>> As I found, mediation debugging feature does not work for APIs. I didn't
>>> even see any functional test cases related to APIs.
>>>
>>> Did you not developed that feature to cover APIs or missed covering APIs
>>> ?
>>>
>>> Any clarifications will be really helpful.
>>>
>>> Thank you.
>>>
>>> --
>>> Best Regards,
>>>
>>> Dilshani Subasinghe
>>> Software Engineer - QA
>>> WSO2, Inc.;http://wso2.com/
>>> <http://www.google.com/url?q=http%3A%2F%2Fwso2.com%2F&sa=D&sntz=1&usg=AFQjCNGJuLRux6KkJwXKVUCYOtEsNCmIAQ>
>>> lean.enterprise.middleware
>>>
>>> Mobile: +94773375185
>>>
>>> Blog: dilshanilive.blogspot.com
>>>
>>
>>
>>
>> --
>> --
>>
>> *Nuwan Chamara Pallewela*
>>
>>
>> *Software Engineer*
>>
>> *WSO2, Inc. *http://wso2.com
>> *lean . enterprise . middleware*
>>
>> Email   *nuw...@wso2.com *
>> Mobile  *+94719079739 <%2B94719079739>@*
>>
>>
>>
>
>
> --
> Best Regards,
>
> Dilshani Subasinghe
> Software Engineer - QA
> WSO2, Inc.;http://wso2.com/
> <http://www.google.com/url?q=http%3A%2F%2Fwso2.com%2F&sa=D&sntz=1&usg=AFQjCNGJuLRux6KkJwXKVUCYOtEsNCmIAQ>
> lean.enterprise.middleware
>
> Mobile: +94773375185
>
> Blog: dilshanilive.blogspot.com
>



-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *http://wso2.com
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739@*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB 5.0.0][Mediation Debugger]After restarting debug process, it will not take previous debug points

2016-05-09 Thread Nuwan Pallewela

Hi Dilshani,

Thank you for pointing out this. ESB will forget the registered debug
points when synapse configuration changes or server gets restarts. So when
one of those happens user need to use the  *"Resend ESB Debug Points"*
command to re-register the debug-points in the server.

But I think we need to do this improvement in ESB side. We should send the
registered debug-points automatically when user connects esb server in
debug mode with esb tool or synapse configuration changes in the server.

Thanks,
Nuwan

On Mon, May 9, 2016 at 12:09 PM, Dilshani Subasinghe 
wrote:

> Hi ESB Team,
>
> After restarting debug process, it may not identify previously added debug
> points. But newly added ESB points will be added to debug process
> successfully.
>
> When we using the option "*Resend ESB Debug Points*", it may send
> previous debug points too.
>
> As Far As I Feel, this is bit of misleading and I also took much time to
> identify relevant option.
>
> What is the improvement you can do about that ?
>
> @Nisrin/Praneesha - As I seen in the blog post (
> https://nuwanpallewela.wordpress.com/2016/04/10/how-to-debug-wso2-esb-mediation-flow/),
> "*Resend ESB Debug Points*" will be useful when we changing the artifact.
> But in documentation it may just give explanation like "Sends all
> registered debugging points to the ESB Server".
>
> Hope it will be better to be more descriptive with relevant
> functionalities (Ex: When to use). Because user may confuse with exact
> options as they are having similar functionalities.
>
> Thank you
>
> --
> Best Regards,
>
> Dilshani Subasinghe
> Software Engineer - QA
> WSO2, Inc.;http://wso2.com/
> 
> lean.enterprise.middleware
> Mobile: +94773375185
> Blog: dilshanilive.blogspot.com
>



-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *http://wso2.com
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739@*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB 5.0.0][Mediation Debugger]After restarting debug process, it will not take previous debug points

2016-05-09 Thread Nuwan Pallewela

Hi Chanaka,

This is not reported as a public JIRA yet.

Thanks,
Nuwan

On Mon, May 9, 2016 at 12:51 PM, Chanaka Fernando  wrote:

> Is there any public JIRA already created?
>
> On Mon, May 9, 2016 at 12:46 PM, Isabelle Mauny  wrote:
>
>> +1 - Can we fix this in 5.0.0 …
>> __
>>
>> Isabelle Mauny
>> VP, Product Management; WSO2, Inc.;  http://wso2.com/
>>
>> On May 9, 2016, at 9:05 AM, Chathurika De Silva 
>> wrote:
>>
>> Hi ESB Team
>>
>> Addition to dilshani' and nuwan's feedback, from user's perspective, when
>> debug points are set and if the artifact is not changed, the need for him
>> to resend debug point information is an additional task. Ideally it's
>> better to give the same feel to a developer who is using this tool after
>> using the general eclipse debugging (since we are based on eclipse). It's
>> understandable that resend is needed when the artifact has changed, but if
>> doesn't the developer should be able to start debugging without any extra
>> effort from the tooling side. So is there any possibility in getting this
>> fixed with this release rather than marking it as an improvement?
>>
>> Thank You
>> Erandi
>>
>> On Mon, May 9, 2016 at 12:09 PM, Dilshani Subasinghe 
>> wrote:
>>
>>> Hi ESB Team,
>>>
>>> After restarting debug process, it may not identify previously added
>>> debug points. But newly added ESB points will be added to debug process
>>> successfully.
>>>
>>> When we using the option "*Resend ESB Debug Points*", it may send
>>> previous debug points too.
>>>
>>> As Far As I Feel, this is bit of misleading and I also took much time to
>>> identify relevant option.
>>>
>>> What is the improvement you can do about that ?
>>>
>>> @Nisrin/Praneesha - As I seen in the blog post (
>>> https://nuwanpallewela.wordpress.com/2016/04/10/how-to-debug-wso2-esb-mediation-flow/),
>>> "*Resend ESB Debug Points*" will be useful when we changing the
>>> artifact. But in documentation it may just give explanation like "Sends
>>> all registered debugging points to the ESB Server".
>>>
>>> Hope it will be better to be more descriptive with relevant
>>> functionalities (Ex: When to use). Because user may confuse with exact
>>> options as they are having similar functionalities.
>>>
>>> Thank you
>>>
>>> --
>>> Best Regards,
>>>
>>> Dilshani Subasinghe
>>> Software Engineer - QA
>>> WSO2, Inc.;http://wso2.com/
>>> 
>>> lean.enterprise.middleware
>>> Mobile: +94773375185
>>> Blog: dilshanilive.blogspot.com
>>>
>>
>>
>>
>> --
>> *Chathurika Erandi*
>> Software Engineer,
>> WSO2 Inc.
>>
>> *E-mail:* chathuri...@wso2.com
>> *Mobile: *+94714 328 612
>> *Blog*: chathurikaerandi.blogspot.com
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "WSO2 Documentation Group" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to documentation+unsubscr...@wso2.com.
>> For more options, visit https://groups.google.com/a/wso2.com/d/optout.
>>
>>
>>
>
>
> --
> Thank you and Best Regards,
> Chanaka Fernando
> Senior Technical Lead
> WSO2, Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: +94 773337238
> Blog : http://soatutorials.blogspot.com
> LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0
> Twitter:https://twitter.com/chanakaudaya
>
>
>
>
>


-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *http://wso2.com
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739@*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Unable to load file for schema generation

2016-05-11 Thread Nuwan Pallewela

Hi Shakila,

Yes. This JSON message format is not yet supported in DataMapper schema
generator. We will inform you when it is fixed[1].

[1] https://wso2.org/jira/browse/DEVTOOLESB-158

Thanks,
Nuwan

On Wed, May 11, 2016 at 4:51 PM, Shakila Sivagnanarajah 
wrote:

> Hi all,
>
> Unable to load the uploaded json file to generate output schema. It says
> "File content cannot be parsed". Could you please check this? Please find
> the attachment below.
>
> Thank you.
>
> --
> Shakila Sivagnanarajah
> Associate Software Engineer
> Mobile :+94 (0) 768 856837
> shak...@wso2.com
>



-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *http://wso2.com
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739@*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Vote] Developer Studio Kernel RC 2 released !

2016-05-11 Thread Nuwan Pallewela

Hi All,

There is an issue reported when creating pass though proxy services[1].
This is because a template file in
org.wso2.developerstudio.eclipse.platform.core/resources/templates/
proxyservices/*pass-through-proxy.xml.* I think we should fix this. I have
sent a PR to fix this issue[2].

[1] https://wso2.org/jira/browse/DEVTOOLESB-166
[2] https://github.com/wso2/developer-studio/pull/143

Thanks,
Nuwan

On Wed, May 11, 2016 at 11:41 AM, Awanthika Senarath 
wrote:

> Hello Jasintha,
>
> Noted, Please find my inline comments
>
> -All submenus should have a menu icon
>
> +1, I will look into this.
>
> -Capp and Maven preferences pages  should be removed from kernel and
> should only appear when that plugins are installed
>
> +1, Will remove these from Kernel and move them to appropriate platform
> bundles.
>
> -In Install feature dialog , WSO2 carbon UI appear before the BPS feature
> , seems there is bug when sorting
>
> I checked this. The sorting happens from the ID of the plugin and not the
> Display name. The IDs of these plugins are in such a way that when they are
> sorted alphabetically the order appears as mentioned. We need to revisit
> the feature IDs of all product plugins bearing the knowledge that the ID
> determines the order in which the plugins appear in the updater tool
>
> -Menu seperators are appearing in Developer studio menu , all the eclipse
> standard menus has menu separators
> -Add keyboard shortcut for relevant sub menus
> -better if we can add submenu under Developer studio menu to reach
> Developer studio preferences  directly
>
> I will look into this. Yet these are not blockers IMO.
>
> Regards
> Awanthika
>
> Awanthika Senarath
> Software Engineer, WSO2 Inc.
> Mobile: +94717681791
>
>
>
> On Tue, May 10, 2016 at 7:55 AM, Jasintha Dasanayake 
> wrote:
>
>> I have noticed following  improvement , those are not blockers but better
>> if we can get it fix in GA from usability point of view
>>
>> -Menu seperators are appearing in Developer studio menu , all the eclipse
>> standard menus has menu separators
>> -Add keyboard shortcut for relevant sub menus
>> -All submenus should have a menu icon
>> -better if we can add submenu under Developer studio menu to reach
>> Developer studio preferences  directly
>> -Capp and Maven preferences pages  should be removed from kernel and
>> should only appear when that plugins are installed
>> -In Install feature dialog , WSO2 carbon UI appear before the BPS
>> feature , seems there is bug when sorting
>>
>> Apart from above important all other major features are working fine
>>
>> Thanks and Regards
>> /Jasintha
>>
>>
>>
>>
>> On Thu, May 5, 2016 at 3:01 PM, Awanthika Senarath 
>> wrote:
>>
>>> Hello Devs,
>>>
>>>
>>> We are pleased to announce the vote for RC-2 of
>>> *WSO2 Developer Studio Kernel 4.1.0.*
>>>
>>> P2 repository of WSO2 developer Studio kernel 4.1.0 is available here
>>> .
>>>  Source
>>> and Tag Location to be voted upon is available here
>>> 
>>> .
>>>
>>> Developer Studio 4.1.0 Kernel is released on Eclipse Mars (Eclipse 4.5)
>>>
>>> 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
>>>- Improvements in the Developer Studio Updater tool for automatic
>>>updates
>>>
>>> The Features and improvements in the RC 2 :
>>>
>>>
>>>1. [+] Stable - go ahead and release
>>>2. [-]  Broken - do not release (please explain why)
>>>
>>>
>>>
>>> Regards,
>>> Dev Studio Team
>>> Awanthika Senarath
>>> Software Engineer, WSO2 Inc.
>>> Mobile: +94717681791
>>>
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>>
>> *Jasintha Dasanayake*
>>
>> *Senior Software EngineerWSO2 Inc. | http://wso2.com
>> lean . enterprise . middleware*
>>
>>
>> *mobile :- 0711368118*
>>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *http://wso2.com
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739@*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Unable to generate the schema if the payload does not contain root element

2016-05-17 Thread Nuwan Pallewela

Hi Shakila,

The JSON schema for above mention payload [1] should be as follows.

{
   "id":"http:\/\/wso2jsonschema.org",
   "title":"root",
   "$schema":"http:\/\/json-schema.org\/draft-04\/schema#",
   "items":[
  {
 "id":"http:\/\/wso2jsonschema.org\/ids\/0",
 "type":"string"
  }
   ],
   "type":"array"
}

Schema title represent the name for the most outer JSON element. In this
case we give the name as root and it is a array. So the "type" attribute
should be "array".

And then the "items" list down the type of elements in the array, in this
case they are string elements.

Thanks,
Nuwan

On Tue, May 17, 2016 at 2:30 PM, Shakila Sivagnanarajah 
wrote:

> Hi,
>
> If the payload does not contain the root element, It is not loading the
> file to generate the schema as reported in [1]. I manually added a root
> element and a child element in the payload [2] as shown in [3] and
> generated the schema [4]. Then I deleted the root element and child
> (highlighted parts in [4]). The final schema looks like [5]. Could you
> please make sure that the output schema [5] is in a correct format?
>
> [1] https://wso2.org/jira/browse/DEVTOOLESB-226
>
> [2]
> [
> "777925",
> "732321"
> ]
>
> [3]
> {
> "rootelem": [
> "777925",
> "732321"
> ],
> "dummychild": "dummyval"
> }
>
> [4]
> {
> "id": "http:\/\/wso2jsonschema.org",
> "title": "root",
> "$schema": "http:\/\/json-schema.org\/draft-04\/schema#",
> "properties": {
> "rootelem": {
> "id": "http:\/\/wso2jsonschema.org\/rootelem",
> "items": [
> {
> "id": "http:\/\/wso2jsonschema.org\/rootelem\/0",
> "type": "string"
> }
> ],
> "type": "array"
> },
> "dummychild": {
> "id": "http:\/\/wso2jsonschema.org\/dummychild",
> "type": "string"
> }
> },
> "type": "object"
> }
>
> [5]
> {
> "id": "http:\/\/wso2jsonschema.org",
> "title": "root",
> "$schema": "http:\/\/json-schema.org\/draft-04\/schema#",
> "properties": {
> "items": [
> {
> "id": "http:\/\/wso2jsonschema.org\/ids\/0",
> "type": "string"
> }
> ]
> },
> "type": "object"
> }
>
>
> Thank you
> --
> Shakila Sivagnanarajah
> Associate Software Engineer
> Mobile :+94 (0) 768 856837
> shak...@wso2.com
>



-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *http://wso2.com
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739@*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Unable to generate the schema if the payload does not contain root element

2016-05-17 Thread Nuwan Pallewela

Hi Shakila,

We can use "http:\/\/wso2jsonschema.org\/root\/0" as the id here. As log as
it is unique from other sub-schema's it is ok to use any value as the id.
But it is better to go with a convention.

Thanks,
Nuwan

On Tue, May 17, 2016 at 3:11 PM, Shakila Sivagnanarajah 
wrote:

> Thanks Nuwan,
>
> In the id of the items element, the *ids *is the name of the root
> element. So what would be the id here?
>
>   "id":"http:\/\/wso2jsonschema.org\/*ids*\/0",
>
> Thanks
>
> On Tue, May 17, 2016 at 2:49 PM, Nuwan Pallewela  wrote:
>
>> Hi Shakila,
>>
>> The JSON schema for above mention payload [1] should be as follows.
>>
>> {
>>"id":"http:\/\/wso2jsonschema.org",
>>"title":"root",
>>"$schema":"http:\/\/json-schema.org\/draft-04\/schema#",
>>"items":[
>>   {
>>  "id":"http:\/\/wso2jsonschema.org\/ids\/0",
>>  "type":"string"
>>   }
>>],
>>"type":"array"
>> }
>>
>> Schema title represent the name for the most outer JSON element. In this
>> case we give the name as root and it is a array. So the "type" attribute
>> should be "array".
>>
>> And then the "items" list down the type of elements in the array, in this
>> case they are string elements.
>>
>> Thanks,
>> Nuwan
>>
>> On Tue, May 17, 2016 at 2:30 PM, Shakila Sivagnanarajah > > wrote:
>>
>>> Hi,
>>>
>>> If the payload does not contain the root element, It is not loading the
>>> file to generate the schema as reported in [1]. I manually added a root
>>> element and a child element in the payload [2] as shown in [3] and
>>> generated the schema [4]. Then I deleted the root element and child
>>> (highlighted parts in [4]). The final schema looks like [5]. Could you
>>> please make sure that the output schema [5] is in a correct format?
>>>
>>> [1] https://wso2.org/jira/browse/DEVTOOLESB-226
>>>
>>> [2]
>>> [
>>> "777925",
>>> "732321"
>>> ]
>>>
>>> [3]
>>> {
>>> "rootelem": [
>>> "777925",
>>> "732321"
>>> ],
>>> "dummychild": "dummyval"
>>> }
>>>
>>> [4]
>>> {
>>> "id": "http:\/\/wso2jsonschema.org",
>>> "title": "root",
>>> "$schema": "http:\/\/json-schema.org\/draft-04\/schema#",
>>> "properties": {
>>> "rootelem": {
>>> "id": "http:\/\/wso2jsonschema.org\/rootelem",
>>> "items": [
>>> {
>>> "id": "http:\/\/wso2jsonschema.org\/rootelem\/0",
>>> "type": "string"
>>> }
>>> ],
>>> "type": "array"
>>> },
>>> "dummychild": {
>>> "id": "http:\/\/wso2jsonschema.org\/dummychild",
>>> "type": "string"
>>> }
>>> },
>>> "type": "object"
>>> }
>>>
>>> [5]
>>> {
>>> "id": "http:\/\/wso2jsonschema.org",
>>> "title": "root",
>>> "$schema": "http:\/\/json-schema.org\/draft-04\/schema#",
>>> "properties": {
>>> "items": [
>>> {
>>> "id": "http:\/\/wso2jsonschema.org\/ids\/0",
>>> "type": "string"
>>> }
>>> ]
>>> },
>>> "type": "object"
>>> }
>>>
>>>
>>> Thank you
>>> --
>>> Shakila Sivagnanarajah
>>> Associate Software Engineer
>>> Mobile :+94 (0) 768 856837
>>> shak...@wso2.com
>>>
>>
>>
>>
>> --
>> --
>>
>> *Nuwan Chamara Pallewela*
>>
>>
>> *Software Engineer*
>>
>> *WSO2, Inc. *http://wso2.com
>> *lean . enterprise . middleware*
>>
>> Email   *nuw...@wso2.com *
>> Mobile  *+94719079739 <%2B94719079739>@*
>>
>>
>>
>
>
> --
> Shakila Sivagnanarajah
> Associate Software Engineer
> Mobile :+94 (0) 768 856837
> shak...@wso2.com
>



-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *http://wso2.com
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739@*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Allowing to map the leaf nodes - json schema

2016-05-17 Thread Nuwan Pallewela

Hi Sohani,

I think we should support to map attributes too.

Thanks,
Nuwan

On Tue, May 17, 2016 at 4:15 PM, Chanaka Fernando  wrote:

> Hi Sohani,
>
> How will it look like if we expand the array item in the "input" window? I
> guess it will expand and show the attribute and the value. If that is the
> case, we can allow them to map attributes also. WDYT?
>
> On Tue, May 17, 2016 at 3:34 PM, Sohani Weerasinghe 
> wrote:
>
>> Hi Viraj,
>>
>> If we consider an xml as below ( primitive array),  the tree view will be
>> as follows
>>
>> 
>> susinda
>> 0112655655
>> 0112655655
>>  
>>
>>
>> What if, there is an attribute for the 'phone' as below?
>>
>> 
>> susinda
>> 0112655655
>> 0112655655
>>  
>>
>> Are we going to allow users to map both phone and the attribute?
>>
>>
>>
>>
>> Sohani Weerasinghe
>> Software Engineer
>> WSO2, Inc: http://wso2.com
>>
>> Mobile  : +94 716439774
>> Blog :http://christinetechtips.blogspot.com/
>> Twitter  : https://twitter.com/sohanichristine
>>
>> On Tue, May 17, 2016 at 3:30 PM, Sohani Weerasinghe 
>> wrote:
>>
>>> Hi All,
>>>
>>> With the current level of the implementation of  visual datamapper
>>> editor, all nodes of the json schema except the root node can be mapped to
>>> the nodes of another json schema.
>>>
>>> As per the offline discussion we had, we are going to allow users only
>>> to map the leaf nodes of the tree and based on the discussions, the tree
>>> view will be as follows
>>>
>>> 
>>> http://schemas.xmlsoap.org/soap/envelope/"; xmlns:urn="urn:
>>> enterprise.soap.sforce.com" xmlns:urn1="urn:
>>> sobject.enterprise.soap.sforce.com" xmlns:xsi="
>>> http://www.w3.org/2001/XMLSchema-instance";>
>>>
>>>   
>>>  QwWsHJyTPW.1pd0_jXlNKOSU
>>>   
>>>
>>>
>>>   
>>>  
>>> 
>>> 
>>> 001D00HRzKD
>>> Jane
>>> Doe
>>>  
>>>  
>>> Acme Rockets, Inc.
>>>  
>>>   
>>>
>>> 
>>>
>>>
>>>
>>> Thanks,
>>> Sohani
>>>
>>>
>>> Sohani Weerasinghe
>>> Software Engineer
>>> WSO2, Inc: http://wso2.com
>>>
>>> Mobile  : +94 716439774
>>> Blog :http://christinetechtips.blogspot.com/
>>> Twitter  : https://twitter.com/sohanichristine
>>>
>>
>>
>
>
> --
> Thank you and Best Regards,
> Chanaka Fernando
> Senior Technical Lead
> WSO2, Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: +94 773337238
> Blog : http://soatutorials.blogspot.com
> LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0
> Twitter:https://twitter.com/chanakaudaya
>
>
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *http://wso2.com
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739@*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Representing a JSON payload with a single parameter - visual datamapper editor

2016-05-17 Thread Nuwan Pallewela

Hi Sohani,

This looks fine.
+1 for this approach.

Thanks,
Nuwan

On Wed, May 18, 2016 at 9:49 AM, Sohani Weerasinghe  wrote:

>
> 
>
> Sohani Weerasinghe
> Software Engineer
> WSO2, Inc: http://wso2.com
>
> Mobile  : +94 716439774
> Blog :http://christinetechtips.blogspot.com/
> Twitter  : https://twitter.com/sohanichristine
>
> On Wed, May 18, 2016 at 9:48 AM, Sohani Weerasinghe 
> wrote:
>
>> Hi All,
>>
>> If we consider $subject, we need to wrap with a root element when
>> generating the json schema for that json payload.
>>
>> { "tasklist_id": "12345" }
>>
>> Shall we wrap with an element called 'root' ? WDYT?
>>
>> If so, the generated tree and the schema will be as follows
>>
>> {
>>   "$schema" : "http://json-schema.org/draft-04/schema#";,
>>   "id" : "http://wso2jsonschema.org";,
>>   "title" : "*root*",
>>   "type" : "object",
>>   "properties" : {
>> "tasklist_id" : {
>>   "id" : "http://wso2jsonschema.org/tasklist_id";,
>>   "type" : "string"
>> }
>>   }
>> }
>>
>>
>>
>>
>> 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 *
Mobile  *+94719079739@*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Representing a JSON payload with null values - visual datamapper editor

2016-05-17 Thread Nuwan Pallewela

Hi All,

@Vivekanathan : If we need to process/map any value in the payload though
it is optional we have to know the type when generating the schema. So the
sample pay load should not contain null values first place. We need to
modify the sample payload with expected values so that in the schema
generation we could set the type correctly for that field.

@Sohani : +1 for the above mention approach in the schema generation. One
small suggestion to remove the arrow head of type null elements to restrict
users from mapping such elements.

Thanks,
Nuwan

On Wed, May 18, 2016 at 11:51 AM, Vivekananthan Sivanayagam <
vivekanant...@wso2.com> wrote:

> Hi Sohani,
>
> Normally we are getting null value for optional parameter in the API
> response, suppose if we get the actual value for that json object , does
> this schema handle that case?
>
>
>
>
>
> *Thank youVivekananthan Sivanayagam*
>
> *Associate Software Engineer | WSO2*
>
> *E:vivekanant...@wso2.com *
> *M:+94752786138 <%2B94752786138>*
>
> On Wed, May 18, 2016 at 11:19 AM, Sohani Weerasinghe 
> wrote:
>
>> Hi All,
>>
>> If a json payload has null values as shown below, how are we going to
>> represent this in the json schema?
>>
>> {
>>   "root": {
>> "tasklist_id": "12345",
>> "test"=null
>> }
>> }
>>
>> If we are serializing that value, then the generated schema and the tree
>> view will be as follows
>>
>> {
>>   "$schema" : "http://json-schema.org/draft-04/schema#";,
>>   "id" : "http://wso2jsonschema.org";,
>>   "title" : "root",
>>   "type" : "object",
>>   "properties" : {
>> *"test" : {*
>> *  "id" : "http://wso2jsonschema.org/test
>> ",*
>> *  "type" : "null"*
>> *},*
>> "tasklist_id" : {
>>   "id" : "http://wso2jsonschema.org/tasklist_id";,
>>   "type" : "string"
>> }
>>   }
>> }
>>
>>
>> 
>>
>> 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
>>
>
>


-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *http://wso2.com
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739@*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Representing a JSON payload with null values - visual datamapper editor

2016-05-18 Thread Nuwan Pallewela

Hi Malaka,

Yes. We may have to refer api docs and find the expected value for those
optional fields and in the esb runtime data mapper engine should handle
them. But the engine is not implemented up-to that level yet. We should
handle these null-able fields.

Thanks,
Nuwan

On Wed, May 18, 2016 at 12:07 PM, Malaka Silva  wrote:

> Actually those are options for the given configuration. We don't really
> have a clear idea what are the optional response elements. (Unless we refer
> api docs)
>
> So I guess we can proceed with sample values.
>
> From datamapper mediator(ESB Side) level we need to handle if we receive a
> null value. Guess this is already considered?
>
> On Wed, May 18, 2016 at 12:02 PM, Sohani Weerasinghe 
> wrote:
>
>>
>>
>> Sohani Weerasinghe
>> Software Engineer
>> WSO2, Inc: http://wso2.com
>>
>> Mobile  : +94 716439774
>> Blog :http://christinetechtips.blogspot.com/
>> Twitter  : https://twitter.com/sohanichristine
>>
>> On Wed, May 18, 2016 at 12:00 PM, Nuwan Pallewela 
>> wrote:
>>
>>> Hi All,
>>>
>>> @Vivekanathan : If we need to process/map any value in the payload
>>> though it is optional we have to know the type when generating the schema.
>>> So the sample pay load should not contain null values first place. We need
>>> to modify the sample payload with expected values so that in the schema
>>> generation we could set the type correctly for that field.
>>>
>>> @Sohani : +1 for the above mention approach in the schema generation.
>>> One small suggestion to remove the arrow head of type null elements to
>>> restrict users from mapping such elements.
>>>
>>
>> Will do.
>>
>>>
>>> Thanks,
>>> Nuwan
>>>
>>> On Wed, May 18, 2016 at 11:51 AM, Vivekananthan Sivanayagam <
>>> vivekanant...@wso2.com> wrote:
>>>
>>>> Hi Sohani,
>>>>
>>>> Normally we are getting null value for optional parameter in the API
>>>> response, suppose if we get the actual value for that json object , does
>>>> this schema handle that case?
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> *Thank youVivekananthan Sivanayagam*
>>>>
>>>> *Associate Software Engineer | WSO2*
>>>>
>>>> *E:vivekanant...@wso2.com *
>>>> *M:+94752786138 <%2B94752786138>*
>>>>
>>>> On Wed, May 18, 2016 at 11:19 AM, Sohani Weerasinghe 
>>>> wrote:
>>>>
>>>>> Hi All,
>>>>>
>>>>> If a json payload has null values as shown below, how are we going to
>>>>> represent this in the json schema?
>>>>>
>>>>> {
>>>>>   "root": {
>>>>> "tasklist_id": "12345",
>>>>> "test"=null
>>>>> }
>>>>> }
>>>>>
>>>>> If we are serializing that value, then the generated schema and the
>>>>> tree view will be as follows
>>>>>
>>>>> {
>>>>>   "$schema" : "http://json-schema.org/draft-04/schema#";,
>>>>>   "id" : "http://wso2jsonschema.org";,
>>>>>   "title" : "root",
>>>>>   "type" : "object",
>>>>>   "properties" : {
>>>>> *"test" : {*
>>>>> *  "id" : "http://wso2jsonschema.org/test
>>>>> <http://wso2jsonschema.org/test>",*
>>>>> *  "type" : "null"*
>>>>> *},*
>>>>> "tasklist_id" : {
>>>>>   "id" : "http://wso2jsonschema.org/tasklist_id";,
>>>>>   "type" : "string"
>>>>> }
>>>>>   }
>>>>> }
>>>>>
>>>>>
>>>>> 
>>>>>
>>>>> 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
>>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> --
>>>
>>> *Nuwan Chamara Pallewela*
>>>
>>>
>>> *Software Engineer*
>>>
>>> *WSO2, Inc. *http://wso2.com
>>> *lean . enterprise . middleware*
>>>
>>> Email   *nuw...@wso2.com *
>>> Mobile  *+94719079739 <%2B94719079739>@*
>>>
>>>
>>>
>>
>
>
> --
>
> 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.
>



-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *http://wso2.com
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739@*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Output Schema generation for Data Mapper - Byte generated as String

2016-05-18 Thread Nuwan Pallewela

Hi Hariprasath,

How did you generate the schema and what is the payload you used to
generate it?

Thanks,
Nuwan

On Wed, May 18, 2016 at 3:32 PM, Hariprasath Thanarajah <
haripras...@wso2.com> wrote:

> Hi All,
>
> Currently I am doing the schema generation for Gmail REST connector. In
> most of the methods in this connector have the response part as[1], But in
> the JSON schema the type was generated as string[2].
>
> Is there any way to generate as bytes or is it ok to proceed as below?
>
> [1] - {
>   "id": string,
>   "threadId": string,
>   "labelIds": [
> string
>   ],
>   "snippet": string,
>   "historyId": unsigned long,
>   "internalDate": long,
>   "payload": {
> "partId": string,
> "mimeType": string,
> "filename": string,
> "headers": [
>   {
> "name": string,
> "value": string
>   }
> ],
> "body": users.messages.attachments Resource,
> "parts": [
>   (MessagePart)
> ]
>   },
>   "sizeEstimate": integer,
>   "raw": bytes
> }
>
> [2] -
> {"id":"http:\/\/wso2jsonschema.org","title":"root","$schema":"http:\/\/
> json-schema.org
> \/draft-04\/schema#","properties":{"history":{"id":"http:\/\/
> wso2jsonschema.org\/history","items":[{"id":"http:\/\/wso2jsonschema.org
> \/history\/0","properties":{"id":{"id":"http:\/\/wso2jsonschema.org
> \/history\/0\/id","type":"number"},"labelsRemoved":{"id":"http:\/\/
> wso2jsonschema.org\/history\/0\/labelsRemoved","items":[{"id":"http:\/\/
> wso2jsonschema.org
> \/history\/0\/labelsRemoved\/0","properties":{"message":{"id":"http:\/\/
> wso2jsonschema.org\/history\/0\/labelsRemoved\/0\/message","properties":{
> "raw":{"id":"http:\/\/wso2jsonschema.org
> \/history\/0\/labelsRemoved\/0\/message\/raw","type":"string"
> },"id":{"id":"http:\/\/wso2jsonschema.org
> \/history\/0\/labelsRemoved\/0\/message\/id","type":"string"},"labelIds":{"id":"http:\/\/
> wso2jsonschema.org
> \/history\/0\/labelsRemoved\/0\/message\/labelIds","items":[{"id":"http:\/\/
> wso2jsonschema.org
> \/history\/0\/labelsRemoved\/0\/message\/labelIds\/0","type":"string"}],"type":"array"},"threadId":{"id":"http:\/\/
> wso2jsonschema.org
> \/history\/0\/labelsRemoved\/0\/message\/threadId","type":"string"},"historyId":{"id":"http:\/\/
> wso2jsonschema.org
> \/history\/0\/labelsRemoved\/0\/message\/historyId","type":"string"},"payload":{"id":"http:\/\/
> wso2jsonschema.org
> \/history\/0\/labelsRemoved\/0\/message\/payload","properties":{"headers":{"id":"http:\/\/
> wso2jsonschema.org
> \/history\/0\/labelsRemoved\/0\/message\/payload\/headers","items":[{"id":"http:\/\/
> wso2jsonschema.org
> \/history\/0\/labelsRemoved\/0\/message\/payload\/headers\/0","type":"object"}],"type":"array"},"body":{"id":"http:\/\/
> wso2jsonschema.org
> \/history\/0\/labelsRemoved\/0\/message\/payload\/body","properties":{"attachmentId":{"id":"http:\/\/
> wso2jsonschema.org
> \/history\/0\/labelsRemoved\/0\/message\/payload\/body\/attachmentId","type":"string"},"data":{"id":"http:\/\/
> wso2jsonschema.org
> \/history\/0\/labelsRemoved\/0\/message\/payload\/body\/data","type":"string"},"size":{"id":"http:\/\/
> wso2jsonschema.org
> \/history\/0\/labelsRemoved\/0\/message\/payload\/body\/size","type":"string"}},"type":"object"},"filename":{"id":"http:\/\/
> wso2jsonschema.org
> \/history\/0\/labelsRemoved\/0\/message\/payload\/filename","type":"string"},"parts":{"id":"http:\/\/
> wso2jsonschema.org
> \/history\/0\/labelsRemoved\/0\/message\/payload\/parts","items":[{"id":"http:\/\/
> wso2jsonschema.org
> \/history\/0\/labelsRemoved\/0\/message\/payload\/parts\/0","properties":{"headers":{"id":"http:\/\/
> wso2jsonschema.org
> \/history\/0\/labelsRemoved\/0\/message\/payload\/parts\/0\/headers","items":[{"id":"http:\/\/
> wso2jsonschema.org
> \/history\/0\/labelsRemoved\/0\/message\/payload\/parts\/0\/headers\/0","properties":{"name":{"id":"http:\/\/
> wso2jsonschema.org
> \/history\/0\/labelsRemoved\/0\/message\/payload\/parts\/0\/headers\/0\/name","type":"string"},"value":{"id":"http:\/\/
> wso2jsonschema.org
> \/history\/0\/labelsRemoved\/0\/message\/payload\/parts\/0\/headers\/0\/value","type":"string"}},"type":"object"}],"type":"array"},"filename":{"id":"http:\/\/
> wso2jsonschema.org
> \/history\/0\/labelsRemoved\/0\/message\/payload\/parts\/0\/filename","type":"string"},"partId":{"id":"http:\/\/
> wso2jsonschema.org
> \/history\/0\/labelsRemoved\/0\/message\/payload\/parts\/0\/partId","type":"string"},"mimeType":{"id":"http:\/\/
> wso2jsonschema.org
> \/history\/0\/labelsRemoved\/0\/message\/payload\/parts\/0\/mimeType","type":"string"}},"type":"object"}],"type":"array"},"partId":{"id":"http:\/\/
> wso2jsonschema.org
> \/history\/0\/labelsRemoved\/0\/message\/payload\/partId","type":"string"},"mimeType":{"id":"http:\/\/
> wso2jsonschema.org
> \/history\/0\/labelsRemoved\/0\/message\/payload\/mimeType","type":"string"}},"type":"object"},"sizeEstimate":{"id":"http:\/\/
> wso2jsonschema.org
> \/history\/0\/labelsRemoved\/0\/message\/sizeEstimate","type":"

Re: [Dev] Output Schema generation for Data Mapper - Byte generated as String

2016-05-18 Thread Nuwan Pallewela

Hi Hariprasath,

Raw field holds a byte stream value. As the JSON Schema only have seven
primitive data types[1], I think current way of defining the type as String
is the correct way to represent it in the schema. That is because we are
not going to process this raw in the data mapper any way. We will only map
it's value into some field in the output message.
WDYT?

[1] http://json-schema.org/latest/json-schema-core.html#anchor8

Thanks,
Nuwan

On Wed, May 18, 2016 at 3:47 PM, Hariprasath Thanarajah <
haripras...@wso2.com> wrote:

> Hi Nuwan,
>
> I have attached the file that I used to create the output schema for
> listTheHistory method for Gmail REST connector.
>
> On Wed, May 18, 2016 at 3:42 PM, Nuwan Pallewela  wrote:
>
>> Hi Hariprasath,
>>
>> How did you generate the schema and what is the payload you used to
>> generate it?
>>
>> Thanks,
>> Nuwan
>>
>> On Wed, May 18, 2016 at 3:32 PM, Hariprasath Thanarajah <
>> haripras...@wso2.com> wrote:
>>
>>> Hi All,
>>>
>>> Currently I am doing the schema generation for Gmail REST connector. In
>>> most of the methods in this connector have the response part as[1], But in
>>> the JSON schema the type was generated as string[2].
>>>
>>> Is there any way to generate as bytes or is it ok to proceed as below?
>>>
>>> [1] - {
>>>   "id": string,
>>>   "threadId": string,
>>>   "labelIds": [
>>> string
>>>   ],
>>>   "snippet": string,
>>>   "historyId": unsigned long,
>>>   "internalDate": long,
>>>   "payload": {
>>> "partId": string,
>>> "mimeType": string,
>>> "filename": string,
>>> "headers": [
>>>   {
>>> "name": string,
>>> "value": string
>>>   }
>>> ],
>>> "body": users.messages.attachments Resource,
>>> "parts": [
>>>   (MessagePart)
>>> ]
>>>   },
>>>   "sizeEstimate": integer,
>>>   "raw": bytes
>>> }
>>>
>>> [2] -
>>> {"id":"http:\/\/wso2jsonschema.org","title":"root","$schema":"http:\/\/
>>> json-schema.org
>>> \/draft-04\/schema#","properties":{"history":{"id":"http:\/\/
>>> wso2jsonschema.org\/history","items":[{"id":"http:\/\/wso2jsonschema.org
>>> \/history\/0","properties":{"id":{"id":"http:\/\/wso2jsonschema.org
>>> \/history\/0\/id","type":"number"},"labelsRemoved":{"id":"http:\/\/
>>> wso2jsonschema.org\/history\/0\/labelsRemoved","items":[{"id":"http:\/\/
>>> wso2jsonschema.org
>>> \/history\/0\/labelsRemoved\/0","properties":{"message":{"id":"http:\/\/
>>> wso2jsonschema.org
>>> \/history\/0\/labelsRemoved\/0\/message","properties":{
>>> "raw":{"id":"http:\/\/wso2jsonschema.org
>>> \/history\/0\/labelsRemoved\/0\/message\/raw","type":"string"
>>> },"id":{"id":"http:\/\/wso2jsonschema.org
>>> \/history\/0\/labelsRemoved\/0\/message\/id","type":"string"},"labelIds":{"id":"http:\/\/
>>> wso2jsonschema.org
>>> \/history\/0\/labelsRemoved\/0\/message\/labelIds","items":[{"id":"http:\/\/
>>> wso2jsonschema.org
>>> \/history\/0\/labelsRemoved\/0\/message\/labelIds\/0","type":"string"}],"type":"array"},"threadId":{"id":"http:\/\/
>>> wso2jsonschema.org
>>> \/history\/0\/labelsRemoved\/0\/message\/threadId","type":"string"},"historyId":{"id":"http:\/\/
>>> wso2jsonschema.org
>>> \/history\/0\/labelsRemoved\/0\/message\/historyId","type":"string"},"payload":{"id":"http:\/\/
>>> wso2jsonschema.org
>>> \/history\/0\/labelsRemoved\/0\/message\/payload","properties":{"headers":{"id":"http:\/\/
>>> wso2jsonschema.org
>>> \/history\/0\/labelsRemoved\/0\/message\/payload\/headers","items&qu

Re: [Dev] [DEV] [VOTE] WSO2 Developer Studio Kernel RC3

2016-05-18 Thread Nuwan Pallewela

Hi All,

I have tested and following issues were found.

https://wso2.org/jira/browse/TOOLS-3413
https://wso2.org/jira/browse/TOOLS-3412
https://wso2.org/jira/browse/TOOLS-3411

Thanks,
Nuwan

On Thu, May 19, 2016 at 9:48 AM, Awanthika Senarath 
wrote:

> Thanks all,
>
> We are closing this vote with 5 +1's and 0 -1's.
>
> The RC has passed the vote.
>
> Regards
> Awanthika
>
> Awanthika Senarath
> Software Engineer, WSO2 Inc.
> Mobile: +94717681791
>
>
>
> On Wed, May 18, 2016 at 12:54 PM, Jasintha Dasanayake 
> wrote:
>
>> Hi All
>>
>> I have tested the update tool , new feature installation and kernel patch
>> process , no major issues found
>>
>> +1
>>
>> Thanks and Regards
>> /Jasintha
>>
>> On Wed, May 18, 2016 at 11:23 AM, Heshitha Hettihewa 
>> wrote:
>>
>>> Hi all,
>>>
>>> I have tested BPS Tooling and no major issues found.
>>>
>>> +1
>>>
>>> Thanks.
>>>
>>> On Wed, May 18, 2016 at 9:10 AM, Isuru Udana  wrote:
>>>
 Hi,

 Tested with ESB tools and found no major issues.

 +1.

 On Wed, May 18, 2016 at 9:05 AM, Sohani Weerasinghe 
 wrote:

> Hi All,
>
> I have tested the updater tool functionality including installing
> features and also the updater tool preferences.
>
> +1
>
> 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 Wed, May 18, 2016 at 8:32 AM, Awanthika Senarath <
> awanth...@wso2.com> wrote:
>
>> I have tested,
>>
>> Installation of Developer Studio Platform, ESB and CEP tools on top
>> of kernel
>> Updater tool functionality, installation and job running
>>
>>
>>
>>  +1,
>>
>> Regards
>> Awanthika
>>
>> Awanthika Senarath
>> Software Engineer, WSO2 Inc.
>> Mobile: +94717681791
>>
>>
>>
>> On Mon, May 16, 2016 at 3:10 PM, Awanthika Senarath <
>> awanth...@wso2.com> wrote:
>>
>>> Hello Devs,
>>>
>>>
>>> We are pleased to announce the vote for RC-3 of
>>> *WSO2 Developer Studio Kernel 4.1.0.*
>>>
>>> P2 repository of WSO2 developer Studio kernel 4.1.0 is available
>>> here
>>> .
>>>  Source
>>> and Tag Location to be voted upon is available here
>>> 
>>> .
>>>
>>> Developer Studio 4.1.0 Kernel is released on Eclipse Mars (Eclipse
>>> 4.5)
>>>
>>> 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
>>>- Improvements in the Developer Studio Updater tool for
>>>automatic updates
>>>
>>>
>>>
>>>1. [+] Stable - go ahead and release
>>>2. [-]  Broken - do not release (please explain why)
>>>
>>>
>>>
>>> Regards,
>>> Dev Studio Team
>>>
>>> Awanthika Senarath
>>> Software Engineer, WSO2 Inc.
>>> Mobile: +94717681791
>>>
>>>
>>>
>>
>> ___
>> 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
>
>


 --
 *Isuru Udana*
 Associate Technical Lead
 WSO2 Inc.; http://wso2.com
 email: isu...@wso2.com cell: +94 77 3791887
 blog: http://mytecheye.blogspot.com/

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


>>>
>>>
>>> --
>>> Heshitha Hettihewa
>>> *Software Engineer*
>>> Mobile : +94716866386
>>> <%2B94%20%280%29%20773%20451194>
>>> heshit...@wso2.com
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>>
>> *Jasintha Dasanayake*
>>
>> *Senior Software EngineerWSO2 Inc. | http://wso2.com
>> lean . enterprise . middleware*
>>
>>
>> *mobile :- 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
>
>


-- 
--

*Nuwan Chamara Pallewela*


*Software

[Dev] [ESB Tooling] Freezing repositories for ESB Tooling Beta release

2016-05-20 Thread Nuwan Pallewela

Hi All,

We are moving towards to release ESB Tooling 5.0.0 beta and please let us
know if you have any improvement to merge before the release.

Thanks,
Nuwan

-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *http://wso2.com
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739@*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] JSON schema for JSON payloads without a root element - visual datamapper editor

2016-05-25 Thread Nuwan Pallewela

Hi Sohani,

On Wed, May 25, 2016 at 11:03 AM, Sohani Weerasinghe 
wrote:

> Hi All,
>
> Since there can be JSON payloads without a root element as shown below, we
> are in a process of generating the JSON schema for such payloads. Please
> find the implementation details
>
> eg 1:
>
> *Input*:
>
> [
> "777925",
> "732321"
> ]
>
> *JSON schema:*
>
> {
>   "$schema" : "http://json-schema.org/draft-04/schema#";,
>   "id" : "http://wso2jsonschema.org";,
>   "title" : "root",
>   "type" : "array",
>   "items" : {
> "id" : "http://wso2jsonschema.org/0";,
> "type" : "string"
>   }
> }
>
>
> I think this primitive array should be able to map.


> eg 2:
>
> *Input*:
>
> [
>{
>  "id": 0,
>  "species": "Capra hircus",
>  "name": "Goat"
>},
>{
>  "id": 1,
>  "species": "Panthera pardus",
>  "name": "Leopard"
>},
>{
>  "id": 2,
>  "species": "Equus zebra",
>  "name": "Zebra"
>}
>  ]
>
> *JSON Schema:*
>
> {
>   "$schema" : "http://json-schema.org/draft-04/schema#";,
>   "id" : "http://wso2jsonschema.org";,
>   "title" : "root",
>   "type" : "array",
>   "items" : {
> "id" : "http://wso2jsonschema.org/0";,
> "type" : "object",
> "properties" : {
>   "species" : {
> "id" : "http://wso2jsonschema.org/0/species";,
> "type" : "string"
>   },
>   "name" : {
> "id" : "http://wso2jsonschema.org/0/name";,
> "type" : "string"
>   },
>   "id" : {
> "id" : "http://wso2jsonschema.org/0/id";,
> "type" : "number"
>   }
> }
>   }
> }
>
>
> 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 *
Mobile  *+94719079739@*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV] [VOTE] WSO2 Developer Studio Tooling for Platform RC2

2016-05-25 Thread Nuwan Pallewela

Hi All,

I have noticed following issues while testing.
https://wso2.org/jira/browse/TOOLS-3412
https://wso2.org/jira/browse/TOOLS-3416

Thanks,
Nuwan

On Wed, May 25, 2016 at 3:08 PM, Heshitha Hettihewa 
wrote:

> Hi all,
>
> I have tested BPS Tooling with the new platform and no major issues found.
>
> +1
>
> Thanks.
>
> On Wed, May 25, 2016 at 2:40 PM, Maheeka Jayasuriya 
> wrote:
>
>> Hi all,
>>
>> I have tested the project nature extension point and found no issues.
>>
>> +1
>>
>> Thanks,
>> Maheeka
>>
>> Maheeka Jayasuriya
>> Software Engineer
>> Mobile : +9450661
>>
>> On Mon, May 23, 2016 at 1:55 PM, Awanthika Senarath 
>> wrote:
>>
>>> Hello Devs,
>>>
>>>
>>> We are pleased to announce the vote for RC-2 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
>>> .
>>>  Source
>>> and Tag Location to be voted upon is available here
>>> 
>>> .
>>>
>>> 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
>>>- Improvements in the Developer Studio Updater tool for automatic
>>>updates
>>>
>>>
>>>
>>>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].
>>>
>>>
>>> [1]
>>> http://builder1.us1.wso2.org/~developerstudio/developer-studio-kernel/4.1.0/
>>>
>>>
>>> Awanthika Senarath
>>> Software Engineer, WSO2 Inc.
>>> Mobile: +94717681791
>>>
>>>
>>>
>>> ___
>>> 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
>>
>>
>
>
> --
> Heshitha Hettihewa
> *Software Engineer*
> Mobile : +94716866386
> <%2B94%20%280%29%20773%20451194>
> heshit...@wso2.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *http://wso2.com
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739@*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] Nullable Support for JSON schema - Visual Data Mapper Editor

2016-06-06 Thread Nuwan Pallewela

Hi Malaka,

On Tue, Jun 7, 2016 at 10:45 AM, Malaka Silva  wrote:

> Hi Sohani,
>
> I guess we are dealing with optional input/output here. So in that case
> are we showing those in a different color or anyway to distinguish?
>
> On execution side this needs to be handled from data mapper mediator.
>
This is handled by the mapping configuration generation in data mapper
editor so that data mapper engine may have minimum changes.

>
> On Tue, Jun 7, 2016 at 9:21 AM, Sohani Weerasinghe 
> wrote:
>
>> Hi All,
>>
>> We are in a process of implementing the $subject and please find the
>> implementation details.
>>
>> *Input*:
>>
>> http://www.w3.org/TR/html4/";>
>> sample
>> 011265565501
>> 011265565501
>> 
>>
>> After loading the above payload, the generated schema will be as follows
>>
>> {
>>   "$schema" : "http://json-schema.org/draft-04/schema#";,
>>   *"nullable" : "false"*,
>>   "id" : "http://wso2jsonschema.org";,
>>   "title" : "h:person",
>>   "type" : "object",
>>   "properties" : {
>> "firstName" : {
>>   *"nullable" : "false",*
>>   "id" : "http://wso2jsonschema.org/firstName";,
>>   "type" : "string"
>> },
>> *"nullable" : "false"*,
>> "phone" : {
>>   "id" : "http://wso2jsonschema.org/phone";,
>>   "type" : "array",
>>   "items" : [ {
>> "attributes" : {
>>   "primary" : {
>>* "nullable" : "false"*,
>> "id" : "http://wso2jsonschema.org/phone/0/primary";,
>> "type" : "boolean"
>>   }
>> },
>> "id" : "http://wso2jsonschema.org/phone/0";,
>> "type" : "object",
>> "value" : {
>>   "type" : "number"
>> },
>> "properties" : {
>>   "ext" : {
>>* "nullable" : "false",*
>> "id" : "http://wso2jsonschema.org/phone/0/ext";,
>> "type" : "number"
>>   }
>> }
>>   } ]
>> }
>>   },
>>   "namespaces" : [ {
>> "prefix" : "h",
>> "url" : "http://www.w3.org/TR/html4/";
>>   } ]
>> }
>>
>> Then, user can right click on the node and click on 'Enable Nullable' and
>> make the object or array or element, etc nullable.
>>
>>
>> The schema will be as follows
>>
>> {
>>   "$schema" : "http://json-schema.org/draft-04/schema#";,
>>  * "nullable" : "true",*
>>   "id" : "http://wso2jsonschema.org";,
>>   "title" : "h:person",
>>   "type" : "object",
>>   "properties" : {
>> "firstName" : {
>>   "nullable" : "false",
>>   "id" : "http://wso2jsonschema.org/firstName";,
>>   "type" : "string"
>> },
>> "nullable" : "false",
>> "phone" : {
>>   "id" : "http://wso2jsonschema.org/phone";,
>>   "type" : "array",
>>   "items" : [ {
>> "attributes" : {
>>   "primary" : {
>> "nullable" : "false",
>> "id" : "http://wso2jsonschema.org/phone/0/primary";,
>> "type" : "boolean"
>>   }
>> },
>> "id" : "http://wso2jsonschema.org/phone/0";,
>> "type" : "object",
>> "value" : {
>>   "type" : "number"
>> },
>> "properties" : {
>>   "ext" : {
>> "nullable" : "false",
>> "id" : "http://wso2jsonschema.org/phone/0/ext";,
>> "type" : "number"
>>   }
>> }
>>   } ]
>> }
>>   },
>>   "namespaces" : [ {
>> "prefix" : "h",
>> "url" : "http://www.w3.org/TR/html4/";
>>   } ]
>> }
>>
>> If a user wants to disable it then, user can right click on the node and
>> click on 'Disable Nullable'
>>
>>
>> 
>> After enabling, we thought of changing the icon of the tree node so that
>> user can easily identify whether a particular node is a nullable or not.
>>
>> Thanks,
>> Sohani
>> Sohani Weerasinghe
>> Senior Software Engineer
>> WSO2, Inc: http://wso2.com
>>
>> Mobile  : +94 716439774
>> Blog :http://christinetechtips.blogspot.com/
>> Twitter  : https://twitter.com/hanichristine
>>
>> ___
>> Architecture mailing list
>> architect...@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
>
> Best Regards,
>
> Malaka Silva
> Senior Technical 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/
> 
> 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,
Nuwan

-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *http://wso2.com
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739 <%2B94719079739>@*

Re: [Dev] [Architecture] Nullable Support for JSON schema - Visual Data Mapper Editor

2016-06-06 Thread Nuwan Pallewela

On Tue, Jun 7, 2016 at 10:54 AM, Malaka Silva  wrote:

> But optional Fields are something we need to handle at run time?
>
 Actually there are several ways we could get optional elements. Some API's
will not send the optional elements if they are null or they will send
empty element with or without xsi:nil attribute. Data mapper engine build
and inject the received payload to JS engine. So the problem will arise
when the mapping configuration tries to execute a undefined optional
parameter. So mapping configuration should check the parameters if they are
optional.

>
> On Tue, Jun 7, 2016 at 10:52 AM, Nuwan Pallewela  wrote:
>
>> Hi Malaka,
>>
>> On Tue, Jun 7, 2016 at 10:45 AM, Malaka Silva  wrote:
>>
>>> Hi Sohani,
>>>
>>> I guess we are dealing with optional input/output here. So in that case
>>> are we showing those in a different color or anyway to distinguish?
>>>
>>> On execution side this needs to be handled from data mapper mediator.
>>>
>> This is handled by the mapping configuration generation in data mapper
>> editor so that data mapper engine may have minimum changes.
>>
>>>
>>> On Tue, Jun 7, 2016 at 9:21 AM, Sohani Weerasinghe 
>>> wrote:
>>>
>>>> Hi All,
>>>>
>>>> We are in a process of implementing the $subject and please find the
>>>> implementation details.
>>>>
>>>> *Input*:
>>>>
>>>> http://www.w3.org/TR/html4/";>
>>>> sample
>>>> 011265565501
>>>> 011265565501
>>>> 
>>>>
>>>> After loading the above payload, the generated schema will be as follows
>>>>
>>>> {
>>>>   "$schema" : "http://json-schema.org/draft-04/schema#";,
>>>>   *"nullable" : "false"*,
>>>>   "id" : "http://wso2jsonschema.org";,
>>>>   "title" : "h:person",
>>>>   "type" : "object",
>>>>   "properties" : {
>>>> "firstName" : {
>>>>   *"nullable" : "false",*
>>>>   "id" : "http://wso2jsonschema.org/firstName";,
>>>>   "type" : "string"
>>>> },
>>>> *"nullable" : "false"*,
>>>> "phone" : {
>>>>   "id" : "http://wso2jsonschema.org/phone";,
>>>>   "type" : "array",
>>>>   "items" : [ {
>>>> "attributes" : {
>>>>   "primary" : {
>>>>* "nullable" : "false"*,
>>>> "id" : "http://wso2jsonschema.org/phone/0/primary";,
>>>> "type" : "boolean"
>>>>   }
>>>> },
>>>> "id" : "http://wso2jsonschema.org/phone/0";,
>>>> "type" : "object",
>>>> "value" : {
>>>>   "type" : "number"
>>>> },
>>>> "properties" : {
>>>>   "ext" : {
>>>>* "nullable" : "false",*
>>>> "id" : "http://wso2jsonschema.org/phone/0/ext";,
>>>> "type" : "number"
>>>>   }
>>>> }
>>>>   } ]
>>>> }
>>>>   },
>>>>   "namespaces" : [ {
>>>> "prefix" : "h",
>>>> "url" : "http://www.w3.org/TR/html4/";
>>>>   } ]
>>>> }
>>>>
>>>> Then, user can right click on the node and click on 'Enable Nullable'
>>>> and make the object or array or element, etc nullable.
>>>>
>>>>
>>>> The schema will be as follows
>>>>
>>>> {
>>>>   "$schema" : "http://json-schema.org/draft-04/schema#";,
>>>>  * "nullable" : "true",*
>>>>   "id" : "http://wso2jsonschema.org";,
>>>>   "title" : "h:person",
>>>>   "type" : "object",
>>>>   "properties" : {
>>>> "firstName" :

Re: [Dev] Developer Studio changes ordering of XML attributes

2016-06-09 Thread Nuwan Pallewela

Hi Rajeevan,

This behavior happens when we try to format the configuration. We use javax
DocumentBuilder to parse and format and it does not care about the
attribute order, since it's meaningless as far as the standard is
concerned.
This for sure we can fix by manually editing the source configuration but
the concern is it will need some considerable effort to do so. Will it be
worth to spend that much time to fix this now because this is an non
blocking issue and we haven't got any complains about this from customers?
Anyways I think it is better to open a JIRA and keep it to be fixed in a
future.

Thanks,
Nuwan

On Fri, Jun 10, 2016 at 10:22 AM, Vimalanathan Rajeevan 
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* 
> Lean.Enterprise.Middleware
>
> Mobile:
> *+94 773090875 <%2B94%20773090875>*
> LinkedIn:
> *https://www.linkedin.com/in/RajeevanVimalanathan
> *
>

-- 
--

*Nuwan Chamara Pallewela*

*Software Engineer*

*WSO2, Inc. *http://wso2.com
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739@*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB][Tooling]Unable to set the scope as registry for the property mediator in ESB Tooling

2016-06-14 Thread Nuwan Pallewela

Hi Kesavan,

Currently ESB tool doesn't have a scope as "registry". So it will reset it
to default when you switch the views. We have to add it in ESB tool.
Open a JIRA for esb tooling to track this.

Meanwhile to continue with the development keep it to the last moment and
edit it in source view and save. Do not switch to design view after that.

Thanks,
Nuwan

On Tue, Jun 14, 2016 at 2:04 PM, Kesavan Yogarajah 
wrote:

> Hi All,
>
> I am using ESB Tooling 5.0.0- BETA to create the synapse configuration for
> Zuora-Salesforce integration and using the property mediator to store the
> date time value in the registry as follows :
>
>  scope="registry"/>
>
> But in the design view, it only shows the Synapse, axis2, axis2-client,
> operation and transport options for the scope.
> If I use the source view, scope is getting overwritten as default when
> switching between design and source view.
>
> How to resolve this issue?
>
> Thanks
>
> Kesavan Yogarajah
> Software Engineer
> Mobile :+94 (0) 779 758021
> kesav...@wso2.com
> WSO2, Inc.
> lean . enterprise . middleware
>

-- 
--

*Nuwan Chamara Pallewela*

*Software Engineer*

*WSO2, Inc. *http://wso2.com
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739@*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 ESB tests

2016-06-17 Thread Nuwan Pallewela

Hi Abhishek,

You can find the existing test cases from the product-esb source[1].
What you may basically have to do is save proxy or API configs as files and
then deploy them in ESB server and test by sending requests. By referring
to already written test cases you can easily understand.

[1]
https://github.com/wso2/product-esb/tree/master/modules/integration/tests-integration

Thanks,
Nuwan

On Fri, Jun 17, 2016 at 10:12 PM, Abhishek Tiwari <
abhishek.tiwari0...@gmail.com> wrote:

> Hi All,
>
> My name is Abhishek, and I am a GSoC student,  working on the test
> framework for WSO2 Dockerfiles. As part of that, I am writing tests for
> individual products once they have been deployed using Docker container.
> Currently I am writing tests for ESB. I plan to write tests for
> - Creating and testing proxy service
> - Creating and testing APIs
> - Applying WS-Security to proxy services and testing the applied security
>
> Are there existing smoke tests in ESB which I can use as reference? Where
> can I get the details around creating proxies, APIs programmatically?
>
> Thanks
> Abhishek
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *http://wso2.com
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739@*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] ClassCastException when using datamapper

2016-06-20 Thread Nuwan Pallewela

Hi Keerthika,

What is the ESB version you are using?

Thanks,
Nuwan

On Mon, Jun 20, 2016 at 4:03 PM, Keerthika Mahendralingam <
keerth...@wso2.com> wrote:

> Hi All,
>
> I am getting the following error when I used data mapper to create an
> integration scenario. I installed the tool from
> http://builder1.us1.wso2.org/~developerstudio/devstudio-tooling-esb/5.0.0/Beta/composite/
> and used input output schema from jira and pagerduty connector schema.
>
> I have added the proxy and data mapper configuration at the end.
>
> What could be the reason for the following error?
>
> [2016-06-20 15:11:10,720] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >>
> "[\r][\n]"
>
> [2016-06-20 15:11:10,720] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >>
> "352[\r][\n]"
>
> [2016-06-20 15:11:10,721] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >> "
> {"id":"PS9VE7M","incident_number":3,"created_on":"2016-06-15T11:33:51Z","status":"resolved","pending_actions":[],"html_url":"
> https://connectordemo.pagerduty.com/incidents/PS9VE7M
> ","incident_key":"3c45415469ed415d8137b8ea9fe2fc03","service":{"id":"P4OWETP","name":"testService","html_url":"
> https://connectordemo.pagerduty.com/services/P4OWETP","deleted_at":null,"description":"This
> is for testing
> purpose"},"escalation_policy":{"id":"PDJQDGY","name":"Default","deleted_at":null},"assigned_to_user":null,"trigger_summary_data":{"subject":"serviceTest"},"trigger_details_html_url":"
> https://connectordemo.pagerduty.com/incidents/PS9VE7M/log_entries/Q324O08PK4VLJV
> ","trigger_type":"web_trigger","last_status_change_on":"2016-06-15T15:33:51Z","last_status_change_by":null,"number_of_escalations":0,"resolved_by_user":null,"assigned_to":[],"urgency":"high"}
> [\r][\n]"
>
> [2016-06-20 15:11:10,722] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >>
> "0[\r][\n]"
>
> [2016-06-20 15:11:10,723] DEBUG - wire HTTPS-Sender I/O dispatcher-3 >>
> "[\r][\n]"
>
> [2016-06-20 15:11:10,731]  WARN - JacksonJSONSchema Element name not found
> : jsonObject
>
> [2016-06-20 15:11:10,732]  WARN - JacksonJSONSchema Element name not found
> : jsonObject
>
> [2016-06-20 15:11:10,732] ERROR - SequenceMediator java.lang.String cannot
> be cast to java.util.Map
>
> java.lang.ClassCastException: java.lang.String cannot be cast to
> java.util.Map
>
> at
> org.wso2.carbon.mediator.datamapper.engine.core.schemas.JacksonJSONSchema.getElementTypeByName(JacksonJSONSchema.java:111)
>
> at
> org.wso2.carbon.mediator.datamapper.engine.input.readers.XMLReader.startElement(XMLReader.java:141)
>
> at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
>
> at
> org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown
> Source)
>
> at
> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.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";
>

Re: [Dev] Maintaining the order for XML payloads in JSON schema - Data Mapper

2016-06-20 Thread Nuwan Pallewela

Hi Harsha,

On Tue, Jun 21, 2016 at 9:27 AM, Harsha Thirimanna  wrote:

> Hi Sohani,
> Just wanted to know one thing and please make me correct if i am wrong
> here.
>
> Normally, XML elements don't have an order and any implementation should
> not depend on the order of the elements in XML file except if it has a XSD
> and saying it as a sequence.
>
No. In the specification it is mentioned that XML consider order. And there
are certain api's which consider the order of the elements. So we should to
support it in xml.

> So why do we need to concern about the order here. Any special reason for
> that ?
>
>
> *Harsha Thirimanna*
> Associate Tech Lead; WSO2, Inc.; http://wso2.com
> * *
> *email: **hars...@wso2.com* * cell: +94 71 5186770 *
> *twitter: **http://twitter.com/ *
> *harshathirimannlinked-in: **http:
> **//www.linkedin.com/pub/harsha-thirimanna/10/ab8/122
> *
>
> *Lean . Enterprise . Middleware*
>
>
> On Mon, Jun 20, 2016 at 2:51 PM, Sohani Weerasinghe 
> wrote:
>
>> Hi All,
>>
>> We are in a process of $subject and the main issue we faced in generating
>> the json schema was as follows.
>>
>> When generating the json schema we mainly convert the xml to json and the
>> xml to json conversion does not guarantee the order since json object is an
>> unordered set of name/value pairs [1].
>>
>> The main reason is the usage of HashMaps instead of LinkedHashMaps in
>> instantiating the JSONObjects and we could solve the issue by using the
>> LinkedHashMaps.
>>
>> This issue again occurs in serializing the schema while iterating through
>> the gmf tree, since we are generating the schema by creating the
>> JSONObjects and JSONArrays appropriately. We could solve this issue as well
>> by using the above solution and as a result, the generated tree and the
>> schema will maintain the order of the XML payload
>>
>> [1]
>> http://stackoverflow.com/questions/26034370/inverted-order-of-json-elements-in-java-after-xml-conversion
>>
>> 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
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
Thanks,
Nuwan

-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *http://wso2.com
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739@*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Maintaining the order for XML payloads in JSON schema - Data Mapper

2016-06-20 Thread Nuwan Pallewela

Hi Harsha,

We can find this in section 3.2.1 Element Content in the W3C
recommendation[1].

[1] https://www.w3.org/TR/REC-xml/

Thanks,
Nuwan

On Tue, Jun 21, 2016 at 10:02 AM, Harsha Thirimanna 
wrote:

> Hi Nuwan,
>
> Thanks for pointing that, can you please point that specification location
> please ?
>
>
> *Harsha Thirimanna*
> Associate Tech Lead; WSO2, Inc.; http://wso2.com
> * <http://www.apache.org/>*
> *email: **hars...@wso2.com* * cell: +94 71 5186770 *
> *twitter: **http://twitter.com/ <http://twitter.com/afkham_azeez>*
> *harshathirimannlinked-in: **http:
> <http://lk.linkedin.com/in/afkhamazeez>**//www.linkedin.com/pub/harsha-thirimanna/10/ab8/122
> <http://www.linkedin.com/pub/harsha-thirimanna/10/ab8/122>*
>
> *Lean . Enterprise . Middleware*
>
>
> On Tue, Jun 21, 2016 at 9:45 AM, Nuwan Pallewela  wrote:
>
>> Hi Harsha,
>>
>> On Tue, Jun 21, 2016 at 9:27 AM, Harsha Thirimanna 
>> wrote:
>>
>>> Hi Sohani,
>>> Just wanted to know one thing and please make me correct if i am wrong
>>> here.
>>>
>>> Normally, XML elements don't have an order and any implementation should
>>> not depend on the order of the elements in XML file except if it has a XSD
>>> and saying it as a sequence.
>>>
>> No. In the specification it is mentioned that XML consider order. And
>> there are certain api's which consider the order of the elements. So we
>> should to support it in xml.
>>
>>> So why do we need to concern about the order here. Any special reason
>>> for that ?
>>>
>>>
>>> *Harsha Thirimanna*
>>> Associate Tech Lead; WSO2, Inc.; http://wso2.com
>>> * <http://www.apache.org/>*
>>> *email: **hars...@wso2.com* * cell: +94 71 5186770 *
>>> *twitter: **http://twitter.com/ <http://twitter.com/afkham_azeez>*
>>> *harshathirimannlinked-in: **http:
>>> <http://lk.linkedin.com/in/afkhamazeez>**//www.linkedin.com/pub/harsha-thirimanna/10/ab8/122
>>> <http://www.linkedin.com/pub/harsha-thirimanna/10/ab8/122>*
>>>
>>> *Lean . Enterprise . Middleware*
>>>
>>>
>>> On Mon, Jun 20, 2016 at 2:51 PM, Sohani Weerasinghe 
>>> wrote:
>>>
>>>> Hi All,
>>>>
>>>> We are in a process of $subject and the main issue we faced in
>>>> generating the json schema was as follows.
>>>>
>>>> When generating the json schema we mainly convert the xml to json and
>>>> the xml to json conversion does not guarantee the order since json object
>>>> is an unordered set of name/value pairs [1].
>>>>
>>>> The main reason is the usage of HashMaps instead of LinkedHashMaps in
>>>> instantiating the JSONObjects and we could solve the issue by using the
>>>> LinkedHashMaps.
>>>>
>>>> This issue again occurs in serializing the schema while iterating
>>>> through the gmf tree, since we are generating the schema by creating the
>>>> JSONObjects and JSONArrays appropriately. We could solve this issue as well
>>>> by using the above solution and as a result, the generated tree and the
>>>> schema will maintain the order of the XML payload
>>>>
>>>> [1]
>>>> http://stackoverflow.com/questions/26034370/inverted-order-of-json-elements-in-java-after-xml-conversion
>>>>
>>>> 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
>>>>
>>>> ___
>>>> Dev mailing list
>>>> Dev@wso2.org
>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>
>>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>> Thanks,
>> Nuwan
>>
>> --
>> --
>>
>> *Nuwan Chamara Pallewela*
>>
>>
>> *Software Engineer*
>>
>> *WSO2, Inc. *http://wso2.com
>> *lean . enterprise . middleware*
>>
>> Email   *nuw...@wso2.com *
>> Mobile  *+94719079739 <%2B94719079739>@*
>>
>>
>>
>


-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *http://wso2.com
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739@*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Maintaining the order for XML payloads in JSON schema - Data Mapper

2016-06-20 Thread Nuwan Pallewela

Problem is that we can not say that we are not guarantee the order of the
xml elements in data mapper. As there are some well known API's who
consider the order(some Salesforce API's), we have to support the order in
xml elements from our side. Otherwise there will be issues when user going
to use data mapper with such API's.

On Tue, Jun 21, 2016 at 10:43 AM, Harsha Thirimanna 
wrote:

> As in the spec , it can be choice, seq or mixed, right ? The ELEMENT Type
> Declaration can be used within an DTD to define the contents on an element
> within the XML document. Is that ok to make sequence for all the cases ?
>
>
> *Harsha Thirimanna*
> Associate Tech Lead; WSO2, Inc.; http://wso2.com
> * <http://www.apache.org/>*
> *email: **hars...@wso2.com* * cell: +94 71 5186770 *
> *twitter: **http://twitter.com/ <http://twitter.com/afkham_azeez>*
> *harshathirimannlinked-in: **http:
> <http://lk.linkedin.com/in/afkhamazeez>**//www.linkedin.com/pub/harsha-thirimanna/10/ab8/122
> <http://www.linkedin.com/pub/harsha-thirimanna/10/ab8/122>*
>
> *Lean . Enterprise . Middleware*
>
>
> On Tue, Jun 21, 2016 at 10:17 AM, Nuwan Pallewela  wrote:
>
>> Hi Harsha,
>>
>> We can find this in section 3.2.1 Element Content in the W3C
>> recommendation[1].
>>
>> [1] https://www.w3.org/TR/REC-xml/
>>
>> Thanks,
>> Nuwan
>>
>> On Tue, Jun 21, 2016 at 10:02 AM, Harsha Thirimanna 
>> wrote:
>>
>>> Hi Nuwan,
>>>
>>> Thanks for pointing that, can you please point that
>>> specification location please ?
>>>
>>>
>>> *Harsha Thirimanna*
>>> Associate Tech Lead; WSO2, Inc.; http://wso2.com
>>> * <http://www.apache.org/>*
>>> *email: **hars...@wso2.com* * cell: +94 71 5186770 *
>>> *twitter: **http://twitter.com/ <http://twitter.com/afkham_azeez>*
>>> *harshathirimannlinked-in: **http:
>>> <http://lk.linkedin.com/in/afkhamazeez>**//www.linkedin.com/pub/harsha-thirimanna/10/ab8/122
>>> <http://www.linkedin.com/pub/harsha-thirimanna/10/ab8/122>*
>>>
>>> *Lean . Enterprise . Middleware*
>>>
>>>
>>> On Tue, Jun 21, 2016 at 9:45 AM, Nuwan Pallewela 
>>> wrote:
>>>
>>>> Hi Harsha,
>>>>
>>>> On Tue, Jun 21, 2016 at 9:27 AM, Harsha Thirimanna 
>>>> wrote:
>>>>
>>>>> Hi Sohani,
>>>>> Just wanted to know one thing and please make me correct if i am wrong
>>>>> here.
>>>>>
>>>>> Normally, XML elements don't have an order and any implementation
>>>>> should not depend on the order of the elements in XML file except if it
>>>>> has a XSD and saying it as a sequence.
>>>>>
>>>> No. In the specification it is mentioned that XML consider order. And
>>>> there are certain api's which consider the order of the elements. So we
>>>> should to support it in xml.
>>>>
>>>>> So why do we need to concern about the order here. Any special reason
>>>>> for that ?
>>>>>
>>>>>
>>>>> *Harsha Thirimanna*
>>>>> Associate Tech Lead; WSO2, Inc.; http://wso2.com
>>>>> * <http://www.apache.org/>*
>>>>> *email: **hars...@wso2.com* * cell: +94 71 5186770 *
>>>>> *twitter: **http://twitter.com/ <http://twitter.com/afkham_azeez>*
>>>>> *harshathirimannlinked-in: **http:
>>>>> <http://lk.linkedin.com/in/afkhamazeez>**//www.linkedin.com/pub/harsha-thirimanna/10/ab8/122
>>>>> <http://www.linkedin.com/pub/harsha-thirimanna/10/ab8/122>*
>>>>>
>>>>> *Lean . Enterprise . Middleware*
>>>>>
>>>>>
>>>>> On Mon, Jun 20, 2016 at 2:51 PM, Sohani Weerasinghe 
>>>>> wrote:
>>>>>
>>>>>> Hi All,
>>>>>>
>>>>>> We are in a process of $subject and the main issue we faced in
>>>>>> generating the json schema was as follows.
>>>>>>
>>>>>> When generating the json schema we mainly convert the xml to json and
>>>>>> the xml to json conversion does not guarantee the order since json object
>>>>>> is an unordered set of name/value pairs [1].
>>>>>>
>>>>>> The main reason is the usage of HashMaps instead of LinkedHashMaps in
>>>>>> instantiating the JSONObjects and we could solve the issue

Re: [Dev] ClassCastException when using datamapper

2016-06-20 Thread Nuwan Pallewela

  "id" : "http://wso2jsonschema.org/issueFields/fields/project
> ",
>   "properties" : {
> "key" : {
>   "id" : "
> http://wso2jsonschema.org/issueFields/fields/project/key";,
>   "type" : "string"
> }
>   },
>   "type" : "object"
> },
> "issuetype" : {
>   "id" : "
> http://wso2jsonschema.org/issueFields/fields/issuetype";,
>   "properties" : {
> "id" : {
>   "id" : "
> http://wso2jsonschema.org/issueFields/fields/issuetype/id";,
>   "type" : "string"
> }
>   },
>   "type" : "object"
> },
> "priority" : {
>   "id" : "
> http://wso2jsonschema.org/issueFields/fields/priority";,
>   "properties" : {
> "id" : {
>   "id" : "
> http://wso2jsonschema.org/issueFields/fields/priority/id";,
>   "type" : "string"
> }
>   },
>   "type" : "object"
> },
> "description" : {
>   "id" : "
> http://wso2jsonschema.org/issueFields/fields/description";,
>   "type" : "string"
> },
> "labels" : {
>   "id" : "http://wso2jsonschema.org/issueFields/fields/labels
> ",
>   "items" : [ {
> "id" : "
> http://wso2jsonschema.org/issueFields/fields/labels/0";,
> "type" : "string"
>   } ],
>   "type" : "array"
> },
> "assignee" : {
>   "id" : "
> http://wso2jsonschema.org/issueFields/fields/assignee";,
>   "properties" : {
> "name" : {
>   "id" : "
> http://wso2jsonschema.org/issueFields/fields/assignee/name";,
>   "type" : "string"
> }
>   },
>   "type" : "object"
> }
>   },
>   "type" : "object"
> }
>   },
>   "type" : "object"
> }
>   },
>   "type" : "object"
> }
>
> On Mon, Jun 20, 2016 at 4:59 PM, Viraj Rajaguru  wrote:
>
>> Hi Keerthika,
>>
>> It seems the schema and the received payload doesn't match each other.
>> Can you send us the payload just before the datamapper mediator.(Log
>> level="full") We will find input and output schemas from [1] and [2]. Hope
>> connector store contains updated connectors with schemas. Or else please
>> share gov:datamapper/pdJiraConfig_inputSchema.json and gov:datamapper/
>> pdJiraConfig_outputSchema.json as well.
>>
>> Thanks,
>> Viraj.
>>
>> [1] -
>> https://store.wso2.com/store/assets/esbconnector/6f3b4bb7-054a-4aaf-a579-3f32c3eca2d3
>> [2] -
>> https://store.wso2.com/store/assets/esbconnector/b6424572-c92c-4422-a8e2-36db83d98e81
>>
>>
>> On Mon, Jun 20, 2016 at 4:39 PM, Keerthika Mahendralingam <
>> keerth...@wso2.com> wrote:
>>
>>> Hi Nuwan,
>>>
>>> Using ESB 5.0.0-BETA.
>>>
>>> Thanks,
>>> Keerthika
>>>
>>> On Mon, Jun 20, 2016 at 4:25 PM, Nuwan Pallewela 
>>> wrote:
>>>
>>>> Hi Keerthika,
>>>>
>>>> What is the ESB version you are using?
>>>>
>>>> Thanks,
>>>> Nuwan
>>>>
>>>> On Mon, Jun 20, 2016 at 4:03 PM, Keerthika Mahendralingam <
>>>> keerth...@wso2.com> wrote:
>>>>
>>>>> Hi All,
>>>>>
>>>>> I am getting the following error when I used data mapper to create an
>>>>> integration scenario. I installed the tool from
>>>>> http://builder1.us1.wso2.org/~developerstudio/devstudio-tooling-esb/5.0.0/Beta/composite/
>>>>> and used input output schema from jira and pagerduty connector schema.
>>&g

[Dev] [ESB] Custom parameters for JMS Message Store

2015-07-28 Thread Nuwan Pallewela

Hi ESB team,

I'm currently working on jira issue [1] Tools-2309 - "Provide an UI option
to define extra parameters for Message Store" reported for developer studio
3.5.0 Beta 1 version. As mentioned in above jira, it is possible to define
custom parameters from the source view in JMS Message Store. But these
custom parameters are not supported in esb management console ui.

Is this a recommended option to have in JMS Message Store and should we
support it in developer Studio.

Thanks,
Nuwan

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

-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *http://wso2.com
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739*

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

[Dev] [DevStudio] Fix for artifact.xml file corruption when deleting multiple ESB artifact files at once

2015-07-31 Thread Nuwan Pallewela

Hi,

Please review and merge following PRs  [1] and [2] which will fix
Tools-2967 and $subject
[1]https://github.com/wso2/developer-studio/pull/92
[2]https://github.com/wso2/developer-studio/pull/93

Following are the changes this PR adds

   - User can select multiple ESB artifact files from one ESB Config
   project or multiple ESB Config projects at once and delete.
   - Ctrl+Z will undo the delete operation by also correctly undoing the
   changes in artifact.xml files which introduced in the delete process.
   - But preview will not show changes done for artifact.xml file
   separately for each artifact. It will show all changes together, done for
   artifact.xml file in each ESB Config project.

Thanks,
-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *http://wso2.com
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739*

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

Re: [Dev] Finding the feature that pack a particular bundle

2015-09-24 Thread Nuwan Pallewela

Hi Maduranga,


I also wanted this some time back. I could not find any way to do it using
osgi console.
So what I did was grep the source code folder which contains the .pom files.
grep -r "bundle_name" .

Thanks,
Nuwan

On Wed, Sep 23, 2015 at 12:37 PM, Thusitha Thilina Dayaratne <
thusit...@wso2.com> wrote:

> Hi Maduranga,
>
> You can go to repository/components/features directory and do a grep for
> the required bundle name
>
> Thanks
> /Thusitha
>
> On Wed, Sep 23, 2015 at 12:35 PM, Hasintha Indrajee 
> wrote:
>
>> Hi Maduranga,
>>
>> You can do a grep from the bundle name, within your product's feature
>> directory and find out. (ie from repository/components/features/).
>>
>>
>> On Wed, Sep 23, 2015 at 12:31 PM, Maduranga Siriwardena <
>> madura...@wso2.com> wrote:
>>
>>> Hi Thilini,
>>>
>>> Thanks for the response. I am looking for a way to find the feature that
>>> packs a bundle.
>>>
>>> Thanks.
>>>
>>> On Wed, Sep 23, 2015 at 11:56 AM, Thilini Cooray 
>>> wrote:
>>>
 Hi,

 From osgi console you can find from where a bundle gets imported and
 exported.
 Use the command
 b 

 [1] contains some more useful commands.

 [1]
 https://isurues.wordpress.com/2009/01/01/useful-equinox-osgi-commands/

 Thanks.

 On Wed, Sep 23, 2015 at 11:35 AM, Maduranga Siriwardena <
 madura...@wso2.com> wrote:

> Hi all,
>
> Is there a way to find the feature that pack a particular bundle?
> (From the osgi console or from any other method)
>
> Thanks,
> Maduranga
>
> --
> Maduranga Siriwardena
> Software Engineer
> WSO2 Inc.
>
> email: madura...@wso2.com
> mobile: +94718990591
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 Best Regards,

 *Thilini Cooray*
 Software Engineer
 Mobile : +94 (0) 774 570 112 <%2B94%20%280%29%20773%20451194>
 E-mail : thili...@wso2.com

 WSO2 Inc. www.wso2.com
 lean.enterprise.middleware

>>>
>>>
>>>
>>> --
>>> Maduranga Siriwardena
>>> Software Engineer
>>> WSO2 Inc.
>>>
>>> email: madura...@wso2.com
>>> mobile: +94718990591
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Hasintha Indrajee
>> Software Engineer
>> WSO2, Inc.
>> Mobile:+94 771892453
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Thusitha Dayaratne
> Software Engineer
> WSO2 Inc. - lean . enterprise . middleware |  wso2.com
>
> Mobile  +94712756809
> Blog  alokayasoya.blogspot.com
> Abouthttp://about.me/thusithathilina
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *http://wso2.com
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739*

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

[Dev] [DEV][DevStudio][Connector] Correct place to read Connector Operation name from a imported connector file

2015-09-30 Thread Nuwan Pallewela

Current implementation in Developer Studio reads the connector operation
names from component.xml files in the imported files.
Is this the correct position to read it?
Do we have to read it from specific component xml file?

I found that in salesforce connector, getUserInformation component have
different names in component.xml (name - getUserInformation) file and
getUserInformation.xml (name-getUserInfo) file.

Thanks,
Nuwan

-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *http://wso2.com
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV][DevStudio][Connector] Correct place to read Connector Operation name from a imported connector file

2015-09-30 Thread Nuwan Pallewela

Hi Rajjaz,

We already reads every components.xml files. But the problem I raised was
do we need to read specific xml files.

For example: endSession.xml , init.xml for Gmail connector.

Thanks,
Nuwan

On Wed, Sep 30, 2015 at 1:56 PM, Rajjaz Mohammed  wrote:

> Hi Nuwan,
> it's ok for salesforce connector because all available methods are in one
> component xml file but like Gmail Connector you need to read every
> components xml file added as dependency in Connector xml File.
>
> [image: Inline image 1]
>
> On Wed, Sep 30, 2015 at 12:58 PM, Nuwan Pallewela  wrote:
>
>> Current implementation in Developer Studio reads the connector operation
>> names from component.xml files in the imported files.
>> Is this the correct position to read it?
>> Do we have to read it from specific component xml file?
>>
>> I found that in salesforce connector, getUserInformation component have
>> different names in component.xml (name - getUserInformation) file and
>> getUserInformation.xml (name-getUserInfo) file.
>>
>> Thanks,
>> Nuwan
>>
>> --
>> --
>>
>> *Nuwan Chamara Pallewela*
>>
>>
>> *Software Engineer*
>>
>> *WSO2, Inc. *http://wso2.com
>> *lean . enterprise . middleware*
>>
>> Email   *nuw...@wso2.com *
>> Mobile  *+94719079739 <%2B94719079739>*
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Thank you
> Best Regards
>
> *Rajjaz HM*
> Associate Software Engineer
> WSO2 Inc. <http://wso2.com/>
> lean | enterprise | middleware
> Mobile | +94752833834
> Email   | raj...@wso2.com
> LinkedIn | Blogger | WSO2 Profile
> <http://wso2.com/about/team/mohammer_rajjaz/>
>



-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *http://wso2.com
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [DEV][GREG] Unable to import registry resources from a dump file

2015-10-06 Thread Nuwan Pallewela

Hi Devs,

I'm trying to test importing registry files using a dump file. I have
created a dump file using following command [1].
[1] sh checkin-client.sh co https://localhost:9443/registry/ -u admin -p
admin -f 10-06-2015_test2.dump

Dump file is successfully created in the bin folder.

Then when I try to import it to another Greg server using [2] command, it
gives following error[3].
[2] sh checkin-client.sh ci https://localhost:9445/registry/ -u admin -p
admin -f 10-06-2015_test2.dump
[3]
Error in restoring the path. Make sure the registry is up and running Or
the username, password is correct! and check the user have the WRITE
permission to the path.
path: /
registry url: https://localhost:9443/registry
username: admin

What would be causing this?

Thanks,
Nuwan

-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *http://wso2.com
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV][GREG] Unable to import registry resources from a dump file

2015-10-06 Thread Nuwan Pallewela

Hi,

After i tried to checkout the dump file , following error is show in
command line when i try to browse registry.

[2015-10-06 15:20:27,354]  WARN
{org.wso2.carbon.registry.core.caching.CacheBackedRegistry} -  User admin
is not authorized to read the resource /.

Thanks,
Nuwan

On Tue, Oct 6, 2015 at 3:16 PM, Nuwan Pallewela  wrote:

> Hi Devs,
>
> I'm trying to test importing registry files using a dump file. I have
> created a dump file using following command [1].
> [1] sh checkin-client.sh co https://localhost:9443/registry/ -u admin -p
> admin -f 10-06-2015_test2.dump
>
> Dump file is successfully created in the bin folder.
>
> Then when I try to import it to another Greg server using [2] command, it
> gives following error[3].
> [2] sh checkin-client.sh ci https://localhost:9445/registry/ -u admin -p
> admin -f 10-06-2015_test2.dump
> [3]
> Error in restoring the path. Make sure the registry is up and running Or
> the username, password is correct! and check the user have the WRITE
> permission to the path.
> path: /
> registry url: https://localhost:9443/registry
> username: admin
>
> What would be causing this?
>
> Thanks,
> Nuwan
>
> --
> --
>
> *Nuwan Chamara Pallewela*
>
>
> *Software Engineer*
>
> *WSO2, Inc. *http://wso2.com
> *lean . enterprise . middleware*
>
> Email   *nuw...@wso2.com *
> Mobile  *+94719079739 <%2B94719079739>*
>
>
>


-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *http://wso2.com
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Developer Studio 3.8.0 RC

2015-10-06 Thread Nuwan Pallewela

Hi All,

I have tested following scenarios.

   - JAX-WS service classes with App Server.
   - JAX-RS service classes with App Server.
   - Created ESB artifacts ,car files and with connectors.
   - Tested most of the security scenarios with proxy services.
   - Tested MMM project creation and building.

I found two main blocking  issues.

[1] Rename refactoring operation on ESB artifacts doesn't update pom file
of the capp and artifact.xml file correctly in some cases.

[2] Validation in source view of ESB artifacts not showing error line
correctly in template and REST-api files.(
https://wso2.org/jira/browse/TOOLS-3225 )

therefore -1

Thanks,

Nuwan

On Mon, Oct 5, 2015 at 3:43 PM, Kavith Lokuhewage  wrote:

> Hi All,
>
> On Mon, Oct 5, 2015 at 12:30 PM, Kavith Lokuhewage 
> wrote:
>
>> Hi All,
>>
>> This is the release candidate of WSO2 Developer Studio 3.8.0.
>>
>> This release fixes following issues:
>> https://wso2.org/jira/browse/TOOLS-3218?filter=12427
>>
>>
> Please ignore above link. Instead, use following link to view issues fixed
> in this version.
> https://wso2.org/jira/issues/?filter=12431
>
> Thanks,
>
> Please download, test and vote. Vote will be open for 72 hours or as
>> needed.
>>
>> *Sources, binary distribution and pre-installed eclipse distributions:*
>> *http://builder1.us1.wso2.org/~developerstudio/developer-studio/3.8.0/RC/
>> *
>>
>> *The tag to be voted upon:*
>> https://github.com/wso2/developer-studio/tree/v3.8.0-RC
>>
>> *[+**]* Stable - go ahead and release
>> *[-]*  Broken - do not release (explain why)
>>
>> Thanks,
>> --
>> *Kavith Lokuhewage*
>> Software Engineer
>> WSO2 Inc. - http://wso2.com
>> lean . enterprise . middleware
>> Mobile - +9477-9-145-123 | +9471-455-6-401
>> Linkedin 
>> Twitter 
>>
>
>
>
> --
> *Kavith Lokuhewage*
> Software Engineer
> WSO2 Inc. - http://wso2.com
> lean . enterprise . middleware
> Mobile - +9477-9-145-123 | +9471-455-6-401
> Linkedin 
> Twitter 
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *http://wso2.com
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV][GREG] Unable to import registry resources from a dump file

2015-10-06 Thread Nuwan Pallewela

Hi Sameera,

I'm using 5.0.0 Greg server.
It was the issue. It worked when I mention a different location.
Thanks.

There was an issue, after I tried to invoke it to root directory it gave
the error that admin is not allowed to write for root.
Then I could not browse any file from the management console. Error message
shown as "An unexpected error occurred. Please check the server logs for
more details" every time when trying to browse.

It solved when I restated the server.

Thanks,
Nuwan



On Tue, Oct 6, 2015 at 4:39 PM, Sameera Kannangara 
wrote:

> Hi Nuwan,
>
> What is the WSO2 server type you are using? and what is the version?
>
> In any case none of the users have ability to check-in to the root
> directory.
> Therefore you'll have to take the checkout from a collection that is
> closer to the resource location you are trying to move.
>
> Ex - sh checkin-client.sh co
> https://localhost:9443/registry/_system/governance/trunk/A -u admin -p
> admin -f A.dump
>
> What is the use case here,
> Are you trying to move an entire repo of a server, into another server?
> Or trying to move a part of the repo?
>
> Thank you,
> SameeraK.
>
>
>
> On Tue, Oct 6, 2015 at 3:23 PM, Nuwan Pallewela  wrote:
>
>> Hi,
>>
>> After i tried to checkout the dump file , following error is show in
>> command line when i try to browse registry.
>>
>> [2015-10-06 15:20:27,354]  WARN
>> {org.wso2.carbon.registry.core.caching.CacheBackedRegistry} -  User admin
>> is not authorized to read the resource /.
>>
>> Thanks,
>> Nuwan
>>
>> On Tue, Oct 6, 2015 at 3:16 PM, Nuwan Pallewela  wrote:
>>
>>> Hi Devs,
>>>
>>> I'm trying to test importing registry files using a dump file. I have
>>> created a dump file using following command [1].
>>> [1] sh checkin-client.sh co https://localhost:9443/registry/ -u admin
>>> -p admin -f 10-06-2015_test2.dump
>>>
>>> Dump file is successfully created in the bin folder.
>>>
>>> Then when I try to import it to another Greg server using [2] command,
>>> it gives following error[3].
>>> [2] sh checkin-client.sh ci https://localhost:9445/registry/ -u admin
>>> -p admin -f 10-06-2015_test2.dump
>>> [3]
>>> Error in restoring the path. Make sure the registry is up and running Or
>>> the username, password is correct! and check the user have the WRITE
>>> permission to the path.
>>> path: /
>>> registry url: https://localhost:9443/registry
>>> username: admin
>>>
>>> What would be causing this?
>>>
>>> Thanks,
>>> Nuwan
>>>
>>> --
>>> --
>>>
>>> *Nuwan Chamara Pallewela*
>>>
>>>
>>> *Software Engineer*
>>>
>>> *WSO2, Inc. *http://wso2.com
>>> *lean . enterprise . middleware*
>>>
>>> Email   *nuw...@wso2.com *
>>> Mobile  *+94719079739 <%2B94719079739>*
>>>
>>>
>>>
>>
>>
>> --
>> --
>>
>> *Nuwan Chamara Pallewela*
>>
>>
>> *Software Engineer*
>>
>> *WSO2, Inc. *http://wso2.com
>> *lean . enterprise . middleware*
>>
>> Email   *nuw...@wso2.com *
>> Mobile  *+94719079739 <%2B94719079739>*
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Sameera Kannangara*
> Software Engineer
> Platform TG; WSO2 Inc. http://wso2.com
> Contact:
> phone: +94719541577
> Lean . Enterprise . Middleware
>



-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *http://wso2.com
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Is "defaultValue" field in the Publish Event Mediator always expected to be Empty?

2015-10-06 Thread Nuwan Pallewela

Hi Awanthika,

I think this defaultValue can be any value. It is assigned for the
attribute if the expression can not find a property value.

Thanks,
Nuwan

On Wed, Oct 7, 2015 at 9:29 AM, Awanthika Senarath 
wrote:

> Hi all,
>
> On testing the developer studio 3.8.0 I could observe that the
> "defaultValue" field for attribute parameters in the Publish Event Mediator
> [1] is always empty and will not store any values.
>
> On referring the documentation [2] for ESB 4.9.0 in the sample displayed
> also I could observe the same. Could you please explain the purpose of
> having this field in the said mediator and whether this is the correct
> use-case to be implemented from Developer Studio end?
>
>
> [1]  
>   
>expression="get-property('axis2', 'HTTP_METHOD')"
>   name="http_method" type="STRING"/>
>name="destination" type="STRING"/>
>   
>   
>expression="get-property('SYSTEM_DATE')" name="date"
> type="STRING"/>
>   
>   
>expression="$body/m0:getQuote/m0:request/m0:symbol"
>   name="symbol" type="STRING" xmlns:m0="
> http://services.samples"/>
>   
>   
> 
>
> [2] https://docs.wso2.com/display/ESB490/Publish+Event+Mediator
>
> Regards
> Awanthika Senarath
> Software Engineer, WSO2 Inc.
> Mobile: +94717681791
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *http://wso2.com
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Developer Studio 3.8.0 RC 2

2015-10-08 Thread Nuwan Pallewela

I have tested the following areas,
App server tools
ESB Basic Functionalities
Registry Basic Functionalities
Carbon servers instances
BRS drl file importing
Capp deployment

And found following issues
https://wso2.org/jira/browse/TOOLS-3235
https://wso2.org/jira/browse/TOOLS-3236
https://wso2.org/jira/browse/TOOLS-3237
https://wso2.org/jira/browse/TOOLS-3238

Thanks,
Nuwan

On Thu, Oct 8, 2015 at 5:00 PM, Susinda Perera  wrote:

> Issues found when testing inbound endpoints is listed below
> https://wso2.org/jira/browse/TOOLS-3243
> https://wso2.org/jira/browse/TOOLS-3244
>
>
> On Thu, Oct 8, 2015 at 4:51 PM, Susinda Perera  wrote:
>
>> I have tested following Areas.
>>
>> All inbound endpoints
>> All registry resources
>> Fixes given from 3.8.0 3.8.0-Rc and RC1
>>
>>
>>
>> On Thu, Oct 8, 2015 at 4:43 PM, Awanthika Senarath 
>> wrote:
>>
>>> Hi all,
>>>
>>> I have tested the basic functionalities related to :
>>>
>>> *Basic Functionalities :*
>>>
>>>
>>>- ESB projects
>>>- DSS projects
>>>- Registry Resource projects
>>>- Carbon servers (remote/local) instances
>>>- Capp deployment/Redeployment with changes in ESB project
>>>- AppFactory/ Cloud perspectives
>>>- Maven Car deploy plugin
>>>
>>>
>>> *New Features Added :*
>>>
>>>
>>>- Publisher/Foreach new mediator addition, Custom class mediator
>>>- Artifact Renaming
>>>- War file Deployment/Exploded web apps/ Automatic updating(hot
>>>deployment)
>>>- APIM perspective- artifact creation/deletion/renaming redeployment
>>>with changes
>>>- Carbon 4.4.0 based servers
>>>
>>>
>>> All functionalities are functioning satisfactorily and have no blockers
>>> were observed on testing, +1
>>>
>>> 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
>>
>>
>
>
> --
> *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
>
>


-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *http://wso2.com
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739@*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += Sasikala Kottegoda

2015-10-11 Thread Nuwan Pallewela

Congrats Sasikala!

On Mon, Oct 12, 2015 at 10:59 AM, Ramith Jayasinghe  wrote:

> Hi Sasikala,
> Congratulations!
> It is with great pleasure that we welcome you as a WSO2 committer. Keep up
> the good work!
> regards,
>
> --
> Ramith Jayasinghe
> Technical Lead
> WSO2 Inc., http://wso2.com
> lean.enterprise.middleware
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *http://wso2.com
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739@*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Documentation for Developer Studio JAXWS and JAXRS Samples

2015-10-12 Thread Nuwan Pallewela

Hi,

Following link [1] contain draft sample documentation for JAX-WS sample
project.

[1]
https://docs.google.com/a/wso2.com/document/d/1LRCeJfcczAIZFi6UD2SCgZT5Q7LWjp8DFrdHj6zpAGE/edit?usp=sharing

Thanks,
Nuwan
-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *http://wso2.com
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739@*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Documentation for Developer Studio JAXWS and JAXRS Samples

2015-10-13 Thread Nuwan Pallewela

Hi,

Following link [2] contain draft sample documentation for JAX-RS sample
project

[2]
https://docs.google.com/a/wso2.com/document/d/1iE9qJtR6yPs193VtF6EwlklC1v-ZOwqRaBKqF5ZZSNU/edit?usp=sharing

Thanks,
Nuwan

On Tue, Oct 13, 2015 at 11:37 AM, Nuwan Pallewela  wrote:

> Hi,
>
> Following link [1] contain draft sample documentation for JAX-WS sample
> project.
>
> [1]
> https://docs.google.com/a/wso2.com/document/d/1LRCeJfcczAIZFi6UD2SCgZT5Q7LWjp8DFrdHj6zpAGE/edit?usp=sharing
>
> Thanks,
> Nuwan
> --
> --
>
> *Nuwan Chamara Pallewela*
>
>
> *Software Engineer*
>
> *WSO2, Inc. *http://wso2.com
> *lean . enterprise . middleware*
>
> Email   *nuw...@wso2.com *
> Mobile  *+94719079739 <%2B94719079739>@*
>
>
>


-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *http://wso2.com
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739@*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Developer Studio 3.8.0 RC 4

2015-10-14 Thread Nuwan Pallewela

Hi All,

I have tested following areas,

   - ESB basic fuctionalities
   - App Server service classes
   - Registry Resources
   - CApp creation and deployments in servers
   - Connector importing and removing
   - Servers

No blocking issues found. So +1

On Wed, Oct 14, 2015 at 3:30 PM, Sajith Dimal  wrote:

> Hi All.
>
> I tested main use cases of the following scenarios and found no issues:
>
>1.
>
>Analytics project creation.
>2.
>
>Analytics artifacts (Execution-plan, Stream, Receiver, Publisher)
>creation.
>3.
>
>Analytics artifact rename.
>4.
>
>CAPP project creation and deploy for Analytics project.
>
> +1 for the release.
>
> Thanks.
>
> On Wed, Oct 14, 2015 at 2:53 PM, Susinda Perera  wrote:
>
>> Hi All
>> I have tested following and no blocking issues found.
>>
>> ESB, DSS, BPEL, CAPP project creation
>> ESB artifact creation
>> Importing connectors
>> Connector exporter project
>> All inbound endpoints
>> APIM perspective - commit/rename/checkout
>>
>> Thanks
>> Susinda
>>
>>
>>
>>
>>
>> On Wed, Oct 14, 2015 at 10:09 AM, Awanthika Senarath 
>> wrote:
>>
>>> Hi
>>>
>>> I have tested the following features and bug fixes and the observations
>>> were positive, hence +1
>>>
>>>
>>>- ESB projects,
>>>- Registry Projects
>>>- Data Service Projects
>>>
>>>
>>>
>>>- Capp projects (creation, deploy, redeploy, removal)
>>>- Servers (remote/local)
>>>
>>>
>>>
>>>- Artifact renaming.
>>>
>>>
>>> Regards
>>> Awanthika
>>>
>>>
>>> Awanthika Senarath
>>> Software Engineer, WSO2 Inc.
>>> Mobile: +94717681791
>>>
>>>
>>>
>>> On Wed, Oct 14, 2015 at 9:25 AM, Kavith Lokuhewage 
>>> wrote:
>>>
 Hi Devs,

 Please vote for the fourth release candidate of WSO2 Developer Studio
 3.8.0.

 This release fixes following issues.
 https://wso2.org/jira/issues/?filter=12453

 Please download, test and vote. Vote will be open for 72 hours or as
 needed.

 Sources, binary distribution and pre-installed eclipse distributions:

 http://builder1.us1.wso2.org/~developerstudio/developer-studio/3.8.0/RC4/

 The tag to be voted upon:
 https://github.com/wso2/developer-studio/tree/v3.8.0-RC4


 [+] Stable - go ahead and release
 [-]  Broken - do not release (explain why)

 Thanks and Regards,
 DevStudio Team

 --
 *Kavith Lokuhewage*
 Software Engineer
 WSO2 Inc. - http://wso2.com
 lean . enterprise . middleware
 Mobile - +9477-9-145-123 | +9471-455-6-401
 Linkedin 
 Twitter 

 ___
 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
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Thanks & Regards
>
> *Sajith Dimal*
> Software Engineer - Intern
> WSO2 Inc.: http://wso2.com
> lean.enterprise.middleware
>
> Email: saji...@wso2.com
> Mobile: +94 783101496 <94783101496>
> LinkedIn: https://lk.linkedin.com/pub/sajith-dimal/b8/1b1/25b
> 
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *http://wso2.com
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739@*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Dependency Inject not working to get IEclipseContext Object

2015-11-03 Thread Nuwan Pallewela

Hi Devs,

I'm trying to get a IEclipseContext object to get IEventBroker. DI method
to get IEventBroker instance always gives a null. Alternative method to get
IEventBroker is through IEclipseContext instance. DI method to get it also
not working. Is there any way to get a instance of IEclipseContext object?

Thanks,
Nuwan

-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *http://wso2.com
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739@*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Dependency Inject not working to get IEclipseContext Object

2015-11-03 Thread Nuwan Pallewela

Hi,

I have tried the above method and got an exception of
"org.eclipse.e4.core.di.InjectionException:
Unable to process "EventBroker.logger": no actual value was found for the
argument "Logger".".
As discussed off line with kavith, this was occurred because of
ServiceContext does not give the logger for IEventBroker.

Alternative way to get IEventBroker instance and subscribe without using DI
was found using PlatformUI and shown in following code.

debuggerEventBroker = (IEventBroker)
PlatformUI.getWorkbench().getService(IEventBroker.class);
debuggerEventBroker.subscribe(ESBDebuggerConstants.ESBDEBUGTARGET_EVENT_TOPIC,
this);

And we can listen and handle events by implementing
org.osgi.service.event.EventHandler interface in our subscriber class.

Thanks,
Nuwan


On Tue, Nov 3, 2015 at 9:52 PM, Kavith Lokuhewage  wrote:

> Hi Nuwan,
>
> You can observe a reference to IEclipseContext using the bundleContext
> object. You can get a reference to bundleContext via bundle activator or
> via FrameworkUtil class.
>
> See following snippet.
>
> BundleContext bundleContext =
> FrameworkUtil.getBundle(SomeClassInYourBundle.class).getBundleContext();
> IEclipseContext eclipseContext =
> EclipseContextFactory.getServiceContext(bundleContext);
>
> BTW, how did you try to get a IEventBroker reference via Dependency
> Injection?
> If you are getting null for injected references always, I suspect that DI
> engine does not manage your object.
>
> FYI, Eclipse E4 DI engine only manages classes in Application Model or
> framework components by default (eg. commands, handlers, activators,
> declarative services, etc.). If your class is not a framework component and
> you manually instantiate it in your code using *new *operator, DI engine
> is not aware of that. In such kind of a situation, you need to manually
> inject the required references using ContextInjectionFactory. See following
> snippet.
>
> YourClass object = new YourClass();
> ContextInjectionFactory.inject(object, eclipseContext);
>
> For the ContextInjectionFactory.inject method, you need to pass the DI
> context (to tell DI engine from which context to obtain references which
> are needed to inject - this should be the global eclipse context in most
> cases) and your object. You can obtain the global eclipseContext using
> first snippet.
>
> For example, you can use below code to get a reference to IEventBroker in
> a custom class which is not a framework component.
>
> public YourClass{
>
> @Inject
> IEventBroker eventBroker;
>
> public YourClass(){}
>
> }
>
> Then, inject reference while instantiating.
>
> BundleContext bundleContext =
> FrameworkUtil.getBundle(YourClass.class).getBundleContext();
> IEclipseContext eclipseContext =
> EclipseContextFactory.getServiceContext(bundleContext);
> YourClass object = new YourClass();
> ContextInjectionFactory.inject(object, eclipseContext);
>
> HTH.
> Thanks,
>
> On Tue, Nov 3, 2015 at 9:07 PM, Nuwan Pallewela  wrote:
>
>> Hi Devs,
>>
>> I'm trying to get a IEclipseContext object to get IEventBroker. DI method
>> to get IEventBroker instance always gives a null. Alternative method to get
>> IEventBroker is through IEclipseContext instance. DI method to get it also
>> not working. Is there any way to get a instance of IEclipseContext object?
>>
>> Thanks,
>> Nuwan
>>
>> --
>> --
>>
>> *Nuwan Chamara Pallewela*
>>
>>
>> *Software Engineer*
>>
>> *WSO2, Inc. *http://wso2.com
>> *lean . enterprise . middleware*
>>
>> Email   *nuw...@wso2.com *
>> Mobile  *+94719079739 <%2B94719079739>@*
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Kavith Lokuhewage*
> Software Engineer
> WSO2 Inc. - http://wso2.com
> lean . enterprise . middleware
> Mobile - +9477-9-145-123 | +9471-455-6-401
> Linkedin <http://www.linkedin.com/pub/kavith-lokuhewage/49/473/419>
> Twitter <https://twitter.com/KavithThiranga>
>



-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *http://wso2.com
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739@*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += Sachith Withana

2015-11-30 Thread Nuwan Pallewela

Congratz sachith

On Tue, Dec 1, 2015 at 11:00 AM, Malintha Adikari  wrote:

> Congratulations Sachith...
>
> On Tue, Dec 1, 2015 at 10:59 AM, Dunith Dhanushka  wrote:
>
>> Congrats Sachith!
>>
>> On Tue, Dec 1, 2015 at 10:54 AM, Anjana Fernando  wrote:
>>
>>> Hi everyone,
>>>
>>> It is my pleasure to welcome Sachith as a WSO2 committer. He has done
>>> numerous contributions to the Data Analytics Server product, in doing
>>> development and bringing in ideas, and has proved to be a valuable and a
>>> dependable person. So Sachith welcome aboard, and keep up with the good
>>> work! ..
>>>
>>> Cheers,
>>> Anjana.
>>> --
>>> *Anjana Fernando*
>>> Senior Technical Lead
>>> WSO2 Inc. | http://wso2.com
>>> lean . enterprise . middleware
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Regards,
>>
>> Dunith Dhanushka,
>> Senior Software Engineer
>> WSO2 Inc,
>>
>> Mobile - +94 71 8615744
>> Blog - dunithd.wordpress.com 
>> Twitter - @dunithd 
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Malintha Adikari*
> Software Engineer
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> Mobile: +94 71 2312958
> Blog:http://malinthas.blogspot.com
> Page:   http://about.me/malintha
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *http://wso2.com
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739@*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] WSO2 ESB 4.10.0 - Milestone 1 Released!

2015-12-06 Thread Nuwan Pallewela

Hi,

In this pack user have to manually modify the synapse.properties file to
start in mediation debug mode. Wouldn't it be more suitable that if default
event and command ports for ESB Mediation debugger was included in
synapse.properties file with the pack.

Thanks,
Nuwan

On Fri, Dec 4, 2015 at 11:07 PM, Jagath Sisirakumara Ariyarathne <
jaga...@wso2.com> wrote:

> *WSO2 ESB 4.10.0-Milestone 1 Released*
>
> ESB Team is pleased to announce the WSO2 ESB 4.10.0 - Milestone 1 Release.
> It contains following new features and bug fixes.
>
> *New Features & Improvements*
>
>- JMS 2.0 support
>- Mediation debugging capability
>
>
> *All resolved Issues*
>
> Bugs
>
>- [ESBJAVA-3832 ] - "ERROR
>- TaskQuartzJobAdapter Error in executing task: null
>java.util.EmptyStackException" observed when publishing jms messages when
>the backend is restarted
>- [ESBJAVA-4142 ] - First
>request sent for tenants (after tenant unloading/ server restart) fails.
>- [ESBJAVA-4195 ] -
>[Standalone] Forwarding MP with interval value < 1000 ms and cron
>expression does not worrk as expected
>- [ESBJAVA-4229 ] - Java
>Heap Space error for huge file processing with Smooks mediator
>- [ESBJAVA-4235 ] - VFS
>stops working when scanning directory for files to read
>- [ESBJAVA-4250 ] - Getting
>NPE time to time when using loadbalnce endpoint
>- [ESBJAVA-4318 ] - Caching
>issue for XML body with processing instructions
>- [ESBJAVA-4333 ] -
>IllegalStateException when accessing APIs of tenants
>
>
> Improvements
>
>- [ESBJAVA-4346 ] -
>Persisting content into registry from the mediation Layer
>
>
> Patches
>
>- [ESBJAVA-4231 ] - Load
>balanced endpoint sending an empty payload to the failover endpoint
>
>
> The distribution is available to download at [1].
>
> [1] -
> https://svn.wso2.org/repos/wso2/scratch/ESB/packs/4.10.0-Releases/4.10.0-M1/
>
> - WSO2 ESB Team -
> --
> Jagath Ariyarathne
> Technical Lead
> WSO2 Inc.  http://wso2.com/
> Email: jaga...@wso2.com
> Mob  : +94 77 386 7048
>
>
> ___
> Architecture mailing list
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *http://wso2.com
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739@*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] WSO2 ESB 4.10.0 - Milestone 1 Released!

2015-12-07 Thread Nuwan Pallewela

Hi Chanaka,

Server will *only use* these ports when it *starts in debug mode *( Server
should start with "-Desb.debug=true" argument to start it in debug mode).
Otherwise those ports will not be used.

However I think commented out entries in the synapse.properties file is
also suitable in this case.

Thanks,
Nuwan

On Mon, Dec 7, 2015 at 4:01 PM, Chanaka Fernando  wrote:

> Hi Nuwan/Kevin,
>
> Will this opens the specified ports by default when the server starts? It
> is not a good idea to open ports which are not necessary by default. If it
> is not opening any port, then +1 to add to the file. Anyway we can add the
> entries and comment out if they are opening the ports.
>
> Cheers,
> Chanaka
>
> On Mon, Dec 7, 2015 at 10:16 AM, Kevin Ratnasekera  wrote:
>
>> +1, Created a Jira for this [1], this will be fixed for next milestone
>> release.
>> [1] https://wso2.org/jira/browse/ESBJAVA-4354
>> Regards
>> Kevin
>>
>> On Mon, Dec 7, 2015 at 12:36 PM, Nuwan Pallewela  wrote:
>>
>>> Hi,
>>>
>>> In this pack user have to manually modify the synapse.properties file to
>>> start in mediation debug mode. Wouldn't it be more suitable that if default
>>> event and command ports for ESB Mediation debugger was included in
>>> synapse.properties file with the pack.
>>>
>>> Thanks,
>>> Nuwan
>>>
>>> On Fri, Dec 4, 2015 at 11:07 PM, Jagath Sisirakumara Ariyarathne <
>>> jaga...@wso2.com> wrote:
>>>
>>>> *WSO2 ESB 4.10.0-Milestone 1 Released*
>>>>
>>>> ESB Team is pleased to announce the WSO2 ESB 4.10.0 - Milestone 1
>>>> Release. It contains following new features and bug fixes.
>>>>
>>>> *New Features & Improvements*
>>>>
>>>>- JMS 2.0 support
>>>>- Mediation debugging capability
>>>>
>>>>
>>>> *All resolved Issues*
>>>>
>>>> Bugs
>>>>
>>>>- [ESBJAVA-3832 <https://wso2.org/jira/browse/ESBJAVA-3832>] -
>>>>"ERROR - TaskQuartzJobAdapter Error in executing task: null
>>>>java.util.EmptyStackException" observed when publishing jms messages 
>>>> when
>>>>the backend is restarted
>>>>- [ESBJAVA-4142 <https://wso2.org/jira/browse/ESBJAVA-4142>] -
>>>>First request sent for tenants (after tenant unloading/ server restart)
>>>>fails.
>>>>- [ESBJAVA-4195 <https://wso2.org/jira/browse/ESBJAVA-4195>] -
>>>>[Standalone] Forwarding MP with interval value < 1000 ms and cron
>>>>expression does not worrk as expected
>>>>- [ESBJAVA-4229 <https://wso2.org/jira/browse/ESBJAVA-4229>] - Java
>>>>Heap Space error for huge file processing with Smooks mediator
>>>>- [ESBJAVA-4235 <https://wso2.org/jira/browse/ESBJAVA-4235>] - VFS
>>>>stops working when scanning directory for files to read
>>>>- [ESBJAVA-4250 <https://wso2.org/jira/browse/ESBJAVA-4250>] -
>>>>Getting NPE time to time when using loadbalnce endpoint
>>>>- [ESBJAVA-4318 <https://wso2.org/jira/browse/ESBJAVA-4318>] -
>>>>Caching issue for XML body with processing instructions
>>>>- [ESBJAVA-4333 <https://wso2.org/jira/browse/ESBJAVA-4333>] -
>>>>IllegalStateException when accessing APIs of tenants
>>>>
>>>>
>>>> Improvements
>>>>
>>>>- [ESBJAVA-4346 <https://wso2.org/jira/browse/ESBJAVA-4346>] -
>>>>Persisting content into registry from the mediation Layer
>>>>
>>>>
>>>> Patches
>>>>
>>>>- [ESBJAVA-4231 <https://wso2.org/jira/browse/ESBJAVA-4231>] - Load
>>>>balanced endpoint sending an empty payload to the failover endpoint
>>>>
>>>>
>>>> The distribution is available to download at [1].
>>>>
>>>> [1] -
>>>> https://svn.wso2.org/repos/wso2/scratch/ESB/packs/4.10.0-Releases/4.10.0-M1/
>>>>
>>>> - WSO2 ESB Team -
>>>> --
>>>> Jagath Ariyarathne
>>>> Technical Lead
>>>> WSO2 Inc.  http://wso2.com/
>>>> Email: jaga...@wso2.com
>>>> Mob  : +94 77 386 7048
>>>>
>>>>
>>>> ___
>>>> Architecture mailing list
>>>> architect...@wso2.org
>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>>
>>>>
>>>
>>>
>>> --
>>> --
>>>
>>> *Nuwan Chamara Pallewela*
>>>
>>>
>>> *Software Engineer*
>>>
>>> *WSO2, Inc. *http://wso2.com
>>> *lean . enterprise . middleware*
>>>
>>> Email   *nuw...@wso2.com *
>>> Mobile  *+94719079739 <%2B94719079739>@*
>>>
>>>
>>>
>>
>
>
> --
> Thank you and Best Regards,
> Chanaka Fernando
> Senior Technical Lead
> WSO2, Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: +94 773337238
> Blog : http://soatutorials.blogspot.com
> LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0
> Twitter:https://twitter.com/chanakaudaya
>
>
>
>
>


-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *http://wso2.com
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739@*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [BPS][BPMN] New REST API for BPMN statistics

2015-12-09 Thread Nuwan Pallewela

Hi Natasha,

Great work.
What happens if an invalid request or request with an illegal argument sent
to the API ?
It is better to have those response messages or response status code also
in the documentation.

Thanks,
Nuwan

On Wed, Dec 9, 2015 at 5:08 PM, Natasha Wijesekara  wrote:

> Hi,
>
> I  documented a user guide which contains details about the new rest API
> implemented to generate the statistics for bpmn.
> Appreciate any suggestions and comments.
>
> Thanks,
> Natasha
>
> On Tue, Dec 8, 2015 at 4:44 PM, Vinod Kavinda  wrote:
>
>> [Adding Architecture group]
>>
>> On Tue, Dec 8, 2015 at 2:45 PM, Natasha Wijesekara 
>> wrote:
>>
>>> Hi ,
>>>
>>> Currently the statistics generated for the bpmn-explorer is generated
>>> using jaggery. When the work load is high, the  bpmn-explorer takes a
>>> longer time to generate these statistics which causes performance issues.
>>>
>>> As a solution I am working a new stats REST api  to generate these
>>> statistics at the back-end. This reduces the work load  and thereby solves
>>> the performance issues caused during peak times (when the workload is at
>>> its maximum).
>>>
>>> After taking in data about  the bpmn processes, tasks  and users
>>> involved, the api  processes these data into meaningful statistics.These
>>> statistics generated is used in the bpmn-explorer reporting dashboard to
>>> generate the statistical graphs.
>>>
>>> The statistics generated includes:
>>>
>>> 1) Average time duration for all completed processes.
>>> The user has the option to either view all completed processes or the
>>> top 10 processes which finished within a short time duration or the top 10
>>> processes which took a long time duration to finish.
>>>
>>> 2) Average time duration of tasks of a  completed process.
>>> The user can select the completed process from the combo box and view
>>> the average time duration.
>>>
>>> 3) User and the no. of tasks he/she has completed upto now.
>>>
>>> 4) Average time taken by each user to complete the tasks assigned to
>>> him/her.
>>>
>>> 5) Task demand variation over time i.e. no. of tasks started and no. of
>>> tasks completed in each month. This is useful for resource allocation
>>> purposes.
>>>
>>> 6) Process demand variation over time i.e. no. of processes started and
>>> no. of processes completed in each month regardless of a specific user.
>>> This is useful for resource allocation purposes.
>>>
>>> 7) User Performance i.e. Task demand variation of users separately over
>>> time i.e. no. of tasks started and no. of tasks completed in each month.
>>> This is useful for resource allocation purposes.
>>>
>>> I have attached the class diagram of the REST api. The new stats REST
>>> api will be integrated with the existing bpmn REST api.
>>> Appreciate any suggestions and comments.
>>>
>>> Thanks,
>>> --
>>> *Natasha Wijesekare*
>>>
>>> *Software Engineering Intern, WSO2  Inc:  http://wso2.com
>>> *
>>> *email  : nata...@wso2.com *
>>> *mobile: +94 771358651 <%2B94%20771358651>*
>>>
>>
>>
>>
>> --
>> Vinod Kavinda
>> Software Engineer
>> *WSO2 Inc. - lean . enterprise . middleware .*
>> Mobile : +94 (0) 712 415544
>> Blog : http://soatechflicks.blogspot.com/
>>
>>
>
>
> --
> *Natasha Wijesekare*
>
> *Software Engineering Intern, WSO2  Inc:  http://wso2.com
> *
> *email  : nata...@wso2.com *
> *mobile: +94 771358651 <%2B94%20771358651>*
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *http://wso2.com
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739@*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] How to get Maven Home for java implementation

2015-12-13 Thread Nuwan Pallewela

Hi Devs,

I need to get the *Maven Home* value to execute maven goal eclipse:eclipse
for a created project. I tried to use *java.lang.System* class to retrieve
it by executing following code. But Maven Home in not listed in there
either properties or process environment.

if (System.getenv("M2_HOME") != null) {
return System.getenv("M2_HOME");
} else if (System.getenv("MAVEN_HOME") != null) {
return System.getenv("MAVEN_HOME");
} else if (System.getenv("M3_HOME") != null) {
return System.getenv("M3_HOME");
} else if (System.getProperty("maven.home") != null) {
return System.getProperty("maven.home");
} else {
log.error("Maven Home variable value is not found in system
properties");
throw new IllegalStateException("Maven Home variable is not set
");
}

Maven is correctly installed in the system and following is the result when
I run "mvn --version"

nuwan@nuwan-ThinkPad-T540p:~$ mvn --version
Apache Maven 3.2.5 (12a6b3acb947671f09b81f49094c53f426d8cea1;
2014-12-14T22:59:23+05:30)
Maven home: /usr/local/apache-maven-3.2.5
Java version: 1.8.0_66, vendor: Oracle Corporation
Java home: /usr/lib/jvm/java-8-oracle/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "3.13.0-68-generic", arch: "amd64", family:
"unix"

I have also had edit the .bashrc file by adding following lines.

export M2_HOME=/usr/local/apache-maven-3.2.5
export M2=$M2_HOME/bin
export PATH=$M2/bin:$PATH

But still I can't read M2_HOME from java.lang.System class.

Any help would be hugely appreciated.

Thanks,
Nuwan

-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *http://wso2.com
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739@*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] How to get Maven Home for java implementation

2015-12-13 Thread Nuwan Pallewela

Hi Devs,

Found the reason. Environment variable was not  registered at that point.
After restarting the system it got updated.

@Rajjaz thanks. You are correct. Modified the config.

Thanks,
Nuwan

On Mon, Dec 14, 2015 at 12:25 PM, Rajjaz Mohammed  wrote:

>
>
>
> export M2_HOME=/usr/local/apache-maven-3.2.5
>> export M2=$M2_HOME/bin
>> export PATH=$M2/bin:$PATH
>>
>> Hi Nuwan,
> why you use M2 variable?
> its seems like /usr/local/apache-maven-3.2.5/bin/bin
>
> try
> export M2_HOME=/usr/local/apache-maven-3.2.5
> export PATH=$M2_HOME/bin:$PATH
>
> --
> Thank you
> Best Regards
>
> *Rajjaz HM*
> Associate Software Engineer
> WSO2 Inc. 
> lean | enterprise | middleware
> Mobile | +94752833834
> Email   | raj...@wso2.com
> LinkedIn | Blogger | WSO2 Profile
> 
>



-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *http://wso2.com
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739@*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Web Application Statistics Monitoring for Application Server 6.0.0

2015-12-15 Thread Nuwan Pallewela

[Moving thread to Architecture group]

Hi Nathasha,

Is statistics information get update per minute?
Do we have the capability to update the statistics using a refresh button
or some other way without waiting for one minute?

It will be great if you could provide a simple diagram which  describes the
design.

Thanks,
Nuwan


On Tue, Dec 15, 2015 at 11:29 AM, Nathasha Naranpanawa 
wrote:

> Hi all,
>
> I'm currently working on adding web application statistics monitoring
> feature to the upcoming Application Server 6.0.0. This was done in two
> iterations as following;
>
>- Adding a custom Valve to the tomcat server in order to collect data
>from the server.
>- Creating necessary CApp packages in order to define means of
>publishing data from tomcat server to DAS, receiving and storing the data.
>
> The custom tomcat Valve behaves as an Event Publisher and publishes data
> to DAS through Thrift data agent. For each request from the server, an
> Event is created including metadata and payload data and is published to
> the DAS by a DataPublisher.
>
> A CApp was created by including the definitions for an Event Stream, Event
> Receiver and Event Store to receive data from the publisher valve and store
> them. This is deployed in the
> wso2das-3.0.0/repository/deployment/server/carbonapps folder.
>
> A Spark script is also added to the CApp in order to query the data
> received by DAS. The script presents a summary of the requests received by
> DAS per minute. The summary includes the following information;
>
>- average request count
>- average response time
>- HTTP request success count
>- HTTP request error count
>
> Any suggestions and feedback are highly appreciated.
>
> Thanks,
>
>
> --
> Nathasha Naranpanawa
> Software Engineering Intern
> WSO2 Inc.
>
> Email: natha...@wso2.com
> Mobile: +94775496142
> LinkedIn: https://lk.linkedin.com/in/nathashanaranpanawa
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *http://wso2.com
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739@*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Web Application Statistics Monitoring for Application Server 6.0.0

2015-12-15 Thread Nuwan Pallewela

[Moving to Architecture group]

On Tue, Dec 15, 2015 at 3:31 PM, Nuwan Pallewela  wrote:

> [Moving thread to Architecture group]
>
> Hi Nathasha,
>
> Is statistics information get update per minute?
> Do we have the capability to update the statistics using a refresh button
> or some other way without waiting for one minute?
>
> It will be great if you could provide a simple diagram which  describes
> the design.
>
> Thanks,
> Nuwan
>
>
> On Tue, Dec 15, 2015 at 11:29 AM, Nathasha Naranpanawa 
> wrote:
>
>> Hi all,
>>
>> I'm currently working on adding web application statistics monitoring
>> feature to the upcoming Application Server 6.0.0. This was done in two
>> iterations as following;
>>
>>- Adding a custom Valve to the tomcat server in order to collect data
>>from the server.
>>- Creating necessary CApp packages in order to define means of
>>publishing data from tomcat server to DAS, receiving and storing the data.
>>
>> The custom tomcat Valve behaves as an Event Publisher and publishes data
>> to DAS through Thrift data agent. For each request from the server, an
>> Event is created including metadata and payload data and is published to
>> the DAS by a DataPublisher.
>>
>> A CApp was created by including the definitions for an Event Stream,
>> Event Receiver and Event Store to receive data from the publisher valve and
>> store them. This is deployed in the
>> wso2das-3.0.0/repository/deployment/server/carbonapps folder.
>>
>> A Spark script is also added to the CApp in order to query the data
>> received by DAS. The script presents a summary of the requests received by
>> DAS per minute. The summary includes the following information;
>>
>>- average request count
>>- average response time
>>- HTTP request success count
>>- HTTP request error count
>>
>> Any suggestions and feedback are highly appreciated.
>>
>> Thanks,
>>
>>
>> --
>> Nathasha Naranpanawa
>> Software Engineering Intern
>> WSO2 Inc.
>>
>> Email: natha...@wso2.com
>> Mobile: +94775496142
>> LinkedIn: https://lk.linkedin.com/in/nathashanaranpanawa
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> --
>
> *Nuwan Chamara Pallewela*
>
>
> *Software Engineer*
>
> *WSO2, Inc. *http://wso2.com
> *lean . enterprise . middleware*
>
> Email   *nuw...@wso2.com *
> Mobile  *+94719079739 <%2B94719079739>@*
>
>
>


-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *http://wso2.com
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739 <%2B94719079739>@*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Efficient way to represent tree data structure

2016-01-20 Thread Nuwan Pallewela

Hi All,

I 'am currently working on Data Mapper feature, data mapping algorithm
development. While implementing I want to store input data in a tree data
structure so that I could access data efficiently. This tree *will not
restructured* *or write *often. But it will be *read heavily*. I'm
wandering is there any better way to implement other than using objects as
nodes. For example : We can use adjacency lists to represent graph like
data structures so that graph operations can be done efficiently.

This tree is basically represent a AVRO schema related data object. ( We
can think of a xml request with converted to a JSON object ) So there can
be lists inside lists and complex data representations.

We may required to navigate and retrieve data's from one of the sibling or
one of the parent node's child or etc.

Is there any *improved , efficient way of storing and do above operations
on this kind of data  tree which will not restructured or written often but
will read heavily* , other than using objects as nodes.

Thanks,
Nuwan


-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *http://wso2.com
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739@*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] How to add patch improvements for Developer Studio update site

2016-01-31 Thread Nuwan Pallewela

Hi All,

What is the process for adding improvements done for a patch, to Developer
Studio update site?

Thanks,
Nuwan

-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *http://wso2.com
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739@*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Including Data Mapper Mediator in ESB 5.0 Release

2016-02-15 Thread Nuwan Pallewela

Hi All,

Data Mapper feature is planned to release with ESB 5.0 and initially it was
done by team developer studio as a POC.

There are three components in data mapper implementation. They are

   1. Data Mapper Tool
   2. Data Mapper Mediator
   3. Data Mapper Engine

Data Mapper Tool should be with the Developer Studio ESB Tooling.

Data Mapper Mediator should be move to Carbon Mediation.

Ideally we should maintain a separate repository for the Data Mapper
Engine. So where we should keep the Data Mapper Engine and how to proceed?

Thanks,

Nuwan
-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *http://wso2.com
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739@*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Including Data Mapper Mediator in ESB 5.0 Release

2016-02-16 Thread Nuwan Pallewela

On Tue, Feb 16, 2016 at 11:17 AM, Jasintha Dasanayake 
wrote:

> IMO , Both data mapper editor and the engine are a cross platform
> components which can be used /ship with other product as well , Only the
> ESB graphical mediator and synapse mediators should be added into exiting
> ESB product and ESB tool repos ,
>
Agree. Both editor and engine are cross platform components.

>
>
Also I feel that it requires more frequent release in data mapper editor to
> make it rock-solid also more new feature should be introduced to improve
> the user experience ,therefore this editor should be able to release on its
> own.
>
+1 for having two repositories for data mapper editor and engine.

>
> WDYT ?
>
> Thanks and Regards
> /Jasintha
>
>
> On Tue, Feb 16, 2016 at 10:11 AM, Chanaka Fernando 
> wrote:
>
>> Hi Nuwan,
>>
>> +1 for keeping the Data mapper engine in a separate repo. That will make
>> it easy to maintain and reuse by other components if there is a requirement
>> in the future.
>>
>>
>> On Tue, Feb 16, 2016 at 10:06 AM, Susinda Perera 
>> wrote:
>>
>>>
>>>
>>> On Tue, Feb 16, 2016 at 10:01 AM, Nuwan Pallewela 
>>> wrote:
>>>
>>>>
>>>> Hi All,
>>>>
>>>> Data Mapper feature is planned to release with ESB 5.0 and initially it
>>>> was done by team developer studio as a POC.
>>>>
>>>> There are three components in data mapper implementation. They are
>>>>
>>>>1. Data Mapper Tool
>>>>2. Data Mapper Mediator
>>>>3. Data Mapper Engine
>>>>
>>>> Data Mapper Tool should be with the Developer Studio ESB Tooling.
>>>>
>>> This can also be place outside as this is a separate plugin. But ESB
>>> plugin has a dependency to datamapper plugin.
>>>
>>>> Data Mapper Mediator should be move to Carbon Mediation.
>>>>
>>>> Ideally we should maintain a separate repository for the Data Mapper
>>>> Engine. So where we should keep the Data Mapper Engine and how to proceed?
>>>>
>>> +1 for place this in a separate place,  At the moment  'Data Mapper
>>> Engine' is needed by datamapper-mediator, but datamapper-tool will also use
>>> the engine (if we are giving some dry-run/emulator feature)
>>>
>>> Susinda
>>>
>>>> Thanks,
>>>>
>>>> Nuwan
>>>> --
>>>> --
>>>>
>>>> *Nuwan Chamara Pallewela*
>>>>
>>>>
>>>> *Software Engineer*
>>>>
>>>> *WSO2, Inc. *http://wso2.com
>>>> *lean . enterprise . middleware*
>>>>
>>>> Email   *nuw...@wso2.com *
>>>> Mobile  *+94719079739 <%2B94719079739>@*
>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> *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
>>>
>>>
>>
>>
>> --
>> Thank you and Best Regards,
>> Chanaka Fernando
>> Senior Technical Lead
>> WSO2, Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> mobile: +94 773337238
>> Blog : http://soatutorials.blogspot.com
>> LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0
>> Twitter:https://twitter.com/chanakaudaya
>>
>>
>>
>>
>>
>
>
> --
>
> *Jasintha Dasanayake*
>
> *Senior Software EngineerWSO2 Inc. | http://wso2.com
> <http://wso2.com/>lean . enterprise . middleware*
>
>
> *mobile :- 0711368118*
>



-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *http://wso2.com
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739@*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] No such method when loading third party jar in eclipse

2016-02-29 Thread Nuwan Pallewela

Hi Awanthika,

Have you exported the packages you need to use?

Thanks,
Nuwan

On Mon, Feb 29, 2016 at 3:47 PM, Awanthika Senarath 
wrote:

> The issue is,
>
> We are using two jackson jars in our source namely,
>
> jackson-mapper-asl-1.9.3.jar and jackson-mapper-asl-1.8.10.jar,
>
> Awanthika Senarath
> Software Engineer, WSO2 Inc.
> Mobile: +94717681791
>
>
>
> On Mon, Feb 29, 2016 at 3:41 PM, Awanthika Senarath 
> wrote:
>
>> Hello All,
>>
>> I have a third party dependency in my eclipse RCP plugin to the following
>> jars,
>>
>> jaxb-impl-2.2.4-1.jar,
>> jaxb-xjc-2.2.4-1.jar,
>> jackson-mapper-asl-1.9.3.jar,
>> jackson-core-asl-1.9.3.jar,
>> jackson-annotations-2.1.0.jar
>>
>> I have loaded them through a lib folder, added to eclipse class-path and
>> have the entry [1] in my META-INF file.
>>
>> There are no errors shown in the project explorer or in the java editor
>> of the classes.
>>
>> During runtime all the other libs are loaded fine, the firt jar loaded is
>> jaxb-xjc-2.2.4-1.jar,, "Driver" method. But it throws a runtime error [2]
>> saying method not found. When I cheked the source of the jar [3] I could
>> see that the method exists.
>>
>> Appreciate any help on resolving this.
>>
>>
>> [1]  lib/jaxb-impl-2.2.4-1.jar,
>>  lib/jaxb-xjc-2.2.4-1.jar,
>>  lib/jackson-mapper-asl-1.9.3.jar,
>>  lib/jackson-core-asl-1.9.3.jar,
>>  lib/jackson-annotations-2.1.0.jar
>>
>> [2] java.util.ServiceConfigurationError: com.sun.tools.xjc.Plugin:
>> Provider
>> org.wso2.developerstudio.visualdatamapper.diagram.avro.generators.AvroSchemagenPlugin
>> could not be instantiated
>> at java.util.ServiceLoader.fail(ServiceLoader.java:232)
>> at java.util.ServiceLoader.access$100(ServiceLoader.java:185)
>> at
>> java.util.ServiceLoader$LazyIterator.nextService(ServiceLoader.java:384)
>> at java.util.ServiceLoader$LazyIterator.next(ServiceLoader.java:404)
>> at java.util.ServiceLoader$1.next(ServiceLoader.java:480)
>> at com.sun.tools.xjc.Options.findServices(Options.java:931)
>> at com.sun.tools.xjc.Options.getAllPlugins(Options.java:367)
>> at com.sun.tools.xjc.Options.parseArgument(Options.java:671)
>> at com.sun.tools.xjc.Driver$OptionsEx.parseArgument(Driver.java:501)
>> at com.sun.tools.xjc.Options.parseArguments(Options.java:781)
>> at com.sun.tools.xjc.Driver.run(Driver.java:239)
>> at com.sun.tools.xjc.Driver.run(Driver.java:199)
>> at com.sun.tools.xjc.Driver._main(Driver.java:122)
>> at com.sun.tools.xjc.Driver.access$000(Driver.java:79)
>> at com.sun.tools.xjc.Driver$1.run(Driver.java:102)
>> Caused by: java.lang.NoSuchMethodError:
>> org.codehaus.jackson.map.introspect.VisibilityChecker.with(Lorg/codehaus/jackson/annotate/JsonAutoDetect$Visibility;)Lorg/codehaus/jackson/map/introspect/VisibilityChecker;
>>
>>
>> [3]
>> http://grepcode.com/file/repo1.maven.org/maven2/org.codehaus.jackson/jackson-mapper-asl/1.9.2/org/codehaus/jackson/map/introspect/VisibilityChecker.java#VisibilityChecker.with%28org.codehaus.jackson.annotate.JsonAutoDetect%29
>>
>> Regards
>>
>> Awanthika Senarath
>> Software Engineer, WSO2 Inc.
>> Mobile: +94717681791
>>
>>
>>
>


-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *http://wso2.com
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739@*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Issue in representing avro records with multiple namespaces

2016-03-01 Thread Nuwan Pallewela

On Tue, Mar 1, 2016 at 7:34 PM, Sohani Weerasinghe  wrote:

> Hi All,
>
> If we consider an XML which has multiple namespaces as below ,
>
> 
> http://www.w3.org/TR/html4/";>
>   Asian Coffee Table
>   74
>   129
> 
> http://www.w3schools.com/furniture";>
>   African Coffee Table
>   80
>   120
> 
> 
>
> The avro schema should be as follows ,
>
> {
>   "type" : "record",
>   "name" : "root",
>   "fields" : [ {
> "type" : "record",
> "name" : "tableRecord",
>* "doc" : "http://www.w3.org/TR/html4/
> ",*
> "namespace" : "http://www.w3.org/TR/html4/";
> "fields" : [ {
>   "name" : "name",
>   "type" : [ "null", "string" ]
>   "doc" : "http://www.w3.org/TR/html4/";
>   } , {
>   "name" : "width",
>   "type" : [ "null", "int" ]
>   },{
>   "name" : "length",
>   "type" : [ "null", "int" ]
>   }]
> }, {
> "type" : "record",
> "name" : "tableRecord",
>   *  "doc" : "http://www.w3schools.com/furniture
> ",*
> "namespace" : "http://www.w3schools.com/furniture";
> "fields" : [ {
>   "name" : "name",
>   "type" : [ "null", "string" ]
>   } , {
>   "name" : "width",
>   "type" : [ "null", "int" ]
>   },{
>   "name" : "length",
>   "type" : [ "null", "int" ]
>   }]
> } ]
> }
>
> When representing this using the Visual DataMapper Editor, in order to
> differentiate the two records, we can add a namespace prefix to the name of
> the record as shown below.
>
>
> But when generating the Avro Schema, if we pass this value as the name of
> the node it  throws *org.apache.avro.SchemaParseException: Illegal
> character in: y:tableRecord.*
>

AVRO name should start with [A-Za-z] and subsequently contain only
[A-Za-z0-9_].
So we can not pass name with namespace prefix.

>
> So, if we use only the name (tableRecord, by removing the prefix) to
> create the avro schema, how are we going to differentiate the records
> separately when generating the mapping config?
>

 We should add above xml namespace prefix as the namespace of AVRO record.
Then two elements can be differentiated.
For Eg:

{
  "type" : "record",
  "name" : "root",
  "fields" : [ {
"type" : "record",
"name" : "tableRecord",
   * "doc" : "http://www.w3.org/TR/html4/
",*
"namespace" : "N1",
"fields" : [ {
  "name" : "name",
  "type" : [ "null", "string" ],
  "doc" : "http://www.w3.org/TR/html4/";
  } , {
  "name" : "width",
  "type" : [ "null", "int" ],
  "doc" : "http://www.w3.org/TR/html4/";
  },{
  "name" : "length",
  "type" : [ "null", "int" ],
  "doc" : "http://www.w3.org/TR/html4/";
  }]
}, {
"type" : "record",
"name" : "tableRecord",
  *  "doc" : "http://www.w3schools.com/furniture
",*
"namespace" : "N2",
"fields" : [ {
  "name" : "name",
  "type" : [ "null", "string" ],
  *"doc" : "http://www.w3schools.com/furniture
"*
  } , {
  "name" : "width",
  "type" : [ "null", "int" ]
  *"doc" : "http://www.w3schools.com/furniture
"*
  },{
  "name" : "length",
  "type" : [ "null", "int" ],
  *"doc" : "http://www.w3schools.com/furniture
"*
  }]
} ]
}

Then the full names of the two tableRecords will be N1.tableRecord and
N2.tableRecord and AVRO can differentiate these two fields.

>
> eg: If we are to map a field in  y:tableRecord with a field
> in y:tableRecord etc. How can we differentiate this?
>
> This usecase of having multiple namespaces can be displayed graphically in
> the Design view by appending a namespace prefix, but it seems this will
> have issues in generating the avro schema and the mapping config.
>

Mapping configuration does not need to be aware of the namespaces as long
as they can be differentiate in the diagram. Output from the mapping will
look into the output schema and will build the output message with desired
namespaces.

>
> Your suggestions are highly appreciated.
>
> 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 *
Mobile  *+94719079739@*
___
Dev mailing list
Dev@wso2.org
http://wso2.

Re: [Dev] Issue in representing avro records with multiple namespaces

2016-03-01 Thread Nuwan Pallewela

+1 for using "attr_" .


On Wed, Mar 2, 2016 at 11:35 AM, Sohani Weerasinghe  wrote:

> Thanks for the input. Let's use -  "name" : "attr_gender"
>
> Sohani Weerasinghe
> Software Engineer
> WSO2, Inc: http://wso2.com
>
> Mobile  : +94 716439774
> Blog :http://christinetechtips.blogspot.com/
> Twitter  : https://twitter.com/sohanichristine
>
> On Wed, Mar 2, 2016 at 11:31 AM, Susinda Perera  wrote:
>
>> How about *attr* (lowercase)
>>
>> On Wed, Mar 2, 2016 at 11:29 AM, Sohani Weerasinghe 
>> wrote:
>>
>>> I think it's better if we can use "ATR" instead of "ATT"
>>>
>>> Sohani Weerasinghe
>>> Software Engineer
>>> WSO2, Inc: http://wso2.com
>>>
>>> Mobile  : +94 716439774
>>> Blog :http://christinetechtips.blogspot.com/
>>> Twitter  : https://twitter.com/sohanichristine
>>>
>>> On Wed, Mar 2, 2016 at 11:25 AM, Sohani Weerasinghe 
>>> wrote:
>>>
>>>> Hi All,
>>>>
>>>> When representing attributes in avro schema,  according to [1] the
>>>> suggested approach is to use @ as a prefix.
>>>>
>>>> Since avro name should start with [A-Za-z] and subsequently contain
>>>> only  [A-Za-z0-9_], shall we represent it as below (adding ATT as a prefix)
>>>>
>>>> "name" : "*ATT*_gender"
>>>>
>>>> [1]
>>>> https://docs.google.com/spreadsheets/d/15eyRuxn9rFazULASqtB2DZaSAVznKqSNnIGrwvdpzic/edit?ts=56d5250b#gid=0
>>>>
>>>> Sohani Weerasinghe
>>>> Software Engineer
>>>> WSO2, Inc: http://wso2.com
>>>>
>>>> Mobile  : +94 716439774
>>>> Blog :http://christinetechtips.blogspot.com/
>>>> Twitter  : https://twitter.com/sohanichristine
>>>>
>>>> On Wed, Mar 2, 2016 at 7:47 AM, Sohani Weerasinghe 
>>>> wrote:
>>>>
>>>>>
>>>>> Please find the attached image which represents the prefix in the
>>>>> tree view
>>>>>
>>>>> Sohani Weerasinghe
>>>>> Software Engineer
>>>>> WSO2, Inc: http://wso2.com
>>>>>
>>>>> Mobile  : +94 716439774
>>>>> Blog :http://christinetechtips.blogspot.com/
>>>>> Twitter  : https://twitter.com/sohanichristine
>>>>>
>>>>> On Wed, Mar 2, 2016 at 7:45 AM, Sohani Weerasinghe 
>>>>> wrote:
>>>>>
>>>>>>
>>>>>>
>>>>>> Sohani Weerasinghe
>>>>>> Software Engineer
>>>>>> WSO2, Inc: http://wso2.com
>>>>>>
>>>>>> Mobile  : +94 716439774
>>>>>> Blog :http://christinetechtips.blogspot.com/
>>>>>> Twitter  : https://twitter.com/sohanichristine
>>>>>>
>>>>>> On Wed, Mar 2, 2016 at 6:28 AM, Jasintha Dasanayake <
>>>>>> jasin...@wso2.com> wrote:
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Tue, Mar 1, 2016 at 9:07 PM, Sohani Weerasinghe 
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Thanks Nuwan for the response.
>>>>>>>>
>>>>>>>> When generating the avro schema by adding elements to the tree
>>>>>>>> view, user can specify the namespace (xml namespace) with the prefix, 
>>>>>>>> so
>>>>>>>> that when generating the the avro schema we can map the namespace to 
>>>>>>>> doc
>>>>>>>> and prefix to the namespace in avro.
>>>>>>>>
>>>>>>>
>>>>>>> Yes that's mapping is fine , somehow we need to show at least prefix
>>>>>>> in the tree view otherwise user experience won't be nice since user 
>>>>>>> have to
>>>>>>> check it explicitly while doing the mapping
>>>>>>>
>>>>>>
>>>>>> Yes, I have implemented that and the prefix will be shown in the tree
>>>>>> view.
>>>>>>
>>>>>>>
>>>>>>> Thanks and Regards
>>>>>>> /Jasintha.
>>>>>>>
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>

Re: [Dev] Libraries to process JSON schema

2016-03-07 Thread Nuwan Pallewela

Hi Sohani,

Currently ESB use StAXON library for JSON parsing. So I think we need to
compare it too.

However another important factor for deciding the library is will it
support to manipulate JSON schema. Because may we need to validate the JSON
object with the given schema's.
Will JSON.simple support schema validation?

So to decide the best library Viraj and myself decided to implement simple
parser from both jackson and StAXON to compare the performance.

Thanks,
Nuwan

On Mon, Mar 7, 2016 at 4:31 PM, Sohani Weerasinghe  wrote:

> Hi All,
>
> We are in a process of evaluating the libraries to process JSON schema
> (read and write) and we found few libraries as listed below:
>
>- Jackson [1]
>- JSON.simple [2]
>- Gson
>
> Based on the findings when comparing the GSON and Jackson [3], it seems
> Jackson has more complete support than Gson
> - Streaming (Streaming API) reading, writing, for ultra-high performance
> (or memory-limited) use cases
> - Tree model (DOM-like access),can convert between various models (tree
> <-> java object <-> stream)
> - Can use any constructors (or static factory methods), not just default
> constructor
> - Field and getter/setter access
> - Interoperability: can also use JAXB annotations, has
> support/work-arounds for common packages
> - Support for deserializing polymorphic types (Jackson 1.5),can serialize
> AND deserialize things like List correctly (with additional type
> information)
>
> When considering the JSON.simple[4], it is a simple Java library for JSON
> processing, read and write JSON data and it is full compliance with json
> specification. If we compare this with other two libraries [5], If we are
> dealing with both small and large schema files,neither Jackson nor GSON
> perform well across multiple files sizes as JSON.simple does. ( Jackson
> support well for large files only)
>
> If we consider the implementation for read JSON schema and generating the
> schema, below things can be highlighted
>
>
>- Jackson - We can use
>an ObjectMapper(com.fasterxml.jackson.databind.ObjectMapper) object and
>read the values of the fields in the schema (Tree Model)  using
>fieldNames(), isObject(), isArray() etc and also can use methods like
>createArrayNode(), createObjectNode() in generating the JSON schema.
>
>
>- JSON.Simple - We can use JSONObject (org.json.simple.JSONObject) and
>JSONArray (org.json.simple.JSONArray)  to read and write values to/from
> JSON schema
>
>
> AFAIU, implementation wise we can use either Jackson or JSON.simple and
> when comparing the performance it seems both are better than GSON
>
> But, when considering selecting the best library i feel JSON.simple would
> be better since it has following features
>
> -Full compliance with JSON specification and reliable
> -Provides multiple functionalities such as encode, decode/parse and escape
> JSON text while keeping the library lightweight
> -Flexible, simple and easy to use by reusing Map and List interfaces
> -Supports streaming output of JSON text
> - High performance
> - No dependency on external libraries
>
> Shall we proceed with JSON.simple? WDYT?
>
> [1] http://wiki.fasterxml.com/JacksonInFiveMinutes
> [2] https://code.google.com/archive/p/json-simple/
> [3] http://stackoverflow.com/questions/2378402/jackson-vs-gson
> [4] https://code.google.com/archive/p/json-simple/
> [5]
> http://blog.takipi.com/the-ultimate-json-library-json-simple-vs-gson-vs-jackson-vs-json/
>
> 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 *
Mobile  *+94719079739@*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Namespaces and Attributes in JSON Schema

2016-03-15 Thread Nuwan Pallewela

Hi sohani,

I think we do not need to include new type called "attr" to define it as a
attribute. We can name the field with a prefix like "@" or "attr_".

Eg:
"@firstname": {
"id": "http://jsonschema.net/employee/0/firstname";,
"type": "string"
  },

or

"attr_firstname": {
"id": "http://jsonschema.net/employee/0/firstname";,
"type": "string"
  },

Thanks,
Nuwan

On Wed, Mar 16, 2016 at 10:15 AM, Sohani Weerasinghe 
wrote:

> Hi Nuwan/ Viraj,
>
> Can you please mention how are we going to handle $subject?
>
> Can we have a new field as attr as below to handle the attributes?
>
> "firstname": {
> "id": "http://jsonschema.net/employee/0/firstname";,
> "type": "string",
> *"attr" : "xyz"*
>   },
>
> 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 *
Mobile  *+94719079739@*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Namespaces and Attributes in JSON Schema

2016-03-15 Thread Nuwan Pallewela

Hi Sohani,

+1 for using "@" for attribute.

Suggestion for listing attributes. Attributes under a element should listed
before the other child field values.
Eg: "no" field should list before city and road.

Thanks,
Nuwan

On Wed, Mar 16, 2016 at 10:54 AM, Sohani Weerasinghe 
wrote:

> Hi,
>
> Please find the schema and the visual representation for representing the
> attributes.
>
>   {
>   "$schema": "http://json-schema.org/draft-04/schema#";,
>   "id": "http://jsonschema.net";,
>   "title" : "employees",
>   "type": "object",
>   "properties": {
> "employee": {
>   "id": "http://jsonschema.net/employee";,
>   "type": "array",
>   "items": {
> "id": "http://jsonschema.net/employee/0";,
> "type": "object",
> "properties": {
>   "firstname": {
> "id": "http://jsonschema.net/employee/0/firstname";,
> "type": "string"
>   },
>   "lastname": {
> "id": "http://jsonschema.net/employee/0/lastname";,
> "type": "string"
>   },
>   "address": {
> "id": "http://jsonschema.net/employee/0/address";,
> "type": "object",
> "properties": {
>   "city": {
> "id": "http://jsonschema.net/employee/0/address/city";,
> "type": "string"
>   },
>  * "@no": {*
> "id": "http://jsonschema.net/employee/0/address/no";,
> "type": "string"
>   },
>   "road": {
> "id": "http://jsonschema.net/employee/0/address/road";,
> "type": "string"
>   }
> }
>   }
> },
> "required": [
>   "firstname",
>   "lastname",
>   "address"
> ]
>   },
>   "required": [
> "0"
>   ]
> }
>   },
>   "required": [
> "employee"
>   ]
> }
>
> 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 Wed, Mar 16, 2016 at 10:35 AM, Sohani Weerasinghe 
> wrote:
>
>> Thanks Nuwan. Shall we go with '@' then?
>>
>> Sohani Weerasinghe
>> Software Engineer
>> WSO2, Inc: http://wso2.com
>>
>> Mobile  : +94 716439774
>> Blog :http://christinetechtips.blogspot.com/
>> Twitter  : https://twitter.com/sohanichristine
>>
>> On Wed, Mar 16, 2016 at 10:23 AM, Nuwan Pallewela 
>> wrote:
>>
>>> Hi sohani,
>>>
>>> I think we do not need to include new type called "attr" to define it as
>>> a attribute. We can name the field with a prefix like "@" or "attr_".
>>>
>>> Eg:
>>> "@firstname": {
>>> "id": "http://jsonschema.net/employee/0/firstname";,
>>> "type": "string"
>>>   },
>>>
>>> or
>>>
>>> "attr_firstname": {
>>> "id": "http://jsonschema.net/employee/0/firstname";,
>>> "type": "string"
>>>   },
>>>
>>> Thanks,
>>> Nuwan
>>>
>>> On Wed, Mar 16, 2016 at 10:15 AM, Sohani Weerasinghe 
>>> wrote:
>>>
>>>> Hi Nuwan/ Viraj,
>>>>
>>>> Can you please mention how are we going to handle $subject?
>>>>
>>>> Can we have a new field as attr as below to handle the attributes?
>>>>
>>>> "firstname": {
>>>> "id": "http://jsonschema.net/employee/0/firstname";,
>>>> "type": "string",
>>>> *"attr" : "xyz"*
>>>>   },
>>>>
>>>> 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 *
>>> Mobile  *+94719079739 <%2B94719079739>@*
>>>
>>>
>>>
>>
>


-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *http://wso2.com
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739@*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Namespaces and Attributes in JSON Schema

2016-03-15 Thread Nuwan Pallewela

 Hi Sohani,

The concern with the listed order is ui can be slightly misleading.

For example actually "no" is a attribute of "address" element. But it is
listed after "city" field element. It will be misleading when "city" will
also have a attribute as shown below in the schema. There will be two
attribute elements listed in the diagram, first one will be a attribute of
"city" and the second one will be a attribute of "address".

A indentation for the attribute of "city" element will give separation for
the above concern, but if this "city" element is another complex object
type, then there will be a big gap between "address" element and it's
attribute "no" which can confuse the user.

{
  "$schema": "http://json-schema.org/draft-04/schema#";,
  "id": "http://jsonschema.net";,
  "title" : "employees",
  "type": "object",
  "properties": {
"employee": {
  "id": "http://jsonschema.net/employee";,
  "type": "array",
  "items": {
"id": "http://jsonschema.net/employee/0";,
"type": "object",
"properties": {
  "firstname": {
"id": "http://jsonschema.net/employee/0/firstname";,
"type": "string"
  },
  "lastname": {
"id": "http://jsonschema.net/employee/0/lastname";,
"type": "string"
  },
  "address": {
"id": "http://jsonschema.net/employee/0/address";,
"type": "object",
"properties": {
  "city": {
"id": "http://jsonschema.net/employee/0/address/city";,
"type": "string"
"properties": {
"@postalcode":{
  "id": "http://jsonschema.net/employee/0/address/no
",
  "type": "string"
 }
  }
  },
     * "@no": {*
   "id": "http://jsonschema.net/employee/0/address/no";,
"type": "string"
  },
  "road": {
"id": "http://jsonschema.net/employee/0/address/road";,
"type": "string"
  }
}
  }
},
"required": [
  "firstname",
  "lastname",
  "address"
]
  },
  "required": [
"0"
  ]
}
  },
  "required": [
"employee"
  ]
}

Thanks,
Nuwan

On Wed, Mar 16, 2016 at 11:00 AM, Nuwan Pallewela  wrote:

> Hi Sohani,
>
> +1 for using "@" for attribute.
>
> Suggestion for listing attributes. Attributes under a element should
> listed before the other child field values.
> Eg: "no" field should list before city and road.
>
> Thanks,
> Nuwan
>
> On Wed, Mar 16, 2016 at 10:54 AM, Sohani Weerasinghe 
> wrote:
>
>> Hi,
>>
>> Please find the schema and the visual representation for representing the
>> attributes.
>>
>>   {
>>   "$schema": "http://json-schema.org/draft-04/schema#";,
>>   "id": "http://jsonschema.net";,
>>   "title" : "employees",
>>   "type": "object",
>>   "properties": {
>> "employee": {
>>   "id": "http://jsonschema.net/employee";,
>>   "type": "array",
>>   "items": {
>> "id": "http://jsonschema.net/employee/0";,
>> "type": "object",
>> "properties": {
>>   "firstname": {
>> "id": "http://jsonschema.net/employee/0/firstname";,
>> "type": "string"
>>   },
>>   "lastname": {
>> "id": "http://jsonschema.net/employee/0/lastname";,
>> "type": "string"
>>   },
>>   "address": {
>> "id": "http://jsonschema.net/employee/0/address";,
>> "type":

Re: [Dev] Namespaces and Attributes in JSON Schema

2016-03-15 Thread Nuwan Pallewela

Hi All,

Exactly. They should listed like above.
Attributes should listed right after the binded element as shown in the
figure.

Thanks,
Nuwan

On Wed, Mar 16, 2016 at 12:11 PM, Sohani Weerasinghe 
wrote:

> Hi All,
>
> When considering the way which Altova has handled the attributes,
> according to the attached image both address and city have attributes and
> they have listed separately ( "value" after the "address" and "anotherAtr"
> under the city element". Let's follow the same way.
>
> Sohani Weerasinghe
> Software Engineer
> WSO2, Inc: http://wso2.com
>
> Mobile  : +94 716439774
> Blog :http://christinetechtips.blogspot.com/
> Twitter  : https://twitter.com/sohanichristine
>
> On Wed, Mar 16, 2016 at 11:35 AM, Nuwan Pallewela  wrote:
>
>> Hi Sohani,
>>
>> The concern with the listed order is ui can be slightly misleading.
>>
>> For example actually "no" is a attribute of "address" element. But it is
>> listed after "city" field element. It will be misleading when "city" will
>> also have a attribute as shown below in the schema. There will be two
>> attribute elements listed in the diagram, first one will be a attribute of
>> "city" and the second one will be a attribute of "address".
>>
>> A indentation for the attribute of "city" element will give separation
>> for the above concern, but if this "city" element is another complex object
>> type, then there will be a big gap between "address" element and it's
>> attribute "no" which can confuse the user.
>>
>> {
>>   "$schema": "http://json-schema.org/draft-04/schema#";,
>>   "id": "http://jsonschema.net";,
>>   "title" : "employees",
>>   "type": "object",
>>   "properties": {
>> "employee": {
>>   "id": "http://jsonschema.net/employee";,
>>   "type": "array",
>>   "items": {
>> "id": "http://jsonschema.net/employee/0";,
>> "type": "object",
>> "properties": {
>>   "firstname": {
>> "id": "http://jsonschema.net/employee/0/firstname";,
>> "type": "string"
>>   },
>>   "lastname": {
>> "id": "http://jsonschema.net/employee/0/lastname";,
>> "type": "string"
>>   },
>>   "address": {
>> "id": "http://jsonschema.net/employee/0/address";,
>> "type": "object",
>> "properties": {
>>   "city": {
>> "id": "http://jsonschema.net/employee/0/address/city";,
>> "type": "string"
>> "properties": {
>>     "@postalcode":{
>>   "id": "
>> http://jsonschema.net/employee/0/address/no";,
>>   "type": "string"
>>  }
>>   }
>>   },
>>  * "@no": {*
>>"id": "http://jsonschema.net/employee/0/address/no";,
>> "type": "string"
>>   },
>>   "road": {
>> "id": "http://jsonschema.net/employee/0/address/road";,
>> "type": "string"
>>   }
>> }
>>   }
>> },
>> "required": [
>>   "firstname",
>>   "lastname",
>>   "address"
>> ]
>>   },
>>   "required": [
>> "0"
>>   ]
>> }
>>   },
>>   "required": [
>> "employee"
>>   ]
>> }
>>
>> Thanks,
>> Nuwan
>>
>> On Wed, Mar 16, 2016 at 11:00 AM, Nuwan Pallewela 
>> wrote:
>>
>>> Hi Sohani,
>>>
>>> +1 for using "@" for attribute.
>>>
>>> Suggestion for listing attributes. Attributes under a element should
>

Re: [Dev] ESB 5 - Beta - Issue with the docs on installing tooling plugins

2016-06-28 Thread Nuwan Pallewela

Hi All,

Yes. The given link contains the main P2, not the composite. So the image
should be changed according to that.
And the steps are also needed to be changed as before installing main p2
user should install the developer studio kernel[1] and platform bundle[2].

RC release will have both composite and main p2.

[1]
http://product-dist.wso2.com/p2/developer-studio-kernel/4.1.0/kernel/releases/
[2]
http://builder1.us1.wso2.org/~developerstudio/developer-studio-kernel/4.1.0/platform-bundles/releases/4.1.0-201606031446/

Thanks,
Nuwan

On Tue, Jun 28, 2016 at 12:18 PM, Kasun Indrasiri  wrote:

> Can't install ESB tool on Eclipse Mars2 with [1]. Seems [1] is not updated
> with the composite tooling plugings (it only contains ESB features).
>
> [1]
> https://docs.wso2.com/display/ESB500/Installing+the+ESB+Tooling+Plug-in
>
>
>
> --
> Kasun Indrasiri
> Software Architect
> WSO2, Inc.; http://wso2.com
> lean.enterprise.middleware
>
> cell: +94 77 556 5206
> Blog : http://kasunpanorama.blogspot.com/
>



-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *http://wso2.com
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739@*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Introducing Custom JSON Schema version identifier for WSO2 Data Mapper schema

2016-07-10 Thread Nuwan Pallewela

Hi All,

As you know we use JSON-schema to define message format of the input and
output of the WSO2 Data Mapper. And we have introduce several new keywords
to meet the requirements to handle complexities of define different
(JSON/XML/CSV) formats, we need to define a *custom URI* for "$schema".
This custom URI must not be one of the predefined values.

Let's use "http://json-schema.org/draft-04/wso2-data-mapper-v5.0.0/schema#
"
as the custom URI for WSO2 Data Mapper schema.

WDYT?

Thanks,
Nuwan

-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *http://wso2.com
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739@*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Introducing Custom JSON Schema version identifier for WSO2 Data Mapper schema

2016-07-10 Thread Nuwan Pallewela

Hi All,

On Mon, Jul 11, 2016 at 10:44 AM, Nuwan Pallewela  wrote:

> Hi All,
>
> As you know we use JSON-schema to define message format of the input and
> output of the WSO2 Data Mapper. And we have introduce several new keywords
> to meet the requirements to handle complexities of define different
> (JSON/XML/CSV) formats, we need to define a *custom URI* for "$schema".
> This custom URI must not be one of the predefined values.
>
> Let's use "http://json-schema.org/draft-04/wso2-data-mapper-v5.0.0/schema#
> <http://www.google.com/url?q=http%3A%2F%2Fjson-schema.org%2Fdraft-04%2Fwso2-data-mapper-v5.0.0%2Fschema%23&sa=D&sntz=1&usg=AFQjCNGJH0LK4M1qOPSchG6Ld6FR6CZ6TQ>"
> as the custom URI for WSO2 Data Mapper schema.
>
small modification for the URL "
http://wso2.org/json-schema/wso2-data-mapper-v5.0.0/schema#";

>
> WDYT?
>
> Thanks,
> Nuwan
>
> --
> --
>
> *Nuwan Chamara Pallewela*
>
>
> *Software Engineer*
>
> *WSO2, Inc. *http://wso2.com
> *lean . enterprise . middleware*
>
> Email   *nuw...@wso2.com *
> Mobile  *+94719079739 <%2B94719079739>@*
>
>
>


-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *http://wso2.com
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739@*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [ESB] Unable to aggregate the XML messages by using Aggregate mediator

2016-07-17 Thread Nuwan Pallewela

Hi Pubudu,

What you have mentioned in the [1] is not an valid SOAP message. It do not
have the name space specified. That may be the case.

Thanks,
Nuwan

On Thu, Jul 14, 2016 at 7:21 AM, Shafreen Anfar  wrote:

> Hi Pubudu,
>
> It seems for some reason back-end response does not have a SOAP message
> but some other. Can you check the wire log and make sure back-end is
> sending a proper SOAP response.
>
> On Wed, Jul 13, 2016 at 10:12 PM, Pubudu Priyashan 
> wrote:
>
>>
>> Hi ESB team,
>>
>> I have a simple proxy service with a clone mediator and within that, I
>> call three different endpoints where each endpoint returns an XML body [1].
>> I would like to aggregate those three XML bodies into one message using
>> the aggregate mediator.
>>
>> But in my config, I am getting the error message [2]. Can someone please
>> advise if something is missing in this config [3]? You can directly add [3]
>> into an ESB proxy and see the error message.
>>
>> *[1] XML Message from the endpoint:-*
>>
>> 
>> 
>>
>> USD
>>
>>
>> *[2] Error Message:-*
>>
>> [2016-07-13 21:53:04,821] ERROR - SequenceMediator Expecting an
>> implementation of SOAP Envelope as the parent. But received some other
>> implementation
>> org.apache.axiom.soap.SOAPProcessingException: Expecting an
>> implementation of SOAP Envelope as the parent. But received some other
>> implementation
>> at
>> org.apache.axiom.soap.impl.llom.SOAPHeaderImpl.checkParent(SOAPHeaderImpl.java:408)
>> at
>> org.apache.axiom.soap.impl.llom.SOAPElement.setParent(SOAPElement.java:81)
>> at
>> org.apache.axiom.om.impl.llom.OMElementImpl.addChild(OMElementImpl.java:296)
>> at
>> org.apache.axiom.om.impl.llom.OMElementImpl.addChild(OMElementImpl.java:212)
>> at
>> org.apache.axiom.soap.impl.llom.SOAPBodyImpl.addChild(SOAPBodyImpl.java:231)
>> at
>> org.apache.synapse.mediators.eip.EIPUtils.addChildren(EIPUtils.java:171)
>> at
>> org.apache.synapse.mediators.eip.EIPUtils.enrichEnvelope(EIPUtils.java:135)
>> at
>> org.apache.synapse.mediators.eip.aggregator.AggregateMediator.getAggregatedMessage(AggregateMediator.java:498)
>> at
>> org.apache.synapse.mediators.eip.aggregator.AggregateMediator.completeAggregate(AggregateMediator.java:416)
>> at
>> org.apache.synapse.mediators.eip.aggregator.AggregateMediator.mediate(AggregateMediator.java:330)
>> at
>> org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:95)
>> at
>> org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:57)
>> at
>> org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:158)
>> at
>> org.apache.synapse.core.axis2.Axis2SynapseEnvironment.injectMessage(Axis2SynapseEnvironment.java:333)
>> at
>> org.apache.synapse.core.axis2.SynapseCallbackReceiver.handleMessage(SynapseCallbackReceiver.java:554)
>> at
>> org.apache.synapse.core.axis2.SynapseCallbackReceiver.receive(SynapseCallbackReceiver.java:188)
>> 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:1142)
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>> at java.lang.Thread.run(Thread.java:745)
>>
>>
>>
>> *[3] ESB  Proxy config:-*
>>
>> 
>> http://ws.apache.org/ns/synapse";
>>name="CloneProxy1"
>>transports="http,https"
>>statistics="disable"
>>trace="disable"
>>startOnLoad="true">
>>
>>   
>>  
>> 
>>  
>>  
>> 
>>
>>   
>>  >value="=== message
>> 1==="/>
>>   
>>   
>>  
>> http://www.mocky.io/v2/5786694b0f740aa58487"/>
>>  
>>   
>>
>> 
>> 
>>
>>   
>>  >
>>  value="=message
>> 2="/>
>>   
>>   
>>  
>> http://www.mocky.io/v2/578669550f740aa58488"/>
>>  
>>   
>>
>> 
>> 
>>
>>   
>>  >value="=== message
>> 3==="/>
>>   
>>   
>>  
>> http://www.mocky.io/v2/5786695f0f740aa58489"/>
>>  
>>   
>>
>> 
>>  
>>  
>>   
>>

Re: [Dev] Is it best practice to return null or an empty object from a method in DAO layer?

2016-07-17 Thread Nuwan Pallewela

Hi,

On Wed, Jul 13, 2016 at 10:15 AM, Sabra Ossen  wrote:

> Hi,
>
> Thank you all for your prompt responses :)
>
> So if it's an ArrayList/Map it's better to return an empty object rather
> than null. Got it.
>
> Regarding a POJO object IMO the usage of null, empty object or exception
> depends on the scenario being considered.
>
> Based on Rasikas' reply since the jaggery level code is using the DAO
> method (via manager interface) basically if no user is found then the
> exception thrown should be propagated and in the UI an appropriate message
> is rendered. Also since anyone else could be using the back end, when an
> exception is thrown they would not have to be aware of the internal
> implementation (if null or an empty object is returned, specifically he
> should be aware if an empty object is returned so that he should write his
> front end code accordingly).
>
> IMO returning an exception is clearer in terms of code but I guess the
> discussion could continue further until a guideline is specified.
>
+1 for throwing an exception in general. If we return a null or empty
object if data is unavailable, we may have to do a null check or empty
object check when trying to process it most probably. And that check may
tend to hide the original problem of unavailability of data and hard to
debug if we face an error in a different place because of that.IMO throwing
a custom exception which we could handle and log later or give an error
message  to user will be more suitable.
What to use with ArrayList and Maps is also depends on how we are going to
manipulate the returned value. If we are going to access data in a
ArrayList by index calling index values individually, it is better to use
exception otherwise we may need to have a null check before that. Same
applies to Maps. If we are going to process each element in a ArrayList we
could use Iterator and process. In that case empty ArrayList would do the
job. So there is not going to be a one for all cases solution in this
argument. It will depend on how we are going to process that returned value
and the nature of the application.

>
> Regards.
>
>
> On Wed, Jul 13, 2016 at 6:49 AM, Harsha Thirimanna 
> wrote:
>
>> HI Sabra,
>>
>> If there is collection type as a return, then you MUST return empty
>> collection object of instead of null. But if you expect POJO as a return,
>> then it would be better to return null instead of empty object. Because if
>> it returns empty object instead of null, then some one get misunderstand
>> who is going to use that API and will try to consume that as expected
>> output. Then there may be more problems. You may not be the only one who
>> consume your backend api.
>>
>>
>>
>>
>> *Harsha Thirimanna*
>> Associate Tech Lead; WSO2, Inc.; http://wso2.com
>> * *
>> *email: **hars...@wso2.com* * cell: +94 71 5186770 *
>> *twitter: **http://twitter.com/ *
>> *harshathirimannlinked-in: **http:
>> **//www.linkedin.com/pub/harsha-thirimanna/10/ab8/122
>> *
>>
>> *Lean . Enterprise . Middleware*
>>
>>
>> On Wed, Jul 13, 2016 at 12:42 AM, Rasika Perera  wrote:
>>
>>> Hi Sabra
>>> 
>>> ,
>>>
>>> I think you need to handle this error at jaggery level.
>>>
>>> Considering a method returning a user object the client code should not
 be able to proceed further if there is no user.
>>>
>>> In this case, -1 for returning NULL. When there is an error,
>>> unless
>>>  it is recoverable locally you 
>>> *should*
>>>  convey it to the upper layers. In your case, If you cannot return a
>>> user object it is more intuitive to return an exception such as
>>> UserManagerException.
>>>
>>> By returning NULL, you cannot make it mandatory to handle exception.
>>> Your client code will not be aware of NULL unless the developer reads your
>>> implementation class OR the documentation. Try to avoid
>>> NullPointerException
>>>  as much as possible.
>>>
>>> In your client code(Jaggery) you can catch this error with try{ }
>>> catch(error){ }. Found this blogpost [1] which discusses on jaggery error
>>> handling.
>>> AFAIK Jaggery will wrap java exceptions with ScriptException object.
>>>
>>> Regards,
>>> Rasika
>>>
>>> [1]
>>> http://ruchirawageesha.blogspot.com/2013/04/error-handling-in-jaggery.html
>>>
>>> On Tue, Jul 12, 2016 at 2:17 PM, Abimaran Kugathasan 
>>> wrote:
>>>
 There are good enough discussion in Stackoverflow [1], [2] and [3]. You
 could return null, empty object or throw exception in the case of data not
 available.

 It's also depends on the type of the Object you are supposed to return,
 if it's a ArrayList/Map, then returning empty ArrayList/Map is better than
 returning null, but, in case of Model object, I think, returning null is
 better than retuning a mock object of that class.


 [1] :
 http://programmers.stackexchan

Re: [Dev] Is it best practice to return null or an empty object from a method in DAO layer?

2016-07-18 Thread Nuwan Pallewela

Hi All,

I also think that using exception for flow control is an anti pattern.
Following [1] describes the best practices in handling exceptions.
And using null references is also not good practice. There is a design
pattern called Null Object Pattern[2] [3] to address this issue. So I think
combining these two we could decide how to approach for certain situation.

[1] http://www.onjava.com/pub/a/onjava/2003/11/19/exceptions.html?page=1
[2] https://sourcemaking.com/design_patterns/null_object
[3] https://en.wikipedia.org/wiki/Null_Object_pattern

Thanks,
Nuwan


On Mon, Jul 18, 2016 at 1:41 PM, Udara Liyanage  wrote:

> Hi,
>
> It is not performance that matters, using exceptions for flow control is
> an anti pattern [1] [2].
>
> [1] http://c2.com/cgi/wiki?DontUseExceptionsForFlowControl
> [2]
> http://programmers.stackexchange.com/questions/189222/are-exceptions-as-control-flow-considered-a-serious-antipattern-if-so-why
>
>
> On Sun, Jul 17, 2016 at 10:46 PM, Rasika Perera  wrote:
>
>> Hi All,
>>
>>
>>> Considering a method returning a user object the client code should not
>>> be able to proceed further if there is no user.
>>
>>  This is the use case we need to achieve. How do we enforce clients to
>> *not* to proceed if the user is not found? I really do promote Design by
>> Contract <https://en.wikipedia.org/wiki/Design_by_contract>. NULL will
>> give over-flexibility here and it is not what we asked for either.
>> Further, it might caused redundant NULL checks and NPEs for FREE.
>>
>> Exceptions are meant to be used for exceptional cases, using them for
>>> flow control is a bad practice. So I don't think it is a good practice to
>>> throw Exceptions instead of returning null. In addition using exceptions is
>>> costly for performance.
>>
>> Yes, Exceptions might be costly if you used it in bad way. Why not for flow
>> control? If your code running happy path most of the times, returning
>> exception on a trap would not be that harmfull. Exceptions are much
>> similar to other objects except the native call fillInStackTrace
>> <http://docs.oracle.com/javase/8/docs/api/java/lang/Throwable.html#fillInStackTrace-->.
>>  Even
>> Throwable has a constructor without a stacktrace, if you worried on
>> performance. My rule of thumb is; If performance matters so much, you
>> may need to re-consider writing your application in Java instead try C or
>> C++. Java meant to be high-level and code should be self explanatory and
>> maintainable[1]. Please refer "Null References: The Billion Dollar
>> Mistake" by T. Hoare[2].
>>
>> This is my two cents for NULLs ;)
>>
>> Choosing return NULL over Exceptions is a choice of writing *unreliable*
>> applications over bad-performance.
>>
>> Thanks,
>> Rasika
>>
>> [1] http://wolfie.github.io/2010/03/14/exceptional-heresy.html
>> [2]
>> https://www.infoq.com/presentations/Null-References-The-Billion-Dollar-Mistake-Tony-Hoare
>>
>> On Sun, Jul 17, 2016 at 5:58 PM, Udara Liyanage  wrote:
>>
>>>
>>>
>>> On Sun, Jul 17, 2016 at 2:53 PM, Nuwan Pallewela 
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> On Wed, Jul 13, 2016 at 10:15 AM, Sabra Ossen  wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> Thank you all for your prompt responses :)
>>>>>
>>>>> So if it's an ArrayList/Map it's better to return an empty object
>>>>> rather than null. Got it.
>>>>>
>>>>> Regarding a POJO object IMO the usage of null, empty object or
>>>>> exception depends on the scenario being considered.
>>>>>
>>>>> Based on Rasikas' reply since the jaggery level code is using the DAO
>>>>> method (via manager interface) basically if no user is found then the
>>>>> exception thrown should be propagated and in the UI an appropriate message
>>>>> is rendered. Also since anyone else could be using the back end, when an
>>>>> exception is thrown they would not have to be aware of the internal
>>>>> implementation (if null or an empty object is returned, specifically he
>>>>> should be aware if an empty object is returned so that he should write his
>>>>> front end code accordingly).
>>>>>
>>>>> IMO returning an exception is clearer in terms of code but I guess the
>>>>> discussion could continue further until a guideline is specified.
>>>>>
>>>> +1 for throw

Re: [Dev] [ESB] DataMapper issue

2016-07-18 Thread Nuwan Pallewela

Adding Sohani

On Tue, Jul 19, 2016 at 12:42 AM, Godwin Shrimal  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 *
> twitter: https://twitter.com/godwinamila
> 
>



-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *http://wso2.com
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739@*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV][ESB Tooling] Compare Operator behaviour for String Values

2016-07-21 Thread Nuwan Pallewela

Hi All,


On Thu, Jul 21, 2016 at 8:31 PM, Chanaka Fernando  wrote:

> Hi Erandi,
>
> Appreciate your feedback on improving the DM. The existing compare
> operator checks for the equality (==) of the values passed into the
> operator. If you passed in 2 String values, it will check the equality of
> strings. If it is integer values, it will check for the equality of integer
> values.
>
Compare operator have 8 different operations. They are,

   - equal value (two inputs are equal or not)
   - equal value type (two inputs are equal in both value and type)
   - not equal value (two inputs are not equal or not)
   - not equal value type (two inputs are not equal in both value and type)
   - greater than
   - greater than or equal
   - lower than
   - lower than or equal


> Are you talking about adding ">" (greater than) and "<" (less than) as new
> operators?
>
> Basically, you can do this kind of operations with a custom function.
>
> Please correct me If I understood your suggestion in a different manner.
>
> On Thu, Jul 21, 2016 at 4:51 PM, Chathurika De Silva  > wrote:
>
>> Hi
>>
>> Currently the data mapper compares (compare operator) String values for >
>> (greater than), < (less than). The native javascript too does the same
>> which is the underlining engine of data mapper.
>>
>> Since we are providing data mapper to the user to enhance conversion and
>> mapping, rather than a graphical UI for javascript itself, it would be
>> better if we should add UI (ESB tooling) validations for similar scenarios
>> as $subject.
>>
>
>> WDYT???
>>
>>
>> Best Regards
>> Erandi
>>
>> --
>> *Chathurika Erandi*
>> Senior Software Engineer,
>> WSO2 Inc.
>>
>> *E-mail:* chathuri...@wso2.com
>> *Mobile: *+94714 328 612
>> *Blog*: chathurikaerandi.blogspot.com
>>
>
>
>
> --
> Thank you and Best Regards,
> Chanaka Fernando
> Senior Technical Lead
> m: +94 773337238
> https://wso2.com 
>
>
>
>
>
>
>


-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *http://wso2.com
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739@*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV][ESB Tooling] Compare Operator behaviour for String Values

2016-07-21 Thread Nuwan Pallewela

Hi Chathurika,

We highly appreciate your suggestions to improve the data mapper. As you
said what we should provide as the data mapper is an enhanced mechanism for
data conversion which would be easy for user to do whatever s/he wants. So
I think we should provide those capabilities without blocking user from
using those provided in JavaScript. I believe your suggestions are mainly
came from the knowledge of JAVA and it's nature. But as we are based on JS
it would be misleading the users if we do not provide those functionalities
available in JS.
I do not think we should build a new standard to our data mapper. The
correct way should be moving with the JS standard as we are moving with JS
underline engine. Otherwise what we would be doing is building a mapping
based on JAVA/WSO2 standard using JavaScript language.

WDYT?

Thanks,
Nuwan

On Fri, Jul 22, 2016 at 9:33 AM, Nuwan Pallewela  wrote:

> Hi All,
>
>
> On Thu, Jul 21, 2016 at 8:31 PM, Chanaka Fernando 
> wrote:
>
>> Hi Erandi,
>>
>> Appreciate your feedback on improving the DM. The existing compare
>> operator checks for the equality (==) of the values passed into the
>> operator. If you passed in 2 String values, it will check the equality of
>> strings. If it is integer values, it will check for the equality of integer
>> values.
>>
> Compare operator have 8 different operations. They are,
>
>- equal value (two inputs are equal or not)
>- equal value type (two inputs are equal in both value and type)
>- not equal value (two inputs are not equal or not)
>- not equal value type (two inputs are not equal in both value and
>type)
>- greater than
>- greater than or equal
>- lower than
>- lower than or equal
>
>
>> Are you talking about adding ">" (greater than) and "<" (less than) as
>> new operators?
>>
>> Basically, you can do this kind of operations with a custom function.
>>
>> Please correct me If I understood your suggestion in a different manner.
>>
>> On Thu, Jul 21, 2016 at 4:51 PM, Chathurika De Silva <
>> chathuri...@wso2.com> wrote:
>>
>>> Hi
>>>
>>> Currently the data mapper compares (compare operator) String values for
>>> > (greater than), < (less than). The native javascript too does the same
>>> which is the underlining engine of data mapper.
>>>
>>> Since we are providing data mapper to the user to enhance conversion and
>>> mapping, rather than a graphical UI for javascript itself, it would be
>>> better if we should add UI (ESB tooling) validations for similar scenarios
>>> as $subject.
>>>
>>
>>> WDYT???
>>>
>>>
>>> Best Regards
>>> Erandi
>>>
>>> --
>>> *Chathurika Erandi*
>>> Senior Software Engineer,
>>> WSO2 Inc.
>>>
>>> *E-mail:* chathuri...@wso2.com
>>> *Mobile: *+94714 328 612
>>> *Blog*: chathurikaerandi.blogspot.com
>>>
>>
>>
>>
>> --
>> Thank you and Best Regards,
>> Chanaka Fernando
>> Senior Technical Lead
>> m: +94 773337238
>> https://wso2.com <https://wso2.com/signature>
>>
>>
>>
>>
>>
>>
>>
>
>
> --
> --
>
> *Nuwan Chamara Pallewela*
>
>
> *Software Engineer*
>
> *WSO2, Inc. *http://wso2.com
> *lean . enterprise . middleware*
>
> Email   *nuw...@wso2.com *
> Mobile  *+94719079739 <%2B94719079739>@*
>
>
>


-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *http://wso2.com
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739@*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV][ESB Tooling] Data mapper interprets multiplication of negative integers by zero results in signed zero

2016-07-22 Thread Nuwan Pallewela

Hi Chanaka,


On Fri, Jul 22, 2016 at 12:47 PM, Chanaka Fernando 
wrote:

> Hi Chathurika,
>
> We understand your point. But this is not a functional blocker. We will
> reduce the priority of this issue and as NuwanP mentioned in the ticket,
> this needs to be fixed from the JS engine level. If we are going to deal
> with that, it will reduce the performance of the entire data mapper and we
> cannot go down this path.
>
> @NuwanP: Please report a JIRA against the JS engine and reduce the
> priority of this issue and keep it opened.
>
Sure. I will do.

>
> Thanks,
> Chanaka
>
> On Fri, Jul 22, 2016 at 12:39 PM, Chathurika De Silva <
> chathuri...@wso2.com> wrote:
>
>> Hi
>>
>> Currently in data mapper, the multiplication of -2 * 0 results in -0.
>> Ideally in basic mathematics the value zero should not have any - or +
>> marking on it. I have reported [1] regarding this and according to jira's
>> comments if this is to be fixed the -0 should be converted to string and
>> then again to a number and it is shown as a concern there that this will
>> have a performance impact due to unnecessary operations.
>>
>> Signed zero itself is used for some mathematical operations[2]  but
>> seemingly there is no such operation that uses signed zero available in
>> data mapper currently. So rather than shipping signed zero, can we ship it
>> to adhere the basic mathematics (if there's no hidden usage of signed -0
>> that is) because first impression matters and first impression depends on
>> minor things like these as well.
>>
>> [1] https://wso2.org/jira/browse/DEVTOOLESB-627
>> [2] https://en.wikipedia.org/wiki/Signed_zero
>>
>> Best Regards
>> Erandi
>> --
>> *Chathurika Erandi*
>> Senior Software Engineer,
>> WSO2 Inc.
>>
>> *E-mail:* chathuri...@wso2.com
>> *Mobile: *+94714 328 612
>> *Blog*: chathurikaerandi.blogspot.com
>>
>
>
>
> --
> Thank you and Best Regards,
> Chanaka Fernando
> Senior Technical Lead
> m: +94 773337238
> https://wso2.com 
>
>
>
>
>
>
>
Thanks,
Nuwan

-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *http://wso2.com
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739@*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV][ESB Tooling] Improvement needed for operators that manipulates values using both input and configuration

2016-07-25 Thread Nuwan Pallewela

Hi Chathurika,

Yes. We have discussed it and going to do it[1]. We will provide a editable
drop down with the configuration need to provide to select the input and
operator description in the configure dialog about it.

[1] https://wso2.org/jira/browse/DEVTOOLESB-655

Thanks,
Nuwan

On Mon, Jul 25, 2016 at 4:36 PM, Chathurika De Silva 
wrote:

> Hi
>
> It was observed that the operators which manipulates values using both the
> configuration and the inputs always takes the configured value as the
> preceded one when both ways are present. According to the discussion in [1]
> the user has to keep the default values in the configuration as it is to
> make the values from the input to take precedence for the manipulation.
>
> In data mapper there are multiple operators that behave similarly and
> currently the user should be either knowledgable or find out by reading
> documentation which is an extra effort.
>
> In order to solve this, can we have an instruction wording in the operator
> it self, so that the user will know how to use it directly. Since this is a
> common improvement for most of the operators, it would be ideal if this is
> done for this release itself.
>
> WDYT?
>
> [1] https://wso2.org/jira/browse/DEVTOOLESB-643
>
> Thank you
> Erandi
>
> --
> *Chathurika Erandi*
> Senior Software Engineer,
> WSO2 Inc.
>
> *E-mail:* chathuri...@wso2.com
> *Mobile: *+94714 328 612
> *Blog*: chathurikaerandi.blogspot.com
>



-- 
--

*Nuwan Chamara Pallewela*


*Software Engineer*

*WSO2, Inc. *http://wso2.com
*lean . enterprise . middleware*

Email   *nuw...@wso2.com *
Mobile  *+94719079739@*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

1 2 >

1 - 100 of 112 matches

Mail list logo