Hi Thilini,
On Wed, Sep 22, 2010 at 5:30 PM, Thilini Ishaka thil...@wso2.com wrote:
On Wed, Sep 22, 2010 at 11:18 AM, Hiranya Jayathilaka hira...@wso2.comwrote:
On Tue, Sep 21, 2010 at 7:27 PM, cham...@wso2.com cham...@wso2.comwrote:
When running log mediator tests manually, we
On Sat, Nov 6, 2010 at 1:19 PM, Charitha Kankanamge chari...@wso2.comwrote:
Hi Thilini,
On Wed, Sep 22, 2010 at 5:30 PM, Thilini Ishaka thil...@wso2.com wrote:
On Wed, Sep 22, 2010 at 11:18 AM, Hiranya Jayathilaka
hira...@wso2.comwrote:
On Tue, Sep 21, 2010 at 7:27 PM,
On Wed, Sep 22, 2010 at 11:18 AM, Hiranya Jayathilaka hira...@wso2.comwrote:
On Tue, Sep 21, 2010 at 7:27 PM, cham...@wso2.com cham...@wso2.comwrote:
When running log mediator tests manually, we usually scan carbon log
to read log messages and decide the success or failure of the tests .
How are you guys looking at the admin services? Using Java code or WSDL?
On Wed, Sep 22, 2010 at 5:30 PM, Thilini Ishaka thil...@wso2.com wrote:
On Wed, Sep 22, 2010 at 11:18 AM, Hiranya Jayathilaka hira...@wso2.comwrote:
On Tue, Sep 21, 2010 at 7:27 PM, cham...@wso2.com
That is not what I asked, basically, how do you get to know the service
interface of the admin service to be invoked? Do we use code generation?
On Wed, Sep 22, 2010 at 8:44 PM, cham...@wso2.com cham...@wso2.com wrote:
We are using java code to invoke admin services.
sample code :
When running log mediator tests manually, we usually scan carbon log
to read log messages and decide the success or failure of the tests .
But how can this be done through admin service automated framework?
Currently we have written a primitive method to capture log messages
based on timestamp and
On Tue, Sep 21, 2010 at 7:27 PM, cham...@wso2.com cham...@wso2.com wrote:
When running log mediator tests manually, we usually scan carbon log
to read log messages and decide the success or failure of the tests .
But how can this be done through admin service automated framework?
Currently we
