Spring 4 and Servlet 3.0

[Cantor, Scott]

On 12/19/13, 4:46 AM, "Rod Widdowson" <rdw at steadingsoftware.com> wrote:
>
>....Whilst at the cost of adding extra impedance to the upgrade path.

I suppose, but all you have to do is upgrade your container first, which
seems like what you'd advise people to do anyway.

>On the other hand we are shipping a container (aren't we?)

Undecided I think, and the later it gets, the less I'm enthused about that
work being part of V3.

>We discussed last week what is happening to the REMOTE_USER interface and,
>as I recall & understood, the upshot was that such Spring dictates that
>handling needs to remain inside the container.

Not REMOTE_USER, the ExternalAuth handler, and it's not really about the
container, it's a WebFlow thing.

>Does the combination of that
>plus the upping of the container version add any new restrictions and if
>so do we care?
>
>The scenario I am imagination is interaction with another SSO system which
>*cannot* run in Servlet3 but can in 2.5.

I suppose that's possible, but other than CAS, there isn't much that's in
Java that would matter, and I don't think there's any issue with CAS.

Nothing that runs on 2.5 should have any real trouble running on 3.0, it's
backward compatible for anything routine. Even Spring itself isn't the
problem here, it's just their mock test class.

-- Scott