This is an automated email from the ASF dual-hosted git repository. nmalin pushed a commit to branch release24.09 in repository https://gitbox.apache.org/repos/asf/ofbiz-framework.git
The following commit(s) were added to refs/heads/release24.09 by this push: new 637d01dd9d Fixed: Improve ViewHandler interface : missing screens in context (OFBIZ-13179) 637d01dd9d is described below commit 637d01dd9d3c847eb1ddc186a6079dc546bea98c Author: Nicolas Malin <nicolas.ma...@nereide.fr> AuthorDate: Thu Dec 19 10:15:32 2024 +0100 Fixed: Improve ViewHandler interface : missing screens in context (OFBIZ-13179) After refactoring view handler to secure the context, the screenRenderer is missing for Screen Fop. This is problematic if you want include some other screen on your fop template like : ${screens.render("component://mycompo/widget/MysScreens#IncludedScreen")} Thanks Leila Mekika that detect this regression --- .../java/org/apache/ofbiz/widget/renderer/fo/ScreenFopViewHandler.java | 1 + 1 file changed, 1 insertion(+) diff --git a/framework/widget/src/main/java/org/apache/ofbiz/widget/renderer/fo/ScreenFopViewHandler.java b/framework/widget/src/main/java/org/apache/ofbiz/widget/renderer/fo/ScreenFopViewHandler.java index e2aac75248..85bd934bbd 100644 --- a/framework/widget/src/main/java/org/apache/ofbiz/widget/renderer/fo/ScreenFopViewHandler.java +++ b/framework/widget/src/main/java/org/apache/ofbiz/widget/renderer/fo/ScreenFopViewHandler.java @@ -108,6 +108,7 @@ public class ScreenFopViewHandler extends AbstractViewHandler { // this is the object used to render forms from their definitions screens.getContext().put("formStringRenderer", formStringRenderer); screens.getContext().put("simpleEncoder", UtilCodec.getEncoder(modelTheme.getEncoder(getName()))); + screens.getContext().put("screens", screens); screens.render(page); } catch (IOException | GeneralException | SAXException | ParserConfigurationException | TemplateException e) { renderError("Problems with the response writer/output stream", e, "[Not Yet Rendered]", request, response, context);