myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "dennis hoersch (JIRA)" <>
Subject [jira] [Commented] (MYFACES-3671) jsf-uncompressed.js contains 'import' of not existing file '_FinalizeableObj.js'
Date Tue, 15 Jan 2013 10:28:12 GMT


dennis hoersch commented on MYFACES-3671:

Thank you.

Maybe it is a good idea to prevent cases like this (see also
if there is a check in the loadScript method? Like the following

this.loadScript = function(src, type, defer, charSet, async) {
    if (!src ) {
        throw Error("Script to load must not be an empty string!");
    // the chrome engine has a nasty javascript bug which prevents
    // a correct order of scripts being loaded
    // if you use script source on the head, we have to revert
    // to xhr+ globalEval for those
    var b = _T.browser;
    if (!b.isFF && !b.isWebkit && !b.isOpera >= 10) {
        _T.loadScriptEval(src, type, defer, charSet);
    } else {
        // only firefox keeps the order, sorry ie...
        _T.loadScriptByBrowser(src, type, defer, charSet, async);
> jsf-uncompressed.js contains 'import' of not existing file '_FinalizeableObj.js'
> --------------------------------------------------------------------------------
>                 Key: MYFACES-3671
>                 URL:
>             Project: MyFaces Core
>          Issue Type: Bug
>    Affects Versions: 2.1.10
>         Environment: Firefox
>            Reporter: dennis hoersch
>            Assignee: Werner Punz
>             Fix For: 2.0.17-SNAPSHOT, 2.2.0, 2.1.11-SNAPSHOT
> The 'jsf-uncompressed.js' tries to load the script '_FinalizeableObj.js' that seams not
to exist?
>   _ls("#{resource['org.apache.myfaces.core.impl.xhrCore:_FinalizeableObj.js']}", null,
null, "UTF-8", false);
> This results in an empty string for the load:
>   _ls("", null, null, "UTF-8", false); 
> which causes a second request to the original page in my browser.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message