Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
1.0-Final
-
None
Description
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.