I think I have seen the same. Are your scripts embedded inside your bundle?
On Oct 23, 2009 6:45 AM, "Vidar Ramdal" <[email protected]> wrote: I'm seeing a problem with the org.apache.sling.commons.classloader bundle. When I update certain of my own bundles, RhinoJavaScriptEngineFactory and JspScriptEngineFactory components are listed as unsatisfied in the web console (see attached screenshot). This only happens with some of my bundles, not all, but the problem seems to be reproducable always. In this state, all attempts to run a rendering script fails with 403 Forbidden, as if the script does not exist. Let's say I have the script /apps/page/GET.esp. Before a bundle update, the script is invoked when I request http://localhost:8080/node. After I update a bundle, the same URL gives me 403 Forbidden, as if the script does not exist. This seems to only apply to scripts, not servlets - http://localhost:8080/node.html always gives me the default output by HtmlRendererServlet. When this problem occurs, I restart the Dynamic Class Loader bundle, and everything is back to normal - until I update one of my problematic bundles again. I have yet to discover exactly what in my bundles is triggering this error, but I'll investigate more. In the mean time, is anyone else seeing this problem? -- Vidar S. Ramdal <[email protected]> - http://www.idium.no Sommerrogata 13-15, N-0255 Oslo, Norway + 47 22 00 84 00 / +47 21 531941, ext 2070
