Composum doesn't work for me - but I assume the next servlets resolver
release will fix that?
Internal Server Error (500)
The requested URL /bin/browser.html resulted in an error in
/libs/composum/nodes/browser/browser.jsp.
Exception:
java.lang.NullPointerException
at
org.apache.sling.servlets.resolver.internal.PathBasedServletAcceptor.accept(PathBasedServletAcceptor.java:46)
at
org.apache.sling.servlets.resolver.internal.SlingServletResolver.resolveServletInternal(SlingServletResolver.java:452)
at
org.apache.sling.servlets.resolver.internal.SlingServletResolver.resolveServlet(SlingServletResolver.java:164)
Carsten
On 04.03.2020 14:37, Radu Cotescu wrote:
Hi Konrad,
On 4 Mar 2020, at 14:23, Konrad Windszus <[email protected]> wrote:
Notice though, that just executing the sling starter via "mvn clean verify"
works fine, but if you manually try to access the WebUI (if you keep the starter running)
I constantly see the described issue.
Also it is always logged in the error.log (but not in the output of the Maven
build).
Maybe some race condition….
I was playing around with the HTL REPL at /htl/repl.html (it requires authentication)
and things were working ok. Composum doesn’t work on the latest starter due to
https://issues.apache.org/jira/browse/SLING-9164
<https://issues.apache.org/jira/browse/SLING-9164>.
What’s your testing scenario?
Regards,
Radu
--
--
Carsten Ziegeler
Adobe Research Switzerland
[email protected]
