Mailing-List: contact users-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@cxf.apache.org
Received-SPF: pass (athena.apache.org: local policy)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.com;
  h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding;
  b=e/3kvNuOLkHjDPtKmkEyk3sVFHNOD/MnDnls+2r/hJl2qmOiEw9wkUApe+diY9cW/1X7v5EuL8uxnKTuRvtPaQjfNoKctJihAKJs8Hy3jKEE2VuU61ndQdmHDuAgEDtNj7fWAnYtm6vGYyhFRQ1ENgN0tzq6riRse1QKuCDwosY=;
Message-ID: <721418.62069.qm@web57409.mail.re1.yahoo.com>
Date: Fri, 20 Nov 2009 08:58:20 -0800 (PST)
From: Coder One <coder_lol@yahoo.com>
Subject: Re: CXF SOAP over JMS and Camel/Generic Interceptor
To: users@cxf.apache.org
In-Reply-To: <4B065F88.4070408@die-schneider.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

This is cool.  I have to try it out. =20

Thanks,


--- On Fri, 11/20/09, Christian Schneider <chris@die-schneider.net> wrote:

> From: Christian Schneider <chris@die-schneider.net>
> Subject: Re: CXF SOAP over JMS and Camel/Generic Interceptor
> To: users@cxf.apache.org
> Date: Friday, November 20, 2009, 1:21 AM
> You can specify a binding file for
> code generation like in the wsdl first example. There you
> can enable the async mapping.
> This will generate client code where you have a listener
> for the response.
>=20
> Will this help?
>=20
> <jaxws:bindings wsdlLocation=3D"CustomerService.wsdl"
> =A0 =A0 =A0 =A0=A0=A0xmlns:jaxws=3D"http://java.sun.com/xml/ns/jaxws"
> =A0 =A0 =A0 =A0=A0=A0xmlns:xs=3D"http://www.w3.org/2001/XMLSchema"
> =A0 =A0 =A0 =A0=A0=A0xmlns:jxb=3D"http://java.sun.com/xml/ns/jaxb"
> =A0 =A0 =A0 =A0=A0=A0xmlns:wsdl=3D"http://schemas.xmlsoap.org/wsdl/">
>=20
> <jaxws:enableAsyncMapping>true</jaxws:enableAsyncMapping>
> </jaxws:bindings>
>=20
> Greetings
>=20
> Christian
>=20
> Coder One schrieb:
> > Hi,
> >=20
> > A webservice call is usually synchronous, so in the
> case of integrating with Camel and using JMS, I actually
> need an async model.
> >=20
> > Would it be possible to configure CXF to route the
> SOAP to Camel, return something to the caller thorough the
> client stub, and let camel deliver the real SOAP response to
> the app using some listener mechanism at a later time?
> >=20
> > Thanks...
> >=20
> > --- On Thu, 11/19/09, Christian Schneider <chris@die-schneider.net>
> wrote:
> >=20
> >=A0=A0=A0
> >> From: Christian Schneider <chris@die-schneider.net>
> >> Subject: Re: CXF SOAP over JMS and Camel/Generic
> Interceptor
> >> To: users@cxf.apache.org
> >> Date: Thursday, November 19, 2009, 4:01 PM
> >> There is an example for SOAP / JMS
> >> with CXF and Camel on:
> >> http://camel.apache.org/better-jms-transport-for-cxf-webservice-using-=
apache-camel.html
> >>=20
> >> If you only want to mess with the SOAP then you
> can use a
> >> CXF interceptor and do not need o use camel. See:
> >> http://cwiki.apache.org/CXF20DOC/interceptors.html
> >>=20
> >> Greetings
> >>=20
> >> Christian
> >>=20
> >> Coder One schrieb:
> >>=A0 =A0=A0=A0
> >>> interface WebService
> >>> {
> >>>=A0 =A0 =A0 String greeting();
> >>> }
> >>>=20
> >>> class WebServiceImpl
> >>> {
> >>>=A0 =A0=A0=A0public String
> greeting()
> >>>=A0 =A0 {
> >>>=A0 =A0 =A0 =A0 return("Hello,
> >>>=A0 =A0 =A0=A0=A0
> >> world");
> >>=A0 =A0=A0=A0
> >>>=A0 =A0=A0=A0}
> >>>=20
> >>> }
> >>>=20
> >>> Using Spring, CXF simple front-end, the client
> code
> >>>=A0 =A0 =A0=A0=A0
> >> just needs a reference the interface WebService
> and CXF will
> >> simply generate the stub/binding to allow the
> client to
> >> invoke the server side implementation.
> >>=A0 =A0=A0=A0
> >>> However, I need to pipe in the Camel code in
> between
> >>>=A0 =A0 =A0=A0=A0
> >> at both end-points and intercept the call.=A0
> Is that
> >> possible at all?
> >>=A0 =A0=A0=A0
> >>> [CXF-WebService Client] [Camel] [JMS] [Camel]
> >>>=A0 =A0 =A0=A0=A0
> >> [CXF-WebService Server]
> >>=A0 =A0=A0=A0
> >>> Rather than Camel, can I intercept the calls
> and do
> >>>=A0 =A0 =A0=A0=A0
> >> the following on both the client and the server
> sides:
> >>=A0 =A0=A0=A0
> >>> 1. Let the SOAP goes through.
> >>> 2. Modify the SOAP and pass it on.
> >>>=20
> >>> Any restrictions?=A0 I would greatly
> appreciate all
> >>>=A0 =A0 =A0=A0=A0
> >> points to docs, examples, etc...
> >>=A0 =A0=A0=A0
> >>> Thanks
> >>>=20
> >>>=20
> >>>=A0 =A0 =A0 =A0=20
> >>>=A0 =A0 =A0 =A0 =A0=20
> >> --=20
> >> Christian Schneider
> >> ---
> >> http://www.liquid-reality.de
> >>=20
> >>=20
> >>=A0 =A0=A0=A0
> >=20
> >=20
> >=A0 =A0 =A0=A0=A0
> >=A0=A0=A0
>=20
> =0A=0A=0A