ky940819
commented
7 months ago I haven't tested it, but this can happen because some of the injected variables come from the sling script bindings (which haven't been initialized before the request gets to your servlet).
Try adding this
/**
* Bundle context.
*/
private BundleContext bundleContext;
/**
* Activate the service.
*
* @param bundleContext The bundle context.
*/
@Activate
protected void activate(final BundleContext bundleContext) {
this.bundleContext = bundleContext;
}
@Override
protected void doGet(final SlingHttpServletRequest req, final SlingHttpServletResponse resp) throws ServletException, IOException {
SlingBindings bindings = new SlingBindings();
bindings.setSling(new ScriptHelper(bundleContext, null, req, resp));
req.setAttribute(SlingBindings.class.getName(), bindings);
// ....
}You can see an example of this being done in the SearchResultServlet
marto
Bug Report
Current Behavior Majority of WCM Core components can not be adapted from a SlingHttpServletRequest to a model in code. We can no longer use and extend WCM Core components using the proxy pattern as per the recommended way of using and extending core components. For example a Teaser or Button component can no longer be adapted. The example below shows how proxy components can't be adapted.
Expected behavior/code
modelFactory.getModelFromRequestmethod should return a valid model and not nullslingHttpServletRequest.adaptTo(Teaser.class)method should return a valid model not nullEnvironment
Possible Solution Not sure if this is an AEM issue or a Core Components issue.
Additional context / Screenshots
Expected Behaviour:
Impact
Errors: