You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@synapse.apache.org by "Asankha C. Perera" <as...@apache.org> on 2009/11/13 05:35:53 UTC
Synapse 1.3 release and dependency on Axis2
Hi Ruwan
It seems like the REST/POX support we checked into Synapse trunk for 1.3
is broken against the Axis2 1.5 release - See snippets [1] and [2] ..
Currently the 1.3-SNAPSHOT depends on Axis2 1.5, but as a 1.5.1 has been
released, do you plan to change the version - I'm afraid that moving to
that may expose other inconsistencies or still be broken as we haven't
still found out.. I guess its another aspect of being too dependent on
Axis2 :( ..
cheers
asankha
1. An example of a HTTP 201 created response being interpreted as a
binary message when sending through Synapse:
HTTP/1.1 201 Created
Content-Type: application/xml; charset=UTF-8
Location: http://localhost:8280/services/oauth/customers/1
Date: Fri, 13 Nov 2009 04:11:04 GMT
Server: Synapse-HttpComponents-NIO
Transfer-Encoding: chunked
Connection: Keep-Alive
09:41:04.465243 IP 127.0.0.1.4488 > 127.0.0.1.8280: . ack 256 win 265
<nop,nop,timestamp 740202 740202>
E..4.;@.@............. XJ...JW.p... .......
..Kj..Kj
09:41:04.470653 IP 127.0.0.1.8280 > 127.0.0.1.4488: P 256:359(103) ack
431 win 273 <nop,nop,timestamp 740204 740202>
E....z@.@.J......... X..JW.pJ..............
..Kl..Kj5c
<axis2ns1:binary
xmlns:axis2ns1="http://ws.apache.org/commons/ns/payload"></axis2ns1:binary>
0
2. The Synapse stacktrace showing the kick-in of a binary builder when
processing a HTTP 204 No content response
2009-11-13 09:41:06,557 [-] [HttpClientWorker-3] ERROR NativeWorkerPool
Uncaught exception
java.lang.NullPointerException
at org.apache.commons.io.IOUtils.copyLarge(IOUtils.java:1025)
at org.apache.commons.io.IOUtils.copy(IOUtils.java:999)
at org.apache.commons.io.IOUtils.toByteArray(IOUtils.java:218)
at
org.apache.axis2.format.BinaryBuilder.processDocument(BinaryBuilder.java:72)
at
org.apache.axis2.transport.TransportUtils.createDocumentElement(TransportUtils.java:192)
at
org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:140)
at
org.apache.synapse.transport.nhttp.ClientWorker.run(ClientWorker.java:183)
at
org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:58)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
--
Asankha C. Perera
AdroitLogic, http://adroitlogic.org
http://esbmagic.blogspot.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
Re: Synapse 1.3 release and dependency on Axis2
Posted by Ruwan Linton <ru...@gmail.com>.
I think we should move to axis2-1.5.1, there are few bug fixes in
axis2-1.5.1 and should be OK to move to it. I think we better switch to it
soon. I am in the process of getting the transports release out, and once
that is out we can build the RC of synapse, I guess.
Thanks,
Ruwan
On Fri, Nov 13, 2009 at 10:05 AM, Asankha C. Perera <as...@apache.org>wrote:
> Hi Ruwan
>
> It seems like the REST/POX support we checked into Synapse trunk for 1.3
> is broken against the Axis2 1.5 release - See snippets [1] and [2] ..
> Currently the 1.3-SNAPSHOT depends on Axis2 1.5, but as a 1.5.1 has been
> released, do you plan to change the version - I'm afraid that moving to
> that may expose other inconsistencies or still be broken as we haven't
> still found out.. I guess its another aspect of being too dependent on
> Axis2 :( ..
>
> cheers
> asankha
>
> 1. An example of a HTTP 201 created response being interpreted as a
> binary message when sending through Synapse:
>
> HTTP/1.1 201 Created
> Content-Type: application/xml; charset=UTF-8
> Location: http://localhost:8280/services/oauth/customers/1
> Date: Fri, 13 Nov 2009 04:11:04 GMT
> Server: Synapse-HttpComponents-NIO
> Transfer-Encoding: chunked
> Connection: Keep-Alive
>
>
> 09:41:04.465243 IP 127.0.0.1.4488 > 127.0.0.1.8280: . ack 256 win 265
> <nop,nop,timestamp 740202 740202>
> E..4.;@.@............. XJ...JW.p... .......
> ..Kj..Kj
> 09:41:04.470653 IP 127.0.0.1.8280 > 127.0.0.1.4488: P 256:359(103) ack
> 431 win 273 <nop,nop,timestamp 740204 740202>
> E....z@.@.J......... X..JW.pJ..............
> ..Kl..Kj5c
> <axis2ns1:binary
> xmlns:axis2ns1="http://ws.apache.org/commons/ns/payload
> "></axis2ns1:binary>
> 0
>
> 2. The Synapse stacktrace showing the kick-in of a binary builder when
> processing a HTTP 204 No content response
>
> 2009-11-13 09:41:06,557 [-] [HttpClientWorker-3] ERROR NativeWorkerPool
> Uncaught exception
> java.lang.NullPointerException
> at org.apache.commons.io.IOUtils.copyLarge(IOUtils.java:1025)
> at org.apache.commons.io.IOUtils.copy(IOUtils.java:999)
> at org.apache.commons.io.IOUtils.toByteArray(IOUtils.java:218)
> at
>
> org.apache.axis2.format.BinaryBuilder.processDocument(BinaryBuilder.java:72)
> at
>
> org.apache.axis2.transport.TransportUtils.createDocumentElement(TransportUtils.java:192)
> at
>
> org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:140)
> at
> org.apache.synapse.transport.nhttp.ClientWorker.run(ClientWorker.java:183)
> at
>
> org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:58)
> at
>
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at
>
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:619)
>
> --
> Asankha C. Perera
> AdroitLogic, http://adroitlogic.org
>
> http://esbmagic.blogspot.com
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
> For additional commands, e-mail: dev-help@synapse.apache.org
>
>
--
Ruwan Linton
Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
WSO2 Inc.; http://wso2.org
email: ruwan@wso2.com; cell: +94 77 341 3097
blog: http://ruwansblog.blogspot.com