Costin:
I'm not sure where to make these changes. In particular, I don't
know to which message(s) the jvmRoute information is attached
or how to extract it from the payload.
Tom
----- Original Message -----
From: "Craig R. McClanahan" <[EMAIL PROTECTED]>
To: "Tomcat Developers List" <[EMAIL PROTECTED]>
Sent: Tuesday, January 15, 2002 8:45 PM
Subject: Re: [PATCH] JvmRoute changes
|
|
| On Tue, 15 Jan 2002 [EMAIL PROTECTED] wrote:
|
| > Date: Tue, 15 Jan 2002 19:51:02 -0800 (PST)
| > From: [EMAIL PROTECTED]
| > Reply-To: Tomcat Developers List <[EMAIL PROTECTED]>
| > To: Tomcat Developers List <[EMAIL PROTECTED]>
| > Subject: Re: [PATCH] JvmRoute changes
| >
| > Hi Tom,
| >
| > Sorry for the late response, I didn't have email last few days.
| >
| > The patch is perfect, I hope Remy will be able to incorporate it
| > in 4.0.2.
| >
| > One extra thing we could try is to look in the jk connector
| > and see if it's possible to set the engine - we have
| > access to the Request and Container, so we should be able
| > to find the engine and set the vmroute automatically if
| > it's not set already.
| >
|
| If you can get to the relevant Context (which is probably the value of
| Container in your description above, but I haven't examined the code to
| make sure), you can find the associated Engine quite easily:
|
| Container container = ... what you already have ...
| Container engine = container;
| while (!(engine instanceof Engine)) {
| engine = engine.getParent();
| }
| ... engine now contains the relevant Engine instance ...
|
| > Costin
| >
|
| Craig
|
|
| --
| To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
| For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>
|
|
|
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
