You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Vidar S. Ramdal (JIRA)" <ji...@apache.org> on 2009/10/26 10:57:59 UTC
[jira] Created: (SLING-1163) Dynamic Class Loader components
unsatisfied after a bundle is updated
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.
[jira] Updated: (SLING-1163) Dynamic Class Loader components
unsatisfied after a bundle is updated
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger updated SLING-1163:
-------------------------------------
Component/s: (was: Commons)
Launchpad
Affects Version/s: (was: Commons ClassLoader 1.0.0)
Launchpad Bundles 5
Launchpad Base 2.0.4
Fix Version/s: (was: Commons ClassLoader 1.0.2)
Launchpad Base 2.0.6
Launchpad Bundles 6
Changing the issue to be a launchpad issue to update to the latest Felix Declarative Services release once the vote has passed.
> 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: Launchpad
> Affects Versions: Launchpad Bundles 5, Launchpad Base 2.0.4
> Reporter: Vidar S. Ramdal
> Assignee: Felix Meschberger
> Fix For: Launchpad Bundles 6, Launchpad Base 2.0.6
>
>
> 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.
[jira] Resolved: (SLING-1163) Dynamic Class Loader components
unsatisfied after a bundle is updated
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger resolved SLING-1163.
--------------------------------------
Resolution: Fixed
Upgraded the Sling bundles project to refer to the released Apache Felix SCR 1.2.0 which implemens the DS 1.1 (Compendium R4.2) spec and also fixes the mentioned issue.
> 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: Launchpad
> Affects Versions: Launchpad Bundles 5
> Reporter: Vidar S. Ramdal
> Assignee: Felix Meschberger
> Fix For: Launchpad Bundles 6
>
>
> 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.
[jira] Commented: (SLING-1163) Dynamic Class Loader components
unsatisfied after a bundle is updated
Posted by "Ray Davis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12777302#action_12777302 ]
Ray Davis commented on SLING-1163:
----------------------------------
The Felix SCR upgrade broke the FsResourceProvider extension: the deployed bundle no longer shows up with implementations of ManagedService and ManagedServiceFactory, and therefore becomes unavailable to Felix Web Console's "Factory Configurations". I'll try to supply a patch tomorrow if no one beats me to it.
> 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: Launchpad
> Affects Versions: Launchpad Bundles 5
> Reporter: Vidar S. Ramdal
> Assignee: Felix Meschberger
> Fix For: Launchpad Bundles 6
>
>
> 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.
[jira] Updated: (SLING-1163) Dynamic Class Loader components
unsatisfied after a bundle is updated
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger updated SLING-1163:
-------------------------------------
Affects Version/s: (was: Launchpad Base 2.0.4)
Fix Version/s: (was: Launchpad Base 2.0.6)
> 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: Launchpad
> Affects Versions: Launchpad Bundles 5
> Reporter: Vidar S. Ramdal
> Assignee: Felix Meschberger
> Fix For: Launchpad Bundles 6
>
>
> 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.
[jira] Commented: (SLING-1163) Dynamic Class Loader components
unsatisfied after a bundle is updated
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12777386#action_12777386 ]
Felix Meschberger commented on SLING-1163:
------------------------------------------
Hi Ray, glad to receive a patch. Could you please create a new issue to track this ? Thanks alot.
> 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: Launchpad
> Affects Versions: Launchpad Bundles 5
> Reporter: Vidar S. Ramdal
> Assignee: Felix Meschberger
> Fix For: Launchpad Bundles 6
>
>
> 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.
[jira] Assigned: (SLING-1163) Dynamic Class Loader components
unsatisfied after a bundle is updated
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger reassigned SLING-1163:
----------------------------------------
Assignee: Felix Meschberger
> 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
> Assignee: Felix Meschberger
> 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.
[jira] Commented: (SLING-1163) Dynamic Class Loader components
unsatisfied after a bundle is updated
Posted by "Vidar S. Ramdal (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12773433#action_12773433 ]
Vidar S. Ramdal commented on SLING-1163:
----------------------------------------
As explained by Felix Meschberger at [1], this is a known issue with the Felix Declarative Services bundle, version 1.0.8.
Workaround: Upgrade to a trunk build of Felix SCR, and set ds.factory.enabled=true in your sling.properties.
[1] http://markmail.org/message/bclkenpu5elmn4ad
> 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.