Hi,
Whoever did this change broke the build. Because, integration tests not
running is breaking the build. In case I missed it, is there a mail saying
there's a platform wide axis2 version change happening, and the products
need to be checked?
We are on the verge of a release, and this wasted a l
On Mon, May 13, 2013 at 1:43 PM, Miyuru Wanninayaka wrote:
> Reason is kernel 4.1.0 packs axis2-transport-jms_1.1.0.wso2v7 even kernel
> 4.1.0 source has transport v8 code.
>
> So patching transport v8 codes does not have effect because v7 versions of
> jars packs by kernel 4.1.0 distribution. We
On Mon, May 13, 2013 at 1:43 PM, Miyuru Wanninayaka wrote:
> Reason is kernel 4.1.0 packs axis2-transport-jms_1.1.0.wso2v7 even kernel
> 4.1.0 source has transport v8 code.
>
> So patching transport v8 codes does not have effect because v7 versions of
> jars packs by kernel 4.1.0 distribution. We
On Mon, May 13, 2013 at 6:59 PM, Kasun Weranga wrote:
> Hi,
>
> We are also getting this issue while running integration tests.
>
> Failed tests:
> startServer(org.wso2.bam.integration.tests.BAMTestServerManager):
> org.testng.internal.InvokeMethodRunnable$TestNGRuntimeException:
> java.lang.NoSu
Hi,
We are also getting this issue while running integration tests.
Failed tests:
startServer(org.wso2.bam.integration.tests.BAMTestServerManager):
org.testng.internal.InvokeMethodRunnable$TestNGRuntimeException:
java.lang.NoSuchMethodError:
org.apache.axis2.transport.TransportUtils.getMessageFor
Reason is kernel 4.1.0 packs axis2-transport-jms_1.1.0.wso2v7 even kernel
4.1.0 source has transport v8 code.
So patching transport v8 codes does not have effect because v7 versions of
jars packs by kernel 4.1.0 distribution. We have to change version of
transport code in patch0001 to v7 to make p
Guys this still broken, seems like though we applied patch it has not
resloved the JMS issue, I can see the ESB instance now packed with two
versions of JMS axis2-transport-jms_1.1.0.wso2v7
and axis2-transport-jms_1.1.0.wso2v8 appricate a quick response ASAP
On Fri, May 10, 2013 at 12:26 PM, Sen
Builds fine.
Thanks,
Senaka.
On Fri, May 10, 2013 at 12:21 PM, Kasun Gajasinghe wrote:
> Thanks for fixing the issue Kishanthan.
>
>
> On Fri, May 10, 2013 at 12:14 PM, Kishanthan Thangarajah <
> kishant...@wso2.com> wrote:
>
>> Yes, It was broken with r172001. The reason is the transport modu
Thanks for fixing the issue Kishanthan.
On Fri, May 10, 2013 at 12:14 PM, Kishanthan Thangarajah <
kishant...@wso2.com> wrote:
> Yes, It was broken with r172001. The reason is the transport modules were
> still referring to an old axis2 dependency. Fixed it with r172095.
>
> All,
>
> When adding
Yes, It was broken with r172001. The reason is the transport modules were
still referring to an old axis2 dependency. Fixed it with r172095.
All,
When adding new fixes to the patch, you have to built it with the *clean
repo*. This will make sure that the fixes you add doesn't break the build
of t
Hi Kasun,
The build is broken with commit r172001. If you do "svn up -r172000" and
build, it works fine.
Thanks,
Senaka.
On Fri, May 10, 2013 at 9:34 AM, Dushan Abeyruwan wrote:
> Do I ? I am suppose to build from root pom available at patch0001 rite?
>
>
> On Fri, May 10, 2013 at 9:18 AM, Ka
Do I ? I am suppose to build from root pom available at patch0001 rite?
On Fri, May 10, 2013 at 9:18 AM, Kasun Gajasinghe wrote:
> Hi Duashan,
>
> Did you build axis2-kernel dependency? It's also available under the
> patch0001.
>
>
> On Friday, May 10, 2013, Dushan Abeyruwan wrote:
>
>> Patch0
Hi Duashan,
Did you build axis2-kernel dependency? It's also available under the
patch0001.
On Friday, May 10, 2013, Dushan Abeyruwan wrote:
> Patch001 not building (when take latest update)
>
>
> [INFO] Apache Axis2 - Clustering . SUCCESS [1.339s]
> [INFO] Apache Axis2 -
Patch001 not building (when take latest update)
[INFO] Apache Axis2 - Clustering . SUCCESS [1.339s]
[INFO] Apache Axis2 - Transport - Base ... FAILURE [1.702s]
[INFO] Apache Axis2 - Transport - JMS SKIPPED
[INFO] Apache Axis2 - Transpor
Yes, since this is not an API change but rather the usage of the new API is
not updated, you can proceed with normal kernel patching process as
described in [1]. Use patch0001.
Thanks,
Kishanthan.
[1]
https://docs.google.com/a/wso2.com/document/d/1Kz6vINXA1j74sM8vb8BE0BSIAUnYJH0BERbJxwxi2xQ/edit
Hi,
Had a chat with kasung related to this. Seems we have to modify the
transports.
Kasung will provide a patch on this.
I believe we can include this fix into kernel patch0001?.
Pradeep/Kishanthan is that the recommended way?.
thanks,
On Thu, May 9, 2013 at 9:56 AM, Dushan Abeyruwan wrote:
>
13-05-09 09:52:41,588] INFO - JMSListener JMS listener started
[2013-05-09 09:52:41,743] INFO - RegistryEventingServiceComponent
Successfully Initialized Eventing on Registry
[2013-05-09 09:52:42,133] INFO - JMXServerManager JMX Service URL :
service:jmx:rmi://localhost:1/jndi/rmi://localho
17 matches
Mail list logo
