Hi Malaka,
As an offline chat with Buddhima,
if a certain version of automation frame work needs a certain axis2
version, then there should be a release version of automation framework
along with that axis2.
On Mon, May 9, 2016 at 9:56 AM, Hariprasath Thanarajah wrote:
>
Noted malaka.
On Monday, May 9, 2016, Malaka Silva wrote:
> I think this is nothing to do with wso2-synapse. You need to change
> automation framework accordingly.
>
> On Mon, May 9, 2016 at 9:48 AM, Hariprasath Thanarajah <
> haripras...@wso2.com
>
I think this is nothing to do with wso2-synapse. You need to change
automation framework accordingly.
On Mon, May 9, 2016 at 9:48 AM, Hariprasath Thanarajah wrote:
> Yes Malaka. I think we have to change the axis2 version to 1.6.1-wso2v17
> in the wso2-synapse. Then we
Yes Malaka. I think we have to change the axis2 version to 1.6.1-wso2v17 in
the wso2-synapse. Then we can release the connector with integration test.
On Monday, May 9, 2016, Malaka Silva wrote:
> Hi Hariprasath,
>
> So clearly this is nothing to do with ESB. Dependency you are
Hi Hariprasath,
So clearly this is nothing to do with ESB. Dependency you are getting from
automation is causing this issue.
On Sun, May 8, 2016 at 10:01 PM, Hariprasath Thanarajah <
haripras...@wso2.com> wrote:
> Hi Malaka,
>
> In the integration test It takes the axis2-version from
Hi Malaka,
In the integration test It takes the axis2-version from wso2-synapse
according to[1]. But still the version of axis2 in wso2-synapse is
1.6.1-wso2v12 according to [2]. When I locally change the version to
axis2-1.6.1-wso2v17
and built then the integration test for salesforce is running
Noted malaka.
On Thursday, April 21, 2016, Malaka Silva wrote:
> Hi Hariprasath,
>
> Best is start debugging fresh pack with the release tag and apply the fix
> and check [1].
>
> Did you check this with esb 5 alpha alread? If not do so.
>
> [1]
>
Hi Hariprasath,
Best is start debugging fresh pack with the release tag and apply the fix
and check [1].
Did you check this with esb 5 alpha alread? If not do so.
[1] https://docs.wso2.com/display/TA430/Debugging+Product+Integration+Tests
On Thu, Apr 21, 2016 at 2:53 AM, Hariprasath Thanarajah
As malaka said this is slightly different from the usual way and Malaka, I
copied the patch to the folder and put the zip to the repository. Need to
investigate further.
On Wednesday, April 20, 2016, Malaka Silva wrote:
> Hariprasath is doing this for connectors. It is slightly
Hariprasath is doing this for connectors. It is slightly different than
running esb integration tests. We need to copy the zip file
to repository folder. Hope you have updated the zip file with patch in that
case.
On Wed, Apr 20, 2016 at 10:08 PM, Thusitha Thilina Dayaratne <
thusit...@wso2.com>
Hi Hariprasath,
Did you apply the patch manually to the pack when you run the integration
test? AFAIK when you run integration tests it will use the already built
default pack. It will not contains the patch.
Thanks
Thusitha
On Wed, Apr 20, 2016 at 9:32 AM, Malaka Silva
Hi Hariprasath,
You need to debug and investigate this further. Find details on debugging
integration test in [1]
[1] https://docs.wso2.com/display/TA430/Debugging+Product+Integration+Tests
On Wed, Apr 20, 2016 at 6:18 PM, Hariprasath Thanarajah <
haripras...@wso2.com> wrote:
> Hi All,
>
> I
Noted Malaka,
I will check and update on this.
On Tue, Apr 19, 2016 at 1:11 PM, Malaka Silva wrote:
> Hi Hariprasath,
>
> Seems like a issue is mentioned in [1]. Ideally this should be fixed in
> ESB alpha release. Please check.
>
> If not apply the fix and see if that works.
Hi Hariprasath,
Seems like a issue is mentioned in [1]. Ideally this should be fixed in ESB
alpha release. Please check.
If not apply the fix and see if that works. If works add a jira for esb 5.
[1] https://wso2.org/jira/browse/ESBJAVA-4388
On Thu, Apr 7, 2016 at 3:59 PM, Hariprasath
Hi Malaka,
I am doing it now. I'll update the status by evening.
On Fri, Apr 8, 2016 at 2:24 PM, Malaka Silva wrote:
> Hariprasath shall we try debugging this?
>
> On Thu, Apr 7, 2016 at 10:47 PM, Hariprasath Thanarajah <
> haripras...@wso2.com> wrote:
>
>> Hi Malaka,
>>
>> No
Hariprasath shall we try debugging this?
On Thu, Apr 7, 2016 at 10:47 PM, Hariprasath Thanarajah <
haripras...@wso2.com> wrote:
> Hi Malaka,
>
> No In this I set the blocking as false and also test it with ESB 5.0.0-M1.
>
> On Thu, Apr 7, 2016 at 9:08 PM, Malaka Silva wrote:
>
Hi Malaka,
No In this I set the blocking as false and also test it with ESB 5.0.0-M1.
On Thu, Apr 7, 2016 at 9:08 PM, Malaka Silva wrote:
> Hariprasath seems like this is related to [1]. Are you using call mediator
> in blocking mode? If so avoid it for integration tests with
Hariprasath seems like this is related to [1]. Are you using call mediator
in blocking mode? If so avoid it for integration tests with esb 490.
[1] https://wso2.org/jira/browse/ESBJAVA-4388
On Thu, Apr 7, 2016 at 3:59 PM, Hariprasath Thanarajah wrote:
> Hi All,
>
> I am
Hi All,
I have attached the wire log here.
On Thu, Apr 7, 2016 at 3:59 PM, Hariprasath Thanarajah wrote:
> Hi All,
>
> I am working on to create integration test for salesforce connector. When
> I create the testcase for a particular method(getUserInfo) I got the
>
Hi All,
I am working on to create integration test for salesforce connector. When I
create the testcase for a particular method(getUserInfo) I got the response
via the ESB call but after that I get the following error in [1].
I have added the proxy[2] and soap request[3] as well.
Can anyone
20 matches
Mail list logo