Ok, I've finally made progress:
if I add:
req.setAttribute("javax.servlet.include.context_path", "/testsuite");
before the cross context dispatch (obviously when using the testsuite)
- everything works. This tells me that something in plutos code is
not allowing tomcat to update this attribute properly during dispatch.
I feel like we're getting closer, so I hope to have a fix checked in
within the next day or so . ..
I probably won't get to it tonight.
David
On 11/18/05, David H. DeWolf <[EMAIL PROTECTED]> wrote:
> Yes.
>
> The original issue was that action test (in the testsuite) were not
> working. Once I dove into it, I discovered the same thing that you
> mentioned - - It's not really an action parameter problem - it's a
> session problem with action requests. Now I understand why we were
> talking past each other. . .and there was some confusion on my part. .
> .
>
> I've been working on this all day and it's driving must nuts. I can't
> figure out why the cross context dispatch is behaving differently
> between a render and action request. The only thing I can think is
> that we're caching a previously retrieved HttpSession from the
> original context within one of the HttpServletRequest wrappers and
> using it later on. . .but I can't find that behavior anywhere.
>
> I guess the other possibility is that it's a tomcat bug, but I can't
> duplicate the problem with a simple test case outside of pluto - so
> I'm guessing it's really a pluto issue.
>
> If anyone else has any ideas, let me know.
>
> David
>
> On 11/18/05, LaCasse, John <[EMAIL PROTECTED]> wrote:
> > David,
> >
> > When you say Action parameters do mean that the session available from
> > processAction method isn't the same as that from render method? The
> > problem that I'm having and I believe has been mentioned by Zhong is for
> > example: if you set a session attribute in render() and then try and
> > access it in processAction() it won't be there.
> >
> > -----Original Message-----
> > From: David H. DeWolf [mailto:[EMAIL PROTECTED]
> > Sent: Thursday, November 17, 2005 7:24 PM
> > To: Pluto Developer List
> > Subject: 1.1: Release Early, Release Often
> >
> > I'm curious what others thoughts are about releasing an alpha version of
> >
> > 1.1 in the next week or so. What are the items we want to make sure we
> > get taken care of before we roll our first 1.1 distribution?
> >
> > A couple of Definates:
> > 1) Action Parameters
> > 2) Portlet Preferences via derby
> > 3) Fix assemble and deploy plugins (reports that they are broken?)
> > 4) Build distributions via m2 (obviously)
> >
> > What else?
> >
> > I don't see any other reasons to postpone an alpha release. . . do you?
> >
> >
> >
> > David
> >
> >
> >
> >
>
