You are viewing a plain text version of this content. The canonical link for it is here.
Posted to adffaces-issues@incubator.apache.org by "Matthias Weßendorf (JIRA)" <ad...@incubator.apache.org> on 2007/03/16 08:17:10 UTC

[jira] Updated: (ADFFACES-255) Have Context Available in the resource loader

     [ https://issues.apache.org/jira/browse/ADFFACES-255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matthias Weßendorf updated ADFFACES-255:
----------------------------------------

        Fix Version/s: 1.0.0-incubating-core
    Affects Version/s: 1.0.0-incubating-core

> Have Context Available in the resource loader
> ---------------------------------------------
>
>                 Key: ADFFACES-255
>                 URL: https://issues.apache.org/jira/browse/ADFFACES-255
>             Project: MyFaces ADF-Faces
>          Issue Type: New Feature
>    Affects Versions: 1.0.0-incubating-core
>         Environment: all
>            Reporter: Michael Elges
>             Fix For: 1.0.0-incubating-core
>
>
> 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). 
> The simple approach would be getting access to init params (though, servlet init, or context init?)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.