Details
-
Type:
Improvement
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: EE-3.3.0.GA_P01, EE-3.3.0.GA_P02
-
Fix Version/s: EE-4.0.0.GA, EE-3.3.0.GA_P03, 4.1
-
Component/s: ACE-Components
-
Labels:None
-
Environment:All
-
Support Case References:Support Case #12949 - https://icesoft.my.salesforce.com/5007000000eco3U
Description
If you use <ace:fileEntry> with a callback handler, this handler is evaluated before the JSF lifecycle starts, which means the callback always has to be a managed bean to not be null on evaluating it.
This request is to see if it can be evaluated later in the JSF lifecycle. Code where this is happening:
FacesServlet.service(…):
try {
ResourceHandler handler = context.getApplication().getResourceHandler();
if (handler.isResourceRequest(context)) {
handler.handleResourceRequest(context); <----- this is where the callback is evaluated!
} else {
lifecycle.execute(context);
lifecycle.render(context);
}
This request is to see if it can be evaluated later in the JSF lifecycle. Code where this is happening:
FacesServlet.service(…):
try {
ResourceHandler handler = context.getApplication().getResourceHandler();
if (handler.isResourceRequest(context)) {
handler.handleResourceRequest(context); <----- this is where the callback is evaluated!
} else {
lifecycle.execute(context);
lifecycle.render(context);
}
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
This issue was already solved by the fixes for
ICE-10110(trunk only). The file callback now is invoked during the JSF lifecycle.Also back-ported
ICE-10110changes (including subsequent changes for FileEntryUpload) to the maintenance branch.