Hi,
Sorry if this has been discussed but I haven't found a huge amount of
discussion on it, just a few comments describing that it was an
important and necessary change. Some time around Shale 1.0.3 changes
were introduced which meant you needed to deploy to a Servlet API 2.4
compliant container. This has left us in the difficult position of
either ripping out Shale or sticking with an increasingly dated version,
as unfortunately we're stuck with a 2.3 servlet container.
Since 1.0.2 there's already been a few patches we've needed, and I
suspect that'll increase as its given more of a workout (certainly the
validation area has needed a few backported patches, the JSF
filter/controller aspect is working fine). Where I'm heading with this
is has anyone tried any workarounds to get the latest release to deploy
under a Servlet 2.3 environment? Or are the changes fundamental in
nature... I was hoping someone had just packaged up a few of the
required javax.servlet classes into a minijar and voila. I'm guessing
not given the classes in question and the need for container support,
but thought I'd ask the question. Or I was going to ask whether its
feasible to implement the functionality provided by the 2.4 spec in a
different fashion, if the changes are fairly localized, we would happily
take the time to do that too if theres an indication its possible.
Cheers
Joe
- Shale 1.0.x change to servlet 2.4 spec Joe Shevland
-
