Hey Raymond, Thanks for the reply - turns out it was because some of the client jars for weblogic and websphere were first on the class path and interfering with the behaviour of binding.jms
Once they were moved around it all went back to normal :) Cheers, Dave. -- Dave Sowerby MEng MBCS On Thu, Sep 25, 2008 at 4:48 PM, Raymond Feng <[EMAIL PROTECTED]> wrote: > What does your interface look like? Does it have the @Remotable annotation? > > Thanks, > Raymond > -------------------------------------------------- > From: "Dave Sowerby" <[EMAIL PROTECTED]> > Sent: Thursday, September 25, 2008 7:48 AM > To: <[email protected]> > Subject: Issues with binding.jms > >> Hi All, >> >> I'm having some trouble with binding.jms in a very simple case. >> >> Basically, the Payload of any TextObject sent to the queue is one of: >> >> null (The string, not the java type) >> [Ljava.lang.Object;@6b6a6b6a (yet again, this is a string) >> >> So this is parsed on the server side, unsurprisingly I get: >> >> SEVERE: Exception invoking service 'JMSService >> org.apache.axiom.om.OMException: >> com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character 'n' >> (code 110) in prolog; expected '<' >> at [row,col {unknown-source}]: [1,1] >> at >> org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:239) >> at >> org.apache.axiom.om.impl.llom.OMDocumentImpl.getOMDocumentElement(OMDocumentImpl.java:130) >> at >> org.apache.axiom.om.impl.builder.StAXOMBuilder.getDocumentElement(StAXOMBuilder.java:359) >> at >> org.apache.tuscany.sca.binding.jms.provider.XMLTextMessageProcessor.extractPayload(XMLTextMessageProcessor.java:57) >> at >> org.apache.tuscany.sca.binding.jms.provider.AbstractMessageProcessor.extractPayloadFromJMSMessage(AbstractMessageProcessor.java:97) >> at >> org.apache.tuscany.sca.binding.jms.provider.JMSBindingListener.invokeService(JMSBindingListener.java:90) >> at >> org.apache.tuscany.sca.binding.jms.provider.JMSBindingListener.onMessage(JMSBindingListener.java:71) >> at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:4072) >> at weblogic.jms.client.JMSSession.execute(JMSSession.java:3962) >> at >> weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4490) >> at >> weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518) >> at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209) >> at weblogic.work.ExecuteThread.run(ExecuteThread.java:181) >> >> Has anyone seen this one before, or should I raise a jira issue? >> >> Cheers, >> >> Dave. >> >> -- >> Dave Sowerby MEng MBCS > >
