Yeah, let's put those params in a map that the Resource loader takes.
-Matthias On 9/14/06, Adam Winer <[EMAIL PROTECTED]> wrote:
+1 for me too - at least something simple like getting access to init params (though, servlet init, or context init?) What would be reaaaally nice is access to a javax.faces.context.ExternalContext object, but it's not a JSF request, so a javax.faces.context.FacesContext is overkill. :) -- Adam On 9/12/06, Matthias Wessendorf <[EMAIL PROTECTED]> wrote: > > Hi Mike, > > I am not sure, why the ResourceLoader has no access to the external > context (portlet / servlet). To me it looks not to bad to have access > to that inside the ResourceLoader. Why not passing some param w/ > ResourceServlet to the loaders. > > Let's see, what others think. > Opening an issue is fine to keep track of this. > Jira ensure it doesn't get lost :) > > -MAtthias > > On 9/12/06, Michael Elges <[EMAIL PROTECTED]> wrote: > > Hello All, > > > > Currently the Trinidad resource loader does not contain the context from > > the servlet/portal. This prevents the JavaScript resource loader from > > providing dynamic capabilities like turning on and off JavaScript > > obfuscation (this is just one example). Allowing the context to be made > > available in the resource loader makes the loaders configurable which > > has other benefits (I have an immediate need for doing obfuscation from > > the resource loader). > > > > I want to open a JIRA on this issue but before I do that I would like to > > get some input from the readers of this mailing list. > > > > Thoughts? > > > > Mike > > > > > > > > > -- > Matthias Wessendorf > > further stuff: > blog: http://jroller.com/page/mwessendorf > mail: mwessendorf-at-gmail-dot-com >
-- Matthias Wessendorf further stuff: blog: http://jroller.com/page/mwessendorf mail: mwessendorf-at-gmail-dot-com
