Mailing-List: contact camel-user-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: camel-user@activemq.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: HttpExchange changes to DefaultExchange - expected?
Date: Tue, 5 Aug 2008 06:02:07 +0200
Message-ID: <4C1FB9C00D24A140906239533638C4D204DBA9D4@EXVS04.exserver.dk>
In-Reply-To: <4C1FB9C00D24A140906239533638C4D204DBA9D3@EXVS04.exserver.dk>
Thread-Topic: HttpExchange changes to DefaultExchange - expected?
Thread-Index: Acj2gLf6QMtaax2aROyhL6nzZU8VSgALno8gAAAqANA=
From: "Claus Ibsen" <ci@silverbullet.dk>
To: <camel-user@activemq.apache.org>

Hi

Just mind thought that it is not all transport types (e.g. JMS) that can =
safely propagate headers over the wire. So if you send the exchange to a =
JMS queue and then retrieve it later from the JMS queue then the =
HttpSession object is not there anymore. The JMS spec doesn't allow =
sending objects as JMS headers.


Med venlig hilsen
=20
Claus Ibsen
......................................
Silverbullet
Skovsg=E5rdsv=E6nget 21
8362 H=F8rning
Tlf. +45 2962 7576
Web: www.silverbullet.dk

-----Original Message-----
From: Claus Ibsen [mailto:ci@silverbullet.dk]=20
Sent: 5. august 2008 05:58
To: camel-user@activemq.apache.org
Subject: RE: HttpExchange changes to DefaultExchange - expected?

Hi

Yes you can also store the HttpSession object itself as a property or =
header on the exchange itself. When you need it later you can you get it =
as a HttpSession object

// store it
exchange.getIn().setHeder("session", the http session object);


// later get it
HttpSession myHttpSession =3D exchange.getIn().getHeader("session", =
HttpSession.class);


Med venlig hilsen
=20
Claus Ibsen
......................................
Silverbullet
Skovsg=E5rdsv=E6nget 21
8362 H=F8rning
Tlf. +45 2962 7576
Web: www.silverbullet.dk
-----Original Message-----
From: Bela Vizy [mailto:magyardude@yahoo.com]=20
Sent: 5. august 2008 00:25
To: camel-user@activemq.apache.org
Subject: RE: HttpExchange changes to DefaultExchange - expected?


Andr=E9,


alu wrote:
>=20
> However, I want to call exchange.getResponse().encodeURL(...) to =
encode a
> URL that includes the session ID. So it's not just the session ID that
> needs propagating, my endpoint really want access to the session =
context
> through an HttpExchange instance... Is this possible in those =
subsequent
> Processors, or should I try a complete different design direction?
>=20

It sounds you want to respond to a form submission from a browser. Camel =
is
no a web server. It's a messaging system. I don't think there is a =
reason to
maintain sessions either with url rewriting or cookies for that matter, =
but
if you really need it, you have full control over the response headers,
basically whatever you set as an output header will go into the response
(with exceptions you can define).=20

Bela
--=20
View this message in context: =
http://www.nabble.com/HttpExchange-changes-to-DefaultExchange---expected-=
-tp18809523s22882p18821081.html
Sent from the Camel - Users mailing list archive at Nabble.com.