Hi, It was indeed the problem with return type. I could get it working when the return type was set to a string.
Is it mandatory to have a return type?? Can the service not have a void return type? I faced a similar problem when I was trying to deploy a native service. The wsdl2code utility did not generate the correct code when I had a void type. But when I used a int return type it worked fine. So I was wondering whether it was mandatory to have a return type. Any clarifications would be greatly appreciated. Regards, Altaf -----Original Message----- From: Konradi, Philipp (CT) [mailto:[EMAIL PROTECTED] Sent: 16 April 2008 14:31 To: tuscany-user@ws.apache.org Subject: AW: FW: JMS Binding - XML message - Message Format problems!! Hi, Some weeks ago I was also trying to switch from ObjectMessages to xml-based ones. I've run into the same problems. Unfortunately due to project deadlines I had to stick to the working solution. Anyway I'd also be interested if somebody has it working and what is the right way to do it (external app invokes via JMS an SCA service). Regards und many thanks, Philipp -----Ursprüngliche Nachricht----- Von: Altaf Muneer [mailto:[EMAIL PROTECTED] Gesendet: Dienstag, 15. April 2008 21:32 An: tuscany-user@ws.apache.org Betreff: Fwd: FW: JMS Binding - XML message - Message Format problems!! Hi, I hava deployed a* Java SCA service* and I am trying to use the* JMS binding* that tuscany provides. I have used a small java program to post a message to an activemq queue. I use the the JMS binding on the Java SCA service side to listen for messages. When I used an "*ObjectMessage*" to post the message to the queue it worked fine with tuscany's* 1.0.1 release*. But when I migrated to the 1.1 release of tuscany I started getting runtime exceptions because the* 1.1 release* accepts only* XML messages*. I therefore used a "*TextMessage*" object and formatted an xml message string and posted this to the queue. This calls the appropriate method. But after calling the method it throws the following runtime exceptions. Exception while processing message:* java.lang.ClassCastException*:*org.apache.tuscany.sca.binding.jms.impl.JMSBindingException * *java.lang.ClassCastException*:* org.apache.tuscany.sca.binding.jms.impl.JMSBindingException* at org.apache.tuscany.sca.binding.jms.provider.JMSMessageProcessorImpl.createXMLJMSMessage( *JMSMessageProcessorImpl.java:140*) at org.apache.tuscany.sca.binding.jms.provider.JMSMessageProcessorImpl.insertPayloadIntoJMSMessage( *JMSMessageProcessorImpl.java:85*) at org.apache.tuscany.sca.binding.jms.provider.JMSBindingListener.sendReply(* JMSBindingListener.java:125*) at org.apache.tuscany.sca.binding.jms.provider.JMSBindingListener.sendFaultReply( *JMSBindingListener.java:152*) at org.apache.tuscany.sca.binding.jms.provider.JMSBindingListener.onMessage(* JMSBindingListener.java:65*) at org.apache.activemq.ActiveMQMessageConsumer.dispatch(* ActiveMQMessageConsumer.java:854*) at org.apache.activemq.ActiveMQSessionExecutor.dispatch(* ActiveMQSessionExecutor.java:99*) at org.apache.activemq.ActiveMQSessionExecutor.iterate(* ActiveMQSessionExecutor.java:166*) at org.apache.activemq.thread.PooledTaskRunner.runTask(* PooledTaskRunner.java:117*) at org.apache.activemq.thread.PooledTaskRunner.access$100(* PooledTaskRunner.java:26*) at org.apache.activemq.thread.PooledTaskRunner$1.run(* PooledTaskRunner.java:44*) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask( *ThreadPoolExecutor.java:665*) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run( *ThreadPoolExecutor.java:690*) at java.lang.Thread.run(Unknown Source) It is a little strange because it throws an exception after calling the right method. The xml message I sent had the following structure. <soapenv:Envelope xmlns:q0="http://namespace1"; xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> <soapenv:Header> </soapenv:Header> <soapenv:Body> <q0:methodname> <q0:argname> <q0:id>myId</q0:id> <q0:name>myName</q0:name> </q0:argname> </q0:methodname> </soapenv:Body> </soapenv:Envelope> I am not sure what the problem here is. I think it might have to do with the message format. Also the method that is called does not have a return argument (that is it has a void return type). Is that a problem? Is there a kindred soul who can help me here :) ? Any help would be greatly appreciated. Cheers, Altaf --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Important notice:This e-mail and any attachment thereto contains corporate proprietary information. If you have received it by mistake, please notify us immediately by reply e-mail and delete this e-mail and its attachments from your system. Thank You. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
