Ok, having made the a little painful experience myself: The ressources like .js, gif's or stylesheets, that many of the components (e.g. htmleditor, or calender or the menue) need to be rendered properly are packaged inside the myfaces.jar and the myfaces-extension.jar. This makes it a little bit easier to package the components together with their ressources.
But: Normally web-apps don't look into jars for gifs or javascript - therefore, you'll find that there is a filter in the web.xml <filter-name>extensionsFilter</filter-name> <filter-class>org.apache.myfaces.component.html.util.ExtensionsFilter</filte r-class> that is applied to *.jsf and /faces/* This Filter is responsible for resolving references to references inside the myfaces-extension.jar and for putting the references to these ressources into the head of your page, when there is a component that needs these references. At least this is my hypothesis after playing around with installing the myfaces-extensions in an existing jsf-application running on suns implementation - maybe one of the myfaces-guys can correct me where I'm wrong. Therefore, there is no need to reproduce this structure in your webapp, as these urls are resolved against the myfaces-extension.jar, not against the ressources-directory of your webapp. Hope this helps (and is at least half way correct...) Stefan > -----Original Message----- > From: Enrique Medina [mailto:[EMAIL PROTECTED] > Sent: Mittwoch, 16. Februar 2005 19:58 > To: myfaces-user@incubator.apache.org > Subject: JSCookMenu and location of needed files > > Hi, > > I have been testing the JSCookMenu component in MyFaces 1.0.8 > (the one from Apache Incubator) and I have found that the tag > automatically generates some head content in this way: > > <script > src="/myapp/faces/myFacesExtensionResource/navmenu.NavigationM > enuItem/jscookmenu/JSCookMenu.js" > type="text/javascript"></script> > <script > src="/myapp/faces/myFacesExtensionResource/navmenu.NavigationM > enuItem/jscookmenu/ThemeOffice/theme.js" > type="text/javascript"></script> > <link rel="stylesheet" > href="/myapp/faces/myFacesExtensionResource/navmenu.Navigation > MenuItem/jscookmenu/ThemeOffice/theme.css" > type="text/css"/> > > But what I can't understand is why this is generated this > way... I mean, if you take a look at myfaces.jar, you will > find a package where all the JSCookMenu JS files and CSS files are: > > org.apache.myfaces.custom.navmenu.resource.jscookmenu > > but it does not coincide with the generated path at all! > > So my question is whether this is a bug, or maybe I am forced > to create a package in my source folder named > "faces/myFacesExtensionResource/navmenu.NavigationMenuItem/jsc > ookmenu"? > > Looking forward to hear your comments. >
