Hi,
I have tested the scenarios for security use cases. I am getting the
following issue when test with the blocking and security. Blocking Sender
is not handled the security scenario properly.
[2015-03-05 12:42:36,601] ERROR {org.apache.axis2.engine.AxisEngine} -
Missing wsse:Security header in
Hi Isuru,
Ok, I will test the scenarios for security use cases.
Thanks,
Kathees
On Tue, Mar 3, 2015 at 8:57 PM, Isuru Udana wrote:
> Hi Kathees,
>
> Please include test scenarios for Security use cases as well.
>
> Thank you.
>
> On Tue, Mar 3, 2015 at 12:05 PM, Kathees Rajendram
> wrote:
>
>
Hi Kathees,
Please include test scenarios for Security use cases as well.
Thank you.
On Tue, Mar 3, 2015 at 12:05 PM, Kathees Rajendram wrote:
> Hi Isuru,
>
> I have tested the core functionality of blocking and non blocking. Please
> find the test plan and some test results.
>
>
>
> Test No
>
Hi Isuru,
I have tested the core functionality of blocking and non blocking. Please
find the test plan and some test results.
Test No
Test
Configuration
Expected result
Observed results
Status
Functional Testing
1
Direct endpoint without blocking
http://localhost:9000/ser
Hi Kathees,
I believe you are conducting developer testing for newly implemented
functionality.
Could you please share the test plan with us.
Thank you.
On Fri, Feb 27, 2015 at 9:36 AM, Kathees Rajendram wrote:
> Hi Isuru,
>
> I will additionally add the following section for blocking function
Hi Isuru,
I will additionally add the following section for blocking functionality in
call mediator.
Thanks
Kathees
On Thu, Feb 26, 2015 at 10:48 AM, Kathees Rajendram
wrote:
> Hi Isuru,
>
> I have implemented the blocking functionality in call mediator.
>
> Please find the pull request [1
Hi Isuru,
I have implemented the blocking functionality in call mediator.
Please find the pull request [1] for wso2-synapse
[1] - https://github.com/wso2/wso2-synapse/pull/93
Thanks,
Kathees
On Wed, Feb 25, 2015 at 5:06 PM, Kathees Rajendram wrote:
> Hi Isuru,
>
> Endpoint with key is not ha
Hi Isuru,
Endpoint with key is not handled in BlockingSender.I will introduce the
changes in BlockingSender.
Thanks,
kathees
On Wed, Feb 25, 2015 at 4:26 PM, Isuru Udana wrote:
> Hi Kathees,
>
> If you find this not working, please introduce this change to the
> BlockingMsgSender but not the C
Hi Kathees,
If you find this not working, please introduce this change to the
BlockingMsgSender but not the Call Mediator. So that all the components
using BlockingMsgSender will inherit this.
Thanks.
On Wed, Feb 25, 2015 at 4:14 PM, Isuru Udana wrote:
> Hi Kathees,
>
> On Tue, Feb 24, 2015 at
Hi Kathees,
On Tue, Feb 24, 2015 at 4:00 PM, Kathees Rajendram wrote:
> Hi Isuru,
>
> The blocking is working in the following synapse configuration.
>
>
>
>http://localhost:9000/services/SimpleStockQuoteService"/>
>
>
>
> but I want to add the blocki
Hi Isuru,
The blocking is working in the following synapse configuration.
http://localhost:9000/services/SimpleStockQuoteService"/>
but I want to add the blocking in the following configuration also, as it
is in call mediator.
Hi Kathees,
On Tue, Feb 24, 2015 at 3:06 PM, Kathees Rajendram wrote:
> Hi,
>
> The call mediator blocking is working with direct endpoint. I want to
> write logic with endpoint key and Xpath. We can't use the existing
> functionality for blocking as it is in call mediator.
>
Could you please
Hi,
The call mediator blocking is working with direct endpoint. I want to write
logic with endpoint key and Xpath. We can't use the existing functionality
for blocking as it is in call mediator.
Thanks,
Kathees
--
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
__
13 matches
Mail list logo
