The latest Version 9.1 PRO has the new feature
ScreenLoaderServlet.addDynamicScreenGenerator() to register a custom screen loader implementing interface DynamicScreenGenerator.
This is great!
The interface for the screen loader DynamicScreenGenerator.getScreen(String viewName) currently only supports the screen name as input parameter, so the custom loader class knows what screen to load by screen name.
In some cases, this can be too limited.
Think of tenant or user specific screens.
Wish:
Add the HttpServletRequest as input parameter to the method.
DynamicScreenGenerator.getScreen(String viewName, HttpServletRequest request)
This way, further parameters used in the screen look up can be feed in via the request or taken from the users session.
Technically it shouldn't be too complicated, as the ScreenLoaderServlet is a servlet and can pass the HttpServletRequest further to the getScreen method.
Thank you,
Best regards,
Daniel
ScreenLoaderServlet.addDynamicScreenGenerator() to register a custom screen loader implementing interface DynamicScreenGenerator.
This is great!
The interface for the screen loader DynamicScreenGenerator.getScreen(String viewName) currently only supports the screen name as input parameter, so the custom loader class knows what screen to load by screen name.
In some cases, this can be too limited.
Think of tenant or user specific screens.
Wish:
Add the HttpServletRequest as input parameter to the method.
DynamicScreenGenerator.getScreen(String viewName, HttpServletRequest request)
This way, further parameters used in the screen look up can be feed in via the request or taken from the users session.
Technically it shouldn't be too complicated, as the ScreenLoaderServlet is a servlet and can pass the HttpServletRequest further to the getScreen method.
Thank you,
Best regards,
Daniel