camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Schneider Christian <>
Subject AW: AW: AW: Calling Soapservices using SoapDataFormat
Date Wed, 20 Oct 2010 14:18:26 GMT
So I guess it worked for jms and file because the data is serialized using java serialization.
Is that true?
Theoretically you could manually annotate the classes to be serialized with jaxb annotations.
In this case you would not need code generation. Currently the soap data format does not try
to use defaults when an annotation is missing so you have to manually make sure all necessary
annotations are present. Besides this scheme only works with one way services. That means
you will not be able to receive a response.

Best Regards


Christian Schneider
Business Solutions
Handel und Dispatching

Tel : +49-(0)721-63-15482

EnBW Systeme Infrastruktur Support GmbH
Sitz der Gesellschaft: Karlsruhe
Handelsregister: Amtsgericht Mannheim ­ HRB 108550
Vorsitzender des Aufsichtsrats: Dr. Bernhard Beck
Geschäftsführer: Jochen Adenau, Hans-Günther Meier

-----Ursprüngliche Nachricht-----
Von: fitzgerald [] 
Gesendet: Mittwoch, 20. Oktober 2010 16:00
Betreff: Re: AW: AW: Calling Soapservices using SoapDataFormat


We wanted to integrate with scala-akka and there is the possiblity to extend
from a producer trait and deliver the uri. That works of course fine for jms
and file, so my collegues wanted the same for soap, but without code
generation(direct wsdl usage instead of this).
Without the need of referencing the generated classes, we would get a kind
of generic loosly coupled component. And I was the nerd, who should do, what
can't be done in this way, what I have ever supposed. Thanks for your

View this message in context:
Sent from the Camel - Users mailing list archive at

View raw message