The typo was on the Camel SOAP documentation page which is corrected now.

Babak


Christian Mueller wrote
> Could you please tell as on which page you found the outdated code
> snipped!?
> 
> Best,
> 
> Christian
> -----------------
> 
> Software Integration Specialist
> 
> Apache Member
> V.P. Apache Camel | Apache Camel PMC Member | Apache Camel committer
> Apache Incubator PMC Member
> 
> https://www.linkedin.com/pub/christian-mueller/11/551/642
> 
> 
> On Sat, Oct 26, 2013 at 5:54 PM, Julián Ignacio Gómez Arias <

> jgomez@

>> wrote:
> 
>> Never Mind I fount that the documentation is outdated and the correct tag
>> is: 
> <soapjaxb>
>>
>>
>> Thanks
>>
>>
>>
>> El 26/10/2013, a las 9:25, Julián Ignacio Gómez Arias &lt;

> jgomez@

> &gt;
>> escribió:
>>
>> > Hi to all,
>> >
>> > I’m having some problems when using the data format soap on a camel
>> Spring XML.
>> >
>> >
>> > I gave for example this:
>> >
>> >                       
> <from
>>
>  uri="cxf:bean:wsLocal?dataFormat=CXF_MESSAGE" />
>> >                       
> <marshal>
>> >                               
> <soap
>>
>  contentPath="co.com.une.interfazhss.InterfazHSS" version="1.2"
>> >                                       elementNameStrategyRef="soapST"
>> />
>> >                       
> </marshal>
>> >
>> >                       
> <to uri="wsRemoto" />
>> >                       
> <process ref="Proceso2" />
>> >
>> > The 
> <soap>
>  tag its not recognized and says this:
>> >
>> > cvc-complex-type.2.4.a: Invalid content was found starting with element
>> 'soap'. One of '{"http://
>> > camel.apache.org/schema/spring":description, "
>> http://camel.apache.org/schema/spring":avro, "http://
>> > camel.apache.org/schema/spring":beanio, "
>> http://camel.apache.org/schema/spring":bindy, "http://
>> > camel.apache.org/schema/spring":c24io, "
>> http://camel.apache.org/schema/spring":castor, "http://
>> > camel.apache.org/schema/spring":crypto, "
>> http://camel.apache.org/schema/spring":csv, "http://
>> > camel.apache.org/schema/spring":custom, "
>> http://camel.apache.org/schema/spring":flatpack, "http://
>> > camel.apache.org/schema/spring":gzip, "
>> http://camel.apache.org/schema/spring":hl7, "http://
>> > camel.apache.org/schema/spring":jaxb, "
>> http://camel.apache.org/schema/spring":jibx, "http://
>> > camel.apache.org/schema/spring":json, "
>> http://camel.apache.org/schema/spring":protobuf, "http://
>> > camel.apache.org/schema/spring":rss, "
>> http://camel.apache.org/schema/spring":secureXML, "http://
>> > camel.apache.org/schema/spring":serialization, "
>> http://camel.apache.org/schema/spring":soapjaxb,
>> > "http://camel.apache.org/schema/spring":string, "
>> http://camel.apache.org/schema/spring":syslog, "http://
>> > camel.apache.org/schema/spring":tidyMarkup, "
>> http://camel.apache.org/schema/spring":xmlBeans, "http://
>> > camel.apache.org/schema/spring":xmljson, "
>> http://camel.apache.org/schema/spring":xstream, "http://
>> > camel.apache.org/schema/spring":pgp, "
>> http://camel.apache.org/schema/spring":zip}' is expected.
>> >
>> >
>> > For other data formats like JSON and others work well.
>> >
>> > Is there something I can do?
>> >
>> >
>> > Best regards,
>> >
>> >
>>
>>





--
View this message in context: 
http://camel.465427.n5.nabble.com/Large-objects-in-headers-and-endpoints-tp5741858p5742272.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Reply via email to