[Dev] Selenium UI Testing [GREG/ES - Publisher]

2016-02-09 Thread Lahiru J Ekanayake
Hi ,

I'm writing selenium tests for GREG publisher UI. When implementing UI test
cases, some situations we need to check whether some elements exists,
before click or make any operations on them.
Selenium provides, *driver.findElement(By.id("elemnt_id")) *
method to find any element by id. Problem is if that element is not exist ,
it will return an error, saying
*org.openqa.selenium.NoSuchElementException: Unable to locate
element:{"method":"id","selector":"elemnt_id"}*

Is there any way to check the existence of any element , without catching
the error? .




Regards



-- 



*Lahiru J Ekanayake**Software Engineer*
Mobile : +94 (0) 77 8812629 / +94(0) 778509547
Email : lahi...@wso2.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] Selenium UI Testing [GREG/ES - Publisher]

2016-02-09 Thread Krishantha Samaraweera
You can use WebDriverWait

see -
http://stackoverflow.com/questions/7991522/selenium-webdriver-test-if-element-is-present

Thanks,
Krishantha.


On Tue, Feb 9, 2016 at 3:01 PM, Lahiru J Ekanayake  wrote:

> Hi ,
>
> I'm writing selenium tests for GREG publisher UI. When implementing UI
> test cases, some situations we need to check whether some elements exists,
> before click or make any operations on them.
> Selenium provides, *driver.findElement(By.id("elemnt_id")) *
> method to find any element by id. Problem is if that element is not exist
> , it will return an error, saying
> *org.openqa.selenium.NoSuchElementException: Unable to locate
> element:{"method":"id","selector":"elemnt_id"}*
>
> Is there any way to check the existence of any element , without catching
> the error? .
>
>
>
>
> Regards
>
>
>
> --
>
>
>
> *Lahiru J Ekanayake**Software Engineer*
> Mobile : +94 (0) 77 8812629 / +94(0) 778509547
> Email : lahi...@wso2.com
> WSO2, Inc.; http://wso2.com/
> lean . enterprise . middleware.
>
>


-- 
Krishantha Samaraweera
Senior Technical Lead - Test Automation
Mobile: +94 77 7759918
WSO2, Inc.; http://wso2.com/
lean . enterprise . middleware.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] Selenium UI Testing [GREG/ES - Publisher]

2016-02-09 Thread Rajeenthini Satkunam
Hi lahiru,

If you need to check that element is present in the current UI, You can go
with this method *isElementPresent(By by)*.

for example in your case *driver.**isElementPresent**(By.id("elemnt_id")) *will
return true if the element is present in current UI or else it will return
false.Hope it will help you.

For your reference

[1] -
https://github.com/wso2/product-ds/blob/master/modules/integration/tests-ui-integration/ui-test-utils/src/main/java/org/wso2/ds/ui/integration/util/DSWebDriver.java#L47

On Tue, Feb 9, 2016 at 3:01 PM, Lahiru J Ekanayake  wrote:

> Hi ,
>
> I'm writing selenium tests for GREG publisher UI. When implementing UI
> test cases, some situations we need to check whether some elements exists,
> before click or make any operations on them.
> Selenium provides, *driver.findElement(By.id("elemnt_id")) *
> method to find any element by id. Problem is if that element is not exist
> , it will return an error, saying
> *org.openqa.selenium.NoSuchElementException: Unable to locate
> element:{"method":"id","selector":"elemnt_id"}*
>
> Is there any way to check the existence of any element , without catching
> the error? .
>
>
>
>
> Regards
>
>
>
> --
>
>
>
> *Lahiru J Ekanayake**Software Engineer*
> Mobile : +94 (0) 77 8812629 / +94(0) 778509547
> Email : lahi...@wso2.com
> WSO2, Inc.; http://wso2.com/
> lean . enterprise . middleware.
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

*Thank You.*

*Rajeenthini Satkunam*

*Associate Software Engineer | WSO2*


*E:rajeenth...@wso2.com *

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


[Dev] [DAS] Null Pointer Exception whe creating a file-tail receiver

2016-02-09 Thread Supun Sethunga
​Hi,

$subject happens in DAS-3.0.2-SNAPSHOT, when there are *no*
meta-data/correlation-data defined in the stream definition.

Attached [1] is a PR with a fix. please review and merge.

[1] https://github.com/wso2/carbon-analytics-common/pull/181

Thanks,
Supun

-- 
*Supun Sethunga*
Software Engineer
WSO2, Inc.
http://wso2.com/
lean | enterprise | middleware
Mobile : +94 716546324
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] Selenium UI Testing [GREG/ES - Publisher]

2016-02-09 Thread Lahiru J Ekanayake
Hi ,

I have already tried with wait.until method. It will also return timeout
exception searching after given timeout.  I think anyway we have to use try
block to check existences of  an element. I have looked for a method that
returns ture/false on a given element existence . I'm not sure that kind of
method already in selenium.
Thank you for your help.

Regards

On Tue, Feb 9, 2016 at 3:13 PM, Rajeenthini Satkunam 
wrote:

> Hi lahiru,
>
> If you need to check that element is present in the current UI, You can go
> with this method *isElementPresent(By by)*.
>
> for example in your case *driver.**isElementPresent*
> *(By.id("elemnt_id")) *will return true if the element is present in
> current UI or else it will return false.Hope it will help you.
>
> For your reference
>
> [1] -
> https://github.com/wso2/product-ds/blob/master/modules/integration/tests-ui-integration/ui-test-utils/src/main/java/org/wso2/ds/ui/integration/util/DSWebDriver.java#L47
>
> On Tue, Feb 9, 2016 at 3:01 PM, Lahiru J Ekanayake 
> wrote:
>
>> Hi ,
>>
>> I'm writing selenium tests for GREG publisher UI. When implementing UI
>> test cases, some situations we need to check whether some elements exists,
>> before click or make any operations on them.
>> Selenium provides, *driver.findElement(By.id("elemnt_id")) *
>> method to find any element by id. Problem is if that element is not exist
>> , it will return an error, saying
>> *org.openqa.selenium.NoSuchElementException: Unable to locate
>> element:{"method":"id","selector":"elemnt_id"}*
>>
>> Is there any way to check the existence of any element , without catching
>> the error? .
>>
>>
>>
>>
>> Regards
>>
>>
>>
>> --
>>
>>
>>
>> *Lahiru J Ekanayake**Software Engineer*
>> Mobile : +94 (0) 77 8812629 / +94(0) 778509547
>> Email : lahi...@wso2.com
>> WSO2, Inc.; http://wso2.com/
>> lean . enterprise . middleware.
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
>
> *Thank You.*
>
> *Rajeenthini Satkunam*
>
> *Associate Software Engineer | WSO2*
>
>
> *E:rajeenth...@wso2.com *
>
> *M :+94770832823 <%2B94770832823>   *
>
>


-- 



*Lahiru J Ekanayake**Software Engineer*
Mobile : +94 (0) 77 8812629 / +94(0) 778509547
Email : lahi...@wso2.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] Issue when starting the server - SSLException: Connection has been shutdown

2016-02-09 Thread Tharindu Edirisinghe
Hi Dilini,

The reason for not being able to access the portal is the self signed
certificate of the server is not being trusted. If you need to access the
portal with this configuration, you can export the public certificate of
the server and import it to the cacerts of the JVM.

Here's the command to export the public certificate.

*keytool -export -alias wso2carbon -file  -keystore
/repository/resources/security/wso2carbon.jks -storepass
wso2carbon*

Here's the command to import the public certificate of the server into the
cacerts of JVM.

*keytool -import -trustcacerts -keystore
/jre/lib/security/cacerts -storepass changeit -noprompt -alias
wso2carbon -file *

After doing this, you should be able to access the portal.


The startup error can be avoided by commenting out only the "tcpSSL"
property in the H2 database configuration in carbon.xml file.

   * *

This is the detailed error printed when SSL debug logs are enabled.


[2016-02-09 12:12:35,942]  INFO
{org.wso2.carbon.h2.osgi.console.ConsoleService} -  Starting H2 TCP
server...
org.h2.server.TcpServerThread@58e793e4 Connect
[2016-02-09 12:12:35,945]  INFO
{org.wso2.carbon.h2.osgi.console.ConsoleService} -  Starting H2 PG server...
Ignoring unavailable cipher suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
Ignoring unavailable cipher suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA
Ignoring unavailable cipher suite: TLS_ECDH_RSA_WITH_AES_256_CBC_SHA
Ignoring unavailable cipher suite: TLS_DHE_DSS_WITH_AES_256_CBC_SHA256
Ignoring unavailable cipher suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA256
Ignoring unavailable cipher suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
Ignoring unavailable cipher suite: TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA384
Connect
Ignoring unavailable cipher suite: TLS_RSA_WITH_AES_256_CBC_SHA256
Ignoring unavailable cipher suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
Disconnect
Close
Ignoring unavailable cipher suite: TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384
Ignoring unavailable cipher suite: TLS_DHE_DSS_WITH_AES_256_CBC_SHA
Ignoring unavailable cipher suite: TLS_ECDH_RSA_WITH_AES_256_CBC_SHA384
Ignoring unavailable cipher suite: TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA
Ignoring unavailable cipher suite: TLS_RSA_WITH_AES_256_CBC_SHA
H2 TCP Server (ssl://127.0.1.1:9092) thread, received EOFException: error
H2 TCP Server (ssl://127.0.1.1:9092) thread, handling exception:
javax.net.ssl.SSLHandshakeException: Remote host closed connection during
handshake
H2 TCP Server (ssl://127.0.1.1:9092) thread,* SEND TLSv1 ALERT:  fatal,
description = handshake_failure*
H2 TCP Server (ssl://127.0.1.1:9092) thread, WRITE: TLSv1 Alert, length = 2
[Raw write]: length = 7
: 15 03 01 00 02 02 28   ..(
H2 TCP Server (ssl://127.0.1.1:9092) thread, called closeSocket()
javax.net.ssl.SSLException: Connection has been shutdown:
javax.net.ssl.SSLHandshakeException: Remote host closed connection during
handshake
at sun.security.ssl.SSLSocketImpl.checkEOF(SSLSocketImpl.java:1496)
at sun.security.ssl.SSLSocketImpl.checkWrite(SSLSocketImpl.java:1508)
at sun.security.ssl.AppOutputStream.write(AppOutputStream.java:70)
at
java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)
at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140)
at java.io.DataOutputStream.flush(DataOutputStream.java:123)
at org.h2.value.Transfer.flush(Transfer.java:85)
at org.h2.server.TcpServerThread.sendError(TcpServerThread.java:197)
at org.h2.server.TcpServerThread.run(TcpServerThread.java:129)
at java.lang.Thread.run(Thread.java:745)
Caused by: javax.net.ssl.SSLHandshakeException: Remote host closed
connection during handshake
at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:953)
at
sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1332)
at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:889)
at sun.security.ssl.AppInputStream.read(AppInputStream.java:102)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:235)
at java.io.BufferedInputStream.read(BufferedInputStream.java:254)
at java.io.DataInputStream.readInt(DataInputStream.java:387)
at org.h2.value.Transfer.readInt(Transfer.java:145)
at org.h2.server.TcpServerThread.run(TcpServerThread.java:71)
... 1 more
Caused by: java.io.EOFException: SSL peer shut down incorrectly
at sun.security.ssl.InputRecord.read(InputRecord.java:482)
at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:934)
... 9 more
org.h2.server.TcpServerThread@58e793e4 Disconnect
org.h2.server.TcpServerThread@58e793e4 Close


>From the above log, according to [1] and [2] it seems the server cannot
deal with the ciphers suite (i.e TLSv1).

Hope this helps.


[1]
http://stackoverflow.com/questions/21245796/javax-net-ssl-sslhandshakeexception-remote-host-closed-connection-during-handsh
[2]
http://stackoverflow.com/questions/31883713/i-received-javax-net-ssl-sslhandshake

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

2016-02-09 Thread Akalanka Pagoda Arachchi
WSO2 Message Broker team is pleased to announce the release of WSO2 Message
Broker 3.1.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 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/MB310/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.1.0 includes following improvements and bug fixes.

New Features

   -

   [MB-1588 ] - Forcefully Delete
   Subscriptions
   -

   [MB-1592 ] - Support for
   PostgreSQL as the Message Store


Bug Fixes

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

Improvements

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

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




-- 
*Darshana Akalanka Pagoda Arachchi,*
*Software Engineer*
*078-4721791*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] Selenium UI Testing [GREG/ES - Publisher]

2016-02-09 Thread Ayesha Dissanayaka
Hi Lahiru,

As Rajeenthini has mentioned above, in product-es also we have written a
method *isElementPresent* to check the existence of an element by wrapping
the try-catch at *findElement *method.

Further, Below mail threads may be helpful for you while writing Selenium
UI test.

   - [ES- Integration Test] Custom WebDriver Class for UI test Automation
   -
   [Dev][ES] Selenium UI Integration Test Generation
   - Dev] Reduce the execution speed of Web Driver

[1]
https://github.com/wso2/product-es/blob/514b439c0b608bca4cca81f7c588a7dfeec598ad/modules/integration/tests-ui-integration/ui-test-utils/src/main/java/org/wso2/es/ui/integration/util/ESWebDriver.java#L74

Thanks!
-Ayesha



On Tue, Feb 9, 2016 at 3:34 PM, Lahiru J Ekanayake  wrote:

> Hi ,
>
> I have already tried with wait.until method. It will also return timeout
> exception searching after given timeout.  I think anyway we have to use try
> block to check existences of  an element. I have looked for a method that
> returns ture/false on a given element existence . I'm not sure that kind of
> method already in selenium.
> Thank you for your help.
>
> Regards
>
> On Tue, Feb 9, 2016 at 3:13 PM, Rajeenthini Satkunam  > wrote:
>
>> Hi lahiru,
>>
>> If you need to check that element is present in the current UI, You can
>> go with this method *isElementPresent(By by)*.
>>
>> for example in your case *driver.**isElementPresent*
>> *(By.id("elemnt_id")) *will return true if the element is present in
>> current UI or else it will return false.Hope it will help you.
>>
>> For your reference
>>
>> [1] -
>> https://github.com/wso2/product-ds/blob/master/modules/integration/tests-ui-integration/ui-test-utils/src/main/java/org/wso2/ds/ui/integration/util/DSWebDriver.java#L47
>>
>> On Tue, Feb 9, 2016 at 3:01 PM, Lahiru J Ekanayake 
>> wrote:
>>
>>> Hi ,
>>>
>>> I'm writing selenium tests for GREG publisher UI. When implementing UI
>>> test cases, some situations we need to check whether some elements exists,
>>> before click or make any operations on them.
>>> Selenium provides, *driver.findElement(By.id("elemnt_id")) *
>>> method to find any element by id. Problem is if that element is not
>>> exist , it will return an error, saying
>>> *org.openqa.selenium.NoSuchElementException: Unable to locate
>>> element:{"method":"id","selector":"elemnt_id"}*
>>>
>>> Is there any way to check the existence of any element , without
>>> catching the error? .
>>>
>>>
>>>
>>>
>>> Regards
>>>
>>>
>>>
>>> --
>>>
>>>
>>>
>>> *Lahiru J Ekanayake**Software Engineer*
>>> Mobile : +94 (0) 77 8812629 / +94(0) 778509547
>>> Email : lahi...@wso2.com
>>> WSO2, Inc.; http://wso2.com/
>>> lean . enterprise . middleware.
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>>
>> *Thank You.*
>>
>> *Rajeenthini Satkunam*
>>
>> *Associate Software Engineer | WSO2*
>>
>>
>> *E:rajeenth...@wso2.com *
>>
>> *M :+94770832823 <%2B94770832823>   *
>>
>>
>
>
> --
>
>
>
> *Lahiru J Ekanayake**Software Engineer*
> Mobile : +94 (0) 77 8812629 / +94(0) 778509547
> Email : lahi...@wso2.com
> WSO2, Inc.; http://wso2.com/
> lean . enterprise . middleware.
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Ayesha Dissanayaka*
Software Engineer,
WSO2, Inc : http://wso2.com

20, Palmgrove Avenue, Colombo 3
E-Mail: aye...@wso2.com 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] Selenium UI Testing [GREG/ES - Publisher]

2016-02-09 Thread Lahiru Cooray
Hi Lahiru,

I have faced the similar issue and I noticed that some times the
dynamically loaded elements are not loading when we are using wait.until()
without a driver refresh() So I used a similar code snipped like this:



 WebDriverWait tempWait = new WebDriverWait(driver, 5); //5 is the waiting
time in seconds

for (int i = 0; i < 2; i++) {
try {

tempWait.until(ExpectedConditions.visibilityOfElementLocated(By.cssSelector(
"a[href*='/store/assets/webapp/" + appId + "']")));
driver.navigate().refresh();
break;
} catch (org.openqa.selenium.TimeoutException e) {
//Expected error when no element found
}
}

Here i'm trying two times and waiting a fair time to load the element.


On Tue, Feb 9, 2016 at 3:34 PM, Lahiru J Ekanayake  wrote:

> Hi ,
>
> I have already tried with wait.until method. It will also return timeout
> exception searching after given timeout.  I think anyway we have to use try
> block to check existences of  an element. I have looked for a method that
> returns ture/false on a given element existence . I'm not sure that kind of
> method already in selenium.
> Thank you for your help.
>
> Regards
>
> On Tue, Feb 9, 2016 at 3:13 PM, Rajeenthini Satkunam  > wrote:
>
>> Hi lahiru,
>>
>> If you need to check that element is present in the current UI, You can
>> go with this method *isElementPresent(By by)*.
>>
>> for example in your case *driver.**isElementPresent*
>> *(By.id("elemnt_id")) *will return true if the element is present in
>> current UI or else it will return false.Hope it will help you.
>>
>> For your reference
>>
>> [1] -
>> https://github.com/wso2/product-ds/blob/master/modules/integration/tests-ui-integration/ui-test-utils/src/main/java/org/wso2/ds/ui/integration/util/DSWebDriver.java#L47
>>
>> On Tue, Feb 9, 2016 at 3:01 PM, Lahiru J Ekanayake 
>> wrote:
>>
>>> Hi ,
>>>
>>> I'm writing selenium tests for GREG publisher UI. When implementing UI
>>> test cases, some situations we need to check whether some elements exists,
>>> before click or make any operations on them.
>>> Selenium provides, *driver.findElement(By.id("elemnt_id")) *
>>> method to find any element by id. Problem is if that element is not
>>> exist , it will return an error, saying
>>> *org.openqa.selenium.NoSuchElementException: Unable to locate
>>> element:{"method":"id","selector":"elemnt_id"}*
>>>
>>> Is there any way to check the existence of any element , without
>>> catching the error? .
>>>
>>>
>>>
>>>
>>> Regards
>>>
>>>
>>>
>>> --
>>>
>>>
>>>
>>> *Lahiru J Ekanayake**Software Engineer*
>>> Mobile : +94 (0) 77 8812629 / +94(0) 778509547
>>> Email : lahi...@wso2.com
>>> WSO2, Inc.; http://wso2.com/
>>> lean . enterprise . middleware.
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>>
>> *Thank You.*
>>
>> *Rajeenthini Satkunam*
>>
>> *Associate Software Engineer | WSO2*
>>
>>
>> *E:rajeenth...@wso2.com *
>>
>> *M :+94770832823 <%2B94770832823>   *
>>
>>
>
>
> --
>
>
>
> *Lahiru J Ekanayake**Software Engineer*
> Mobile : +94 (0) 77 8812629 / +94(0) 778509547
> Email : lahi...@wso2.com
> WSO2, Inc.; http://wso2.com/
> lean . enterprise . middleware.
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Lahiru Cooray*
Software Engineer
WSO2, Inc.;http://wso2.com/
lean.enterprise.middleware

Mobile: +94 715 654154
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


[Dev] wso2-axis2 - 1.6.1-wso2v17 released !

2016-02-09 Thread Manuri Amaya Perera
Hi devs,

Please note $subject.

org.apache.axis2
axis2
1.6.1-wso2v17

​Thank you.​

-- 

*Manuri Amaya Perera*

*Software Engineer*

*WSO2 Inc.*

*Blog: http://manuriamayaperera.blogspot.com
*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] MB C5-migration new folder structure

2016-02-09 Thread Hasitha Hiranya
Hi Asitha,

Yep. If we install above 4 features on a vanila Cabon server, it should
become a MB server.

Thanks

On Tue, Feb 9, 2016 at 4:26 PM, Asitha Nanayakkara  wrote:

> Adding dev@
>
> On Tue, Feb 9, 2016 at 4:03 PM, Hasitha Hiranya  wrote:
>
>> hi Asitha,
>>
>> Ah, so there is no need for components be in a separate repo?
>> I think the reason to keep components in a separate repo was to share the
>> components between various product level features.
>>
>> Agreed, if we want to do a release for a specific feature then we have to
> release the whole product. If we have a separate repo for features we won't
> have that issue. At the moment we don't have such requirement. Will this be
> a valid requriment in future?
>
> Even though we are moving all the components and features to product mb
> repo still we will have four features. Namely they are
> Andes feature - andes core functionality will be implemented in this
> feature
> MB-UI feature - ui components of MB
> AMQP-feature - AMQP transport implementation
> MQTT feature - MQTT transport implementation
>
> So these features can be used in other products. For instance we can have
> a lean MB with Andes feature and MQTT feature.
>
> Regards,
> Asitha
>
>
>
>> Let us use Dev/Architecture mail threads to discuss these.
>>
>> Thanks
>>
>> On Tue, Feb 9, 2016 at 3:55 PM, Asitha Nanayakkara 
>> wrote:
>>
>>> Hi all,
>>>
>>> We (Hemika and I) are in the process of bootstrapping the product.
>>>
>>> We have come up with a folder structure for the project[2]. We will be
>>> working on product-mb/c5-migration branch [1].
>>>
>>> We will be moving all the components and features to product-mb repo
>>> (since we don't have any shared features in there) and eventually will get
>>> rid of the cabon-business-messaging repo
>>>
>>> Any concerns,thoughts and suggestions on the approach?
>>>
>>> [1] https://github.com/wso2/product-mb/tree/c5-migration
>>> [2]
>>> .
>>> ├── carbon-mb
>>> │   ├── components
>>> │   │   ├── andes
>>> │   │   │   ├── andes.iml
>>> │   │   │   ├── pom.xml
>>> │   │   │   ├── src
>>> │   │   │   └── target
>>> │   │   ├── mb-ui
>>> │   │   │   ├── mb-ui.iml
>>> │   │   │   ├── pom.xml
>>> │   │   │   ├── src
>>> │   │   │   └── target
>>> │   │   └── transports
>>> │   │   ├── amqp
>>> │   │   └── mqtt
>>> │   └── features
>>> │   ├── andes.feature
>>> │   │   ├── andes.feature.iml
>>> │   │   ├── pom.xml
>>> │   │   └── target
>>> │   ├── etc
>>> │   │   └── feature.properties
>>> │   ├── mb-ui.feature
>>> │   │   ├── mb-ui.feature.iml
>>> │   │   ├── pom.xml
>>> │   │   └── target
>>> │   └── transports
>>> │   ├── amqp.feature
>>> │   └── mqtt.feature
>>> ├── LICENSE.txt
>>> ├── pom.xml
>>> ├── README.md
>>> ├── README.txt
>>> ├── tests
>>> │   └── osgi-tests
>>> │   ├── carbon-mb-osgi-tests.iml
>>> │   ├── pom.xml
>>> │   └── target
>>> │   ├── carbon-mb-osgi-tests-3.5.0-SNAPSHOT.jar
>>> │   ├── classes
>>> │   ├── maven-archiver
>>> │   ├── maven-shared-archive-resources
>>> │   └── test-classes
>>> └── tools
>>> ├── mb-tools.iml
>>> ├── pom.xml
>>> └── target
>>> ├── classes
>>> │   └── META-INF
>>> ├── maven-archiver
>>> │   └── pom.properties
>>> ├── maven-shared-archive-resources
>>> │   └── META-INF
>>> ├── mb-tools-3.5.0-SNAPSHOT.jar
>>> └── test-classes
>>> └── META-INF
>>>
>>>
>>> Regards,
>>>
>>> --
>>> *Asitha Nanayakkara*
>>> Software Engineer
>>> WSO2, Inc. http://wso2.com/
>>> Mob: + 94 77 85 30 682
>>>
>>>
>>
>>
>> --
>> *Hasitha Abeykoon*
>> Senior Software Engineer; WSO2, Inc.; http://wso2.com
>> *cell:* *+94 719363063*
>> *blog: **abeykoon.blogspot.com* 
>>
>>
>
>
> --
> *Asitha Nanayakkara*
> Software Engineer
> WSO2, Inc. http://wso2.com/
> Mob: + 94 77 85 30 682
>
>


-- 
*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] Selenium UI Testing [GREG/ES - Publisher]

2016-02-09 Thread Lahiru J Ekanayake
Hi Ayesha,

Currently I have not included ESWebDriver . I have used default selenium
WebDriver. Now i can integrate ESWebDriver to implement Selenium UI tests.

Thank you.


On Tue, Feb 9, 2016 at 4:32 PM, Lahiru Cooray  wrote:

> Hi Lahiru,
>
> I have faced the similar issue and I noticed that some times the
> dynamically loaded elements are not loading when we are using wait.until()
> without a driver refresh() So I used a similar code snipped like this:
>
>
>
>  WebDriverWait tempWait = new WebDriverWait(driver, 5); //5 is the waiting
> time in seconds
>
> for (int i = 0; i < 2; i++) {
> try {
>
> tempWait.until(ExpectedConditions.visibilityOfElementLocated(By.cssSelector(
> "a[href*='/store/assets/webapp/" + appId + "']")));
> driver.navigate().refresh();
> break;
> } catch (org.openqa.selenium.TimeoutException e) {
> //Expected error when no element found
> }
> }
>
> Here i'm trying two times and waiting a fair time to load the element.
>
>
> On Tue, Feb 9, 2016 at 3:34 PM, Lahiru J Ekanayake 
> wrote:
>
>> Hi ,
>>
>> I have already tried with wait.until method. It will also return timeout
>> exception searching after given timeout.  I think anyway we have to use try
>> block to check existences of  an element. I have looked for a method that
>> returns ture/false on a given element existence . I'm not sure that kind of
>> method already in selenium.
>> Thank you for your help.
>>
>> Regards
>>
>> On Tue, Feb 9, 2016 at 3:13 PM, Rajeenthini Satkunam <
>> rajeenth...@wso2.com> wrote:
>>
>>> Hi lahiru,
>>>
>>> If you need to check that element is present in the current UI, You can
>>> go with this method *isElementPresent(By by)*.
>>>
>>> for example in your case *driver.**isElementPresent*
>>> *(By.id("elemnt_id")) *will return true if the element is present in
>>> current UI or else it will return false.Hope it will help you.
>>>
>>> For your reference
>>>
>>> [1] -
>>> https://github.com/wso2/product-ds/blob/master/modules/integration/tests-ui-integration/ui-test-utils/src/main/java/org/wso2/ds/ui/integration/util/DSWebDriver.java#L47
>>>
>>> On Tue, Feb 9, 2016 at 3:01 PM, Lahiru J Ekanayake 
>>> wrote:
>>>
 Hi ,

 I'm writing selenium tests for GREG publisher UI. When implementing UI
 test cases, some situations we need to check whether some elements exists,
 before click or make any operations on them.
 Selenium provides, *driver.findElement(By.id("elemnt_id")) *
 method to find any element by id. Problem is if that element is not
 exist , it will return an error, saying
 *org.openqa.selenium.NoSuchElementException: Unable to locate
 element:{"method":"id","selector":"elemnt_id"}*

 Is there any way to check the existence of any element , without
 catching the error? .




 Regards



 --



 *Lahiru J Ekanayake**Software Engineer*
 Mobile : +94 (0) 77 8812629 / +94(0) 778509547
 Email : lahi...@wso2.com
 WSO2, Inc.; http://wso2.com/
 lean . enterprise . middleware.


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


>>>
>>>
>>> --
>>>
>>> *Thank You.*
>>>
>>> *Rajeenthini Satkunam*
>>>
>>> *Associate Software Engineer | WSO2*
>>>
>>>
>>> *E:rajeenth...@wso2.com *
>>>
>>> *M :+94770832823 <%2B94770832823>   *
>>>
>>>
>>
>>
>> --
>>
>>
>>
>> *Lahiru J Ekanayake**Software Engineer*
>> Mobile : +94 (0) 77 8812629 / +94(0) 778509547
>> Email : lahi...@wso2.com
>> WSO2, Inc.; http://wso2.com/
>> lean . enterprise . middleware.
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Lahiru Cooray*
> Software Engineer
> WSO2, Inc.;http://wso2.com/
> lean.enterprise.middleware
>
> Mobile: +94 715 654154
>



-- 



*Lahiru J Ekanayake**Software Engineer*
Mobile : +94 (0) 77 8812629 / +94(0) 778509547
Email : lahi...@wso2.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] Selenium UI Testing [GREG/ES - Publisher]

2016-02-09 Thread Madhawa Perera
Hi Lahiru,

Try following code snippet, if you are looking for a method, that returns
true/false when checking the existence of an element.

 private boolean isElementPresent(By by) {

if(driver.findElements(by).size() != 0){
//System.out.println("true");
return true;
} else {
//System.out.println("false");
return false;
}
}

Hope this will help you. Check the following [1] reference too.

[1]
http://stackoverflow.com/questions/6521270/webdriver-check-if-an-element-exists

Regards,
Madhawa


On Tue, Feb 9, 2016 at 4:32 PM, Lahiru Cooray  wrote:

> Hi Lahiru,
>
> I have faced the similar issue and I noticed that some times the
> dynamically loaded elements are not loading when we are using wait.until()
> without a driver refresh() So I used a similar code snipped like this:
>
>
>
>  WebDriverWait tempWait = new WebDriverWait(driver, 5); //5 is the waiting
> time in seconds
>
> for (int i = 0; i < 2; i++) {
> try {
>
> tempWait.until(ExpectedConditions.visibilityOfElementLocated(By.cssSelector(
> "a[href*='/store/assets/webapp/" + appId + "']")));
> driver.navigate().refresh();
> break;
> } catch (org.openqa.selenium.TimeoutException e) {
> //Expected error when no element found
> }
> }
>
> Here i'm trying two times and waiting a fair time to load the element.
>
>
> On Tue, Feb 9, 2016 at 3:34 PM, Lahiru J Ekanayake 
> wrote:
>
>> Hi ,
>>
>> I have already tried with wait.until method. It will also return timeout
>> exception searching after given timeout.  I think anyway we have to use try
>> block to check existences of  an element. I have looked for a method that
>> returns ture/false on a given element existence . I'm not sure that kind of
>> method already in selenium.
>> Thank you for your help.
>>
>> Regards
>>
>> On Tue, Feb 9, 2016 at 3:13 PM, Rajeenthini Satkunam <
>> rajeenth...@wso2.com> wrote:
>>
>>> Hi lahiru,
>>>
>>> If you need to check that element is present in the current UI, You can
>>> go with this method *isElementPresent(By by)*.
>>>
>>> for example in your case *driver.**isElementPresent*
>>> *(By.id("elemnt_id")) *will return true if the element is present in
>>> current UI or else it will return false.Hope it will help you.
>>>
>>> For your reference
>>>
>>> [1] -
>>> https://github.com/wso2/product-ds/blob/master/modules/integration/tests-ui-integration/ui-test-utils/src/main/java/org/wso2/ds/ui/integration/util/DSWebDriver.java#L47
>>>
>>> On Tue, Feb 9, 2016 at 3:01 PM, Lahiru J Ekanayake 
>>> wrote:
>>>
 Hi ,

 I'm writing selenium tests for GREG publisher UI. When implementing UI
 test cases, some situations we need to check whether some elements exists,
 before click or make any operations on them.
 Selenium provides, *driver.findElement(By.id("elemnt_id")) *
 method to find any element by id. Problem is if that element is not
 exist , it will return an error, saying
 *org.openqa.selenium.NoSuchElementException: Unable to locate
 element:{"method":"id","selector":"elemnt_id"}*

 Is there any way to check the existence of any element , without
 catching the error? .




 Regards



 --



 *Lahiru J Ekanayake**Software Engineer*
 Mobile : +94 (0) 77 8812629 / +94(0) 778509547
 Email : lahi...@wso2.com
 WSO2, Inc.; http://wso2.com/
 lean . enterprise . middleware.


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


>>>
>>>
>>> --
>>>
>>> *Thank You.*
>>>
>>> *Rajeenthini Satkunam*
>>>
>>> *Associate Software Engineer | WSO2*
>>>
>>>
>>> *E:rajeenth...@wso2.com *
>>>
>>> *M :+94770832823 <%2B94770832823>   *
>>>
>>>
>>
>>
>> --
>>
>>
>>
>> *Lahiru J Ekanayake**Software Engineer*
>> Mobile : +94 (0) 77 8812629 / +94(0) 778509547
>> Email : lahi...@wso2.com
>> WSO2, Inc.; http://wso2.com/
>> lean . enterprise . middleware.
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Lahiru Cooray*
> Software Engineer
> WSO2, Inc.;http://wso2.com/
> lean.enterprise.middleware
>
> Mobile: +94 715 654154
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Madhawa Perera
*Software Engineer*
Mobile : +94 (0) 773655496
<%2B94%20%280%29%20773%20451194>
madha...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


[Dev] [DEV] WSO2 Complex Event Processor 4.1.0 Beta Released

2016-02-09 Thread Mohanadarshan Vivekanandalingam
Hi All,

WSO2 CEP Team is pleased to announce the Beta release of WSO2 Complex Event
Processor 4.1.0.

WSO2 Complex Event Processor (CEP) can be used to identify the most
meaningful events within an event cloud, analyzes their impacts, and acts
on them in real time. Built to be extremely high performing it offers
significant time saving and affordable acquisition. WSO2 CEP Manager is
released under the Apache Software License 2.0.

The distribution is available at [1]. The documentation for CEP 4.1.0 Beta
can be found at [2] (which is WIP). Your feedback is most welcome, and any
issues can be reported to the project at [3].

Following bug fixes and improvements have been added along with this
release .

*Bug*

   - [CEP-1347 ] - Refreshing Arc
   and Map charts is visible when throughput is high
   - [CEP-1367 ] - Cannot add a
   datasource, with name having character 's'
   - [CEP-1383 ] - Intermittently an
   NPE is thrown on worker logs when updating execution planner with Output
   Rate Limiting patterns
   - [CEP-1387 ] - Analytics
   Dashboard - Multiline Y axis Limitations
   - [CEP-1388 ] - "Error while
   indexing" issue observed in worker node when starting a fresh pack in CEP
   distributed cluster
   - [CEP-1389 ] - Analytics
   Dashboard - Line and Area charts miss first event when plotting
   - [CEP-1391 ] - OOM when nodes
   are disconnected from hazelcast cluster in distributed mode
   - [CEP-1392 ] - Restrict setting
   up incorrect configurations in event simulator configuration files for
   sample mode
   - [CEP-1395 ] - Analytics
   Dashboard - Login redirection does not work in Sample mode
   - [CEP-1431 ] - Cannot put
   "((true) in SomeEventTable)" as an attribute in the select statement
   - [CEP-1438 ] - Siddhi PMML
   extension is always expecting an output field
   - [CEP-1460 ] - MQTT Event
   receiver unsubscribes from the topic on shutdown, even cleanSession is set
   to false.
   - [CEP-1461 ] - Issue on viewing
   system logs in management console
   - [CEP-1466 ] - two get calls
   executes when datasources getting populated for Batch and realtime


*Improvement*

   - [CEP-1406 ] - Need to have tool
   tips for icons in the Dashboard
   - [CEP-1467 ] - When deleting a
   gadget need a configurable option to either delete whole layout with block
   or only the block(gadget content))



References:

​[1] https://github.com/wso2/product-cep/releases/tag/v4.1.0-beta
[2]
https://docs.wso2.com/display/CEP410/WSO2+Complex+Event+Processor+Documentation
[3] https://wso2.org/jira/browse/CEP


Thanks,
-WSO2 CEP Team-

-- 
*V. Mohanadarshan*
*Senior Software Engineer,*
*Data Technologies Team,*
*WSO2, Inc. http://wso2.com  *
*lean.enterprise.middleware.*

email: mo...@wso2.com
phone:(+94) 771117673
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


[Dev] Native inbound and connector for IBM MQ 7.5

2016-02-09 Thread Riyafa Abdul Hameed
Dear sir,

I am a third year Computer Science and Engineering undergraduate at
University of Moratuwa. I would like to take part in GSoC 2016 with the
open source community of WSO2.

I am quite familiar with the ESB-Connectors of WSO2. I have previously
worked with the saleforce, google-spreadsheet and the peopleHR connectors
on a project that involved automating the filling of a google spreadsheet
with details from salesforce. I am also quite familiar working with the
WSO2 ESB and have prior experience of writing proxy services. And I am a
quick learner.

I have also contributed to the peopleHR connector of WSO2 [1].

Being quite familiar with the WSO2 connector development, I consider doing
the project "Native inbound and connector for IBM MQ 7.5" with the WSO2
community for GSoC this year.

Please kindly make any suggestions on how I could proceed.


[1] https://github.com/wso2/esb-connectors/pull/419

Thank you.

Yours sincerely,
Riyafa

-- 
Riyafa Abdul Hameed
Undergraduate, University of Moratuwa

Email: riyafa...@cse.mrt.ac.lk
Website: https://riyafa.wordpress.com/ 
  

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


[Dev] [APIM] Integrating APIM testng tests with Heartbeat

2016-02-09 Thread Erandi Ganepola
Hi All,

I'm going to run Api manager integration test cases through Heartbeat system
in cloud. For that I need to use automation.xml, testng.xml and some
listeners.

Is there an automation xml and a testng xml you are using separately for
APIM team? What are the relevant listeners to be used?

Thanks and Regards,
Erandi

Erandi Ganepola
Software Engineering Intern
+94710695692
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


[Dev] [VOTE] Release WSO2 MSF4J 1.0.0 RC5

2016-02-09 Thread Samiyuru Senarathne
Hi Devs,

This is the 5th Release Candidate of WSO2 Microservices Framework for
Java 1.0.0.

Please download, test the framework and vote.
Note: Refer github readmes for guides.

*​Source and binary distribution files:*
*https://github.com/wso2/msf4j/releases/tag/v1.0.0-RC5
*

*Maven staging repository:*
*http://maven.wso2.org/nexus/content/repositories/orgwso2-327/
*

*The tag to be voted upon:*
*https://github.com/wso2/msf4j/tree/v1.0.0-RC5
*


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

Thank you,
Carbon Team

-- 
Samiyuru Senarathne
*Software Engineer*
Mobile : +94 (0) 71 134 6087
samiy...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


[Dev] [ESB Connectors] Connectors with Refresh token support

2016-02-09 Thread Kasun Indrasiri
Have we upgraded connectors to support refresh token persisting mechanism
in the latest ESB?

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

cell: +94 77 556 5206
Blog : http://kasunpanorama.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] [ESB Connectors] Connectors with Refresh token support

2016-02-09 Thread Kesavan Yogarajah
Hi Kasun,

Please find progress in mail thread [1].

[1] - [Architecture] Fully automate cloud to cloud (iPaaS) use cases

Thanks

Kesavan Yogarajah
Associate Software Engineer
Mobile :+94 (0) 779 758021
kesav...@wso2.com
WSO2, Inc.
lean . enterprise . middleware

On Wed, Feb 10, 2016 at 10:35 AM, Kasun Indrasiri  wrote:

> Have we upgraded connectors to support refresh token persisting mechanism
> in the latest ESB?
>
> --
> Kasun Indrasiri
> Software Architect
> WSO2, Inc.; http://wso2.com
> lean.enterprise.middleware
>
> cell: +94 77 556 5206
> Blog : http://kasunpanorama.blogspot.com/
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] MB C5-migration new folder structure

2016-02-09 Thread Akalanka Pagoda Arachchi
To be clear on this, if we have all the features in one repository,
connecting them from the same parent pom, we will not be able release one
feature without releasing the others.

Therefore, if the requirement is to make these available to be individually
released, we have to logically separate them which ideally means to have
separate repositories per each feature.

Thanks,
Akalanka.

On Tue, Feb 9, 2016 at 5:24 PM, Hasitha Hiranya  wrote:

> Hi Asitha,
>
> Yep. If we install above 4 features on a vanila Cabon server, it should
> become a MB server.
>
> Thanks
>
> On Tue, Feb 9, 2016 at 4:26 PM, Asitha Nanayakkara 
> wrote:
>
>> Adding dev@
>>
>> On Tue, Feb 9, 2016 at 4:03 PM, Hasitha Hiranya 
>> wrote:
>>
>>> hi Asitha,
>>>
>>> Ah, so there is no need for components be in a separate repo?
>>> I think the reason to keep components in a separate repo was to share
>>> the components between various product level features.
>>>
>>> Agreed, if we want to do a release for a specific feature then we have
>> to release the whole product. If we have a separate repo for features we
>> won't have that issue. At the moment we don't have such requirement. Will
>> this be a valid requriment in future?
>>
>> Even though we are moving all the components and features to product mb
>> repo still we will have four features. Namely they are
>> Andes feature - andes core functionality will be implemented in this
>> feature
>> MB-UI feature - ui components of MB
>> AMQP-feature - AMQP transport implementation
>> MQTT feature - MQTT transport implementation
>>
>> So these features can be used in other products. For instance we can have
>> a lean MB with Andes feature and MQTT feature.
>>
>> Regards,
>> Asitha
>>
>>
>>
>>> Let us use Dev/Architecture mail threads to discuss these.
>>>
>>> Thanks
>>>
>>> On Tue, Feb 9, 2016 at 3:55 PM, Asitha Nanayakkara 
>>> wrote:
>>>
 Hi all,

 We (Hemika and I) are in the process of bootstrapping the product.

 We have come up with a folder structure for the project[2]. We will be
 working on product-mb/c5-migration branch [1].

 We will be moving all the components and features to product-mb repo
 (since we don't have any shared features in there) and eventually will get
 rid of the cabon-business-messaging repo

 Any concerns,thoughts and suggestions on the approach?

 [1] https://github.com/wso2/product-mb/tree/c5-migration
 [2]
 .
 ├── carbon-mb
 │   ├── components
 │   │   ├── andes
 │   │   │   ├── andes.iml
 │   │   │   ├── pom.xml
 │   │   │   ├── src
 │   │   │   └── target
 │   │   ├── mb-ui
 │   │   │   ├── mb-ui.iml
 │   │   │   ├── pom.xml
 │   │   │   ├── src
 │   │   │   └── target
 │   │   └── transports
 │   │   ├── amqp
 │   │   └── mqtt
 │   └── features
 │   ├── andes.feature
 │   │   ├── andes.feature.iml
 │   │   ├── pom.xml
 │   │   └── target
 │   ├── etc
 │   │   └── feature.properties
 │   ├── mb-ui.feature
 │   │   ├── mb-ui.feature.iml
 │   │   ├── pom.xml
 │   │   └── target
 │   └── transports
 │   ├── amqp.feature
 │   └── mqtt.feature
 ├── LICENSE.txt
 ├── pom.xml
 ├── README.md
 ├── README.txt
 ├── tests
 │   └── osgi-tests
 │   ├── carbon-mb-osgi-tests.iml
 │   ├── pom.xml
 │   └── target
 │   ├── carbon-mb-osgi-tests-3.5.0-SNAPSHOT.jar
 │   ├── classes
 │   ├── maven-archiver
 │   ├── maven-shared-archive-resources
 │   └── test-classes
 └── tools
 ├── mb-tools.iml
 ├── pom.xml
 └── target
 ├── classes
 │   └── META-INF
 ├── maven-archiver
 │   └── pom.properties
 ├── maven-shared-archive-resources
 │   └── META-INF
 ├── mb-tools-3.5.0-SNAPSHOT.jar
 └── test-classes
 └── META-INF


 Regards,

 --
 *Asitha Nanayakkara*
 Software Engineer
 WSO2, Inc. http://wso2.com/
 Mob: + 94 77 85 30 682


>>>
>>>
>>> --
>>> *Hasitha Abeykoon*
>>> Senior Software Engineer; WSO2, Inc.; http://wso2.com
>>> *cell:* *+94 719363063*
>>> *blog: **abeykoon.blogspot.com* 
>>>
>>>
>>
>>
>> --
>> *Asitha Nanayakkara*
>> Software Engineer
>> WSO2, Inc. http://wso2.com/
>> Mob: + 94 77 85 30 682
>>
>>
>
>
> --
> *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
>
>


-- 
*Darshana Akalanka Pagoda Arachchi,*
*Software Engineer*
*078-4721791*
__

Re: [Dev] Selenium UI Testing [GREG/ES - Publisher]

2016-02-09 Thread Dharshana Warusavitharana
Hi Lahiru,

You can use TestNg soft assert for this.

Basically what you want is
1. Check the element whether it is exists.
2. It should not make assert fail and stop the test execution if element is
not there.
please refer [1] for soft assert.

[1].
https://rameshbaskar.wordpress.com/2013/09/11/soft-assertions-using-testng/

Thank you,
Dharshana.

On Tue, Feb 9, 2016 at 5:32 PM, Madhawa Perera  wrote:

> Hi Lahiru,
>
> Try following code snippet, if you are looking for a method, that returns
> true/false when checking the existence of an element.
>
>  private boolean isElementPresent(By by) {
>
> if(driver.findElements(by).size() != 0){
> //System.out.println("true");
> return true;
> } else {
> //System.out.println("false");
> return false;
> }
> }
>
> Hope this will help you. Check the following [1] reference too.
>
> [1]
> http://stackoverflow.com/questions/6521270/webdriver-check-if-an-element-exists
>
> Regards,
> Madhawa
>
>
> On Tue, Feb 9, 2016 at 4:32 PM, Lahiru Cooray  wrote:
>
>> Hi Lahiru,
>>
>> I have faced the similar issue and I noticed that some times the
>> dynamically loaded elements are not loading when we are using wait.until()
>> without a driver refresh() So I used a similar code snipped like this:
>>
>>
>>
>>  WebDriverWait tempWait = new WebDriverWait(driver, 5); //5 is the
>> waiting time in seconds
>>
>> for (int i = 0; i < 2; i++) {
>> try {
>>
>> tempWait.until(ExpectedConditions.visibilityOfElementLocated(By.cssSelector(
>> "a[href*='/store/assets/webapp/" + appId +
>> "']")));
>> driver.navigate().refresh();
>> break;
>> } catch (org.openqa.selenium.TimeoutException e) {
>> //Expected error when no element found
>> }
>> }
>>
>> Here i'm trying two times and waiting a fair time to load the element.
>>
>>
>> On Tue, Feb 9, 2016 at 3:34 PM, Lahiru J Ekanayake 
>> wrote:
>>
>>> Hi ,
>>>
>>> I have already tried with wait.until method. It will also return
>>> timeout exception searching after given timeout.  I think anyway we have to
>>> use try block to check existences of  an element. I have looked for a
>>> method that returns ture/false on a given element existence . I'm not sure
>>> that kind of method already in selenium.
>>> Thank you for your help.
>>>
>>> Regards
>>>
>>> On Tue, Feb 9, 2016 at 3:13 PM, Rajeenthini Satkunam <
>>> rajeenth...@wso2.com> wrote:
>>>
 Hi lahiru,

 If you need to check that element is present in the current UI, You can
 go with this method *isElementPresent(By by)*.

 for example in your case *driver.**isElementPresent*
 *(By.id("elemnt_id")) *will return true if the element is present in
 current UI or else it will return false.Hope it will help you.

 For your reference

 [1] -
 https://github.com/wso2/product-ds/blob/master/modules/integration/tests-ui-integration/ui-test-utils/src/main/java/org/wso2/ds/ui/integration/util/DSWebDriver.java#L47

 On Tue, Feb 9, 2016 at 3:01 PM, Lahiru J Ekanayake 
 wrote:

> Hi ,
>
> I'm writing selenium tests for GREG publisher UI. When implementing UI
> test cases, some situations we need to check whether some elements exists,
> before click or make any operations on them.
> Selenium provides, *driver.findElement(By.id("elemnt_id")) *
> method to find any element by id. Problem is if that element is not
> exist , it will return an error, saying
> *org.openqa.selenium.NoSuchElementException: Unable to locate
> element:{"method":"id","selector":"elemnt_id"}*
>
> Is there any way to check the existence of any element , without
> catching the error? .
>
>
>
>
> Regards
>
>
>
> --
>
>
>
> *Lahiru J Ekanayake**Software Engineer*
> Mobile : +94 (0) 77 8812629 / +94(0) 778509547
> Email : lahi...@wso2.com
> WSO2, Inc.; http://wso2.com/
> lean . enterprise . middleware.
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --

 *Thank You.*

 *Rajeenthini Satkunam*

 *Associate Software Engineer | WSO2*


 *E:rajeenth...@wso2.com *

 *M :+94770832823 <%2B94770832823>   *


>>>
>>>
>>> --
>>>
>>>
>>>
>>> *Lahiru J Ekanayake**Software Engineer*
>>> Mobile : +94 (0) 77 8812629 / +94(0) 778509547
>>> Email : lahi...@wso2.com
>>> WSO2, Inc.; http://wso2.com/
>>> lean . enterprise . middleware.
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Lahiru Cooray*
>> Software Engineer
>> WSO2, Inc.;http://wso2.com/
>> lean.enterprise.middleware
>>
>> Mo

[Dev] Using OSGI "Configuration Property Types" - for interpretation of configurations

2016-02-09 Thread Pamod Sylvester
Hi All,

DS 1.3 provides the capability of defining custom types for configurations.
This might be a cleaner approach we could use to interpret our
configurations. using @interface annotation.

WDYT ?

[1] http://njbartlett.name/2015/08/17/osgir6-declarative-services.html

Thanks,
Pamod

-- 
*Pamod Sylvester *

*WSO2 Inc.; http://wso2.com *
cell: +94 77 7779495
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] MB C5-migration new folder structure

2016-02-09 Thread Sameera Jayasoma
Hi All,

Maintaining MB components and features within the product-mb is the right
thing to do IMO.

Do we have a real requirement release separate features individually?


Thanks,
Sameera.

On Wed, Feb 10, 2016 at 11:35 AM, Akalanka Pagoda Arachchi <
darsha...@wso2.com> wrote:

> To be clear on this, if we have all the features in one repository,
> connecting them from the same parent pom, we will not be able release one
> feature without releasing the others.
>
> Therefore, if the requirement is to make these available to be
> individually released, we have to logically separate them which ideally
> means to have separate repositories per each feature.
>
> Thanks,
> Akalanka.
>
> On Tue, Feb 9, 2016 at 5:24 PM, Hasitha Hiranya  wrote:
>
>> Hi Asitha,
>>
>> Yep. If we install above 4 features on a vanila Cabon server, it should
>> become a MB server.
>>
>> Thanks
>>
>> On Tue, Feb 9, 2016 at 4:26 PM, Asitha Nanayakkara 
>> wrote:
>>
>>> Adding dev@
>>>
>>> On Tue, Feb 9, 2016 at 4:03 PM, Hasitha Hiranya 
>>> wrote:
>>>
 hi Asitha,

 Ah, so there is no need for components be in a separate repo?
 I think the reason to keep components in a separate repo was to share
 the components between various product level features.

 Agreed, if we want to do a release for a specific feature then we have
>>> to release the whole product. If we have a separate repo for features we
>>> won't have that issue. At the moment we don't have such requirement. Will
>>> this be a valid requriment in future?
>>>
>>> Even though we are moving all the components and features to product mb
>>> repo still we will have four features. Namely they are
>>> Andes feature - andes core functionality will be implemented in this
>>> feature
>>> MB-UI feature - ui components of MB
>>> AMQP-feature - AMQP transport implementation
>>> MQTT feature - MQTT transport implementation
>>>
>>> So these features can be used in other products. For instance we can
>>> have a lean MB with Andes feature and MQTT feature.
>>>
>>> Regards,
>>> Asitha
>>>
>>>
>>>
 Let us use Dev/Architecture mail threads to discuss these.

 Thanks

 On Tue, Feb 9, 2016 at 3:55 PM, Asitha Nanayakkara 
 wrote:

> Hi all,
>
> We (Hemika and I) are in the process of bootstrapping the product.
>
> We have come up with a folder structure for the project[2]. We will be
> working on product-mb/c5-migration branch [1].
>
> We will be moving all the components and features to product-mb repo
> (since we don't have any shared features in there) and eventually will get
> rid of the cabon-business-messaging repo
>
> Any concerns,thoughts and suggestions on the approach?
>
> [1] https://github.com/wso2/product-mb/tree/c5-migration
> [2]
> .
> ├── carbon-mb
> │   ├── components
> │   │   ├── andes
> │   │   │   ├── andes.iml
> │   │   │   ├── pom.xml
> │   │   │   ├── src
> │   │   │   └── target
> │   │   ├── mb-ui
> │   │   │   ├── mb-ui.iml
> │   │   │   ├── pom.xml
> │   │   │   ├── src
> │   │   │   └── target
> │   │   └── transports
> │   │   ├── amqp
> │   │   └── mqtt
> │   └── features
> │   ├── andes.feature
> │   │   ├── andes.feature.iml
> │   │   ├── pom.xml
> │   │   └── target
> │   ├── etc
> │   │   └── feature.properties
> │   ├── mb-ui.feature
> │   │   ├── mb-ui.feature.iml
> │   │   ├── pom.xml
> │   │   └── target
> │   └── transports
> │   ├── amqp.feature
> │   └── mqtt.feature
> ├── LICENSE.txt
> ├── pom.xml
> ├── README.md
> ├── README.txt
> ├── tests
> │   └── osgi-tests
> │   ├── carbon-mb-osgi-tests.iml
> │   ├── pom.xml
> │   └── target
> │   ├── carbon-mb-osgi-tests-3.5.0-SNAPSHOT.jar
> │   ├── classes
> │   ├── maven-archiver
> │   ├── maven-shared-archive-resources
> │   └── test-classes
> └── tools
> ├── mb-tools.iml
> ├── pom.xml
> └── target
> ├── classes
> │   └── META-INF
> ├── maven-archiver
> │   └── pom.properties
> ├── maven-shared-archive-resources
> │   └── META-INF
> ├── mb-tools-3.5.0-SNAPSHOT.jar
> └── test-classes
> └── META-INF
>
>
> Regards,
>
> --
> *Asitha Nanayakkara*
> Software Engineer
> WSO2, Inc. http://wso2.com/
> Mob: + 94 77 85 30 682
>
>


 --
 *Hasitha Abeykoon*
 Senior Software Engineer; WSO2, Inc.; http://wso2.com
 *cell:* *+94 719363063*
 *blog: **abeykoon.blogspot.com* 


>>>
>>>
>>> --
>>> *Asitha Nanayakkara*
>>> Software Engineer
>>> WSO2, Inc. http://wso2.com/
>>> Mob: + 94 

Re: [Dev] Native inbound and connector for IBM MQ 7.5

2016-02-09 Thread Malaka Silva
Hi Riyafa,

First you should install IBM MQ 7.5.

Then try connection as consumer and producer from a java client. Using IBM
MQ client.

This need to add consumer functionality to custom inbound endpoint and
producer to a connector.

On Wed, Feb 10, 2016 at 7:16 AM, Riyafa Abdul Hameed <
riyafa...@cse.mrt.ac.lk> wrote:

> Dear sir,
>
> I am a third year Computer Science and Engineering undergraduate at
> University of Moratuwa. I would like to take part in GSoC 2016 with the
> open source community of WSO2.
>
> I am quite familiar with the ESB-Connectors of WSO2. I have previously
> worked with the saleforce, google-spreadsheet and the peopleHR connectors
> on a project that involved automating the filling of a google spreadsheet
> with details from salesforce. I am also quite familiar working with the
> WSO2 ESB and have prior experience of writing proxy services. And I am a
> quick learner.
>
> I have also contributed to the peopleHR connector of WSO2 [1].
>
> Being quite familiar with the WSO2 connector development, I consider doing
> the project "Native inbound and connector for IBM MQ 7.5" with the WSO2
> community for GSoC this year.
>
> Please kindly make any suggestions on how I could proceed.
>
>
> [1] https://github.com/wso2/esb-connectors/pull/419
>
> Thank you.
>
> Yours sincerely,
> Riyafa
>
> --
> Riyafa Abdul Hameed
> Undergraduate, University of Moratuwa
>
> Email: riyafa...@cse.mrt.ac.lk
> Website: https://riyafa.wordpress.com/ 
>   
> 
>



-- 

Best Regards,

Malaka Silva
Senior Tech Lead
M: +94 777 219 791
Tel : 94 11 214 5345
Fax :94 11 2145300
Skype : malaka.sampath.silva
LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
Blog : http://mrmalakasilva.blogspot.com/

WSO2, Inc.
lean . enterprise . middleware
http://www.wso2.com/
http://www.wso2.com/about/team/malaka-silva/

https://store.wso2.com/store/

Save a tree -Conserve nature & Save the world for your future. Print this
email only if it is absolutely necessary.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


[Dev] Is rfc6570-encoding supported in ESB 4.9.0?

2016-02-09 Thread Dulitha Wijewantha
Hi guys,
I am trying to invoke an endpoint with rfc6570-encoding (since the URI
parameter has an email on it). Below is the definition -


http://localhost:9763/services/test/foo/bar/{uri.var.email}";
method="get">



But I get the error -

13:13:11,075 Axis2Sender  Unexpected error during sending message out
org.apache.axis2.AxisFault: The system cannot infer the transport
information from the rfc6570-encoding:
http://localhost:9763/services/test/foo/bar/dulitha%40wso2.com URL.
at
org.apache.axis2.description.ClientUtils.inferOutTransport(ClientUtils.java:81)
at
org.apache.synapse.core.axis2.DynamicAxisOperation$DynamicOperationClient.executeImpl(DynamicAxisOperation.java:115)
at org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
at
org.apache.synapse.core.axis2.Axis2FlexibleMEPClient.send(Axis2FlexibleMEPClient.java:542)
at org.apache.synapse.core.axis2.Axis2Sender.sendOn(Axis2Sender.java:79)
at
org.apache.synapse.core.axis2.Axis2SynapseEnvironment.send(Axis2SynapseEnvironment.java:461)
at
org.apache.synapse.endpoints.AbstractEndpoint.send(AbstractEndpoint.java:372)
at org.apache.synapse.endpoints.HTTPEndpoint.send(HTTPEndpoint.java:89)
at
org.apache.synapse.mediators.builtin.CallMediator.handleNonBlockingCall(CallMediator.java:204)
at
org.apache.synapse.mediators.builtin.CallMediator.mediate(CallMediator.java:87)
at
org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:81)
at
org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:48)
at
org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:149)
at org.apache.synapse.rest.Resource.process(Resource.java:297)
at org.apache.synapse.rest.API.process(API.java:378)
at
org.apache.synapse.rest.RESTRequestHandler.dispatchToAPI(RESTRequestHandler.java:97)
at
org.apache.synapse.rest.RESTRequestHandler.process(RESTRequestHandler.java:65)
at
org.apache.synapse.core.axis2.Axis2SynapseEnvironment.injectMessage(Axis2SynapseEnvironment.java:266)
at
org.apache.synapse.core.axis2.SynapseMessageReceiver.receive(SynapseMessageReceiver.java:83)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
at
org.apache.synapse.transport.passthru.ServerWorker.processNonEntityEnclosingRESTHandler(ServerWorker.java:317)
at
org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:149)
at
org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
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)

-- 
Dulitha Wijewantha (Chan)
Software Engineer - Mobile Development
WSO2 Inc
Lean.Enterprise.Middleware
 * ~Email   duli...@wso2.com *
*  ~Mobile +94712112165*
*  ~Website   dulitha.me *
*  ~Twitter @dulitharw *
  *~Github @dulichan *
  *~SO @chan *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev