Two steps forward, one step back, or so it seems. The jmsFlow seems to be broken - at least in my custom build of ServiceMix. The version of the codebase that I am using is 1055, with "servicemix/components/http/*" and "servicemix/components/saaj/*" from the Apache-HEAD. In addition, I am using the xfire-all-1.0-20051222.jar. This is happening using the Sun Java 5 JVM for both ActiveMQ 3.2.1 and ServiceMix.
With this build, the SEDA flow works properly, and the client gets the response from the invoked SOAP service (SOAP client -> HttpSoapClient -> SaajComponent -> SOAP service). When I change the flow to JMS, using ActiveMQ 3.2.1 with the "reliable" connect string, my client throws a NullPointerException. This is because the SOAP-Body in the response is completely empty. I have verified that the body is populated correclty by the SaajComponent (visible in the DEBUG output in log4j), but the actual HttpResponse from the HttpSoapConnector has an empty SOAP-Body. As this problem only presents itself using the JMS flow, and only surfaced after using the newer classes and library, I am fairly certain that these events are all highly correlated, but I am not sure what the root cause is. I need the new classes, and the newer xfire library in order for my services to call successfully under SEDA, and cannot revert. regards, /jonathan > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Wednesday, December 28, 2005 9:53 AM > To: [email protected] > Subject: RE: [servicemix-user] Problems invoking a web > service with SOAP > > > Guillaume, > > Installing the new Xfire library did the trick: The XML > returned from the > SaajComponent is well formed, and the HttpSoapConnector handles the > Http+SOAP calls properly. Thanks to everyone who helped me to get Soap > communication working, especially Guillaume :-) > > Now I'm off to wrestle with the IBM Java 5 JVM (beta) on AIX. > > best wishes for the holidays, > /jonathan >
