myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Werner Punz (JIRA)" <...@myfaces.apache.org>
Subject [jira] Resolved: (EXTSCRIPT-135) Changes in the myfaces initialisation between 2.0.0 and 2.0.1 broke the startup of ext-scripting
Date Mon, 28 Jun 2010 09:59:57 GMT

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

Werner Punz resolved EXTSCRIPT-135.
-----------------------------------

    Fix Version/s: 1.0-Final
       Resolution: Fixed

> Changes in the myfaces initialisation between 2.0.0 and 2.0.1 broke the startup of ext-scripting
> ------------------------------------------------------------------------------------------------
>
>                 Key: EXTSCRIPT-135
>                 URL: https://issues.apache.org/jira/browse/EXTSCRIPT-135
>             Project: MyFaces Extensions Scripting
>          Issue Type: Bug
>          Components: MyFaces 2.0 Extension
>    Affects Versions: 1.0-Final
>            Reporter: Werner Punz
>            Assignee: Werner Punz
>             Fix For: 1.0-Final
>
>
> There have been some variations in the startup behavior of myfaces 2.0.0 - > 2.0.1
which are perfectly valid but which broke our startup in ext-scripting.
> Ext-Scripting relies on an initial compile and scan before myfaces initialises its own
artifacts but somehow the code already relies on an existing application object to work in
this startup phase which is wrong.
> This has to be changed on the ext-scripting side.
> The assumption of the initial compile is correct but not the application access.

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


Mime
View raw message