Should we open a Jira issue? -----Original Message----- From: Adam Winer [mailto:[EMAIL PROTECTED] Sent: Friday, June 29, 2007 12:05 PM To: MyFaces Discussion Subject: Re: [Trinidad] How To Add Custom Component Resources Other Than Script
On 6/29/07, William Hoover <[EMAIL PROTECTED]> wrote: > > > Thanks for the info Adam! I do have an additional question concerning this. > I haven't looked in to this for a while but I remember at one point the > "org.apache.myfaces.trinidadinternal.renderkit.core.pages.GenericEntry" > -> "FredJSP.service" used for dialogs having an issue with servlet-mapping: > > <servlet-mapping> > <servlet-name>faces</servlet-name> > <url-pattern>*.jsf</url-pattern> > </servlet-mapping> > > ...and to get the dialog working I had to use: > > <servlet-mapping> > <servlet-name>faces</servlet-name> > <url-pattern>/faces/*</url-pattern> > </servlet-mapping> > > ...is this still the case? The reason why I ask is that I'm using the > suggested InternalView API with: > > /META-INF/org.apache.myfaces.trinidad.InternalView.properties > contents: > /__MYRESOURCEv__=some.path.to.my.internalview.class.MyResourceClass > > ...I have similar code for the "FedJSP.service" call in > "org.apache.myfaces.trinidadinternal.renderkit.core.pages.GenericEntry", > but when calling the resource url http://foo/__MYRESOURCEv__.jsf I get a 404 > (the same as what I get for dialogs w/*.jsf). Am I missing something? The GenericEntry code is going through exactly the same codepaths, so if *.jsf doesn't work there, it won't work for __MYRESOURCE__ either... I thought this had been fixed, but evidently not. I don't think we have an open JIRA issue on this either. -- Adam > > -----Original Message----- > From: Adam Winer [mailto:[EMAIL PROTECTED] > Sent: Thursday, June 28, 2007 6:37 PM > To: MyFaces Discussion > Subject: Re: [Trinidad] How To Add Custom Component Resources Other Than > Script > > Check out the InternalView API of Trinidad. > > > -- Adam > > > > On 6/28/07, William Hoover < [EMAIL PROTECTED]> wrote: > > Is there a way to add resources other than scripts in custom components? > > > > What I would like to be able to do is add a static HTML page bundled with > the component that will be available through a resource URL similar to how > "outputScriptlet" works (i.e. http://foo/adf/jsLibs/someScriptResource.js). > That way the page will be available without having to be present in the web > directory of the application. > > > > > >
