You're in a portal environment? Well, this might as well be your problem. There are several known issues with the extension-filter and portlets, they boil down to the fact that the two don't work together ;)
regards, Martin On 12/22/05, CD <[EMAIL PROTECTED]> wrote: > Martin, > > I am encountering both as the resources and the javascript are not showing > up in the head. I had modified my xmls (portlet, faces-config, and web) to > represent how I thought they should be configured for MyFaces but I > encountered a ClassCastException in the container that involved IBM's > WebSphere WebApp. My environment once again is WebSphere Portal v5.1. > Don't know that it would be beneficial for me to to send the content of the > config files in this thread, though I do think it would help. What would be > the best way of posting this information as I think I am just incapable of > configuring it properly :) > > > > > On 12/22/05, Martin Marinschek <[EMAIL PROTECTED] > wrote: > > To come back to Kurt's and CDs original problem - > > > > Kurt - your header is rendered correctly - can you fire up something > > like HTTPFiddler and check if the files are actually delivered to your > > browser? > > > > Next step - start your app in debugging mode, attach the > > myfaces-sources to the jar-file, and debug into ExtensionsFilter? > > > > CD - do you have the same issue as Kurt - no resources being > > delivered, or is your head not showing the additional scripts? > > > > regards, > > > > Martin > > > > On 12/22/05, Martin Marinschek < [EMAIL PROTECTED]> wrote: > > > Sounds good to me! > > > > > > this also bears documentation with it ;) > > > > > > regards, > > > > > > Martin > > > > > > On 12/21/05, Mike Kienenberger < [EMAIL PROTECTED]> wrote: > > > > On 12/21/05, Simon Kitching < [EMAIL PROTECTED]> wrote: > > > > > > <!-- extension mapping for serving page-independent resources > > > > > > (javascript, stylesheets, images, etc.) --> > > > > > > <filter-mapping> > > > > > > > <filter-name>MyFacesExtensionsFilter</filter-name> > > > > > > <url-pattern>/faces/*</ url-pattern> > > > > > > </filter-mapping> > > > > > > > > > > > > > > > > I liked your suggestion of mapping this to > > > > > /faces/myFacesExtensionResource/* > > > > > > > > > > This mapping is what I use in the app I'm currently developing, and > it > > > > > works fine. Is there a reason you changed your mind? > > > > > > > > As I mentioned on the dev list, I couldn't get it to work! > > > > > > > > As soon as I switched from /faces/* to > > > > /faces/myFacesExtensionResource/*, the buttons on my > popup > > > > t:inputCalendar components stopped drawing. > > > > > > > > Strangely enough, I tried it yet again, and now it's working. Guess > > > > it must have been user error on my part. I think maybe what happened > > > > is that I broke the other piece (my web.xml uses "FacesServlet" while > > > > MyFaces docs and examples have "Faces Servlet") and didn't notice the > > > > difference until after I stopped trying to use > > > > /faces/myFacesExtensionResource/* > > > > > > > > I'm +1 for changing it to > /faces/myFacesExtensionResource/* since > > > > you've been using that successfully. > > > > > > > > > > > > > -- > > > > > > http://www.irian.at > > > > > > Your JSF powerhouse - > > > JSF Consulting, Development and > > > Courses in English and German > > > > > > Professional Support for Apache MyFaces > > > > > > > > > -- > > > > http://www.irian.at > > > > Your JSF powerhouse - > > JSF Consulting, Development and > > Courses in English and German > > > > Professional Support for Apache MyFaces > > > > -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces
