Indeed, we should definitely add a Synapse sample to demonstrate the MapMessage support.
Andreas On Wed, Oct 29, 2008 at 21:17, Senaka Fernando <[EMAIL PROTECTED]> wrote: > Hi Andreas, > Many thanks. I will modify the JMS Map Message implementation I'm working on > at the moment to reflect the new changes and try it out. We can perhaps > improve the existing Synapse sample to make use of Map Messages as well as a > proof of concept. WDYT? > Regards, > Senaka > > On Thu, Oct 30, 2008 at 1:40 AM, Andreas Veithen <[EMAIL PROTECTED]> > wrote: >> >> Samples (250-253) are now all checked and fixed. >> >> Andreas >> >> On Mon, Oct 27, 2008 at 14:59, Senaka Fernando <[EMAIL PROTECTED]> >> wrote: >> > Hi Andreas, >> > >> > OK with latest revisions of transport and Synapse (I'm using the trunk >> > in >> > both projects), when running, >> > >> > sample 250: >> > >> > Error on Synapse: >> > >> > ERROR AxisEngine The endpoint reference (EPR) for the Operation not >> > found >> > is and the WSA Action = null >> > org.apache.axis2.AxisFault: The endpoint reference (EPR) for the >> > Operation >> > not found is and the WSA Action = null >> > at >> > >> > org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhase.java:89) >> > at org.apache.axis2.engine.Phase.invoke(Phase.java:334) >> > at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:248) >> > at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:157) >> > at >> > >> > org.apache.axis2.transport.base.AbstractTransportListener.handleIncomingMessage(AbstractTransportListener.java:286) >> > at >> > >> > org.apache.axis2.transport.jms.JMSMessageReceiver$Worker.run(JMSMessageReceiver.java:216) >> > at >> > >> > org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:58) >> > at >> > >> > java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885) >> > at >> > >> > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907) >> > at java.lang.Thread.run(Thread.java:619) >> > org.apache.axis2.AxisFault: The endpoint reference (EPR) for the >> > Operation >> > not found is and the WSA Action = null >> > at >> > >> > org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPhase.java:89) >> > at org.apache.axis2.engine.Phase.invoke(Phase.java:334) >> > at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:248) >> > at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:157) >> > at >> > >> > org.apache.axis2.transport.base.AbstractTransportListener.handleIncomingMessage(AbstractTransportListener.java:286) >> > at >> > >> > org.apache.axis2.transport.jms.JMSMessageReceiver$Worker.run(JMSMessageReceiver.java:216) >> > at >> > >> > org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:58) >> > at >> > >> > java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885) >> > at >> > >> > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907) >> > at java.lang.Thread.run(Thread.java:619) >> > 2008-10-27 19:14:54,063 [127.0.1.1-home] [jms-Worker-1] ERROR >> > JMSMessageReceiver java.lang.NullPointerException >> > >> > sample 252: >> > >> > Error on axis2Server: >> > >> > [HttpServerWorker-2] ERROR RPCInOnlyMessageReceiver Exception occurred >> > while >> > trying to invoke service method placeOrder >> > org.apache.axis2.AxisFault: namespace mismatch require >> > http://services.samples found http://services.samples/xsd >> > at >> > >> > org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:177) >> > at >> > >> > org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver.invokeBusinessLogic(RPCInOnlyMessageReceiver.java:63) >> > at >> > >> > org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:114) >> > at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:170) >> > at >> > >> > org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:167) >> > at >> > >> > org.apache.synapse.transport.nhttp.ServerWorker.processPost(ServerWorker.java:278) >> > at >> > >> > org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:187) >> > at >> > >> > org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:58) >> > at >> > >> > java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885) >> > at >> > >> > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907) >> > at java.lang.Thread.run(Thread.java:619) >> > 2008-10-27 19:22:24,310 [-] [HttpServerWorker-2] ERROR >> > AbstractMessageReceiver org.apache.axis2.AxisFault: Exception occurred >> > while >> > trying to invoke service method placeOrder >> > >> > These might need some trivial fixing (especially sample 252), which I >> > have >> > not tried. >> > >> > Regards, >> > Senaka >> > >> > N.B. I have copied this mail to Synapse dev as well. >> > >> > On Mon, Oct 27, 2008 at 3:06 PM, Senaka Fernando >> > <[EMAIL PROTECTED]>wrote: >> > >> >> On Mon, Oct 27, 2008 at 08:56, Senaka Fernando <[EMAIL PROTECTED]> >> >> wrote: >> >> >> >>> > Hi Andreas, >> >>> > >> >>> > Thanks. However, If the BaseUtils#setSOAPEnvelope is only used by >> >>> > the >> >>> AMQP >> >>> > Transport in Synapse, that is better off. This was another question >> >>> > that >> >>> I >> >>> > wanted to ask. Certain features of BaseUtils are only used by >> >>> > certain >> >>> > Transports and not all. Thus, is it really some feature that must >> >>> > remain >> >>> at >> >>> > the base level? This is the point, certain aspects of certain >> >>> > transports >> >>> > will never really require such functionality. >> >>> >> >>> In the beginning, BaseUtils#setSOAPEnvelope was used by several >> >>> transports (mail, JMS, AMQP and VFS I think). I changed the mail and >> >>> VFS transports already some time ago. Now that the JMS transport no >> >>> longer relies on this method, I will move this code to the AMQP >> >>> transport and clean up BaseUtils. >> >> >> >> >> >> Thanks for the clarification. >> >> >> >>> >> >>> >> >>> > Also, since you are familiar with Synapse, does the Synapse JMS >> >>> "samples" >> >>> > work with the new Transport? Has it been tested? I couldn't run some >> >>> > of >> >>> them >> >>> > (may be due to some of the dependant jars being disorganized on my >> >>> > box). >> >>> >> >>> Good point. I need to check that. Which are the samples that didn't >> >>> work for you? >> >> >> >> >> >> Let me get back to you with exact revision details. >> >> >> >> >> >> >> > >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
