That is all good to know. Thanks Martin and Mike for a good explanation of what the filter represents. I have changed the web.xml to look identical to the example given on the myfaces website yet I still get the same JScript issue. Here is the snippet of my
web.xml that has changed (everything else posted previously remains the same. One question I would have is this. My page has a jsp extension as opposed to a jsf extension. Will the extensions filter still correctly operate under this condition? Thanks!
<
filter-mapping> <filter-name>MyFacesExtensionsFilter </filter-name> <url-pattern>*.jsf</ url-pattern> </filter-mapping> <filter-mapping> <filter-name>MyFacesExtensionsFilter </filter-name> <url-pattern>/faces/*</ url-pattern> </filter-mapping>On 12/21/05, Mike Kienenberger <[EMAIL PROTECTED]> wrote:
It's my understanding that the tomahawk component *creates* urls
containing the /faces/* path in your response. The extensions filter
then resolves those requests.
This does raise another question. Is there any reason why the
extension filter has a *.jsf mapping? It would seem less confusing
if the only mapping provided for the extension filter in the
documentation and examples was the "/faces/*" path if the other
mapping is unnecessary.
On 12/21/05, CD <[EMAIL PROTECTED]> wrote:
> That did not work as was expected since the /faces/* path is used nowhere in
> my application. Thank you for the suggestion though :)
>
>
>
>
> On 12/21/05, Mario Ivankovits <[EMAIL PROTECTED]> wrote:
> > Hi !
> > > However, I am running into _javascript_ errors resulting from
> > > loadPopupScript not being defined as well as DateFormatSymbols not
> > > being defined.
> > You have to map the extension filter to /faces/* too.
> >
> > ---
> > Mario
> >
> >
>
>
