Well, in case anyone else runs into a similar issue, this link had a
solution that worked:
http://groups.google.com/group/google-guice/browse_thread/thread/493af2e2d5f0ea16/4971253e99f4a202
For some reason I misread/misunderstood and assumed the issue had been
modified in WebSphere 7; this was not the case.
I was unable to get the custom WAS properties to have any affect, and
declaring a SimpleFileServlet didn't make any difference for us
either.
Looks like it was an issue between Guice and WebSphere; Guice was
expecting a value for the servlet path and WebSphere was returning an
empty string, so the filter didn't match and the request wasn't passed
to our dispatch servlet.
Adding a filter that set the servlet path and having that filter
called before the guice filter fixed the issue.
Hope that helps.
On Oct 27, 1:42 am, David Peterson <
da...@randombits.org> wrote:
> I haven't tested it I'm afraid, but I've generally avoided WebSphere - it
> seems to cause the most problems of all the containers I've come across. Not
> sure why exactly...
>
> David
>