Is the problem on the http side or the jsr181 side ?
Check the log file at debug level to see if the exchange
send by the http component is correct.
Btw, do you really need to pass an xml as a string ?
It seems a bit weird, but ...
Also, you may want to try with another binding like
xmlbeans or jaxb2.
On 10/27/06, robottaway <[EMAIL PROTECTED]> wrote:
I use the servicemix-http component to invoke a jsr181 POJO. The POJO has a
method which will take a string, the string is always a XML document. So I
call the service via the WSDL exposed by the servicemix-http component and
things go bad. The http component seems to strip out my XML that I pass in
the SOAP request. I end up passing an empty element to the jsr181 POJO. If I
pass a non-XML string everything works fine. Is this a known issue?
It would make sense to send in the XML docs straight to Servicemix.
Currently we send messages through an external web service, which uses JMS
connections to get message to Smix. Could this issue possibly tie to the xsd
for the string type? I get this wierd AegisBinding error all the time:
DEBUG - Jsr181Component - Received exchange: status: Active,
role: provider
DEBUG - JbiTransport - Creating new channel for uri:
urn:xfire:transport:jbi:11619025657711474131095
INFO - AegisBindingProvider - xsi:type="" was specified, but no
corresponding Type was registered; defaulting to
{http://www.w3.org/2001/XMLSchema}string
Oct 26, 2006 3:42:45 PM org.mf.smix.axdatagateway.jsr181.ItemdataGate
releaseDocument
INFO: Xml doc:
DEBUG - DeliveryChannelImpl - SendSync
ID:robert-ottaways-computer.local-52119-1161900037379-7:4 in
DeliveryChannel{servicemix-jsr181}
DEBUG - DeliveryChannelImpl - Sent: InOnly[
--
View this message in context:
http://www.nabble.com/servicemix-http-tf2517441.html#a7021459
Sent from the ServiceMix - User mailing list archive at Nabble.com.
--
Cheers,
Guillaume Nodet
