phtan wrote:
>
> I see, that kind of explains. However, the javascript is suppose to be
> fetched
> by MyFacesExtensionsFilter. From your stacktrace, I wonder why the
> myfaces
> filter is not invoked to fetch the resource.... it shouldn't be handled
> by
> websphere here.
>
> ph
>
I have done some looking into this problem as well. It appears the
Websphere DefaultExtensionProcessor is failing the request even though the
Myfaces filter has handled the request and and short circuited the filter
chain. has anyone entered a ticket with Websphere to look at this? I've
created a tomahawk issue to help track this problem:
TOMAHAWK-663
Mike
--
View this message in context:
http://www.nabble.com/problem-with-myfaces1.1.3--websphere6.1-tf2182105.html#a6252789
Sent from the MyFaces - Users forum at Nabble.com.
