Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
From: Scott Came <scott.came@search.org>
To: "users@camel.apache.org" <users@camel.apache.org>
Date: Sat, 26 Feb 2011 07:28:05 -0800
Subject: RE: File consumer to CXF issues
Thread-Topic: File consumer to CXF issues
Thread-Index: AcvVh/xq+ME78CmVQLaEeTyLmpNDpwAQURxA
Message-ID: 
 <C44E58389D52844CB0CB648B1BC15C73011867488D36@VA3DIAXVS121.RED001.local>
References: 
 <C44E58389D52844CB0CB648B1BC15C73011867488B9B@VA3DIAXVS121.RED001.local>
 <C44E58389D52844CB0CB648B1BC15C73011867488D24@VA3DIAXVS121.RED001.local>
 <AANLkTimU_sML3bNjf0rt-5p4e44XFFjiwtosCuezYn-V@mail.gmail.com>
In-Reply-To: <AANLkTimU_sML3bNjf0rt-5p4e44XFFjiwtosCuezYn-V@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

The file contains XML...the root element of the xml document in the file is=
 the child element of soap:body.

I tried MESSAGE and it seems the CXF component is expecting the file to con=
tain the entire SOAP message (envelope and body), which would be a pain to =
create.  I'd rather avoid POJO mode since I really don't want to have to ge=
nerate code.  But nonetheless I tried it and ran into a whole bunch more ex=
ceptions...probably wasn't configuring it right.

I'd rather learn how to write a converter and do that than have to generate=
 code.

How do I explore whether there is a converter missing?  Again, it's surpris=
ing that there isn't a converter that will take a GenericFile (or String) a=
nd plop it into the soap:body, since that seems like such a common scenario=
...so there must be something I'm missing.

Thanks.

-----Original Message-----
From: Claus Ibsen [mailto:claus.ibsen@gmail.com]=20
Sent: Friday, February 25, 2011 11:35 PM
To: users@camel.apache.org
Subject: Re: File consumer to CXF issues

Hi

What does your file contain?

Often people use either POJO or MESSAGE format. So there could be a convert=
er to/from CxfPayload missing. Especially for String, byte[], streams which=
 is common types.


On Sat, Feb 26, 2011 at 7:53 AM, Scott Came <scott.came@search.org> wrote:
> After looking at this a bit more (and upgrading to the 4.3.1-fuse-00-00 v=
ersion of ServiceMix, which contains Camel 2.6.0), it seems the problem boi=
ls down to Camel not knowing how to convert a GenericFile (what results fro=
m the <from> part of the route) to a CxfPayload (what is expected by the <t=
o> part of the route).
>
> Am I on the right track here?
>
> If so, is there an available converter that does that? =A0It seems like a=
 fairly common scenario to pick up an XML document that fits the schema for=
 a particular SOAP operation and send that document in the body of a SOAP m=
essage to a web service. =A0So I'm surprised this isn't built in...perhaps =
it is, and I'm just not doing something correctly.
>
> By the way, I tried using convertBodyTo to convert the input file to java=
.lang.String and org.w3c.dom.Document, and those efforts resulted in except=
ions too.
>
> Any help appreciated.
>
> Thanks.
> --Scott
>
> -----Original Message-----
> From: Scott Came [mailto:scott.came@search.org]
> Sent: Friday, February 25, 2011 1:57 PM
> To: users@camel.apache.org
> Subject: File consumer to CXF issues
>
> I have a route that looks like this:
>
> <osgi:camelContext xmlns=3D"http://camel.apache.org/schema/spring">
> =A0 =A0<route>
> =A0 =A0 =A0<from uri=3D"file:/tmp/tsc-input"/>
> =A0 =A0 =A0<to uri=3D"cxf:bean:outEndpoint"/>
> =A0 =A0</route>
> =A0</osgi:camelContext>
>
> (As you can tell, I'm deploying this in ServiceMix, but the issue I'm=20
> having is in the Camel realm, thus my posting here...)
>
> I have defined outEndpoint earlier in the camel-context.xml file using cx=
fEndpoint.
>
> This route is creating exceptions over several different techniques.
>
> What I really would like is not to generate code using cxf's wsdl2java (f=
ollowing this example (http://camel.apache.org/tutorial-osgi-camel-part2.ht=
ml) though, I did). =A0I would like to use <to uri=3D"cxf:bean:outEndpoint?=
dataFormat=3DPAYLOAD"/> which, as I understand it, should not require code =
generation. =A0However, when I try to do it this way, I get a NullPointerEx=
ception in org.apache.camel.component.cxf.CxfEndpoint, at line 577, in the =
setParameters() method.
>
> I don't see anything in the documentation of the Camel CXF component that=
 states or implies that this isn't supported on the client side.
>
> So my question is... =A0Is it possible to use the cxf component in the=20
> <to> part of a Camel route, WSDL-first, and not generate code, but=20
> rather have it (under the covers) use the JAX-WS Dispatch approach? =A0
> Is there an example anywhere that does this (I've looked at all the=20
> examples on the Camel website, and several blog postings, and couldn't=20
> find anything that matched my scenario...)
>
> If it would be better to post this on the CXF or even ServiceMix lists, p=
lease advise.
>
> Thanks.
> --Scott
>


--
Claus Ibsen
-----------------
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/