Dynamic Class Loader components unsatisfied after a bundle is updated
---------------------------------------------------------------------
Key: SLING-1163
URL: https://issues.apache.org/jira/browse/SLING-1163
Project: Sling
Issue Type: Bug
Components: Commons
Affects Versions: Commons ClassLoader 1.0.0
Reporter: Vidar S. Ramdal
Fix For: Commons ClassLoader 1.0.2
The components of the org.apache.sling.commons.classloader bundle gets
unsatisifed when another bundle is updated. This only applies to some bundles,
and it is currently unclear what exact characteristics are necessary for the
symptoms to appear. However, the error seems to be allways reproducible with
certain bundles.
More background at http://markmail.org/thread/mh5frzq57b4bmb7q
To reproduce:
1. Create a script at /apps/sling/servlet/default/html.esp
2. Create a node at /node
3. Browse to /node.html
4. Observe how the script is used for rendering
5. Update an "offending" bundle
6. Browse to /node.html again
Expected result:
- Your html.esp script is used for rendering
Actual result:
- The HtmlRendererServlet is used for rendering, just as if your script did not
exist. The Felix Web Console lists
org.apache.sling.scripting.javascript.internal.RhinoJavaScriptEngineFactory and
org.apache.sling.scripting.jsp.JspScriptEngineFactory components as
"unsatisfied".
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
