Hi Tom,
You're completely right - and this is probably a misinterpretation of
the spec from our part at some point.
As far as I can see, there's no critical usage of this method in the
Magnolia code base, so it should cause any issue fixing it. If you're
willing to provide a patch, that'd be awesome. You might want to have
a look at ServletDispatchingFilterTest and fix/add tests in there
(particularly, there's a nasty one which is commented out because we
couldn't get it to pass - or let's be honest: we couldn't be bothered
fixing the code be compliant with this part of the spec)
If you just patched the test case, i'd be willing to help and get the
green bar for fixing the real code ;)
Cheers,
-greg
On Apr 9, 2008, at 00:20 , Tom Jensen wrote:
I'm trying to hookup DWR 1.1.4 within Magnolia 3.5.4. I have it
mapped in the /config/server/filters/servlet section configured to use
the mapping /dwr/*. The problem is that DWR depends on the
request.getServletPath() to return back the value as specified in the
servlet spec (at least 2.2-2.4, I didn't check other versions of the
spec). In the above mapping it should return back /dwr, but in
Magnolia it returns back /dwr/interface/MappingName.js or whatever
the url is requested under /dwr/.
The question I have is: is this a bug or does Magnolia not intend to
fully support the servlet spec in that regard? I really like the
configuration capabilities of Magnolia for servlets but if it doesn't
fully support the spec I don't feel comfortable using it to deploy
servlets.
Thanks,
Tom
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------
