Re: [Dev] How can we add multi language support in javascript files

[SajithAR Ariyarathna]

Hi Prasanna,

We have implemented server-side JS function for i18n [1]. One can use it as
follows.


i18n("message.key");


i18n("message.key", param1, param2, ...);


This feature is in the current master, will do a milestone release with
this soon.

[1] https://github.com/wso2/carbon-uuf/pull/220


On Tue, Apr 25, 2017 at 10:03 AM, Prasanna Dangalla 
wrote:

> Hi All,
>
> Kind reminder on this. What should we follow to do internationalization
> in javascript code ?
>
> @UUF Team: Shall we come to a final decision regarding this.
>
> Thanks
>
> *Prasanna Dangalla*
> Senior Software Engineer, WSO2, Inc.; http://wso2.com/
> lean.enterprise.middleware
>
>
> *cell: +94 718 11 27 51*
> *twitter: @prasa77*
>
> On Sun, Mar 26, 2017 at 9:50 AM, Ruwan Abeykoon  wrote:
>
>> Hi All,
>> Interesting article about similar requirement[1]
>>
>> [1] http://nerds.airbnb.com/slides-and-video-from-spike-brehms-tech-talk/
>>
>> Cheers,
>> Ruwan
>>
>> On Fri, Mar 24, 2017 at 10:55 PM, Prasanna Dangalla 
>> wrote:
>>
>>>
>>>
>>> On Fri, Mar 24, 2017 at 6:34 PM Manuranga Perera  wrote:
>>>
 We need to bring whole i18n (combined all lang files) to the UI and
 cache it.

>>>
>>> Bringing the whole thing will be an expensive operation in the fist time
>>> before caching them, IMO we should load page wise and then cache them. WDYT
>>> ?
>>>


 On Fri, Mar 24, 2017 at 8:40 AM, Nuwandi Wickramasinghe <
 nuwan...@wso2.com> wrote:



 On Fri, Mar 24, 2017 at 1:49 PM, Nuwan Dias  wrote:



 On Fri, Mar 24, 2017 at 1:23 PM, Ruwan Abeykoon 
 wrote:

 Hi All,
 What if,
 i18n is handled on the server side only, and encode the relevant
 localized strings into HTML by the server-side (js or hbs).
 Client side libraries only read the string values already in the client
 locale within HTML DOM itself and just render the data. No client-side 
 i18n.

 I have a situation where a part of the DOM is created in client side
 JS. In that case this wouldn't work.


 What is would be the limitations?


 Limitations would be for SPAs where the rendering is done at the client
 side. Which would basically mean that SPAs can't have localization.


 Cheers,
 Ruwan

 On Fri, Mar 24, 2017 at 11:54 AM, Nipuna Chandradasa 
 wrote:

 API of somekind(Rest or a http service endpoint), That we have to think
 about,  that exposes a functionality to retrieve i18n as a json object to
 layout level or any other global level of the application. So on client
 side we can use the i18n language details anywhere.
 We can get the language data from the browser.. that's how we do it
 anyway i think. We get the i18n based on the what language browser has
 configured to use.

 Thank you,

 On Fri, Mar 24, 2017 at 10:14 AM, Prasanna Dangalla 
 wrote:

 On Fri, Mar 24, 2017 at 12:53 AM, Nipuna Chandradasa 
 wrote:

 I don't think there is a feasible solution rather than loading i18n
 config file as a json object to the client side in the beginning of the
 app... i think from uuf side we can provide a api for that... WDYT?

 API in the sense, what kind of an API ? Does this loads all the data
 into front end or are you thinking about a filtering mechanism for the
 language data by page before you send them to front end ?


 On Thu, Mar 23, 2017 at 5:29 PM, SajithAR Ariyarathna <
 sajit...@wso2.com> wrote:

 Currently UUF doesn't support i18n in client-side.

 @UUF Team,
 We need to come up with a solution for client-side i18n. Shall we start
 a discussion on this?

 Thanks.


 On Thu, Mar 23, 2017 at 4:36 PM, Prasanna Dangalla 
 wrote:

 Hi Sajith,

 This is for Client-side JS

 *Prasanna Dangalla*
 Senior Software Engineer, WSO2, Inc.; http://wso2.com/
 lean.enterprise.middleware


 *cell: +94 718 11 27 51*
 *twitter: @prasa77*

 On Thu, Mar 23, 2017 at 2:54 PM, SajithAR Ariyarathna <
 sajit...@wso2.com> wrote:

 Hi Prasanna,

 Is there a mechanism defined to use something like i18n in javascript ?

 Server-side JS or Client-side JS?

 On Thu, Mar 23, 2017 at 11:02 AM, Ayesha Dissanayaka 
 wrote:

 Hi Prasanna,

 Similar discussion was started sometime back in [1].
 Issues in [2], [3] have some suggestions.

 [1] [Dev][UUF][IS-6] Enable i18n support in javascript
 [2] https://github.com/wso2/carbon-uuf/issues/160
 [3] https://github.com/wso2/carbon-uuf/issues/166

 @Ayesha: As I understood all these are done for server side JS, I'm

Re: [Dev] [APIM] Incorrect resource mapping during api invokation when a resource with "/*" exists.

[Nuwan Dias]

Ayoob, both these resources are valid for the request you are sending. You
can't say one is wrong and the other is right. What you're expecting is
like a best match scenario, which synapse doesn't support at the moment. It
should be possible to implement it using a scoring mechanism or something
like that, but it'll definitely impact performance.

>From a REST point of view, its an invalid design. So my question is why
bother anyway? Do you really have resource paths that are impossible to
determine at design time?

On Tue, Apr 25, 2017 at 10:06 AM, Ayyoob Hamza  wrote:

> Hi All,
>
> In IoTS, We have exposed all the APIs through the API manager. In a
> particular API, we have 2 API resources
>
> 1) POST /* with a scope X1
> 2) POST /{type}/operations with a scope X2.
>
> When we invoke the second resource, API call ends up going to the first
> one in the synapse layer. However after synapse forwards it to the backend,
> it ends up to the correct resource in the Jax-rs.
> The issue we are facing in here is that during scope validation it picks
> up the wrong resource.
>
> So this made me wondered why is the mapping is correctly evaluated in the
> tomcat but not in the synapse layer. Do we have a bug here? or was it an
> architecture decision to go with the first matching resource.
>
> Are there any solutions to pick the best possible matching resource in the
> synapse layer?
>
> Thanks
> *Ayyoob Hamza*
> *Senior Software Engineer*
> WSO2 Inc.; http://wso2.com
> email: ayy...@wso2.com cell: +94 77 1681010 <%2B94%2077%207779495>
>



-- 
Nuwan Dias

Software Architect - WSO2, Inc. http://wso2.com
email : nuw...@wso2.com
Phone : +94 777 775 729
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] User-pref implementation for the UUF based dashboard view component

[Udara Rathnayake]

*What is user-pref?*
This allows end-user configuration options within a widget.


*Implementation*
Widget author can enable user-prefs and provide necessary
implementation(HTML/JS) within the widget. End-user specific user-prefs
will be kept in the dashboard json and saved in the DB with a user
reference(Similar to the dashboard personalization). This dashboard config
will have high priority during dashboard rendering than the default
configuration for the logged-in user.


*​End-user experience*
Widget content may flip similar to the previous implementation and render
the configuration UI.
User can fill whatever required data and save the configuration. This
particular widget will be rendered with the new configuration.

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

[Dev] [APIM] Incorrect resource mapping during api invokation when a resource with "/*" exists.

[Ayyoob Hamza]

Hi All,

In IoTS, We have exposed all the APIs through the API manager. In a
particular API, we have 2 API resources

1) POST /* with a scope X1
2) POST /{type}/operations with a scope X2.

When we invoke the second resource, API call ends up going to the first one
in the synapse layer. However after synapse forwards it to the backend, it
ends up to the correct resource in the Jax-rs.
The issue we are facing in here is that during scope validation it picks up
the wrong resource.

So this made me wondered why is the mapping is correctly evaluated in the
tomcat but not in the synapse layer. Do we have a bug here? or was it an
architecture decision to go with the first matching resource.

Are there any solutions to pick the best possible matching resource in the
synapse layer?

Thanks
*Ayyoob Hamza*
*Senior Software Engineer*
WSO2 Inc.; http://wso2.com
email: ayy...@wso2.com cell: +94 77 1681010 <%2B94%2077%207779495>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] How can we add multi language support in javascript files

[Prasanna Dangalla]

Hi All,

Kind reminder on this. What should we follow to do internationalization in
javascript code ?

@UUF Team: Shall we come to a final decision regarding this.

Thanks

*Prasanna Dangalla*
Senior Software Engineer, WSO2, Inc.; http://wso2.com/
lean.enterprise.middleware


*cell: +94 718 11 27 51*
*twitter: @prasa77*

On Sun, Mar 26, 2017 at 9:50 AM, Ruwan Abeykoon  wrote:

> Hi All,
> Interesting article about similar requirement[1]
>
> [1] http://nerds.airbnb.com/slides-and-video-from-spike-brehms-tech-talk/
>
> Cheers,
> Ruwan
>
> On Fri, Mar 24, 2017 at 10:55 PM, Prasanna Dangalla 
> wrote:
>
>>
>>
>> On Fri, Mar 24, 2017 at 6:34 PM Manuranga Perera  wrote:
>>
>>> We need to bring whole i18n (combined all lang files) to the UI and
>>> cache it.
>>>
>>
>> Bringing the whole thing will be an expensive operation in the fist time
>> before caching them, IMO we should load page wise and then cache them. WDYT
>> ?
>>
>>>
>>>
>>> On Fri, Mar 24, 2017 at 8:40 AM, Nuwandi Wickramasinghe <
>>> nuwan...@wso2.com> wrote:
>>>
>>>
>>>
>>> On Fri, Mar 24, 2017 at 1:49 PM, Nuwan Dias  wrote:
>>>
>>>
>>>
>>> On Fri, Mar 24, 2017 at 1:23 PM, Ruwan Abeykoon  wrote:
>>>
>>> Hi All,
>>> What if,
>>> i18n is handled on the server side only, and encode the relevant
>>> localized strings into HTML by the server-side (js or hbs).
>>> Client side libraries only read the string values already in the client
>>> locale within HTML DOM itself and just render the data. No client-side i18n.
>>>
>>> I have a situation where a part of the DOM is created in client side JS.
>>> In that case this wouldn't work.
>>>
>>>
>>> What is would be the limitations?
>>>
>>>
>>> Limitations would be for SPAs where the rendering is done at the client
>>> side. Which would basically mean that SPAs can't have localization.
>>>
>>>
>>> Cheers,
>>> Ruwan
>>>
>>> On Fri, Mar 24, 2017 at 11:54 AM, Nipuna Chandradasa 
>>> wrote:
>>>
>>> API of somekind(Rest or a http service endpoint), That we have to think
>>> about,  that exposes a functionality to retrieve i18n as a json object to
>>> layout level or any other global level of the application. So on client
>>> side we can use the i18n language details anywhere.
>>> We can get the language data from the browser.. that's how we do it
>>> anyway i think. We get the i18n based on the what language browser has
>>> configured to use.
>>>
>>> Thank you,
>>>
>>> On Fri, Mar 24, 2017 at 10:14 AM, Prasanna Dangalla 
>>> wrote:
>>>
>>> On Fri, Mar 24, 2017 at 12:53 AM, Nipuna Chandradasa 
>>> wrote:
>>>
>>> I don't think there is a feasible solution rather than loading i18n
>>> config file as a json object to the client side in the beginning of the
>>> app... i think from uuf side we can provide a api for that... WDYT?
>>>
>>> API in the sense, what kind of an API ? Does this loads all the data
>>> into front end or are you thinking about a filtering mechanism for the
>>> language data by page before you send them to front end ?
>>>
>>>
>>> On Thu, Mar 23, 2017 at 5:29 PM, SajithAR Ariyarathna >> > wrote:
>>>
>>> Currently UUF doesn't support i18n in client-side.
>>>
>>> @UUF Team,
>>> We need to come up with a solution for client-side i18n. Shall we start
>>> a discussion on this?
>>>
>>> Thanks.
>>>
>>>
>>> On Thu, Mar 23, 2017 at 4:36 PM, Prasanna Dangalla 
>>> wrote:
>>>
>>> Hi Sajith,
>>>
>>> This is for Client-side JS
>>>
>>> *Prasanna Dangalla*
>>> Senior Software Engineer, WSO2, Inc.; http://wso2.com/
>>> lean.enterprise.middleware
>>>
>>>
>>> *cell: +94 718 11 27 51*
>>> *twitter: @prasa77*
>>>
>>> On Thu, Mar 23, 2017 at 2:54 PM, SajithAR Ariyarathna >> > wrote:
>>>
>>> Hi Prasanna,
>>>
>>> Is there a mechanism defined to use something like i18n in javascript ?
>>>
>>> Server-side JS or Client-side JS?
>>>
>>> On Thu, Mar 23, 2017 at 11:02 AM, Ayesha Dissanayaka 
>>> wrote:
>>>
>>> Hi Prasanna,
>>>
>>> Similar discussion was started sometime back in [1].
>>> Issues in [2], [3] have some suggestions.
>>>
>>> [1] [Dev][UUF][IS-6] Enable i18n support in javascript
>>> [2] https://github.com/wso2/carbon-uuf/issues/160
>>> [3] https://github.com/wso2/carbon-uuf/issues/166
>>>
>>> @Ayesha: As I understood all these are done for server side JS, I'm
>>> wondering about client side JS.
>>>
>>>
>>>
>>> On Thu, Mar 23, 2017 at 10:46 AM, Pubudu Gunatilaka 
>>> wrote:
>>>
>>> Adding Manu and Sajith.
>>>
>>> On Thu, Mar 23, 2017 at 10:44 AM, Prasanna Dangalla 
>>> wrote:
>>>
>>> Hi Nisala,
>>>
>>> I was wondering how to include this in javascript files, not in hbs
>>> files. Is there a way to include in javascrip fiels ?
>>>
>>> Thanks
>>>
>>> *Prasanna Dangalla*
>>> Senior Software Engineer, WSO2, Inc.; http://wso2.com/
>>> lean.enterprise.middleware
>>>
>>>
>>> 

Re: [Dev] Dynamically redraw grid-stack content through UUFClient

[Rajith Roshan]

Hi,

I once had a offline discussion with SajithAR regarding zoneMaps not
initializing. He said zone maps are initialized once  because its a heavy
operation. He asked me to use renderFragment method without passing the
defzone attribute. I am not sure whether this will be a valid for your use
case.

Thanks !
Rajith

On Mon, Apr 24, 2017 at 11:45 AM, Udara Rathnayake  wrote:

> I tried populateZonesMap(); before calling renderFragmentImpl() inside
> UUFClient.renderFragment function. This works.
>
> Can we make this a configuration property if there is no other way?
>
>
>
>
> On Mon, Apr 24, 2017 at 10:56 AM, Udara Rathnayake 
> wrote:
>
>> ​Assume we have following grid-stack div rendered through the UUFClient.​
>>
>>
>>
>> ​
>> ​Now I want to re-render the same with a different content (Eg:- Change
>> the dashboard layout )
>> There is a grid-stack function to destroy the existing content[1].
>>
>> $('.grid-stack').data('gridstack').destroy(true);
>>>
>>
>> So this will basically remove following also, used by the UUF to append
>> the content.
>>
>> 
>>> 
>>>
>>
>> Tried manually adding above before calling the UUFClient.renderFragment()
>> but it seems not working. zonesMap which is there in the UUFClient still
>> contains the gridContent zone.
>>
>> Any idea?
>>
>> [1] https://github.com/troolee/gridstack.js/tree/develop/doc#des
>> troydetachgrid​
>>
>>
>
>
> --
> Regards,
> UdaraR
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Rajith Roshan
Software Engineer, WSO2 Inc.
Mobile: +94-72-642-8350 <%2B94-71-554-8430>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Architecture] WSO2 Message Broker 3.2.0 Released !!

[Hasitha Amal De Silva]

WSO2 Message Broker team is pleased to announce the release of WSO2 Message
Broker 3.2.0!

WSO2 Message Broker is a 100% open source, distributed, highly scalable,
portable, and interoperable product that supports JMS, AMQP and MQTT
standards for enterprise messaging and can be used in scenarios where
guaranteed message delivery is vital. It offers a flexible deployment model
that supports single node execution to massively distributed execution. It
provides a message brokering solution that enables asynchronous exchange of
communications or publishing of messages for timely access by subscribers.

For more information on WSO2 Message Broker and to download the product
please visit http://wso2.com/products/message-broker/. Also take a look at
the online product documentation on
https://docs.wso2.com/display/MB320/WSO2+Message+Broker+Documentation.

*How to Run*


   1.

   Extract the downloaded zip
   2.

   Go to the bin directory in the extracted folder
   3.

   Run the wso2server.sh or wso2server.bat as appropriate
   4.

   Launch a web browser and navigate to https://localhost:9443/carbon to
   access the admin console
   5.

   Use "admin", "admin" as the username and password to login as an admin


WSO2 Message Broker 3.2.0 includes following improvements and bug fixes.

*New Features*


   -

 [MB-1686]  - Message expiration
   (TTL)
   -

 [MB-1701]  - Per message
   acknowledgements
   -

 [MB-1687]  - Message re-delivery
   delay
   -

 [MB-1879]  - Support XA
   Transactions


*Bug Fixes*

https://wso2.org/jira/issues/?filter=13677


*Key Features of WSO2 Message Broker*
Standards Compliant, Portable, Interoperable Message Broker

   -

   Support for JMS v1.0 and v1.1 API
   -

   Advanced Message Queuing Protocol (AMQP) v0.91, a leading industry
   standard protocol for interoperable reliable messaging
   -

   Supports MQTT protocol with support for all QoS levels and retained
   messaging
   -

   Interoperability with many languages / platforms via AMQP clients for
   Java, .Net, C, C++, PHP, Ruby, Erlang and more

Support for Distributed Queues

   -

   Publishers and subscribers can connect to any broker
   -

   Support for in-order reliable message delivery
   -

   Support for strict and best effort (faster) delivery guarantees
   -

   Support for dead letter channel

Support for Publish/Subscribe Model (Topics)

   -

   Publishers and subscribers can connect to any broker nodes
   -

   Supports shared subscription

Management Console

   -

   Console to manage the cluster and to view statistics about the cluster
   -

   Support to browse publish/subscribe topics through management console
   -

   Support to create, delete queues and browse queues using management
   console
   -

   Support to display the messages inside a queue, send a messages to a
   queue, and purge the messages in the queue using management console

Manage & Monitor

   -

   Comprehensive management & monitoring Web console with enterprise-level
   security
   -

   Built-in collection and monitoring of standard access and performance
   statistics
   -

   JMX MBeans for key metrics monitoring and management
   -

   Flow control mechanism to control and safeguard from bursts of message
   loads
   -

   User based authorization support for queues
   -

   Role based authorization support for topics and users


*Known Issues*

All the open issues pertaining to WSO2 Message Broker are reported at the
following location:

   -

   Known Issues 

How You Can ContributeMailing Lists

Join our mailing list and correspond with the developers directly.

   -

   Developer List : dev@wso2.org | Subscribe | Mail Archive
   

Reporting Issues

We encourage you to report issues, documentation faults and feature
requests regarding WSO2 Message Broker through the public JIRA
.
Support

We are committed to ensuring that your enterprise middleware deployment is
completely supported from evaluation to production. Our unique approach
ensures that all support leverages our open development methodology and is
provided by the very same engineers who build the technology.

For more details and to take advantage of this unique opportunity please
visit http://wso2.com/support.

To learn more about WSO2 Message Broker and WSO2 support offerings please
visit http://wso2.com/products/message-broker/.

-- The WSO2 Message Broker Team --
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Dynamically redraw grid-stack content through UUFClient

[Udara Rathnayake]

Solution is to get the response (HTML) within the callback and do append
part within our logic.
Following is my onSuccess function,

onSuccess: function (data) {
> $('.grid-stack').append(data);
> }
> }
>

On Mon, Apr 24, 2017 at 5:21 PM, Rajith Roshan  wrote:

> Hi,
>
> I once had a offline discussion with SajithAR regarding zoneMaps not
> initializing. He said zone maps are initialized once  because its a heavy
> operation. He asked me to use renderFragment method without passing the
> defzone attribute. I am not sure whether this will be a valid for your use
> case.
>
> Thanks !
> Rajith
>
> On Mon, Apr 24, 2017 at 11:45 AM, Udara Rathnayake 
> wrote:
>
>> I tried populateZonesMap(); before calling renderFragmentImpl() inside
>> UUFClient.renderFragment function. This works.
>>
>> Can we make this a configuration property if there is no other way?
>>
>>
>>
>>
>> On Mon, Apr 24, 2017 at 10:56 AM, Udara Rathnayake 
>> wrote:
>>
>>> ​Assume we have following grid-stack div rendered through the UUFClient.​
>>>
>>>
>>>
>>> ​
>>> ​Now I want to re-render the same with a different content (Eg:- Change
>>> the dashboard layout )
>>> There is a grid-stack function to destroy the existing content[1].
>>>
>>> $('.grid-stack').data('gridstack').destroy(true);

>>>
>>> So this will basically remove following also, used by the UUF to append
>>> the content.
>>>
>>> 
 

>>>
>>> Tried manually adding above before calling the
>>> UUFClient.renderFragment() but it seems not working. zonesMap which is
>>> there in the UUFClient still contains the gridContent zone.
>>>
>>> Any idea?
>>>
>>> [1] https://github.com/troolee/gridstack.js/tree/develop/doc#des
>>> troydetachgrid​
>>>
>>>
>>
>>
>> --
>> Regards,
>> UdaraR
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Rajith Roshan
> Software Engineer, WSO2 Inc.
> Mobile: +94-72-642-8350 <%2B94-71-554-8430>
>



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

Re: [Dev] Adding File part support in MultipartFormDataFormatter

[Asanka Abeyweera]

Hi all,

I have attached the new patch to the CARBON-16121 with the review fixes. Can
you please review and commit?

On Mon, Apr 24, 2017 at 5:51 PM, Asanka Abeyweera  wrote:

> Hi Kishanthan/Kasun,
>
> Could you please review and approve the fix?
>
> On Mon, Apr 24, 2017 at 2:11 PM, Asanka Abeyweera 
> wrote:
>
>> Hi all,
>>
>> I have attached the fix done for CARBON-16121[1] in the corresponding
>> JIRA. Can you please review and commit?
>>
>> [1] https://wso2.org/jira/browse/CARBON-16121
>>
>> --
>> Asanka Abeyweera
>> Senior Software Engineer
>> WSO2 Inc.
>>
>> Phone: +94 712228648 <+94%2071%20222%208648>
>> Blog: a5anka.github.io
>>
>> 
>>
>
>
>
> --
> Asanka Abeyweera
> Senior Software Engineer
> WSO2 Inc.
>
> Phone: +94 712228648 <+94%2071%20222%208648>
> Blog: a5anka.github.io
>
> 
>



-- 
Asanka Abeyweera
Senior Software Engineer
WSO2 Inc.

Phone: +94 712228648
Blog: a5anka.github.io


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

Re: [Dev] Adding File part support in MultipartFormDataFormatter

[Asanka Abeyweera]

Hi Kishanthan/Kasun,

Could you please review and approve the fix?

On Mon, Apr 24, 2017 at 2:11 PM, Asanka Abeyweera  wrote:

> Hi all,
>
> I have attached the fix done for CARBON-16121[1] in the corresponding
> JIRA. Can you please review and commit?
>
> [1] https://wso2.org/jira/browse/CARBON-16121
>
> --
> Asanka Abeyweera
> Senior Software Engineer
> WSO2 Inc.
>
> Phone: +94 712228648 <+94%2071%20222%208648>
> Blog: a5anka.github.io
>
> 
>



-- 
Asanka Abeyweera
Senior Software Engineer
WSO2 Inc.

Phone: +94 712228648
Blog: a5anka.github.io


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

Re: [Dev] WSO2 Message Broker 3.2.0 RC2 Released !!

[Hasitha Amal De Silva]

Hi All,

Thanks for testing and verifying the WSO2 Message Broker 3.2.0 RC2. We are
closing the vote now. This vote has passed with 6+1s and 0 -1s. Therefore
we are proceeding with the WSO2 Message Broker 3.2.0 release.

6 +1
0 -1


On Mon, Apr 24, 2017 at 3:37 PM, Hasitha Hiranya  wrote:

> Hi all,
>
> Tested the following scenarios .
>
> 1. Failover for queues - with publish/subscribe
> 2. Failover for durable topic subscriptions - with publish/subscribe
>
> No issues found. So, +1 to release.
>
> Thanks
>
> On Mon, Apr 24, 2017 at 2:08 PM, Sasikala Kottegoda 
> wrote:
>
>> Hi all,
>>
>> Tested the following scenarios in distributed transactions.
>>
>>1. publish message to queue. Transactionally receive and publish to
>>another queue.
>>2. Publish errorneous message to the same queue. Keep recovering
>>messages until the malformed message gets moved to DLC.
>>
>>
>> [+] Stable - go ahead and release
>>
>> Thank you,
>> Sasikala
>>
>> On Thu, Apr 20, 2017 at 6:47 PM, Pamod Sylvester  wrote:
>>
>>> Hi Devs,
>>>
>>> This is the 2nd release candidate of WSO2 Message Broker 3.2.0.
>>>
>>> *This release fixes the following issues:*
>>> *https://wso2.org/jira/browse/MB-1910?filter=13675
>>> *
>>>
>>> *Known Issues:*
>>> *https://wso2.org/jira/browse/MB-1757?filter=13676
>>> *
>>>
>>> 
>>> Please download MB 3.2.0 RC2 and test the functionality and vote. The
>>> vote will be open for 72 hours or as needed.
>>>
>>> *Source & binary distribution files:*
>>> https://github.com/wso2/product-mb/releases/tag/v3.2.0-RC2
>>>
>>> *The tag to be voted upon:*
>>> https://github.com/wso2/product-mb/tree/v3.2.0-RC2
>>>
>>>
>>> [+] Stable - go ahead and release
>>> [-]  Broken - do not release (explain why)
>>>
>>> Thanks and Regards,
>>>
>>> --
>>> *Pamod Sylvester *
>>>
>>> *WSO2 Inc.; http://wso2.com *
>>> cell: +94 77 7779495 <077%20777%209495>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Sasikala Kottegoda
>> *Senior Software Engineer*
>> WSO2 Inc., http://wso2.com/
>> lean. enterprise. middleware
>> Mobile: +94 774835928 <+94%2077%20483%205928>
>>
>> [image: https://wso2.com/signature] 
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Hasitha Abeykoon*
> Senior Software Engineer; WSO2, Inc.; http://wso2.com
> *cell:* *+94 719363063*
> *blog: **abeykoon.blogspot.com* 
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Cheers,

Hasitha Amal De Silva
Senior Software Engineer
Mobile : +94772037426
Blog: http://devnutshell.tumblr.com/
WSO2 Inc.: http://wso2.com ( lean.enterprise.middleware. )
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [IDENTITY-5131] A solution for the possible deadlock due to session cleanup task

[Thanuja Jayasinghe]

Hi Ruwan,

On Mon, Apr 24, 2017 at 2:32 PM, Ruwan Abeykoon  wrote:

> Hi Dinali,
> Do we know any figures for
>  >> time taken by "deleteSTOREOperationsTask" operation
>
> We need to measure how long it takes to complete the data deletion per X
> number of records. Only then we could arrive at a correct strategy.
>
+1

> Having stored-procedure or handling it on queries does not make much
> difference.
> I would vote for changing the cleanup task schedule and making the delete
> query optimizations.
>

When we handle it this way we have to figure out following things,

- Only one server in the cluster should run this operation. If two nodes
run this operation at the same time there is a possibility for deadlock.
- Then if that node is down for some reason, one of the other nodes must
run this as this tables get huge number of entries each day
- Need to provide a way to configure the time which this operation need to
run. Do we need to configure this in every node? (Only one node will run
this operation)

Having stored procedures to handle this, does not have above complexities.


> Cheers,
> Ruwan
>
> On Mon, Apr 24, 2017 at 2:17 PM, Thanuja Jayasinghe 
> wrote:
>
>> Hi Dinali,
>>
>> +1 for the 2nd solution.
>>
>> Since this operation takes a considerable amount of time, it's better to
>> handle this from the DB side during the off-peak hours.
>>
>> Thanks,
>> Thanuja
>>
>> On Fri, Apr 21, 2017 at 11:12 AM, Dinali Dabarera 
>> wrote:
>>
>>> Hi All,
>>>
>>> There is a public issue reported in [3],  due to a deadlock happened in
>>> the long-running scenario.
>>>
>>> This deadlock occurs due the time taken by "deleteSTOREOperationsTask"
>>> operation which is responsible for cleaning session data which is scheduled
>>> daily.
>>>
>>> We have currently come up with two solutions for this deadlock problem,
>>>
>>>1. *We can add a property like " start-time" in the identity.xml
>>>file, In code level we can start the cleanup task during an off-peak 
>>> time.*
>>>2. *We can create two stored procedures to handle session data
>>>cleanup tasks and run them as scheduled jobs during the off-peak hours.*
>>>
>>> Here both 1 and 2 have advantages and disadvantages.
>>>
>>> In a cluster scenario, if we implement *1 *one server
>>> should only run this task.. if all of them run at the same time, there is a
>>> chance for deadlock.
>>>  If we implement *2, *the clean-up is handled by the data
>>> source itself, without interrupting any IS operations.
>>>
>>> What will be the best solution, out of 1 and 2 for this deadlock
>>> scenario? Please leave your ideas on this.
>>>
>>> [3] https://wso2.org/jira/browse/IDENTITY-5131
>>>
>>> Thank you.!
>>>
>>> Regards.
>>>
>>> --
>>> *Dinali Rosemin Dabarera*
>>> Software Engineer
>>> WSO2 Lanka (pvt) Ltd.
>>> Web: http://wso2.com/
>>> Email : gdrdabar...@gmail.com
>>> LinkedIn 
>>> Mobile: +94770198933 <+94%2077%20019%208933>
>>>
>>>
>>>
>>>
>>> 
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>> --
>> *Thanuja Lakmal*
>> Senior Software Engineer
>> WSO2 Inc. http://wso2.com/
>> *lean.enterprise.middleware*
>> Mobile: +94715979891 +94758009992
>>
>
>
>
> --
>
> *Ruwan Abeykoon*
> *Associate Director/Architect**,*
> *WSO2, Inc. http://wso2.com  *
> *lean.enterprise.middleware.*
>
>

Thanks,
Thanuja
-- 
*Thanuja Lakmal*
Senior Software Engineer
WSO2 Inc. http://wso2.com/
*lean.enterprise.middleware*
Mobile: +94715979891 +94758009992
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [IDENTITY-5131] A solution for the possible deadlock due to session cleanup task

[Johann Nallathamby]

On Mon, Apr 24, 2017 at 3:40 PM, Thanuja Jayasinghe 
wrote:

> Hi Ruwan,
>
> On Mon, Apr 24, 2017 at 2:32 PM, Ruwan Abeykoon  wrote:
>
>> Hi Dinali,
>> Do we know any figures for
>>  >> time taken by "deleteSTOREOperationsTask" operation
>>
>> We need to measure how long it takes to complete the data deletion per X
>> number of records. Only then we could arrive at a correct strategy.
>>
> +1
>
>> Having stored-procedure or handling it on queries does not make much
>> difference.
>> I would vote for changing the cleanup task schedule and making the delete
>> query optimizations.
>>
>
> When we handle it this way we have to figure out following things,
>
> - Only one server in the cluster should run this operation. If two nodes
> run this operation at the same time there is a possibility for deadlock.
> - Then if that node is down for some reason, one of the other nodes must
> run this as this tables get huge number of entries each day
> - Need to provide a way to configure the time which this operation need to
> run. Do we need to configure this in every node? (Only one node will run
> this operation)
>

Need to have a coordinated ntask with input provided as a cron expression.
Better we discuss this with Anjana/DataTeam and find out if there are any
caveats in this approach and then decide. Because I don't want to put
effort and then find problems in customer's production environment. We
could be better off writing stored procedures for all database types. But
no harm trying this.

Regards,
Johann.


>
> Having stored procedures to handle this, does not have above complexities.
>
>
>> Cheers,
>> Ruwan
>>
>> On Mon, Apr 24, 2017 at 2:17 PM, Thanuja Jayasinghe 
>> wrote:
>>
>>> Hi Dinali,
>>>
>>> +1 for the 2nd solution.
>>>
>>> Since this operation takes a considerable amount of time, it's better to
>>> handle this from the DB side during the off-peak hours.
>>>
>>> Thanks,
>>> Thanuja
>>>
>>> On Fri, Apr 21, 2017 at 11:12 AM, Dinali Dabarera 
>>> wrote:
>>>
 Hi All,

 There is a public issue reported in [3],  due to a deadlock happened in
 the long-running scenario.

 This deadlock occurs due the time taken by "deleteSTOREOperationsTask"
 operation which is responsible for cleaning session data which is scheduled
 daily.

 We have currently come up with two solutions for this deadlock problem,

1. *We can add a property like " start-time" in the identity.xml
file, In code level we can start the cleanup task during an off-peak 
 time.*
2. *We can create two stored procedures to handle session data
cleanup tasks and run them as scheduled jobs during the off-peak hours.*

 Here both 1 and 2 have advantages and disadvantages.

 In a cluster scenario, if we implement *1 *one server
 should only run this task.. if all of them run at the same time, there is a
 chance for deadlock.
  If we implement *2, *the clean-up is handled by the data
 source itself, without interrupting any IS operations.

 What will be the best solution, out of 1 and 2 for this deadlock
 scenario? Please leave your ideas on this.

 [3] https://wso2.org/jira/browse/IDENTITY-5131

 Thank you.!

 Regards.

 --
 *Dinali Rosemin Dabarera*
 Software Engineer
 WSO2 Lanka (pvt) Ltd.
 Web: http://wso2.com/
 Email : gdrdabar...@gmail.com
 LinkedIn 
 Mobile: +94770198933 <+94%2077%20019%208933>




 














>>>
>>>
>>> --
>>> *Thanuja Lakmal*
>>> Senior Software Engineer
>>> WSO2 Inc. http://wso2.com/
>>> *lean.enterprise.middleware*
>>> Mobile: +94715979891 +94758009992
>>>
>>
>>
>>
>> --
>>
>> *Ruwan Abeykoon*
>> *Associate Director/Architect**,*
>> *WSO2, Inc. http://wso2.com  *
>> *lean.enterprise.middleware.*
>>
>>
>
> Thanks,
> Thanuja
> --
> *Thanuja Lakmal*
> Senior Software Engineer
> WSO2 Inc. http://wso2.com/
> *lean.enterprise.middleware*
> Mobile: +94715979891 +94758009992
>



-- 
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] WSO2 Message Broker 3.2.0 RC2 Released !!

[Hasitha Hiranya]

Hi all,

Tested the following scenarios .

1. Failover for queues - with publish/subscribe
2. Failover for durable topic subscriptions - with publish/subscribe

No issues found. So, +1 to release.

Thanks

On Mon, Apr 24, 2017 at 2:08 PM, Sasikala Kottegoda 
wrote:

> Hi all,
>
> Tested the following scenarios in distributed transactions.
>
>1. publish message to queue. Transactionally receive and publish to
>another queue.
>2. Publish errorneous message to the same queue. Keep recovering
>messages until the malformed message gets moved to DLC.
>
>
> [+] Stable - go ahead and release
>
> Thank you,
> Sasikala
>
> On Thu, Apr 20, 2017 at 6:47 PM, Pamod Sylvester  wrote:
>
>> Hi Devs,
>>
>> This is the 2nd release candidate of WSO2 Message Broker 3.2.0.
>>
>> *This release fixes the following issues:*
>> *https://wso2.org/jira/browse/MB-1910?filter=13675
>> *
>>
>> *Known Issues:*
>> *https://wso2.org/jira/browse/MB-1757?filter=13676
>> *
>>
>> 
>> Please download MB 3.2.0 RC2 and test the functionality and vote. The
>> vote will be open for 72 hours or as needed.
>>
>> *Source & binary distribution files:*
>> https://github.com/wso2/product-mb/releases/tag/v3.2.0-RC2
>>
>> *The tag to be voted upon:*
>> https://github.com/wso2/product-mb/tree/v3.2.0-RC2
>>
>>
>> [+] Stable - go ahead and release
>> [-]  Broken - do not release (explain why)
>>
>> Thanks and Regards,
>>
>> --
>> *Pamod Sylvester *
>>
>> *WSO2 Inc.; http://wso2.com *
>> cell: +94 77 7779495 <077%20777%209495>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Sasikala Kottegoda
> *Senior Software Engineer*
> WSO2 Inc., http://wso2.com/
> lean. enterprise. middleware
> Mobile: +94 774835928
>
> [image: https://wso2.com/signature] 
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Hasitha Abeykoon*
Senior Software Engineer; WSO2, Inc.; http://wso2.com
*cell:* *+94 719363063*
*blog: **abeykoon.blogspot.com* 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Message Broker 3.2.0 RC2 Released !!

[Sasikala Kottegoda]

Hi all,

Tested the following scenarios in distributed transactions.

   1. publish message to queue. Transactionally receive and publish to
   another queue.
   2. Publish errorneous message to the same queue. Keep recovering
   messages until the malformed message gets moved to DLC.


[+] Stable - go ahead and release

Thank you,
Sasikala

On Thu, Apr 20, 2017 at 6:47 PM, Pamod Sylvester  wrote:

> Hi Devs,
>
> This is the 2nd release candidate of WSO2 Message Broker 3.2.0.
>
> *This release fixes the following issues:*
> *https://wso2.org/jira/browse/MB-1910?filter=13675
> *
>
> *Known Issues:*
> *https://wso2.org/jira/browse/MB-1757?filter=13676
> *
>
> 
> Please download MB 3.2.0 RC2 and test the functionality and vote. The
> vote will be open for 72 hours or as needed.
>
> *Source & binary distribution files:*
> https://github.com/wso2/product-mb/releases/tag/v3.2.0-RC2
>
> *The tag to be voted upon:*
> https://github.com/wso2/product-mb/tree/v3.2.0-RC2
>
>
> [+] Stable - go ahead and release
> [-]  Broken - do not release (explain why)
>
> Thanks and Regards,
>
> --
> *Pamod Sylvester *
>
> *WSO2 Inc.; http://wso2.com *
> cell: +94 77 7779495 <077%20777%209495>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Sasikala Kottegoda
*Senior Software Engineer*
WSO2 Inc., http://wso2.com/
lean. enterprise. middleware
Mobile: +94 774835928

[image: https://wso2.com/signature] 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [IDENTITY-5131] A solution for the possible deadlock due to session cleanup task

[Ruwan Abeykoon]

Hi Dinali,
Do we know any figures for
 >> time taken by "deleteSTOREOperationsTask" operation

We need to measure how long it takes to complete the data deletion per X
number of records. Only then we could arrive at a correct strategy.
Having stored-procedure or handling it on queries does not make much
difference.
I would vote for changing the cleanup task schedule and making the delete
query optimizations.

Cheers,
Ruwan

On Mon, Apr 24, 2017 at 2:17 PM, Thanuja Jayasinghe 
wrote:

> Hi Dinali,
>
> +1 for the 2nd solution.
>
> Since this operation takes a considerable amount of time, it's better to
> handle this from the DB side during the off-peak hours.
>
> Thanks,
> Thanuja
>
> On Fri, Apr 21, 2017 at 11:12 AM, Dinali Dabarera  wrote:
>
>> Hi All,
>>
>> There is a public issue reported in [3],  due to a deadlock happened in
>> the long-running scenario.
>>
>> This deadlock occurs due the time taken by "deleteSTOREOperationsTask"
>> operation which is responsible for cleaning session data which is scheduled
>> daily.
>>
>> We have currently come up with two solutions for this deadlock problem,
>>
>>1. *We can add a property like " start-time" in the identity.xml
>>file, In code level we can start the cleanup task during an off-peak 
>> time.*
>>2. *We can create two stored procedures to handle session data
>>cleanup tasks and run them as scheduled jobs during the off-peak hours.*
>>
>> Here both 1 and 2 have advantages and disadvantages.
>>
>> In a cluster scenario, if we implement *1 *one server should
>> only run this task.. if all of them run at the same time, there is a chance
>> for deadlock.
>>  If we implement *2, *the clean-up is handled by the data
>> source itself, without interrupting any IS operations.
>>
>> What will be the best solution, out of 1 and 2 for this deadlock
>> scenario? Please leave your ideas on this.
>>
>> [3] https://wso2.org/jira/browse/IDENTITY-5131
>>
>> Thank you.!
>>
>> Regards.
>>
>> --
>> *Dinali Rosemin Dabarera*
>> Software Engineer
>> WSO2 Lanka (pvt) Ltd.
>> Web: http://wso2.com/
>> Email : gdrdabar...@gmail.com
>> LinkedIn 
>> Mobile: +94770198933 <+94%2077%20019%208933>
>>
>>
>>
>>
>> 
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>
>
> --
> *Thanuja Lakmal*
> Senior Software Engineer
> WSO2 Inc. http://wso2.com/
> *lean.enterprise.middleware*
> Mobile: +94715979891 +94758009992
>



-- 

*Ruwan Abeykoon*
*Associate Director/Architect**,*
*WSO2, Inc. http://wso2.com  *
*lean.enterprise.middleware.*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [IDENTITY-5131] A solution for the possible deadlock due to session cleanup task

[Thanuja Jayasinghe]

Hi Dinali,

+1 for the 2nd solution.

Since this operation takes a considerable amount of time, it's better to
handle this from the DB side during the off-peak hours.

Thanks,
Thanuja

On Fri, Apr 21, 2017 at 11:12 AM, Dinali Dabarera  wrote:

> Hi All,
>
> There is a public issue reported in [3],  due to a deadlock happened in
> the long-running scenario.
>
> This deadlock occurs due the time taken by "deleteSTOREOperationsTask"
> operation which is responsible for cleaning session data which is scheduled
> daily.
>
> We have currently come up with two solutions for this deadlock problem,
>
>1. *We can add a property like " start-time" in the identity.xml
>file, In code level we can start the cleanup task during an off-peak time.*
>2. *We can create two stored procedures to handle session data cleanup
>tasks and run them as scheduled jobs during the off-peak hours.*
>
> Here both 1 and 2 have advantages and disadvantages.
>
> In a cluster scenario, if we implement *1 *one server should
> only run this task.. if all of them run at the same time, there is a chance
> for deadlock.
>  If we implement *2, *the clean-up is handled by the data
> source itself, without interrupting any IS operations.
>
> What will be the best solution, out of 1 and 2 for this deadlock scenario?
> Please leave your ideas on this.
>
> [3] https://wso2.org/jira/browse/IDENTITY-5131
>
> Thank you.!
>
> Regards.
>
> --
> *Dinali Rosemin Dabarera*
> Software Engineer
> WSO2 Lanka (pvt) Ltd.
> Web: http://wso2.com/
> Email : gdrdabar...@gmail.com
> LinkedIn 
> Mobile: +94770198933 <+94%2077%20019%208933>
>
>
>
>
> 
>
>
>
>
>
>
>
>
>
>
>
>
>
>


-- 
*Thanuja Lakmal*
Senior Software Engineer
WSO2 Inc. http://wso2.com/
*lean.enterprise.middleware*
Mobile: +94715979891 +94758009992
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Adding File part support in MultipartFormDataFormatter

[Asanka Abeyweera]

Hi all,

I have attached the fix done for CARBON-16121[1] in the corresponding JIRA.
Can you please review and commit?

[1] https://wso2.org/jira/browse/CARBON-16121

-- 
Asanka Abeyweera
Senior Software Engineer
WSO2 Inc.

Phone: +94 712228648
Blog: a5anka.github.io


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

[Dev] Changes for carbon-transport release-4.3.0-m1

[Irunika Weeraratne]

Hi all,
There is a requirement to implement WebSocket session user properties
for *"[Architecture]
[Identity Cloud] Outbound on-premise user store"*.
Currently, MSF4J is in carbon-transport release-4.3.0-m1. We need to add
current changes to that release version.
So first I tried to merge the current master branch to release-4.3.0-m1.
But there are many file changes and it seems it is too risky to merge them
and do the change within this limited time.
So is it ok *not* to merge master branch to release-4.3.0-m1 branch and do
the necessary change only in release-4.3.0-m1 branch and do a milestone
release for now?
WDYT?

Thanks,
Irunika
*Irunika Weeraratne*
*Software Engineer | WSO2, Inc. *
*Email : irun...@wso2.com *
*LinkedIn : https://lk.linkedin.com/in/irunika
*
*Mobile : +94712403314*
*Lean . Enterprise . Middleware*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] VizGrammar polluting the JS global scope

[Jerad Rutnam]

+1, yes that would be a better. Thanks for pointing Udara.

On Mon, Apr 24, 2017 at 9:05 AM, Tharik Kanaka  wrote:

> +1
> functions like getPieMark, getPieMidText were added to access from other
> chart types in order to draw combinations (eg:- including a best fit line
> for a scatter plot) other functions are from util js. Let's include all
> those functions to vizg and include vizg to global scope.
>
> On Sun, Apr 23, 2017 at 12:38 AM, Udara Rathnayake 
> wrote:
>
>> Looks like we are doing the $subject.
>>
>> While looking at the window object, noticed we have following[1], Shall
>> we try to update the library by only adding vizg to the global scope?
>>
>> [1]
>> "d3", "vg", "getPieMark", "getPieMidText", "getPieText", "getAreaMark",
>> "getBarMark", "getStackBarMark", "getGroupBarMark", "calculateBarGap",
>> "getLineMark", "getTopoJson", "getMapMark", "getMapSignals",
>> "getMapPredicates", "getMapLegends", "loadGeoMapCodes", "getMapCode",
>> "getScatterMark", "getScatterToolTipMark", "checkConfig", "buildTable",
>> "buildData", "getSymbolMark", "getSignals", "bindTooltip", "createTooltip",
>> "cumulativeOffset", "getXYAxes", "getXYScales", "getRangeSignals",
>> "getRangeMark", "getLegend", "drawChart", "arc", "area", "bar", "vizg",
>> "line", "map", "number", "scatter", "table", "extend", "stack"
>>
>> --
>> Regards,
>> UdaraR
>>
>
>
>
> --
>
> *Tharik Kanaka*
>
> WSO2, Inc | lean . enterprise . middleware
>
> Email: tha...@wso2.com | Web: www.wso2.com
>



-- 
*Jerad Rutnam*
*Senior Software Engineer*

WSO2 Inc.
lean | enterprise | middleware
M : +94 77 959 1609 | E : je...@wso2.com | W : www.wso2.com


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

Re: [Dev] Dynamically redraw grid-stack content through UUFClient

[Udara Rathnayake]

I tried populateZonesMap(); before calling renderFragmentImpl() inside
UUFClient.renderFragment function. This works.

Can we make this a configuration property if there is no other way?




On Mon, Apr 24, 2017 at 10:56 AM, Udara Rathnayake  wrote:

> ​Assume we have following grid-stack div rendered through the UUFClient.​
>
>
>
> ​
> ​Now I want to re-render the same with a different content (Eg:- Change
> the dashboard layout )
> There is a grid-stack function to destroy the existing content[1].
>
> $('.grid-stack').data('gridstack').destroy(true);
>>
>
> So this will basically remove following also, used by the UUF to append
> the content.
>
> 
>> 
>>
>
> Tried manually adding above before calling the UUFClient.renderFragment()
> but it seems not working. zonesMap which is there in the UUFClient still
> contains the gridContent zone.
>
> Any idea?
>
> [1] https://github.com/troolee/gridstack.js/tree/develop/doc#
> destroydetachgrid​
>
>


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