4.0.38 *seems* to be working. It's always a bit clunky to update to a new
version of Resin, getting all the config back to what I had gotten to with the
previous version (in this case, I just copied all my config from .36).
Now my webapp jumps to an ugly login page, which I think is the Spring S
THANKS!!
If this is the kind of news that comes out of you being stupid, then please be
stupid more often ;-)
On Mar 20, 2014, at 12:47 , Paul Cowan wrote:
> Oh I feel stupid now - my Resin 4 codebase was out of date (been working on
> Resin 5).
>
> There already was a bug and we just added
Oh I feel stupid now - my Resin 4 codebase was out of date (been working on
Resin 5).
There already was a bug and we just added session tracking mode support in
version 4.0.38.
So you’ll just need to upgrade your Resin version to get it.
-Paul
On Mar 20, 2014, at 3:11 PM, Rick Mann wrote:
Please enter the bug, at least. I'll look into seeing if there's a way around
the problem.
On Mar 20, 2014, at 11:29 , Paul Cowan wrote:
>
> On Mar 20, 2014, at 6:00 AM, Rick Mann wrote:
>
>> I'm trying to add Spring Security to my pure-JavaConfig web app, and I'm
>> getting this error on m
On Mar 20, 2014, at 6:00 AM, Rick Mann wrote:
> I'm trying to add Spring Security to my pure-JavaConfig web app, and I'm
> getting this error on my first request. Any idea what it means? Is this a
> Resin problem (v 4.0.36)?
That’s definitely being thrown by Resin. I looked at our code and w
