[Dev] WSO2 Committers += Praminda Jayawardana

[Janaka Ranabahu]

Hi,

It is with great pleasure we welcome Praminda Jayawardana as a
WSO2 Committer. Congratulations Praminda and keep up the good work!

​Thanks,
Janaka​

-- 
*Janaka Ranabahu*
Associate Technical Lead, WSO2 Inc.
http://wso2.com


*E-mail: jan...@wso2.com **M: **+94 718370861*

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

Re: [Dev] [DAS]Abnormal behavior of data after purging a table

[Nirmal Fernando]

Great work ! :)

On Tue, Mar 29, 2016 at 11:06 AM, Sachith Withana  wrote:

> Hi all,
>
> This happened due to the tmp folder getting deleted when running the
> backup tool.
> This is fixed now.
>
> Thanks,
> Sachith
>
> On Wed, Mar 23, 2016 at 11:40 AM, Sachith Withana 
> wrote:
>
>> Nirmal: I'm looking into this.
>>
>> On Wed, Mar 23, 2016 at 11:20 AM, Nirmal Fernando 
>> wrote:
>>
>>> Hi, Anyone looking into this?
>>>
>>> On Mon, Mar 21, 2016 at 11:23 AM, Nirmal Fernando 
>>> wrote:
>>>
 Hi All,

 Any thoughts on this? This seems to be a L1.

 On Fri, Mar 18, 2016 at 3:27 PM, Sachith Withana 
 wrote:

> [+Gimantha]
>
> On Fri, Mar 18, 2016 at 3:26 PM, Sachith Withana 
> wrote:
>
>> Hi all,
>>
>> We reproduced the issue, but if we take out the spark script step, it
>> works fine.
>> (by using the simulator to get the data in to the table).
>>
>> @Niranda:
>> Any thoughts on why this might be happening?
>>
>> Thanks,
>> Sachith
>>
>> On Fri, Mar 18, 2016 at 2:28 PM, Vithulan Vijayanandan <
>> vithu...@wso2.com> wrote:
>>
>>> Hi,
>>>
>>> We are encountering an abnormal behavior of data after purging DAS
>>> table using analytics backup tool kit [1], -purge command.
>>>
>>> To reproduce this issue,
>>>
>>>1. Generate a table (x) from spark script using y table.
>>>2. Purge all the data in x using analytics backup tool command
>>>-purge.
>>>3. Re-populate the table x as in 1.
>>>4. Send events to stream y (Execution plan will refer to table x
>>>when you send events to y)
>>>5. Now if you see the table x, it will be empty.
>>>
>>> [1] https://docs.wso2.com/pages/viewpage.action?pageId=45957285
>>>
>>> Thanks.
>>>
>>> Regards,
>>> Vithulan.
>>> --
>>> *Vithulan MV*
>>>
>>> Intern-Software Engineering
>>> WSO2, Inc : wso2.com
>>> Mobile: +94712540524
>>>
>>
>>
>>
>> --
>> Sachith Withana
>> Software Engineer; WSO2 Inc.; http://wso2.com
>> E-mail: sachith AT wso2.com
>> M: +94715518127
>> Linked-In: 
>> https://lk.linkedin.com/in/sachithwithana
>>
>
>
>
> --
> Sachith Withana
> Software Engineer; WSO2 Inc.; http://wso2.com
> E-mail: sachith AT wso2.com
> M: +94715518127
> Linked-In: 
> https://lk.linkedin.com/in/sachithwithana
>



 --

 Thanks & regards,
 Nirmal

 Team Lead - WSO2 Machine Learner
 Associate Technical Lead - Data Technologies Team, WSO2 Inc.
 Mobile: +94715779733
 Blog: http://nirmalfdo.blogspot.com/



>>>
>>>
>>> --
>>>
>>> Thanks & regards,
>>> Nirmal
>>>
>>> Team Lead - WSO2 Machine Learner
>>> Associate Technical Lead - Data Technologies Team, WSO2 Inc.
>>> Mobile: +94715779733
>>> Blog: http://nirmalfdo.blogspot.com/
>>>
>>>
>>>
>>
>>
>> --
>> Sachith Withana
>> Software Engineer; WSO2 Inc.; http://wso2.com
>> E-mail: sachith AT wso2.com
>> M: +94715518127
>> Linked-In: 
>> https://lk.linkedin.com/in/sachithwithana
>>
>
>
>
> --
> Sachith Withana
> Software Engineer; WSO2 Inc.; http://wso2.com
> E-mail: sachith AT wso2.com
> M: +94715518127
> Linked-In: 
> https://lk.linkedin.com/in/sachithwithana
>



-- 

Thanks & regards,
Nirmal

Team Lead - WSO2 Machine Learner
Associate Technical Lead - Data Technologies Team, WSO2 Inc.
Mobile: +94715779733
Blog: http://nirmalfdo.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] How to create database tables with -Dsetup in Carbon 5?

[Isuru Perera]

Hi Aruna,

I think this feature will be important for other products as most of the
products will eventually need to create the database schema based on the
database vendor.

I hope MB team will also need this feature soon and it would be good if
this feature can be supported in next platform release.

Thanks!

On Fri, Mar 25, 2016 at 2:03 PM, Aruna Karunarathna  wrote:

>
>
> On Fri, Mar 25, 2016 at 1:45 PM, Isuru Perera  wrote:
>
>> Hi,
>>
>> In Carbon 4.x.x, we extend [1]
>> org.wso2.carbon.utils.dbcreator.DatabaseCreator [2]. How can we do the same
>> in Carbon 5?
>>
>
> Hi Isuru,
>
> There is no such feature planned or available ATM for hamming platform
> release.
> Regards,
> Aruna
>
>>
>> Thanks!
>>
>> [1]
>> https://github.com/search?l==DatabaseCreator++user%3Awso2=advsearch=Code=%E2%9C%93
>> [2]
>> https://github.com/wso2/carbon-kernel/blob/4.4.x/core/org.wso2.carbon.utils/src/main/java/org/wso2/carbon/utils/dbcreator/DatabaseCreator.java
>>
>> --
>> Isuru Perera
>> Associate Technical Lead | WSO2, Inc. | http://wso2.com/
>> Lean . Enterprise . Middleware
>>
>> about.me/chrishantha
>> Contact: +IsuruPereraWSO2 
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
>
> *Aruna Sujith Karunarathna *
> WSO2, Inc | lean. enterprise. middleware.
> #20, Palm Grove, Colombo 03, Sri Lanka
> Mobile: +94 71 9040362 | Work: +94 112145345
> Email: ar...@wso2.com | Web: www.wso2.com
>
>



-- 
Isuru Perera
Associate Technical Lead | WSO2, Inc. | http://wso2.com/
Lean . Enterprise . Middleware

about.me/chrishantha
Contact: +IsuruPereraWSO2 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DAS]Abnormal behavior of data after purging a table

[Sachith Withana]

Hi all,

This happened due to the tmp folder getting deleted when running the backup
tool.
This is fixed now.

Thanks,
Sachith

On Wed, Mar 23, 2016 at 11:40 AM, Sachith Withana  wrote:

> Nirmal: I'm looking into this.
>
> On Wed, Mar 23, 2016 at 11:20 AM, Nirmal Fernando  wrote:
>
>> Hi, Anyone looking into this?
>>
>> On Mon, Mar 21, 2016 at 11:23 AM, Nirmal Fernando 
>> wrote:
>>
>>> Hi All,
>>>
>>> Any thoughts on this? This seems to be a L1.
>>>
>>> On Fri, Mar 18, 2016 at 3:27 PM, Sachith Withana 
>>> wrote:
>>>
 [+Gimantha]

 On Fri, Mar 18, 2016 at 3:26 PM, Sachith Withana 
 wrote:

> Hi all,
>
> We reproduced the issue, but if we take out the spark script step, it
> works fine.
> (by using the simulator to get the data in to the table).
>
> @Niranda:
> Any thoughts on why this might be happening?
>
> Thanks,
> Sachith
>
> On Fri, Mar 18, 2016 at 2:28 PM, Vithulan Vijayanandan <
> vithu...@wso2.com> wrote:
>
>> Hi,
>>
>> We are encountering an abnormal behavior of data after purging DAS
>> table using analytics backup tool kit [1], -purge command.
>>
>> To reproduce this issue,
>>
>>1. Generate a table (x) from spark script using y table.
>>2. Purge all the data in x using analytics backup tool command
>>-purge.
>>3. Re-populate the table x as in 1.
>>4. Send events to stream y (Execution plan will refer to table x
>>when you send events to y)
>>5. Now if you see the table x, it will be empty.
>>
>> [1] https://docs.wso2.com/pages/viewpage.action?pageId=45957285
>>
>> Thanks.
>>
>> Regards,
>> Vithulan.
>> --
>> *Vithulan MV*
>>
>> Intern-Software Engineering
>> WSO2, Inc : wso2.com
>> Mobile: +94712540524
>>
>
>
>
> --
> Sachith Withana
> Software Engineer; WSO2 Inc.; http://wso2.com
> E-mail: sachith AT wso2.com
> M: +94715518127
> Linked-In: 
> https://lk.linkedin.com/in/sachithwithana
>



 --
 Sachith Withana
 Software Engineer; WSO2 Inc.; http://wso2.com
 E-mail: sachith AT wso2.com
 M: +94715518127
 Linked-In: 
 https://lk.linkedin.com/in/sachithwithana

>>>
>>>
>>>
>>> --
>>>
>>> Thanks & regards,
>>> Nirmal
>>>
>>> Team Lead - WSO2 Machine Learner
>>> Associate Technical Lead - Data Technologies Team, WSO2 Inc.
>>> Mobile: +94715779733
>>> Blog: http://nirmalfdo.blogspot.com/
>>>
>>>
>>>
>>
>>
>> --
>>
>> Thanks & regards,
>> Nirmal
>>
>> Team Lead - WSO2 Machine Learner
>> Associate Technical Lead - Data Technologies Team, WSO2 Inc.
>> Mobile: +94715779733
>> Blog: http://nirmalfdo.blogspot.com/
>>
>>
>>
>
>
> --
> Sachith Withana
> Software Engineer; WSO2 Inc.; http://wso2.com
> E-mail: sachith AT wso2.com
> M: +94715518127
> Linked-In: 
> https://lk.linkedin.com/in/sachithwithana
>



-- 
Sachith Withana
Software Engineer; WSO2 Inc.; http://wso2.com
E-mail: sachith AT wso2.com
M: +94715518127
Linked-In: https://lk.linkedin.com/in/sachithwithana
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] XML attribute representation of JSON Schema

[Sohani Weerasinghe]

Thanks Maheeka for the response

Regards,
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, Mar 29, 2016 at 9:44 AM, Maheeka Jayasuriya 
wrote:

> Hi Sohani,
>
> As per previous discussion, instead of properties array with attributes
> supported with @ prefix, we use an attributes array in the schema.
>
> For example :
>
> Current definition :
>
> "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"
>   }
> }
>   }
>
> With attributes array :
>
> "address": {
> "id": "http://jsonschema.net/employee/0/address;,
> "type": "object",
> "attributes": {
> "no": {
> "id": "http://jsonschema.net/employee/0/address/no;,
>  "type": "string"
> }
> },
> "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)
>
>
> Thanks,
> Maheeka
>
> Maheeka Jayasuriya
> Software Engineer
> Mobile : +9450661
>
> On Tue, Mar 29, 2016 at 8:41 AM, Sohani Weerasinghe 
> wrote:
>
>> Hi All,
>>
>> Currently we are representing the attributes using @prefix in JSON
>> Schema. Can someone please specify the expected representation using the
>> "attributes" field.
>>
>> Thanks,
>> Sohani
>> Sohani Weerasinghe
>> Software Engineer
>> WSO2, Inc: http://wso2.com
>>
>> Mobile  : +94 716439774
>> Blog :http://christinetechtips.blogspot.com/
>> Twitter  : https://twitter.com/sohanichristine
>>
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [BPS] Error when passing parameters to a SOAP operation with Apache CXF

[Hasitha Aravinda]

Yes, IMO this approach is very complicated and we will face more
issues when we are going to integrate with WebService Task. Can you have a
look at [1] and try that ?

​[1] -
http://stackoverflow.com/questions/6849892/whats-a-good-java-library-for-dynamic-soap-client-operations
​

Thanks,
Hasitha.

On Mon, Mar 28, 2016 at 12:07 PM, Natasha Wijesekara 
wrote:

>  Hi,
>
> There are many complexities when trying to implement a SOAP client using
> the dynamic client capability of Apache CXF. I was able to provide a
> workaround for the error which occurred when passing parameters to a SOAP
> operation with Apache CXF .
>
> The workaround provided does not work with WSDLs which have complex types
> as the request or response message type  i.e. the request/response message
> parts of the WSDL can be primitive or complex, so 2 different approaches
> should be followed to get/set the values of the primitive and complex types
> respectively. When having complex types, the message part is iterated over
> multiple times, which will take more processing time and reduce the
> performance.
>
> The approach I used is described below. By using this approach the
> JaxWsDynamicClientFactory takes care of generating Java classes for complex
> types :
>
> Create a new instance of the Client using the JaxWsDynamicClientFactory by
> passing the wsdl url. The url of the WSDL, operation name and the input
> variables is provided by the user.
>
>
>
>
>
> *JaxWsDynamicClientFactory factory =
> JaxWsDynamicClientFactory.newInstance();URL wsdlURL = new
> URL("http://localhost:9763/services/DivisionProcessService?wsdl
> ");String
> operationName = "process";Client client =
> factory.createClient(wsdlURL.toExternalForm());ClientImpl clientImpl =
> (ClientImpl) client;*
>
> Get the endpoint i.e. the URL where the web service can be accessed by a
> client application using the cilent.
>
> *Endpoint endpoint = clientImpl.getEndpoint();*
>
> Get the target namespace of the WSDL by creating a ServiceInfo object
> which walks over the CXF service model
>
> *ServiceInfo serviceInfo = endpoint.getService().getServiceInfos().get(0);*
> *String targetNameSpace = serviceInfo.getTargetNamespace();*
>
> Get the binding name of the WSDL by creating a BindingInfo object which
> gets the name of the binding.
>
> *BindingInfo bindingInfo = serviceInfo.getBindings().iterator().next();*
> *String bName = bindingInfo.getName().getLocalPart();*
>
> Create a Qname by passing the namespace and the binding name as parameters
> and get the binding which has the specified QName.
>
> *QName bindingName = new QName(targetNameSpace, bName);*
> *BindingInfo binding = serviceInfo.getBinding(bindingName);*
>
> Get details about the soap operation which is to be invoked by creating a
> QName with the namespace and the operation name.
>
> *QName opName = new QName(targetNameSpace, operationName);*
> *BindingOperationInfo boi = binding.getOperation(opName);*
>
> Get the input/request message type
> *BindingMessageInfo inputMessageInfo = boi.getInput();*
> *List parts = inputMessageInfo.getMessageParts();*
> *MessagePartInfo partInfo = parts.get(0);*
>
> Get the  class type of the request/input message and dynamically create an
> instance of it
> *Class partClass = partInfo.getTypeClass();*
> *Object obj = partClass.newInstance();*
>
> The input variables provided by the user is stored inside a  HashTable
> which will hold the variable name and its value as a key-value pair
>
> *Hashtable table = new Hashtable();*
> *table.put("dividend", 40);*
> *table.put("divisor", 10);*
>
> Get the methods from the generated request class. This class will have
> getter and setter methods for the variables taken as the input/request.
>
> *Method [] methods = obj.getClass().getDeclaredMethods();*
> *for(Method m : methods){*
> * if(m.getName().contains("set")){*
> * String methodName = m.getName(); *
> * Class paramType = m.getParameterTypes()[0];*
> * String[] output = methodName.split("set");*
> * String varName = output[1].toLowerCase(); *
> * Object value = table.get(varName); *
> * Method m1 = obj.getClass().getMethod(methodName, paramType); *
> * m1.invoke(obj, value);*
> * } else {*
> * }*
> *}*
>
> Invoking the operation
> *Object[] response = client.invoke(operationName, obj);*
>
> Get the methods from the generated response class. This class will have getter
> and setter methods for the variables given as the output.
>
> *Method [] responseMethods = response[0].getClass().getDeclaredMethods();*
> *for(Method rm : responseMethods){*
> * if(rm.getName().contains("get")){*
> * String responseMethod = rm.getName();*
> * Object result =
> response[0].getClass().getMethod(responseMethod).invoke(response[0]);*
> * System.**out**.println("Response: " + result);*
> * } else {*
> * }*
> *}*
>
> Is this approach correct or is there any way to overcome these limitations
> when using CXF ?
>
> Any 

[Dev] Is it possible to store a custom file in the P2 repo and read it via eclipse?

[Awanthika Senarath]

Hi all,


In order to modify the developer studio updater tool and prevent it from
searching through the whole P2 repo for updates, we need to introduce a
meta file to the p2 repo and get eclipse to read that file to identify
possible updates to be installed.


Is it possible to get the eclipse P2 reader to read a custom file from P2
repo? if not we have to download the custom meta deta file from the P2 repo
or any other storage location and read it prior to running the developer
studio updater tool


@ Kavith : Any thoughts on this?


Regards
Awanthika Senarath
Software Engineer, WSO2 Inc.
Mobile: +94717681791
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] XML attribute representation of JSON Schema

[Maheeka Jayasuriya]

Hi Sohani,

As per previous discussion, instead of properties array with attributes
supported with @ prefix, we use an attributes array in the schema.

For example :

Current definition :

"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"
  }
}
  }

With attributes array :

"address": {
"id": "http://jsonschema.net/employee/0/address;,
"type": "object",
"attributes": {
"no": {
"id": "http://jsonschema.net/employee/0/address/no;,
 "type": "string"
}
},
"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)


Thanks,
Maheeka

Maheeka Jayasuriya
Software Engineer
Mobile : +9450661

On Tue, Mar 29, 2016 at 8:41 AM, Sohani Weerasinghe  wrote:

> Hi All,
>
> Currently we are representing the attributes using @prefix in JSON Schema.
> Can someone please specify the expected representation using the
> "attributes" field.
>
> Thanks,
> Sohani
> Sohani Weerasinghe
> Software Engineer
> WSO2, Inc: http://wso2.com
>
> Mobile  : +94 716439774
> Blog :http://christinetechtips.blogspot.com/
> Twitter  : https://twitter.com/sohanichristine
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Typo in "Deployment Synchronizer" section in carbon.xml file

[Thusitha Thilina Dayaratne]

Hi All,

JIRA link should be [1]
[1] - https://wso2.org/jira/browse/CARBON-15832

Thanks

On Tue, Mar 29, 2016 at 9:17 AM, Thusitha Thilina Dayaratne <
thusit...@wso2.com> wrote:

> Hi Niranjan,
>
> I already fixed the typo and created the JIRA[1] for registry based
> depsync config
> [1] - https://wso2.org/jira/browse/CARBON-15831
>
> Thanks
>
> On Tue, Mar 29, 2016 at 8:52 AM, Niranjan Karunanandham  > wrote:
>
>> Hi Thusitha,
>>
>> Will you be able to create Carbon JIRAs for this please?
>>
>> Regards,
>> Nira
>>
>> On Tue, Mar 29, 2016 at 6:57 AM, Thusitha Thilina Dayaratne <
>> thusit...@wso2.com> wrote:
>>
>>> Hi Johann,
>>>
>>> Also there seems to be two DeploymentSynchronizer tags, one for svn and
 one for registry. Do we have the registry based one now ? and how do you
 identify the different configuratino tags ?
>>>
>>> AFAIK Registry based depsync functinality is also no longer being used
>>> with newer products (from 4.2.0 onwards)[1] Therefore I think we can remove
>>> that config section as well. Will update that as well.
>>>
>>> [1] -
>>> https://docs.wso2.com/display/CLUSTER420/Configuring+Deployment+Synchronizer
>>>
>>> Thanks
>>>
>>> On Tue, Mar 29, 2016 at 6:50 AM, Thusitha Thilina Dayaratne <
>>> thusit...@wso2.com> wrote:
>>>
 Hi Johann,

 Typo is being fix with the PR
 https://github.com/wso2/carbon-kernel/pull/899

 Thanks

 On Mon, Mar 28, 2016 at 10:31 PM, Johann Nallathamby 
 wrote:

> Kernel Team,
>
> Why was there no reply for this mail? It seems this issue is still not
> fixed in latest kernel 4.4.x. Please fix this for next patch release.
>
> Also there seems to be two DeploymentSynchronizer tags, one for svn
> and one for registry. Do we have the registry based one now ? and how do
> you identify the different configuratino tags ?
>
> Thanks.
>
> On Wed, Nov 11, 2015 at 6:48 AM, Malintha Adikari 
> wrote:
>
>> Hi,
>>
>> There is a typo[1] in $subject. Found this in APIM 1.10.x pack.
>>
>>  [1]  
>>
>> Regards,
>> Malintha
>> --
>> *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
>>
>>
>
>
> --
> Thanks & Regards,
>
> *Johann Dilantha Nallathamby*
> Technical Lead & Product Lead of WSO2 Identity Server
> Governance Technologies Team
> WSO2, Inc.
> lean.enterprise.middleware
>
> Mobile - *+9476950*
> Blog - *http://nallaa.wordpress.com *
>



 --
 Thusitha Dayaratne
 Software Engineer
 WSO2 Inc. - lean . enterprise . middleware |  wso2.com

 Mobile  +94712756809
 Blog  alokayasoya.blogspot.com
 Abouthttp://about.me/thusithathilina


>>>
>>>
>>> --
>>> Thusitha Dayaratne
>>> Software Engineer
>>> WSO2 Inc. - lean . enterprise . middleware |  wso2.com
>>>
>>> Mobile  +94712756809
>>> Blog  alokayasoya.blogspot.com
>>> Abouthttp://about.me/thusithathilina
>>>
>>>
>>
>>
>> --
>>
>> *Niranjan Karunanandham*
>> Senior Software Engineer - WSO2 Inc.
>> WSO2 Inc.: http://www.wso2.com
>>
>
>
>
> --
> Thusitha Dayaratne
> Software Engineer
> WSO2 Inc. - lean . enterprise . middleware |  wso2.com
>
> Mobile  +94712756809
> Blog  alokayasoya.blogspot.com
> Abouthttp://about.me/thusithathilina
>
>


-- 
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

Re: [Dev] Typo in "Deployment Synchronizer" section in carbon.xml file

[Thusitha Thilina Dayaratne]

Hi Niranjan,

I already fixed the typo and created the JIRA[1] for registry based depsync
config
[1] - https://wso2.org/jira/browse/CARBON-15831

Thanks

On Tue, Mar 29, 2016 at 8:52 AM, Niranjan Karunanandham 
wrote:

> Hi Thusitha,
>
> Will you be able to create Carbon JIRAs for this please?
>
> Regards,
> Nira
>
> On Tue, Mar 29, 2016 at 6:57 AM, Thusitha Thilina Dayaratne <
> thusit...@wso2.com> wrote:
>
>> Hi Johann,
>>
>> Also there seems to be two DeploymentSynchronizer tags, one for svn and
>>> one for registry. Do we have the registry based one now ? and how do you
>>> identify the different configuratino tags ?
>>
>> AFAIK Registry based depsync functinality is also no longer being used
>> with newer products (from 4.2.0 onwards)[1] Therefore I think we can remove
>> that config section as well. Will update that as well.
>>
>> [1] -
>> https://docs.wso2.com/display/CLUSTER420/Configuring+Deployment+Synchronizer
>>
>> Thanks
>>
>> On Tue, Mar 29, 2016 at 6:50 AM, Thusitha Thilina Dayaratne <
>> thusit...@wso2.com> wrote:
>>
>>> Hi Johann,
>>>
>>> Typo is being fix with the PR
>>> https://github.com/wso2/carbon-kernel/pull/899
>>>
>>> Thanks
>>>
>>> On Mon, Mar 28, 2016 at 10:31 PM, Johann Nallathamby 
>>> wrote:
>>>
 Kernel Team,

 Why was there no reply for this mail? It seems this issue is still not
 fixed in latest kernel 4.4.x. Please fix this for next patch release.

 Also there seems to be two DeploymentSynchronizer tags, one for svn and
 one for registry. Do we have the registry based one now ? and how do you
 identify the different configuratino tags ?

 Thanks.

 On Wed, Nov 11, 2015 at 6:48 AM, Malintha Adikari 
 wrote:

> Hi,
>
> There is a typo[1] in $subject. Found this in APIM 1.10.x pack.
>
>  [1]  
>
> Regards,
> Malintha
> --
> *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
>
>


 --
 Thanks & Regards,

 *Johann Dilantha Nallathamby*
 Technical Lead & Product Lead of WSO2 Identity Server
 Governance Technologies Team
 WSO2, Inc.
 lean.enterprise.middleware

 Mobile - *+9476950*
 Blog - *http://nallaa.wordpress.com *

>>>
>>>
>>>
>>> --
>>> Thusitha Dayaratne
>>> Software Engineer
>>> WSO2 Inc. - lean . enterprise . middleware |  wso2.com
>>>
>>> Mobile  +94712756809
>>> Blog  alokayasoya.blogspot.com
>>> Abouthttp://about.me/thusithathilina
>>>
>>>
>>
>>
>> --
>> Thusitha Dayaratne
>> Software Engineer
>> WSO2 Inc. - lean . enterprise . middleware |  wso2.com
>>
>> Mobile  +94712756809
>> Blog  alokayasoya.blogspot.com
>> Abouthttp://about.me/thusithathilina
>>
>>
>
>
> --
>
> *Niranjan Karunanandham*
> Senior Software Engineer - WSO2 Inc.
> WSO2 Inc.: http://www.wso2.com
>



-- 
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

Re: [Dev] Typo in "Deployment Synchronizer" section in carbon.xml file

[Niranjan Karunanandham]

Hi Thusitha,

Will you be able to create Carbon JIRAs for this please?

Regards,
Nira

On Tue, Mar 29, 2016 at 6:57 AM, Thusitha Thilina Dayaratne <
thusit...@wso2.com> wrote:

> Hi Johann,
>
> Also there seems to be two DeploymentSynchronizer tags, one for svn and
>> one for registry. Do we have the registry based one now ? and how do you
>> identify the different configuratino tags ?
>
> AFAIK Registry based depsync functinality is also no longer being used
> with newer products (from 4.2.0 onwards)[1] Therefore I think we can remove
> that config section as well. Will update that as well.
>
> [1] -
> https://docs.wso2.com/display/CLUSTER420/Configuring+Deployment+Synchronizer
>
> Thanks
>
> On Tue, Mar 29, 2016 at 6:50 AM, Thusitha Thilina Dayaratne <
> thusit...@wso2.com> wrote:
>
>> Hi Johann,
>>
>> Typo is being fix with the PR
>> https://github.com/wso2/carbon-kernel/pull/899
>>
>> Thanks
>>
>> On Mon, Mar 28, 2016 at 10:31 PM, Johann Nallathamby 
>> wrote:
>>
>>> Kernel Team,
>>>
>>> Why was there no reply for this mail? It seems this issue is still not
>>> fixed in latest kernel 4.4.x. Please fix this for next patch release.
>>>
>>> Also there seems to be two DeploymentSynchronizer tags, one for svn and
>>> one for registry. Do we have the registry based one now ? and how do you
>>> identify the different configuratino tags ?
>>>
>>> Thanks.
>>>
>>> On Wed, Nov 11, 2015 at 6:48 AM, Malintha Adikari 
>>> wrote:
>>>
 Hi,

 There is a typo[1] in $subject. Found this in APIM 1.10.x pack.

  [1]  

 Regards,
 Malintha
 --
 *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


>>>
>>>
>>> --
>>> Thanks & Regards,
>>>
>>> *Johann Dilantha Nallathamby*
>>> Technical Lead & Product Lead of WSO2 Identity Server
>>> Governance Technologies Team
>>> WSO2, Inc.
>>> lean.enterprise.middleware
>>>
>>> Mobile - *+9476950*
>>> Blog - *http://nallaa.wordpress.com *
>>>
>>
>>
>>
>> --
>> Thusitha Dayaratne
>> Software Engineer
>> WSO2 Inc. - lean . enterprise . middleware |  wso2.com
>>
>> Mobile  +94712756809
>> Blog  alokayasoya.blogspot.com
>> Abouthttp://about.me/thusithathilina
>>
>>
>
>
> --
> Thusitha Dayaratne
> Software Engineer
> WSO2 Inc. - lean . enterprise . middleware |  wso2.com
>
> Mobile  +94712756809
> Blog  alokayasoya.blogspot.com
> Abouthttp://about.me/thusithathilina
>
>


-- 

*Niranjan Karunanandham*
Senior Software Engineer - WSO2 Inc.
WSO2 Inc.: http://www.wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] XML attribute representation of JSON Schema

[Sohani Weerasinghe]

Hi All,

Currently we are representing the attributes using @prefix in JSON Schema.
Can someone please specify the expected representation using the
"attributes" field.

Thanks,
Sohani
Sohani Weerasinghe
Software Engineer
WSO2, Inc: http://wso2.com

Mobile  : +94 716439774
Blog :http://christinetechtips.blogspot.com/
Twitter  : https://twitter.com/sohanichristine
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] WSO2 API Manager 2.0.0-M1 Released!

[Bhathiya Jayasekara]

*WSO2 API Manager 2.0.0-M1 Released!*

WSO2 API Manager team is pleased to announce WSO2 API Manager 2.0.0 -M1
release. Download distribution here
.
This release contains following bug fixes, improvements, new features and
tasks.
Bug Fixes

   - [APIMANAGER-1337 ] - [MT
   mode] Continuous error when deployment synchronizer is enabled
   - [APIMANAGER-1674 ] -
   Re-generate Key from UI should remove from KeyManager Cached Key for
   consistency
   - [APIMANAGER-1784 ] -
   Eventhough the server is restarted, an old app name will be printed in JWT
   caching
   - [APIMANAGER-2375 ] -
   Resource not found exception when tenant getting loaded on gateway node
   - [APIMANAGER-2408 ] -
   when registry path is there as wsdl url test option will not work.
   - [APIMANAGER-2420 ] -
   Subscription related usability issue
   - [APIMANAGER-2496 ] -
   Http 500 error page after creating a new topic in the forum, in tenant mode
   - [APIMANAGER-2624 ] -
   Issue with forum display on firefox [Intermittent]
   - [APIMANAGER-2636 ] -
   Inconsistency in API Manager consent page - Deny action
   - [APIMANAGER-2749 ] -
   Logging in with email from profile attribute - email is not supported
   - [APIMANAGER-2842 ] - if
   two publishers are updating the same API then the user who deletes a scope
   record may see that record still existing
   - [APIMANAGER-2859 ] -
   Foceful shutdown throws exceptions
   - [APIMANAGER-2869 ] -
   Issue with Store loading when email based SSO log in is enabled
   - [APIMANAGER-2974 ] -
   WorkFlows: Multiple Tasks are created for the same production application
   registration and sanbox application registration
   - [APIMANAGER-2994 ] -
   Workflows: The user is granted access eventhough the wrong task is approved
   - [APIMANAGER-3156 ] - UI
   issues in Publisher
   - [APIMANAGER-3210 ] -
   Issue in the Access Token 'Copy to clipboard' function
   - [APIMANAGER-3365 ] -
   OAuth Cache is not invalidated when an application is deleted
   - [APIMANAGER-3372 ] - I/O
   operations in a synchronized block
   - [APIMANAGER-3463 ] - API
   Publisher page loading time highly increase with no of APIs incresed
   - [APIMANAGER-3549 ] -
   When update the original application tier it allows one request addition to
   the throttling limit in APIM 1.9.0 SNAPSHOT
   - [APIMANAGER-3659 ] -
   Throttling not replicated correctly on Gateway cluster for tenant APIs
   - [APIMANAGER-3756 ] -
   Inline JavaScript is failing when the last line is a comment
   - [APIMANAGER-4082 ] -
   enableJWTassertion creates extra 'assertion' header in API requests
   - [APIMANAGER-4118 ] -
   Renaming an application using the store API seems to mess up subscriptions
   page in store
   - [APIMANAGER-4126 ] -
   Reverse Proxy with Tenants on Carbon
   - [APIMANAGER-4292 ] -
   Issues occur when resources have & or 
   - [APIMANAGER-4297 ] -
   Remove key manager issue due to connection issue to thrift server
   - [APIMANAGER-4306 ] -
   Admin-dashboard allowed role name for default admin role is hard coded
   - [APIMANAGER-4317 ] -
   Error while generating keys for a new application [Intermittent]
   - [APIMANAGER-4341 ] -
   [Tenant mode]Number of concurrent requests exceeds the application
   throttling limit in large scale when a hard throttling limit has enabled
   and the hard throttling limit > application throttling limit
   - [APIMANAGER-4448 ] -
   Editing an API with an inline 

Re: [Dev] Typo in "Deployment Synchronizer" section in carbon.xml file

[Thusitha Thilina Dayaratne]

Hi Johann,

Also there seems to be two DeploymentSynchronizer tags, one for svn and one
> for registry. Do we have the registry based one now ? and how do you
> identify the different configuratino tags ?

AFAIK Registry based depsync functinality is also no longer being used with
newer products (from 4.2.0 onwards)[1] Therefore I think we can remove that
config section as well. Will update that as well.

[1] -
https://docs.wso2.com/display/CLUSTER420/Configuring+Deployment+Synchronizer

Thanks

On Tue, Mar 29, 2016 at 6:50 AM, Thusitha Thilina Dayaratne <
thusit...@wso2.com> wrote:

> Hi Johann,
>
> Typo is being fix with the PR
> https://github.com/wso2/carbon-kernel/pull/899
>
> Thanks
>
> On Mon, Mar 28, 2016 at 10:31 PM, Johann Nallathamby 
> wrote:
>
>> Kernel Team,
>>
>> Why was there no reply for this mail? It seems this issue is still not
>> fixed in latest kernel 4.4.x. Please fix this for next patch release.
>>
>> Also there seems to be two DeploymentSynchronizer tags, one for svn and
>> one for registry. Do we have the registry based one now ? and how do you
>> identify the different configuratino tags ?
>>
>> Thanks.
>>
>> On Wed, Nov 11, 2015 at 6:48 AM, Malintha Adikari 
>> wrote:
>>
>>> Hi,
>>>
>>> There is a typo[1] in $subject. Found this in APIM 1.10.x pack.
>>>
>>>  [1]  
>>>
>>> Regards,
>>> Malintha
>>> --
>>> *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
>>>
>>>
>>
>>
>> --
>> Thanks & Regards,
>>
>> *Johann Dilantha Nallathamby*
>> Technical Lead & Product Lead of WSO2 Identity Server
>> Governance Technologies Team
>> WSO2, Inc.
>> lean.enterprise.middleware
>>
>> Mobile - *+9476950*
>> Blog - *http://nallaa.wordpress.com *
>>
>
>
>
> --
> Thusitha Dayaratne
> Software Engineer
> WSO2 Inc. - lean . enterprise . middleware |  wso2.com
>
> Mobile  +94712756809
> Blog  alokayasoya.blogspot.com
> Abouthttp://about.me/thusithathilina
>
>


-- 
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

Re: [Dev] Typo in "Deployment Synchronizer" section in carbon.xml file

[Thusitha Thilina Dayaratne]

Hi Johann,

Typo is being fix with the PR https://github.com/wso2/carbon-kernel/pull/899

Thanks

On Mon, Mar 28, 2016 at 10:31 PM, Johann Nallathamby 
wrote:

> Kernel Team,
>
> Why was there no reply for this mail? It seems this issue is still not
> fixed in latest kernel 4.4.x. Please fix this for next patch release.
>
> Also there seems to be two DeploymentSynchronizer tags, one for svn and
> one for registry. Do we have the registry based one now ? and how do you
> identify the different configuratino tags ?
>
> Thanks.
>
> On Wed, Nov 11, 2015 at 6:48 AM, Malintha Adikari 
> wrote:
>
>> Hi,
>>
>> There is a typo[1] in $subject. Found this in APIM 1.10.x pack.
>>
>>  [1]  
>>
>> Regards,
>> Malintha
>> --
>> *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
>>
>>
>
>
> --
> Thanks & Regards,
>
> *Johann Dilantha Nallathamby*
> Technical Lead & Product Lead of WSO2 Identity Server
> Governance Technologies Team
> WSO2, Inc.
> lean.enterprise.middleware
>
> Mobile - *+9476950*
> Blog - *http://nallaa.wordpress.com *
>



-- 
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

Re: [Dev] wso2emm enroll agent problem

[Dilshan Edirisuriya]

Hi,

Check config.json file found in following URLs. You need to add your IP
address there.

/repository/deployment/server/jaggeryapps/emm/config

/repository/deployment/server/jaggeryapps/emm-web-agent/config


Change LBHostPortPrefix in /repository/conf/cdm-config.xml

Regards,

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

Re: [Dev] Typo in "Deployment Synchronizer" section in carbon.xml file

[Johann Nallathamby]

Kernel Team,

Why was there no reply for this mail? It seems this issue is still not
fixed in latest kernel 4.4.x. Please fix this for next patch release.

Also there seems to be two DeploymentSynchronizer tags, one for svn and one
for registry. Do we have the registry based one now ? and how do you
identify the different configuratino tags ?

Thanks.

On Wed, Nov 11, 2015 at 6:48 AM, Malintha Adikari  wrote:

> Hi,
>
> There is a typo[1] in $subject. Found this in APIM 1.10.x pack.
>
>  [1]  
>
> Regards,
> Malintha
> --
> *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
>
>


-- 
Thanks & Regards,

*Johann Dilantha Nallathamby*
Technical Lead & Product Lead of WSO2 Identity Server
Governance Technologies Team
WSO2, Inc.
lean.enterprise.middleware

Mobile - *+9476950*
Blog - *http://nallaa.wordpress.com *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Test Automation] Mocking Thrift server for an integration test

[Kalpa Welivitigoda]

On Mon, Mar 28, 2016 at 7:03 PM, Mohanadarshan Vivekanandalingam <
mo...@wso2.com> wrote:

>
>
>
> On Mon, Mar 28, 2016 at 5:36 PM, Kalpa Welivitigoda 
> wrote:
>
>> Hi Lasantha,
>>
>> Is there a way in which we can verify the events being published to the
>> thrift server?
>>
>
> Why can't you have a counter in thrift agent server side and increment it
> when event received.. We have used similar approach in our test cases [1] ..
>
> [1]
> https://github.com/wso2/product-cep/blob/master/modules/integration/tests-integration/tests/src/test/java/org/wso2/carbon/integration/test/client/Wso2EventServer.java#L160
>
>
Thanks Mohan, I was thinking of whether we can verify the event data as
well.


>
>
>>
>> We have the http statistics publishing module in application server 6.0.0
>> and need to verify the events published to the thrift server in an
>> integration test.
>>
>> On Tue, Dec 1, 2015 at 3:20 PM, Thanuja Uruththirakodeeswaran <
>> thanu...@wso2.com> wrote:
>>
>>> Hi Lasantha,
>>>
>>> Sorry, I tried this with different ports and when changing the client
>>> port to 7613, forgot to change the server port to 7613. I've corrected it
>>> and attached the new log.
>>>
>>> [main] INFO
>>>  org.wso2.carbon.databridge.receiver.thrift.ThriftDataReceiver  - Thrift
>>> Server started at localhost
>>> [main] INFO
>>>  org.wso2.carbon.databridge.receiver.thrift.ThriftDataReceiver  - Thrift
>>> SSL port : 7713
>>> [main] INFO
>>>  org.wso2.carbon.databridge.receiver.thrift.ThriftDataReceiver  - Thrift
>>> port : 7613
>>> [main] INFO
>>>  org.apache.stratos.cloud.controller.statistics.publisher.ThriftTestServer
>>>  - Test Server Started
>>> [main] INFO  org.wso2.carbon.databridge.agent.thrift.AgentHolder  -
>>> Agent created !
>>> [main] INFO  org.apache.stratos.common.threading.StratosThreadPool  -
>>> Thread pool created: [type] Executor Service [id]
>>> cloud.controller.stats.publisher.thread.pool [size] 10
>>> [pool-5-thread-1] ERROR
>>> org.wso2.carbon.databridge.agent.thrift.AsyncDataPublisher  - Error while
>>> connection to event receiver
>>> org.wso2.carbon.databridge.agent.thrift.exception.AgentException: Cannot
>>> borrow client for TCP,localhost:7613,TCP,localhost:7713
>>> at
>>> org.wso2.carbon.databridge.agent.thrift.internal.publisher.authenticator.AgentAuthenticator.connect(AgentAuthenticator.java:58)
>>> at
>>> org.wso2.carbon.databridge.agent.thrift.DataPublisher.start(DataPublisher.java:273)
>>> at
>>> org.wso2.carbon.databridge.agent.thrift.DataPublisher.(DataPublisher.java:161)
>>> at
>>> org.wso2.carbon.databridge.agent.thrift.AsyncDataPublisher$ReceiverConnectionWorker.run(AsyncDataPublisher.java:787)
>>> at
>>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
>>> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
>>> at
>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>>> at
>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>>> at java.lang.Thread.run(Thread.java:745)
>>> Caused by: org.apache.thrift.transport.TTransportException: Could not
>>> connect to 172.17.8.1 on port 7713
>>> at
>>> org.apache.thrift.transport.TSSLTransportFactory.createClient(TSSLTransportFactory.java:212)
>>> at
>>> org.apache.thrift.transport.TSSLTransportFactory.getClientSocket(TSSLTransportFactory.java:166)
>>> at
>>> org.wso2.carbon.databridge.agent.thrift.internal.pool.client.secure.SecureClientPoolFactory.makeObject(SecureClientPoolFactory.java:90)
>>> at
>>> org.wso2.carbon.databridge.agent.thrift.internal.pool.client.secure.SecureClientPoolFactory.makeObject(SecureClientPoolFactory.java:48)
>>> at
>>> org.apache.commons.pool.impl.GenericKeyedObjectPool.borrowObject(GenericKeyedObjectPool.java:1212)
>>> at
>>> org.wso2.carbon.databridge.agent.thrift.internal.publisher.authenticator.AgentAuthenticator.connect(AgentAuthenticator.java:50)
>>> ... 8 more
>>> Caused by: java.net.ConnectException: Connection refused
>>> at java.net.PlainSocketImpl.socketConnect(Native Method)
>>> at
>>> java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)
>>> at
>>> java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)
>>> at
>>> java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)
>>> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
>>> at java.net.Socket.connect(Socket.java:579)
>>> at sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:625)
>>> at sun.security.ssl.SSLSocketImpl.(SSLSocketImpl.java:413)
>>> at
>>> sun.security.ssl.SSLSocketFactoryImpl.createSocket(SSLSocketFactoryImpl.java:88)
>>> at
>>> org.apache.thrift.transport.TSSLTransportFactory.createClient(TSSLTransportFactory.java:208)
>>> ... 13 more
>>>
>>> Thanks.
>>>
>>> On Tue, Dec 1, 2015 at 3:14 PM, Lasantha Fernando 
>>> wrote:
>>>
 Hi Thanuja,

 Looking at the logs above, it seems that the ThriftDataReceiver started
 

Re: [Dev] [Test Automation] Mocking Thrift server for an integration test

[Mohanadarshan Vivekanandalingam]

On Mon, Mar 28, 2016 at 5:36 PM, Kalpa Welivitigoda  wrote:

> Hi Lasantha,
>
> Is there a way in which we can verify the events being published to the
> thrift server?
>

Why can't you have a counter in thrift agent server side and increment it
when event received.. We have used similar approach in our test cases [1] ..

[1]
https://github.com/wso2/product-cep/blob/master/modules/integration/tests-integration/tests/src/test/java/org/wso2/carbon/integration/test/client/Wso2EventServer.java#L160



>
> We have the http statistics publishing module in application server 6.0.0
> and need to verify the events published to the thrift server in an
> integration test.
>
> On Tue, Dec 1, 2015 at 3:20 PM, Thanuja Uruththirakodeeswaran <
> thanu...@wso2.com> wrote:
>
>> Hi Lasantha,
>>
>> Sorry, I tried this with different ports and when changing the client
>> port to 7613, forgot to change the server port to 7613. I've corrected it
>> and attached the new log.
>>
>> [main] INFO
>>  org.wso2.carbon.databridge.receiver.thrift.ThriftDataReceiver  - Thrift
>> Server started at localhost
>> [main] INFO
>>  org.wso2.carbon.databridge.receiver.thrift.ThriftDataReceiver  - Thrift
>> SSL port : 7713
>> [main] INFO
>>  org.wso2.carbon.databridge.receiver.thrift.ThriftDataReceiver  - Thrift
>> port : 7613
>> [main] INFO
>>  org.apache.stratos.cloud.controller.statistics.publisher.ThriftTestServer
>>  - Test Server Started
>> [main] INFO  org.wso2.carbon.databridge.agent.thrift.AgentHolder  - Agent
>> created !
>> [main] INFO  org.apache.stratos.common.threading.StratosThreadPool  -
>> Thread pool created: [type] Executor Service [id]
>> cloud.controller.stats.publisher.thread.pool [size] 10
>> [pool-5-thread-1] ERROR
>> org.wso2.carbon.databridge.agent.thrift.AsyncDataPublisher  - Error while
>> connection to event receiver
>> org.wso2.carbon.databridge.agent.thrift.exception.AgentException: Cannot
>> borrow client for TCP,localhost:7613,TCP,localhost:7713
>> at
>> org.wso2.carbon.databridge.agent.thrift.internal.publisher.authenticator.AgentAuthenticator.connect(AgentAuthenticator.java:58)
>> at
>> org.wso2.carbon.databridge.agent.thrift.DataPublisher.start(DataPublisher.java:273)
>> at
>> org.wso2.carbon.databridge.agent.thrift.DataPublisher.(DataPublisher.java:161)
>> at
>> org.wso2.carbon.databridge.agent.thrift.AsyncDataPublisher$ReceiverConnectionWorker.run(AsyncDataPublisher.java:787)
>> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
>> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
>> at
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>> at java.lang.Thread.run(Thread.java:745)
>> Caused by: org.apache.thrift.transport.TTransportException: Could not
>> connect to 172.17.8.1 on port 7713
>> at
>> org.apache.thrift.transport.TSSLTransportFactory.createClient(TSSLTransportFactory.java:212)
>> at
>> org.apache.thrift.transport.TSSLTransportFactory.getClientSocket(TSSLTransportFactory.java:166)
>> at
>> org.wso2.carbon.databridge.agent.thrift.internal.pool.client.secure.SecureClientPoolFactory.makeObject(SecureClientPoolFactory.java:90)
>> at
>> org.wso2.carbon.databridge.agent.thrift.internal.pool.client.secure.SecureClientPoolFactory.makeObject(SecureClientPoolFactory.java:48)
>> at
>> org.apache.commons.pool.impl.GenericKeyedObjectPool.borrowObject(GenericKeyedObjectPool.java:1212)
>> at
>> org.wso2.carbon.databridge.agent.thrift.internal.publisher.authenticator.AgentAuthenticator.connect(AgentAuthenticator.java:50)
>> ... 8 more
>> Caused by: java.net.ConnectException: Connection refused
>> at java.net.PlainSocketImpl.socketConnect(Native Method)
>> at
>> java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)
>> at
>> java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)
>> at
>> java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)
>> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
>> at java.net.Socket.connect(Socket.java:579)
>> at sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:625)
>> at sun.security.ssl.SSLSocketImpl.(SSLSocketImpl.java:413)
>> at
>> sun.security.ssl.SSLSocketFactoryImpl.createSocket(SSLSocketFactoryImpl.java:88)
>> at
>> org.apache.thrift.transport.TSSLTransportFactory.createClient(TSSLTransportFactory.java:208)
>> ... 13 more
>>
>> Thanks.
>>
>> On Tue, Dec 1, 2015 at 3:14 PM, Lasantha Fernando 
>> wrote:
>>
>>> Hi Thanuja,
>>>
>>> Looking at the logs above, it seems that the ThriftDataReceiver started
>>> on port 7612, with SSL port 7712.
>>>
>>> [main] INFO
>>>  org.wso2.carbon.databridge.receiver.thrift.ThriftDataReceiver  - Thrift
>>> SSL port : 7712
>>> [main] INFO
>>>  org.wso2.carbon.databridge.receiver.thrift.ThriftDataReceiver  - Thrift
>>> port : 7612
>>> [main] INFO
>>>  

Re: [Dev] [Test Automation] Mocking Thrift server for an integration test

[Kalpa Welivitigoda]

Hi Lasantha,

Is there a way in which we can verify the events being published to the
thrift server?

We have the http statistics publishing module in application server 6.0.0
and need to verify the events published to the thrift server in an
integration test.

On Tue, Dec 1, 2015 at 3:20 PM, Thanuja Uruththirakodeeswaran <
thanu...@wso2.com> wrote:

> Hi Lasantha,
>
> Sorry, I tried this with different ports and when changing the client port
> to 7613, forgot to change the server port to 7613. I've corrected it and
> attached the new log.
>
> [main] INFO  org.wso2.carbon.databridge.receiver.thrift.ThriftDataReceiver
>  - Thrift Server started at localhost
> [main] INFO  org.wso2.carbon.databridge.receiver.thrift.ThriftDataReceiver
>  - Thrift SSL port : 7713
> [main] INFO  org.wso2.carbon.databridge.receiver.thrift.ThriftDataReceiver
>  - Thrift port : 7613
> [main] INFO
>  org.apache.stratos.cloud.controller.statistics.publisher.ThriftTestServer
>  - Test Server Started
> [main] INFO  org.wso2.carbon.databridge.agent.thrift.AgentHolder  - Agent
> created !
> [main] INFO  org.apache.stratos.common.threading.StratosThreadPool  -
> Thread pool created: [type] Executor Service [id]
> cloud.controller.stats.publisher.thread.pool [size] 10
> [pool-5-thread-1] ERROR
> org.wso2.carbon.databridge.agent.thrift.AsyncDataPublisher  - Error while
> connection to event receiver
> org.wso2.carbon.databridge.agent.thrift.exception.AgentException: Cannot
> borrow client for TCP,localhost:7613,TCP,localhost:7713
> at
> org.wso2.carbon.databridge.agent.thrift.internal.publisher.authenticator.AgentAuthenticator.connect(AgentAuthenticator.java:58)
> at
> org.wso2.carbon.databridge.agent.thrift.DataPublisher.start(DataPublisher.java:273)
> at
> org.wso2.carbon.databridge.agent.thrift.DataPublisher.(DataPublisher.java:161)
> at
> org.wso2.carbon.databridge.agent.thrift.AsyncDataPublisher$ReceiverConnectionWorker.run(AsyncDataPublisher.java:787)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: org.apache.thrift.transport.TTransportException: Could not
> connect to 172.17.8.1 on port 7713
> at
> org.apache.thrift.transport.TSSLTransportFactory.createClient(TSSLTransportFactory.java:212)
> at
> org.apache.thrift.transport.TSSLTransportFactory.getClientSocket(TSSLTransportFactory.java:166)
> at
> org.wso2.carbon.databridge.agent.thrift.internal.pool.client.secure.SecureClientPoolFactory.makeObject(SecureClientPoolFactory.java:90)
> at
> org.wso2.carbon.databridge.agent.thrift.internal.pool.client.secure.SecureClientPoolFactory.makeObject(SecureClientPoolFactory.java:48)
> at
> org.apache.commons.pool.impl.GenericKeyedObjectPool.borrowObject(GenericKeyedObjectPool.java:1212)
> at
> org.wso2.carbon.databridge.agent.thrift.internal.publisher.authenticator.AgentAuthenticator.connect(AgentAuthenticator.java:50)
> ... 8 more
> Caused by: java.net.ConnectException: Connection refused
> at java.net.PlainSocketImpl.socketConnect(Native Method)
> at
> java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)
> at
> java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)
> at
> java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)
> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
> at java.net.Socket.connect(Socket.java:579)
> at sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:625)
> at sun.security.ssl.SSLSocketImpl.(SSLSocketImpl.java:413)
> at
> sun.security.ssl.SSLSocketFactoryImpl.createSocket(SSLSocketFactoryImpl.java:88)
> at
> org.apache.thrift.transport.TSSLTransportFactory.createClient(TSSLTransportFactory.java:208)
> ... 13 more
>
> Thanks.
>
> On Tue, Dec 1, 2015 at 3:14 PM, Lasantha Fernando 
> wrote:
>
>> Hi Thanuja,
>>
>> Looking at the logs above, it seems that the ThriftDataReceiver started
>> on port 7612, with SSL port 7712.
>>
>> [main] INFO
>>  org.wso2.carbon.databridge.receiver.thrift.ThriftDataReceiver  - Thrift
>> SSL port : 7712
>> [main] INFO
>>  org.wso2.carbon.databridge.receiver.thrift.ThriftDataReceiver  - Thrift
>> port : 7612
>> [main] INFO
>>  org.apache.stratos.cloud.controller.statistics.publisher.ThriftTestServer
>>  - Test Server Started
>>
>> But the agent is trying to connect to port 7613,7713.
>>
>> [pool-5-thread-1] ERROR
>> org.wso2.carbon.databridge.agent.thrift.AsyncDataPublisher  - Error while
>> connection to event receiver
>> org.wso2.carbon.databridge.agent.thrift.exception.AgentException: Cannot
>> borrow client for TCP,localhost:7613,TCP,localhost:7713
>>
>> Can you go through the code and verify that the agent is sending to the
>> same port on which agent is started? 

Re: [Dev] Tenant-aware logging for ESB

[Amila Maha Arachchi]

Hi Manjula,

Due to the time taken by an ESB docker image to start and the cost of
keeping them running, it was decided to use a shared multi-tenanted ESB
instance for ESB-as-a-Service for the beginning.

On Mon, Mar 28, 2016 at 12:36 PM, Manjula Rathnayake 
wrote:

> Hi all,
>
> IMO, when we run ESB for multi-tenant scenarios, we will have containers
> per each tenant. So we don't need to have tenant specific filtering in
> multi tenant scenarios.
>
> If we consider container approach for car files;
> we currently allow single artifact deployment for App Server like products
> where you upload only a single war file and it is bundled to App server and
> image is created.
> but for ESB, we promote having multiple car files where endpoints are
> packaged into one car and business logic is packaged into another car. So
> having log filtering based on car name would be useful even with container
> model.
>
> thank you.
>
>
> On Mon, Mar 28, 2016 at 10:06 AM, Kasun Indrasiri  wrote:
>
>> Hi Nadeeshan,
>>
>> Can you please do the needful to verify this for ESB 5. 0 and make sure
>> we cover all the iPaaS requirements for tenant/cApp specific log filtering.
>>
>>
>> On Fri, Mar 25, 2016 at 5:47 PM, Nadeeshaan Gunasinghe <
>> nadeesh...@wso2.com> wrote:
>>
>>> Hi Kasun,
>>>
>>> +1 for including the Tenant Specific filtering enabled and we have
>>> already included this feature for logging the car file name for the
>>> artifacts deployed through car file.
>>>
>>> Thanks,
>>>
>>> *Nadeeshaan Gunasinghe*
>>> Software Engineer, WSO2 Inc. http://wso2.com
>>> +94770596754 | nadeesh...@wso2.com | Skype: nadeeshaan.gunasinghe
>>> <#m_-6937215353571362766_m_52855956923528221_m_257616742262875097_>
>>> 
>>>   
>>> 
>>> Get a signature like this: Click here!
>>> 
>>>
>>> On Fri, Mar 25, 2016 at 1:22 PM, Kasun Indrasiri  wrote:
>>>
 Hi,

 AFAIR, Nadeeshan has implemented this features (for ESB 5). We want to
 make sure that what we have at the moment is sufficient to filter out the
 tenant specific logs (and even cApp specific logs).

 @Nadeeshan/Manjula wdyt?

 --
 Kasun Indrasiri
 Software Architect
 WSO2, Inc.; http://wso2.com
 lean.enterprise.middleware

 cell: +94 77 556 5206
 Blog : http://kasunpanorama.blogspot.com/

>>>
>>>
>>
>>
>> --
>> Kasun Indrasiri
>> Software Architect
>> WSO2, Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> cell: +94 77 556 5206
>> Blog : http://kasunpanorama.blogspot.com/
>>
>
>
>
> --
> Manjula Rathnayaka
> Associate Technical Lead
> WSO2, Inc.
> Mobile:+94 77 743 1987
>



-- 
*Amila Maharachchi*
Senior Technical Lead
WSO2, Inc.; http://wso2.com

Blog: http://maharachchi.blogspot.com
Mobile: +94719371446
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] NPE due to concurrency issue in DocumentBuilderFactoryImpl

[Chamara Philips]

Hi devs,

We have a version problem with apache-rampart and apache-axiom versions we
are using in wso2-rampart and axiom orbits. The concurrency issue reported
at [1], has a fix introduced for apache-rampart at [2]. We can't apply the
same fix they have done, as we are using a different apache-axiom version,
which they have used at the time of fix.

The main reason for this is well explained at [3]. Also a solution is
introduced with new DOOMDocumentBuilder and DOOMDocumentBuilderFactory is
introduced in [3]. (Please refer this ticket to know more)

In this particular scenario we are going to use DocumentBuilderFactoryImpl
with setDOOMRequired(true)[4] and setDOOMRequired(false)[5]. When one
thread is done with line at[4], ( if another thread who is not using that
option, in this particular case [6]), will get a null pointer exception as
in the attached file.

The root cause is in the [7] line.

isDOOMRequired() ? new DocumentBuilderImpl(this) :
originalDocumentBuilderFactory.newDocumentBuilder();

the originalDocumentBuiderFactory is set to null by the first thread. This
cause the NPE.

Any thoughts for solving this issue is highly appreciated.

[1] https://wso2.org/jira/browse/IDENTITY-4450
[2]
https://github.com/apache/rampart/commit/0f23004fc32fb47892dcedab4678915527857a53#diff-ced16c6496574ca0f7b5bcaf522251a7
[3] https://issues.apache.org/jira/browse/AXIS2-1570
[4]
https://github.com/wso2/wso2-rampart/blob/master/modules/rampart-trust/src/main/java/org/apache/rahas/impl/SAMLTokenIssuer.java#L132
[5]
https://github.com/wso2/wso2-rampart/blob/master/modules/rampart-trust/src/main/java/org/apache/rahas/impl/SAMLTokenIssuer.java#L293
[6]
https://github.com/ChamaraPhilipsuom/carbon-identity/blob/master/components/sso-saml/org.wso2.carbon.identity.sso.saml/src/main/java/org/wso2/carbon/identity/sso/saml/util/SAMLSSOUtil.java#L292
[7]
https://github.com/wso2/wso2-axiom/blob/master/modules/axiom-dom/src/main/java/org/apache/axiom/om/impl/dom/jaxp/DocumentBuilderFactoryImpl.java#L93

-- 
Hareendra Chamara Philips
*Software  Engineer*
Mobile : +94 (0) 767 184161 <%2B94%20%280%29%20773%20451194>
chama...@wso2.com 
[2016-03-18 12:48:03,312] ERROR 
{org.wso2.carbon.identity.sts.passive.ui.PassiveSTS} -  AuthenticationResult 
does not exist. Probably due to cache timeout
[2016-03-18 12:48:03,319] ERROR 
{org.wso2.carbon.identity.sso.saml.util.SAMLSSOUtil} -  Error in constructing 
AuthRequest from the encoded String
java.lang.NullPointerException
at 
org.apache.axiom.om.impl.dom.jaxp.DocumentBuilderFactoryImpl.newDocumentBuilder(DocumentBuilderFactoryImpl.java:93)
at 
org.wso2.carbon.identity.sso.saml.util.SAMLSSOUtil.unmarshall(SAMLSSOUtil.java:300)
at 
org.wso2.carbon.identity.sso.saml.SAMLSSOService.validateSPInitSSORequest(SAMLSSOService.java:83)
at 
org.wso2.carbon.identity.sso.saml.servlet.SAMLSSOProviderServlet.handleSPInitSSO(SAMLSSOProviderServlet.java:355)
at 
org.wso2.carbon.identity.sso.saml.servlet.SAMLSSOProviderServlet.handleRequest(SAMLSSOProviderServlet.java:195)
at 
org.wso2.carbon.identity.sso.saml.servlet.SAMLSSOProviderServlet.doGet(SAMLSSOProviderServlet.java:95)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:620)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at 
org.eclipse.equinox.http.helper.ContextPathServletAdaptor.service(ContextPathServletAdaptor.java:37)
at 
org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61)
at 
org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:128)
at 
org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:60)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at 
org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:68)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at 
org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at 
org.wso2.carbon.ui.filters.CSRFPreventionFilter.doFilter(CSRFPreventionFilter.java:88)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at 
org.wso2.carbon.ui.filters.CRLFPreventionFilter.doFilter(CRLFPreventionFilter.java:59)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at 

Re: [Dev] ESB Analytics - Verifying the common production use cases

[Buddhima Wijeweera]

Hi All,

We are currently in the process of testing statistics & tracing for various
scenarios.
Initially we planned to cover on the areas we have identified for
functionality testing.
Then we planned to move on to common scenarios, and performance testing as
well.

Thank you,

On Mon, Mar 28, 2016 at 2:34 PM, Srinath Perera  wrote:

> Please run ESB benchmark, get the events comes out of it to DAS, and use
> that for testing.
>
> --Srinath
>
> On Mon, Mar 28, 2016 at 10:02 AM, Kasun Indrasiri  wrote:
>
>> Hi Buddhima/VirajS,
>>
>> Once the end to end functionalities are implemented on the ESB analytics
>> side, can we start testing the current implementation for production use
>> cases of ESB. Basically we need to cover all the common integration
>> scenarios and stress test the implemented with high load too.
>>
>> Thanks,
>> Kasun
>>
>> --
>> Kasun Indrasiri
>> Software Architect
>> WSO2, Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> cell: +94 77 556 5206
>> Blog : http://kasunpanorama.blogspot.com/
>>
>
>
>
> --
> 
> Blog: http://srinathsview.blogspot.com twitter:@srinath_perera
> Site: http://home.apache.org/~hemapani/
> Photos: http://www.flickr.com/photos/hemapani/
> Phone: 0772360902
>



-- 
Buddhima Wijeweera
Software Engineer; WSO2 Inc.; http://wso2.com ,

Mobile: +94 71 427 9966
Email: buddh...@wso2.com
Blog:   https://buddhimawijeweera.wordpress.com
GitHub Profile: https://github.com/Buddhima
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] ESB Analytics - Verifying the common production use cases

[Srinath Perera]

Please run ESB benchmark, get the events comes out of it to DAS, and use
that for testing.

--Srinath

On Mon, Mar 28, 2016 at 10:02 AM, Kasun Indrasiri  wrote:

> Hi Buddhima/VirajS,
>
> Once the end to end functionalities are implemented on the ESB analytics
> side, can we start testing the current implementation for production use
> cases of ESB. Basically we need to cover all the common integration
> scenarios and stress test the implemented with high load too.
>
> Thanks,
> Kasun
>
> --
> Kasun Indrasiri
> Software Architect
> WSO2, Inc.; http://wso2.com
> lean.enterprise.middleware
>
> cell: +94 77 556 5206
> Blog : http://kasunpanorama.blogspot.com/
>



-- 

Blog: http://srinathsview.blogspot.com twitter:@srinath_perera
Site: http://home.apache.org/~hemapani/
Photos: http://www.flickr.com/photos/hemapani/
Phone: 0772360902
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] IoTS-1.0.0-M4 Build order

[Charitha Goonetilleke]

Hi All,

We have made some of changes to product and build order has been changed
accordingly. We will be able to move to master branch of carbon-device-mgt
and carbon-device-mgt-plugins, once we completed required changes to work
with changes in carbon-device-mgt master.

https://github.com/wso2-incubator/uuf-template-app

  branch:*IoTS-1.0.0-M4*
https://github.com/wso2-extensions/identity-oauth2-grant-jwt

 branch:*master*
https://github.com/wso2/carbon-device-mgt

  branch:*IoTS-1.0.0-M4*
https://github.com/wso2/carbon-device-mgt-plugins

  branch:*IoTS-1.0.0-M4*
https://github.com/wso2-incubator/product-iot-server

  branch:*master*


On Wed, Mar 16, 2016 at 10:33 AM, Sumedha Rubasinghe 
wrote:

> Resending to dev list.
> On Mar 16, 2016 10:22 AM, "Charitha Goonetilleke" 
> wrote:
>
>> Hi All,
>>
>> Since few PRs are merged to depended repos, here is the new build order.
>>
>>1. https://github.com/wso2-incubator/uuf-template-app
>> branch:IoTS-1.0.0-M4
>>2. https://github.com/wso2/carbon-apimgt  branch:release-4.3.x
>>3. https://github.com/wso2/carbon-device-mgt  branch:IoTS-1.0.0-M4
>>4. https://github.com/wso2/carbon-device-mgt-plugins
>> branch:IoTS-1.0.0-M4
>>5. https://github.com/wso2-incubator/product-iot-server  branch:master
>>
>>
>>
>> On Wed, Feb 24, 2016 at 4:48 PM, Ruwan Yatawara  wrote:
>>
>>> Please follow the following instructions to build the M4 branch.
>>>
>>> https://github.com/wso2-incubator/uuf-template-app  branch:
>>> *IoTS-1.0.0-M4*
>>> https://github.com/wso2/carbon-apimgt  branch:*release-4.3.x*
>>> https://github.com/ruwany/carbon-analytics-common branch:*master*
>>> https://github.com/wso2/carbon-device-mgt  branch:*IoTS-1.0.0-M4*
>>> https://github.com/wso2/carbon-device-mgt-plugins  branch:
>>> *IoTS-1.0.0-M4*
>>> https://github.com/wso2-incubator/product-iot-server  branch:*master*
>>>
>>> Please note that the analytics-common repo is my personal one, there are
>>> some OSGI import related fixes i have done, that have not been merged yet.
>>> Once done, building same wont be necessary. However, if in case an
>>> carbon-commons related issue is encountered, please build the following as
>>> well.
>>>
>>> https://github.com/wso2/carbon-commons branch:*4.4.x*
>>>
>>> Thanks and Regards,
>>>
>>> Ruwan Yatawara
>>>
>>> Senior Software Engineer,
>>> WSO2 Inc.
>>>
>>> email : ruw...@wso2.com
>>> mobile : +94 77 9110413
>>> blog : http://ruwansrants.blogspot.com/
>>> www: :http://wso2.com
>>>
>>>
>>> On Thu, Feb 11, 2016 at 6:44 PM, Charitha Goonetilleke <
>>> charit...@wso2.com> wrote:
>>>
 Hi All,

 This is the latest build order for the M4.

 https://github.com/wso2-incubator/uuf-template-app  branch:
 *IoTS-1.0.0-M4*
 https://github.com/wso2/carbon-apimgt  branch:*release-4.3.x*
 https://github.com/ruwany/carbon-commons.git  branch:*IoTS-1.0.0-M2*
 https://github.com/wso2/carbon-device-mgt  branch:*IoTS-1.0.0-M4*
 https://github.com/wso2/carbon-device-mgt-plugins  branch:
 *IoTS-1.0.0-M4*
 https://github.com/wso2-incubator/product-iot-server  branch:*master*


 --
 *Charitha Goonetilleke*
 Software Engineer
 WSO2 Inc.; http://wso2.com
 lean.enterprise.middleware

 mobile: +94 77 751 3669 <%2B94777513669>
 Twitter:@CharithaWs , fb: charithag
 , linkedin: charithag
 

>>>
>>>
>>
>>
>> --
>> *Charitha Goonetilleke*
>> Software Engineer
>> WSO2 Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> mobile: +94 77 751 3669 <%2B94777513669>
>> Twitter:@CharithaWs , fb: charithag
>> , linkedin: charithag
>> 
>>
>


-- 
*Charitha Goonetilleke*
Software Engineer
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware

mobile: +94 77 751 3669 <%2B94777513669>
Twitter:@CharithaWs , fb: charithag
, linkedin: charithag

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

Re: [Dev] Tenant-aware logging for ESB

[Manjula Rathnayake]

Hi all,

IMO, when we run ESB for multi-tenant scenarios, we will have containers
per each tenant. So we don't need to have tenant specific filtering in
multi tenant scenarios.

If we consider container approach for car files;
we currently allow single artifact deployment for App Server like products
where you upload only a single war file and it is bundled to App server and
image is created.
but for ESB, we promote having multiple car files where endpoints are
packaged into one car and business logic is packaged into another car. So
having log filtering based on car name would be useful even with container
model.

thank you.


On Mon, Mar 28, 2016 at 10:06 AM, Kasun Indrasiri  wrote:

> Hi Nadeeshan,
>
> Can you please do the needful to verify this for ESB 5. 0 and make sure we
> cover all the iPaaS requirements for tenant/cApp specific log filtering.
>
>
> On Fri, Mar 25, 2016 at 5:47 PM, Nadeeshaan Gunasinghe <
> nadeesh...@wso2.com> wrote:
>
>> Hi Kasun,
>>
>> +1 for including the Tenant Specific filtering enabled and we have
>> already included this feature for logging the car file name for the
>> artifacts deployed through car file.
>>
>> Thanks,
>>
>> *Nadeeshaan Gunasinghe*
>> Software Engineer, WSO2 Inc. http://wso2.com
>> +94770596754 | nadeesh...@wso2.com | Skype: nadeeshaan.gunasinghe
>> <#m_52855956923528221_m_257616742262875097_>
>> 
>>   
>> 
>> Get a signature like this: Click here!
>> 
>>
>> On Fri, Mar 25, 2016 at 1:22 PM, Kasun Indrasiri  wrote:
>>
>>> Hi,
>>>
>>> AFAIR, Nadeeshan has implemented this features (for ESB 5). We want to
>>> make sure that what we have at the moment is sufficient to filter out the
>>> tenant specific logs (and even cApp specific logs).
>>>
>>> @Nadeeshan/Manjula wdyt?
>>>
>>> --
>>> Kasun Indrasiri
>>> Software Architect
>>> WSO2, Inc.; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> cell: +94 77 556 5206
>>> Blog : http://kasunpanorama.blogspot.com/
>>>
>>
>>
>
>
> --
> Kasun Indrasiri
> Software Architect
> WSO2, Inc.; http://wso2.com
> lean.enterprise.middleware
>
> cell: +94 77 556 5206
> Blog : http://kasunpanorama.blogspot.com/
>



-- 
Manjula Rathnayaka
Associate Technical Lead
WSO2, Inc.
Mobile:+94 77 743 1987
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [BPS] Error when passing parameters to a SOAP operation with Apache CXF

[Natasha Wijesekara]

 Hi,

There are many complexities when trying to implement a SOAP client using
the dynamic client capability of Apache CXF. I was able to provide a
workaround for the error which occurred when passing parameters to a SOAP
operation with Apache CXF .

The workaround provided does not work with WSDLs which have complex types
as the request or response message type  i.e. the request/response message
parts of the WSDL can be primitive or complex, so 2 different approaches
should be followed to get/set the values of the primitive and complex types
respectively. When having complex types, the message part is iterated over
multiple times, which will take more processing time and reduce the
performance.

The approach I used is described below. By using this approach the
JaxWsDynamicClientFactory takes care of generating Java classes for complex
types :

Create a new instance of the Client using the JaxWsDynamicClientFactory by
passing the wsdl url. The url of the WSDL, operation name and the input
variables is provided by the user.





*JaxWsDynamicClientFactory factory =
JaxWsDynamicClientFactory.newInstance();URL wsdlURL = new
URL("http://localhost:9763/services/DivisionProcessService?wsdl
");String
operationName = "process";Client client =
factory.createClient(wsdlURL.toExternalForm());ClientImpl clientImpl =
(ClientImpl) client;*

Get the endpoint i.e. the URL where the web service can be accessed by a
client application using the cilent.

*Endpoint endpoint = clientImpl.getEndpoint();*

Get the target namespace of the WSDL by creating a ServiceInfo object which
walks over the CXF service model

*ServiceInfo serviceInfo = endpoint.getService().getServiceInfos().get(0);*
*String targetNameSpace = serviceInfo.getTargetNamespace();*

Get the binding name of the WSDL by creating a BindingInfo object which
gets the name of the binding.

*BindingInfo bindingInfo = serviceInfo.getBindings().iterator().next();*
*String bName = bindingInfo.getName().getLocalPart();*

Create a Qname by passing the namespace and the binding name as parameters
and get the binding which has the specified QName.

*QName bindingName = new QName(targetNameSpace, bName);*
*BindingInfo binding = serviceInfo.getBinding(bindingName);*

Get details about the soap operation which is to be invoked by creating a
QName with the namespace and the operation name.

*QName opName = new QName(targetNameSpace, operationName);*
*BindingOperationInfo boi = binding.getOperation(opName);*

Get the input/request message type
*BindingMessageInfo inputMessageInfo = boi.getInput();*
*List parts = inputMessageInfo.getMessageParts();*
*MessagePartInfo partInfo = parts.get(0);*

Get the  class type of the request/input message and dynamically create an
instance of it
*Class partClass = partInfo.getTypeClass();*
*Object obj = partClass.newInstance();*

The input variables provided by the user is stored inside a  HashTable
which will hold the variable name and its value as a key-value pair

*Hashtable table = new Hashtable();*
*table.put("dividend", 40);*
*table.put("divisor", 10);*

Get the methods from the generated request class. This class will have
getter and setter methods for the variables taken as the input/request.

*Method [] methods = obj.getClass().getDeclaredMethods();*
*for(Method m : methods){*
* if(m.getName().contains("set")){*
* String methodName = m.getName(); *
* Class paramType = m.getParameterTypes()[0];*
* String[] output = methodName.split("set");*
* String varName = output[1].toLowerCase(); *
* Object value = table.get(varName); *
* Method m1 = obj.getClass().getMethod(methodName, paramType); *
* m1.invoke(obj, value);*
* } else {*
* }*
*}*

Invoking the operation
*Object[] response = client.invoke(operationName, obj);*

Get the methods from the generated response class. This class will have getter
and setter methods for the variables given as the output.

*Method [] responseMethods = response[0].getClass().getDeclaredMethods();*
*for(Method rm : responseMethods){*
* if(rm.getName().contains("get")){*
* String responseMethod = rm.getName();*
* Object result =
response[0].getClass().getMethod(responseMethod).invoke(response[0]);*
* System.**out**.println("Response: " + result);*
* } else {*
* }*
*}*

Is this approach correct or is there any way to overcome these limitations
when using CXF ?

Any suggestions and feedback are highly appreciated.

Best Regards,

Natasha Wijesekare

On Thu, Mar 17, 2016 at 4:47 PM, Natasha Wijesekara 
wrote:

> Hi ,
>
> I tried passing the operation name with the namespace but it didn't work.
> I get the same exception as below.
>
> *java.lang.IllegalArgumentException: Part
> {http://wso2.org/wso2con/2011/sample/adder}payload
>  should be of type
> org.wso2.wso2con._2011.sample.adder.AdderProcessRequest, not
> java.lang.Integer*
> * at
> 

Re: [Dev] [BPS] What is the best approach to create BPMN processes

[Hasitha Aravinda]

This can be done in a single process.

Start Event -> Service Task ( Update Database) -> User Task ( to Change the
status ) -> Service Task ( to Change the status ) -> End Event.

Thanks,
Hasitha.

On Mon, Mar 28, 2016 at 11:30 AM, Amalka Subasinghe  wrote:

> Hi,
>
> I have a scenario like
> 1. User log in and fill a form and save, it will save in external database
> with the status 'Created'
> 2. later time User log in again, he sees the records which are in
> "Created" status and change the status of those records to 'In Progress',
> it will again update the database.
>
> for this kind of scenario, the best approach would be creating 1 BPMN
> process including both or creating 2 BPMN processes ?
>
> Thanks
> Amalka
>
>


-- 
--
Hasitha Aravinda,
Senior Software Engineer,
WSO2 Inc.
Email: hasi...@wso2.com
Mobile : +94 718 210 200
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [BPS] What is the best approach to create BPMN processes

[Amalka Subasinghe]

Hi,

I have a scenario like
1. User log in and fill a form and save, it will save in external database
with the status 'Created'
2. later time User log in again, he sees the records which are in "Created"
status and change the status of those records to 'In Progress', it will
again update the database.

for this kind of scenario, the best approach would be creating 1 BPMN
process including both or creating 2 BPMN processes ?

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