on 2/7/00 12:04 AM, Kevin A. Burton <[EMAIL PROTECTED]> wrote:
>
> The fix seems to work sometimes. The problem is that when it does work
> you get no output from the Turbine servlet. What servlet engine? I
> think it might have been a problem with Tomcat > 3.0. I was running
> Tomcat right from CVS and I noticed the problem, then I downgraded to
> the "stable" 3.1M1 and still had the problem, then I tried 3.0 and it
> appears to have disapeared ( but I am not sure ).
>
> Was this under JServ? You mentioned that you haven't used
> Jakarta/Tomcat so I assume is the case.
>
> I initially thought it might have been a deprecated API that we were
> compiling against that might have returned null. Then I went over the
> recent CVS commit logs and noticed nothing that could have brought this
> up.
>
> If it also happens under JServ then it is probably a Turbine bug. At
> this point we will just have to step through the code and find where it
> infinitely redirects...
>
> ug.
Ok, I *think* that I found the solution to this. I believe it was related to
having old classes laying around. I re-built everything from scratch and the
problem went away. Now I'm running into a problem with BasePeer, but John is
working on that since that code is largely undocumented (which I also hope
he will fix). ;-(
-jon
--
Come to the first official Apache Software Foundation
Conference! <http://ApacheCon.Com/>
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
