Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: pass (athena.apache.org: domain of willem.jiang@gmail.com
 designates 209.85.210.49 as permitted sender)
Date: Tue, 29 Jan 2013 14:43:16 +0800
From: Willem jiang <willem.jiang@gmail.com>
To: users@camel.apache.org
Message-ID: <FC807A3857564C6A87415ACC89BB1D9F@gmail.com>
In-Reply-To: <1359401820207-5726438.post@n5.nabble.com>
References: <1359378196815-5726415.post@n5.nabble.com>
 <1359401820207-5726438.post@n5.nabble.com>
Subject: Re: insert custom Soap Header problem
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Yeah, you can do it by setting up a customer interceptor on the CX=46 end=
point.


-- =20
Willem Jiang

Red Hat, Inc.
=46useSource is now part of Red Hat
Web: http://www.fusesource.com =7C http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/) =
(English)
          http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese)
Twitter: willemjiang =20
Weibo: =E5=A7=9C=E5=AE=81willem


On Tuesday, January 29, 2013 at 3:37 AM, peter.berkman wrote:

> not sure if this is the same, but I had to do something similar for SAM=
L. =20
> =20
> I did it through an Interecepter:
> =20
> =7Bcode=7D
> public class SAMLResponseInterceptor extends AbstractSoapInterceptor =7B=

> =20
> private static final transient Logger LOG =3D
> Logger=46actory.getLogger(SAMLResponseInterceptor.class);
> =20
> public SAMLResponseInterceptor() =7B
> super(Phase.PRE=5FPROTOCOL);
> =7D
> =20
> =40Override
> public void handleMessage(SoapMessage message) throws =46ault =7B
> =20
> LOG.debug(=22Out interceptor called.....=22);
> =20
> SAMLHelper sam =3D new SAMLHelper();
> =20
> Element saml =3D sam.getResponseSAML();
> =20
> if (saml =21=3D null) =7B
> =20
> QName q =3D new
> QName(=22http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecu=
rity-secext-1.0.xsd=22,=22Security=22,
> =22wsse=22);
> Header h =3D message.getHeader(q);
> =20
> if (h =3D=3D null) =7B
> =20
> QName q1 =3D new
> QName(=22http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecu=
rity-secext-1.0.xsd=22,=22Security=22,
> =22o=22);
> Header h1 =3D message.getHeader(q1);
> =20
> if (h1 =3D=3D null) =7B
> =20
> h =3D new Header(q, saml);
> message.getHeaders().add(h);
> LOG.debug(=22New soap header added=22);
> =7D
> else =7B
> h1.setObject(saml);
> LOG.debug(=22soap header updated=22);
> =7D
> =7D
> else =7B
> h.setObject(saml);
> LOG.debug(=22soap header updated=22);
> =7D
> =7D
> =7D
> =7D
> =20
> =7Bcode=7D
> =20
> =20
> =20
> --
> View this message in context: http://camel.465427.n5.nabble.com/insert-=
custom-Soap-Header-problem-tp5726415p5726438.html
> Sent from the Camel - Users mailing list archive at Nabble.com (http://=
Nabble.com).