date:20141208

Re: [Architecture] Nest ESB connector

2014-12-08 Thread Kasun Indrasiri

What's the verification use case/s for this connector?

On Mon, Dec 8, 2014 at 5:37 PM, Shakila Sivagnanarajah 
wrote:

> Hi Vanjikumaran,
>
> Thanks for your review and comments.
> I will correct the matters given in your comments.
>
> On Mon, Dec 8, 2014 at 5:03 PM, Vanjikumaran Sivajothy 
> wrote:
>
>> Hi shakila,
>>
>> I see there are some miss matching on the standard that we follow, Hence
>> please correct the changes on bellow mention item as we discussed
>>
>> 1) Change the Init Method to get the token from the user(Currently it is
>> hard coded)
>> 2) Add licensing header
>> 3) Maintain the consistency on naming on methods.
>> 4) Add .ignore file for git
>> 5) Change the README file with more accurate information. example :-
>> 6) Add the integration test information into the given document.
>> 7) All the files should be modified and intent correctly
>>
>>
>>
>>
>>
>> On Mon, Dec 8, 2014 at 4:23 PM, Vanjikumaran Sivajothy 
>> wrote:
>>
>>> Hi Shakila,
>>>
>>> Please give me access to comment on your document.
>>>
>>> Thank you,
>>> Best Regards,
>>> Vanji
>>>
>>> On Mon, Dec 8, 2014 at 3:46 PM, Samisa Abeysinghe 
>>> wrote:
>>>
 Please have the final review and see what the outcomes are...

 Thanks,
 Samisa...


 Samisa Abeysinghe

 Vice President Delivery

 WSO2 Inc.
 http://wso2.com


 On Mon, Dec 8, 2014 at 3:39 PM, Shakila Sivagnanarajah <
 shak...@wso2.com> wrote:

> Hi all,
>
> According to the milestone plan given in [1], the implementation is
> completed.
>
> Since there are two operations listed in [2] depend on actual nest
> device, the relevant automated test cases of those methods are not
> included.
>
> Please find the git-hub repository [3] and documentation [4] given
> below.
>
> [1]
> https://docs.google.com/a/wso2.com/spreadsheets/d/18OxjEOnd02DQCQi2LM_dGhP1Gy-JBjHYfnHofXBvlM4/edit#gid=0
>
> [2] View last connection information(of Thermostat) and View last
> manual test status (of Smoke + CO alarm).
>
> [3] https://github.com/Shakila/NestESBConnector
>
> [4]
> https://docs.google.com/a/wso2.com/document/d/18OcKKkARdJEH80Wzs-j9IeZw6Gp561QWi-rGje9hXEI/edit
>
>
> Thank you.
>
> --
> Shakila Sivagnanarajah
> Associate Software Engineer
> Mobile :+94 (0) 770 760240
> shak...@wso2.com
>


>>>
>>>
>>> --
>>> Sivajothy Vanjikumaran
>>> *Senior Software Engineer*
>>> *Integration Technologies Team*
>>> *WSO2 Inc. http://wso2.com *
>>> *Mobile:(+94)777219209*
>>> [image: Facebook]  [image:
>>> Twitter]  [image: LinkedIn]
>>>  [image:
>>> Blogger]  [image: SlideShare]
>>> 
>>>
>>> This communication may contain privileged or other
>>> confidential information and is intended exclusively for the addressee/s.
>>> If you are not the intended recipient/s, or believe that you may
>>> have received this communication in error, please reply to the
>>> sender indicating that fact and delete the copy you received and in
>>> addition, you should not print, copy, re-transmit, disseminate, or
>>> otherwise use the information contained in this communication.
>>> Internet communications cannot be guaranteed to be timely, secure, error
>>> or virus-free. The sender does not accept liability for any errors
>>> or omissions
>>>
>>
>>
>>
>> --
>> Sivajothy Vanjikumaran
>> *Senior Software Engineer*
>> *Integration Technologies Team*
>> *WSO2 Inc. http://wso2.com *
>> *Mobile:(+94)777219209*
>> [image: Facebook]  [image:
>> Twitter]  [image: LinkedIn]
>>  [image:
>> Blogger]  [image: SlideShare]
>> 
>>
>> This communication may contain privileged or other
>> confidential information and is intended exclusively for the addressee/s.
>> If you are not the intended recipient/s, or believe that you may
>> have received this communication in error, please reply to the
>> sender indicating that fact and delete the copy you received and in
>> addition, you should not print, copy, re-transmit, disseminate, or
>> otherwise use the information contained in this communication.
>> Internet communications cannot be guaranteed to be timely, secure, error
>> or virus-free. The sender does not accept liability for any errors
>> or omissions
>>
>
>
>
> --
> Shakila Sivagnanarajah
> Associate Software Engineer
> Mobile :+94 (0) 770 760240
> shak...@wso2.com
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2

Re: [Architecture] RFC: Building a Generic Configurable UI Gadget for Analytics

2014-12-08 Thread Mohammed Fawsan

+1

On Mon, Dec 8, 2014 at 12:14 PM, Srinath Perera  wrote:

> In #2, I mean to say we will go and choose two columns in the table as X
> and Y axis. E.g. In the plot, I have used year as the X axis and GDP as the
> Y axis.
>
> --Srinath
>
> On Mon, Dec 8, 2014 at 12:12 PM, Srinath Perera  wrote:
>
>> Currently to visualize the data, users have to write their own gadgets.
>> If a advanced user this is OK, but not for all. Specially, things like
>> drill downs need complicated planning.
>>
>> I believe it is possible to start with data in tabular form, and write a
>> generic Gadget that let user configure and create his own data chart with
>> filters and drill downs.
>>
>> Chart could look like following ( some of the controls can be hidden
>> under configure button)
>>
>> 
>> Lets work though an example.
>>
>> 1) Key idea is that we load data to the Gadget as a table (always).
>> Following can be a example data.
>> *Country* *Year* *GDP* *Population* *LifeExpect*  Sri Lanka 2004 20
>> 19435000 73  Sri Lanka 2005 24 19644000 73  Sri Lanka 2006 28 19858000 73  
>> Sri
>> Lanka 2007 32 20039000 73
>> 2) When Gadget is loaded, it shows the data as a table. User can select
>> and add a data type and fields.  Following are some example.
>>
>>1. Line - two Numerical  fields
>>2. Bar - one numerical, one categorical field
>>3. Scatter - two numerical fields
>>4. Map - Location field + categorical or numerical field
>>5. Graph - two categorical or string fields that provide links
>>
>>
>> 3) Let user add more information to the chart using other fields in the
>> table
>>
>>1. Add  color (Categorical field) or shade (numerical field) to the
>>plot (e.g. Use different color for each country)
>>2. Point Size - Numerical field (e.g. Adjust the point size in the
>>scatter plot according to the population)
>>3. Label - any field
>>
>> 4) Then he can add filters based on a variable. Then the chart will have
>> sliders (for numerical data) and tick buttons (for categorical data). When
>> those sliders are changed they will change the chart.
>>
>> 5) Final step is define drill downs. Drill downs are done using two
>> columns in the table that has hierarchical relationships. (e.g. Country and
>> State fields, Year and month fields) . We need users to select two of those
>> fields and tell us about relationships and then we can code the support of
>> drill downs.
>>
>> When above steps are done, user save configs and save it in the DataViz
>> store as a visualisation, so others can pull it and use it.
>>
>> This will not cover all cases, but IMO it will cover 80% and also a very
>> good tool for demos etc.
>>
>> Please comment
>>
>> --Srinath
>>
>>
>>
>> --
>> 
>> Blog: http://srinathsview.blogspot.com twitter:@srinath_perera
>> Site: http://people.apache.org/~hemapani/
>> Photos: http://www.flickr.com/photos/hemapani/
>> Phone: 0772360902
>>
>
>
>
> --
> 
> Blog: http://srinathsview.blogspot.com twitter:@srinath_perera
> Site: http://people.apache.org/~hemapani/
> Photos: http://www.flickr.com/photos/hemapani/
> Phone: 0772360902
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
Mohammed Fawsan
Software Engineering Intern,
Faculty of Engineering, University of Peradeniya.
+94771121195
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

[Architecture] ESB message processor configure number of messages per an attempt

2014-12-08 Thread Udara Liyanage

Hi,

Message processors as I experienced process single message per a given
interval [1] . How about giving the capability of processing configured
number of messages per an interval. Please note that changing interval is
not the same.


[1] https://docs.wso2.com/display/ESB460/Message+Sampling+Processor

-- 

Udara Liyanage
Software Engineer
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware

web: http://udaraliyanage.wordpress.com
phone: +94 71 443 6897
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] Nest ESB connector

2014-12-08 Thread Shakila Sivagnanarajah

Hi Vanjikumaran,

Thanks for your review and comments.
I will correct the matters given in your comments.

On Mon, Dec 8, 2014 at 5:03 PM, Vanjikumaran Sivajothy 
wrote:

> Hi shakila,
>
> I see there are some miss matching on the standard that we follow, Hence
> please correct the changes on bellow mention item as we discussed
>
> 1) Change the Init Method to get the token from the user(Currently it is
> hard coded)
> 2) Add licensing header
> 3) Maintain the consistency on naming on methods.
> 4) Add .ignore file for git
> 5) Change the README file with more accurate information. example :-
> 6) Add the integration test information into the given document.
> 7) All the files should be modified and intent correctly
>
>
>
>
>
> On Mon, Dec 8, 2014 at 4:23 PM, Vanjikumaran Sivajothy 
> wrote:
>
>> Hi Shakila,
>>
>> Please give me access to comment on your document.
>>
>> Thank you,
>> Best Regards,
>> Vanji
>>
>> On Mon, Dec 8, 2014 at 3:46 PM, Samisa Abeysinghe 
>> wrote:
>>
>>> Please have the final review and see what the outcomes are...
>>>
>>> Thanks,
>>> Samisa...
>>>
>>>
>>> Samisa Abeysinghe
>>>
>>> Vice President Delivery
>>>
>>> WSO2 Inc.
>>> http://wso2.com
>>>
>>>
>>> On Mon, Dec 8, 2014 at 3:39 PM, Shakila Sivagnanarajah >> > wrote:
>>>
 Hi all,

 According to the milestone plan given in [1], the implementation is
 completed.

 Since there are two operations listed in [2] depend on actual nest
 device, the relevant automated test cases of those methods are not
 included.

 Please find the git-hub repository [3] and documentation [4] given
 below.

 [1]
 https://docs.google.com/a/wso2.com/spreadsheets/d/18OxjEOnd02DQCQi2LM_dGhP1Gy-JBjHYfnHofXBvlM4/edit#gid=0

 [2] View last connection information(of Thermostat) and View last
 manual test status (of Smoke + CO alarm).

 [3] https://github.com/Shakila/NestESBConnector

 [4]
 https://docs.google.com/a/wso2.com/document/d/18OcKKkARdJEH80Wzs-j9IeZw6Gp561QWi-rGje9hXEI/edit


 Thank you.

 --
 Shakila Sivagnanarajah
 Associate Software Engineer
 Mobile :+94 (0) 770 760240
 shak...@wso2.com

>>>
>>>
>>
>>
>> --
>> Sivajothy Vanjikumaran
>> *Senior Software Engineer*
>> *Integration Technologies Team*
>> *WSO2 Inc. http://wso2.com *
>> *Mobile:(+94)777219209*
>> [image: Facebook]  [image:
>> Twitter]  [image: LinkedIn]
>>  [image:
>> Blogger]  [image: SlideShare]
>> 
>>
>> This communication may contain privileged or other
>> confidential information and is intended exclusively for the addressee/s.
>> If you are not the intended recipient/s, or believe that you may
>> have received this communication in error, please reply to the
>> sender indicating that fact and delete the copy you received and in
>> addition, you should not print, copy, re-transmit, disseminate, or
>> otherwise use the information contained in this communication.
>> Internet communications cannot be guaranteed to be timely, secure, error
>> or virus-free. The sender does not accept liability for any errors
>> or omissions
>>
>
>
>
> --
> Sivajothy Vanjikumaran
> *Senior Software Engineer*
> *Integration Technologies Team*
> *WSO2 Inc. http://wso2.com *
> *Mobile:(+94)777219209*
> [image: Facebook]  [image: Twitter]
>  [image: LinkedIn]
>  [image:
> Blogger]  [image: SlideShare]
> 
>
> This communication may contain privileged or other
> confidential information and is intended exclusively for the addressee/s.
> If you are not the intended recipient/s, or believe that you may
> have received this communication in error, please reply to the
> sender indicating that fact and delete the copy you received and in
> addition, you should not print, copy, re-transmit, disseminate, or
> otherwise use the information contained in this communication.
> Internet communications cannot be guaranteed to be timely, secure, error
> or virus-free. The sender does not accept liability for any errors
> or omissions
>



-- 
Shakila Sivagnanarajah
Associate Software Engineer
Mobile :+94 (0) 770 760240
shak...@wso2.com
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] Nest ESB connector

2014-12-08 Thread Vanjikumaran Sivajothy

Hi shakila,

I see there are some miss matching on the standard that we follow, Hence
please correct the changes on bellow mention item as we discussed

1) Change the Init Method to get the token from the user(Currently it is
hard coded)
2) Add licensing header
3) Maintain the consistency on naming on methods.
4) Add .ignore file for git
5) Change the README file with more accurate information. example :-
6) Add the integration test information into the given document.
7) All the files should be modified and intent correctly

On Mon, Dec 8, 2014 at 4:23 PM, Vanjikumaran Sivajothy 
wrote:

> Hi Shakila,
>
> Please give me access to comment on your document.
>
> Thank you,
> Best Regards,
> Vanji
>
> On Mon, Dec 8, 2014 at 3:46 PM, Samisa Abeysinghe  wrote:
>
>> Please have the final review and see what the outcomes are...
>>
>> Thanks,
>> Samisa...
>>
>>
>> Samisa Abeysinghe
>>
>> Vice President Delivery
>>
>> WSO2 Inc.
>> http://wso2.com
>>
>>
>> On Mon, Dec 8, 2014 at 3:39 PM, Shakila Sivagnanarajah 
>> wrote:
>>
>>> Hi all,
>>>
>>> According to the milestone plan given in [1], the implementation is
>>> completed.
>>>
>>> Since there are two operations listed in [2] depend on actual nest
>>> device, the relevant automated test cases of those methods are not
>>> included.
>>>
>>> Please find the git-hub repository [3] and documentation [4] given below.
>>>
>>> [1]
>>> https://docs.google.com/a/wso2.com/spreadsheets/d/18OxjEOnd02DQCQi2LM_dGhP1Gy-JBjHYfnHofXBvlM4/edit#gid=0
>>>
>>> [2] View last connection information(of Thermostat) and View last
>>> manual test status (of Smoke + CO alarm).
>>>
>>> [3] https://github.com/Shakila/NestESBConnector
>>>
>>> [4]
>>> https://docs.google.com/a/wso2.com/document/d/18OcKKkARdJEH80Wzs-j9IeZw6Gp561QWi-rGje9hXEI/edit
>>>
>>>
>>> Thank you.
>>>
>>> --
>>> Shakila Sivagnanarajah
>>> Associate Software Engineer
>>> Mobile :+94 (0) 770 760240
>>> shak...@wso2.com
>>>
>>
>>
>
>
> --
> Sivajothy Vanjikumaran
> *Senior Software Engineer*
> *Integration Technologies Team*
> *WSO2 Inc. http://wso2.com *
> *Mobile:(+94)777219209*
> [image: Facebook]  [image: Twitter]
>  [image: LinkedIn]
>  [image:
> Blogger]  [image: SlideShare]
> 
>
> This communication may contain privileged or other
> confidential information and is intended exclusively for the addressee/s.
> If you are not the intended recipient/s, or believe that you may
> have received this communication in error, please reply to the
> sender indicating that fact and delete the copy you received and in
> addition, you should not print, copy, re-transmit, disseminate, or
> otherwise use the information contained in this communication.
> Internet communications cannot be guaranteed to be timely, secure, error
> or virus-free. The sender does not accept liability for any errors
> or omissions
>

-- 
Sivajothy Vanjikumaran
*Senior Software Engineer*
*Integration Technologies Team*
*WSO2 Inc. http://wso2.com *
*Mobile:(+94)777219209*
[image: Facebook]  [image: Twitter]
 [image: LinkedIn]
 [image:
Blogger]  [image: SlideShare]

This communication may contain privileged or other confidential information
and is intended exclusively for the addressee/s. If you are not the
intended recipient/s, or believe that you may have received this
communication in error, please reply to the sender indicating that fact and
delete the copy you received and in addition, you should not print,
copy, re-transmit, disseminate, or otherwise use the information contained
in this communication. Internet communications cannot be guaranteed to be
timely, secure, error or virus-free. The sender does not accept liability
for any errors or omissions
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] Nest ESB connector

2014-12-08 Thread Shakila Sivagnanarajah

Hi,
Now you can comment on it.

On Mon, Dec 8, 2014 at 4:23 PM, Vanjikumaran Sivajothy 
wrote:

> Hi Shakila,
>
> Please give me access to comment on your document.
>
> Thank you,
> Best Regards,
> Vanji
>
> On Mon, Dec 8, 2014 at 3:46 PM, Samisa Abeysinghe  wrote:
>
>> Please have the final review and see what the outcomes are...
>>
>> Thanks,
>> Samisa...
>>
>>
>> Samisa Abeysinghe
>>
>> Vice President Delivery
>>
>> WSO2 Inc.
>> http://wso2.com
>>
>>
>> On Mon, Dec 8, 2014 at 3:39 PM, Shakila Sivagnanarajah 
>> wrote:
>>
>>> Hi all,
>>>
>>> According to the milestone plan given in [1], the implementation is
>>> completed.
>>>
>>> Since there are two operations listed in [2] depend on actual nest
>>> device, the relevant automated test cases of those methods are not
>>> included.
>>>
>>> Please find the git-hub repository [3] and documentation [4] given below.
>>>
>>> [1]
>>> https://docs.google.com/a/wso2.com/spreadsheets/d/18OxjEOnd02DQCQi2LM_dGhP1Gy-JBjHYfnHofXBvlM4/edit#gid=0
>>>
>>> [2] View last connection information(of Thermostat) and View last
>>> manual test status (of Smoke + CO alarm).
>>>
>>> [3] https://github.com/Shakila/NestESBConnector
>>>
>>> [4]
>>> https://docs.google.com/a/wso2.com/document/d/18OcKKkARdJEH80Wzs-j9IeZw6Gp561QWi-rGje9hXEI/edit
>>>
>>>
>>> Thank you.
>>>
>>> --
>>> Shakila Sivagnanarajah
>>> Associate Software Engineer
>>> Mobile :+94 (0) 770 760240
>>> shak...@wso2.com
>>>
>>
>>
>
>
> --
> Sivajothy Vanjikumaran
> *Senior Software Engineer*
> *Integration Technologies Team*
> *WSO2 Inc. http://wso2.com *
> *Mobile:(+94)777219209*
> [image: Facebook]  [image: Twitter]
>  [image: LinkedIn]
>  [image:
> Blogger]  [image: SlideShare]
> 
>
> This communication may contain privileged or other
> confidential information and is intended exclusively for the addressee/s.
> If you are not the intended recipient/s, or believe that you may
> have received this communication in error, please reply to the
> sender indicating that fact and delete the copy you received and in
> addition, you should not print, copy, re-transmit, disseminate, or
> otherwise use the information contained in this communication.
> Internet communications cannot be guaranteed to be timely, secure, error
> or virus-free. The sender does not accept liability for any errors
> or omissions
>



-- 
Shakila Sivagnanarajah
Associate Software Engineer
Mobile :+94 (0) 770 760240
shak...@wso2.com
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] Nest ESB connector

2014-12-08 Thread Vanjikumaran Sivajothy

Hi Shakila,

Please give me access to comment on your document.

Thank you,
Best Regards,
Vanji

On Mon, Dec 8, 2014 at 3:46 PM, Samisa Abeysinghe  wrote:

> Please have the final review and see what the outcomes are...
>
> Thanks,
> Samisa...
>
>
> Samisa Abeysinghe
>
> Vice President Delivery
>
> WSO2 Inc.
> http://wso2.com
>
>
> On Mon, Dec 8, 2014 at 3:39 PM, Shakila Sivagnanarajah 
> wrote:
>
>> Hi all,
>>
>> According to the milestone plan given in [1], the implementation is
>> completed.
>>
>> Since there are two operations listed in [2] depend on actual nest
>> device, the relevant automated test cases of those methods are not
>> included.
>>
>> Please find the git-hub repository [3] and documentation [4] given below.
>>
>> [1]
>> https://docs.google.com/a/wso2.com/spreadsheets/d/18OxjEOnd02DQCQi2LM_dGhP1Gy-JBjHYfnHofXBvlM4/edit#gid=0
>>
>> [2] View last connection information(of Thermostat) and View last manual
>> test status (of Smoke + CO alarm).
>>
>> [3] https://github.com/Shakila/NestESBConnector
>>
>> [4]
>> https://docs.google.com/a/wso2.com/document/d/18OcKKkARdJEH80Wzs-j9IeZw6Gp561QWi-rGje9hXEI/edit
>>
>>
>> Thank you.
>>
>> --
>> Shakila Sivagnanarajah
>> Associate Software Engineer
>> Mobile :+94 (0) 770 760240
>> shak...@wso2.com
>>
>
>

-- 
Sivajothy Vanjikumaran
*Senior Software Engineer*
*Integration Technologies Team*
*WSO2 Inc. http://wso2.com *
*Mobile:(+94)777219209*
[image: Facebook]  [image: Twitter]
 [image: LinkedIn]
 [image:
Blogger]  [image: SlideShare]

This communication may contain privileged or other confidential information
and is intended exclusively for the addressee/s. If you are not the
intended recipient/s, or believe that you may have received this
communication in error, please reply to the sender indicating that fact and
delete the copy you received and in addition, you should not print,
copy, re-transmit, disseminate, or otherwise use the information contained
in this communication. Internet communications cannot be guaranteed to be
timely, secure, error or virus-free. The sender does not accept liability
for any errors or omissions
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] Nest ESB connector

2014-12-08 Thread Samisa Abeysinghe

Please have the final review and see what the outcomes are...

Thanks,
Samisa...


Samisa Abeysinghe

Vice President Delivery

WSO2 Inc.
http://wso2.com


On Mon, Dec 8, 2014 at 3:39 PM, Shakila Sivagnanarajah 
wrote:

> Hi all,
>
> According to the milestone plan given in [1], the implementation is
> completed.
>
> Since there are two operations listed in [2] depend on actual nest device,
> the relevant automated test cases of those methods are not included.
>
> Please find the git-hub repository [3] and documentation [4] given below.
>
> [1]
> https://docs.google.com/a/wso2.com/spreadsheets/d/18OxjEOnd02DQCQi2LM_dGhP1Gy-JBjHYfnHofXBvlM4/edit#gid=0
>
> [2] View last connection information(of Thermostat) and View last manual
> test status (of Smoke + CO alarm).
>
> [3] https://github.com/Shakila/NestESBConnector
>
> [4]
> https://docs.google.com/a/wso2.com/document/d/18OcKKkARdJEH80Wzs-j9IeZw6Gp561QWi-rGje9hXEI/edit
>
>
> Thank you.
>
> --
> Shakila Sivagnanarajah
> Associate Software Engineer
> Mobile :+94 (0) 770 760240
> shak...@wso2.com
>
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

[Architecture] Nest ESB connector

2014-12-08 Thread Shakila Sivagnanarajah

Hi all,

According to the milestone plan given in [1], the implementation is
completed.

Since there are two operations listed in [2] depend on actual nest device,
the relevant automated test cases of those methods are not included.

Please find the git-hub repository [3] and documentation [4] given below.

[1]
https://docs.google.com/a/wso2.com/spreadsheets/d/18OxjEOnd02DQCQi2LM_dGhP1Gy-JBjHYfnHofXBvlM4/edit#gid=0

[2] View last connection information(of Thermostat) and View last manual
test status (of Smoke + CO alarm).

[3] https://github.com/Shakila/NestESBConnector

[4]
https://docs.google.com/a/wso2.com/document/d/18OcKKkARdJEH80Wzs-j9IeZw6Gp561QWi-rGje9hXEI/edit


Thank you.

-- 
Shakila Sivagnanarajah
Associate Software Engineer
Mobile :+94 (0) 770 760240
shak...@wso2.com
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] Nest ESB connector

Re: [Architecture] RFC: Building a Generic Configurable UI Gadget for Analytics

[Architecture] ESB message processor configure number of messages per an attempt

Re: [Architecture] Nest ESB connector

Re: [Architecture] Nest ESB connector

Re: [Architecture] Nest ESB connector

Re: [Architecture] Nest ESB connector

Re: [Architecture] Nest ESB connector

[Architecture] Nest ESB connector

9 matches

Site Navigation

Mail list logo

Footer information