[SLING-1163] Dynamic Class Loader components unsatisfied after a bundle is updated

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Launchpad Bundles 5
• Fix Version/s: Launchpad Builder 6
• Component/s: Launchpad
• Assignee: Felix Meschberger
• Reporter: Vidar Skauge Ramdal
• Created: 26/Oct/09 09:56
• Updated: 20/Sep/17 12:17
• Resolved: 06/Nov/09 18:59

Description

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".

Issue Links

• is related to: SLING-1186 FsResourceProvider no longer configurable