[jira] Created: (SLING-640) Add provider for status information about timed events
Add provider for status information about timed events -- Key: SLING-640 URL: https://issues.apache.org/jira/browse/SLING-640 Project: Sling Issue Type: Improvement Components: Event Affects Versions: Extensions Event 2.0.2 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Extensions Event 2.0.4 Currently it is only possible to start and stop timed events (by sending events) A new interface TimedEventStatusProvider should be added which allows to query if something is scheduled. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-641) Implement cache for bundle resources
Implement cache for bundle resources Key: SLING-641 URL: https://issues.apache.org/jira/browse/SLING-641 Project: Sling Issue Type: Bug Components: Extensions Affects Versions: Extensions Bundleresource 2.0.2 Reporter: Felix Meschberger Assignee: Felix Meschberger When accessing bundle resources, the BundleResourceProvider currently accesses the bundle for each check, which in turn accesses and lock sthe bundle jar file. A simple cache should be built into the BundleResourceProvider to cache resources found for faster access on future access. This cache should be limited and on a per-bundle level, such that the cache may simply be dropped if the bundle is stopped. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-641) Implement cache for bundle resources
[ https://issues.apache.org/jira/browse/SLING-641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12627996#action_12627996 ] Felix Meschberger commented on SLING-641: - Implemented first version in Rev. 691609. JavaDoc pending, therefore keeping issue open > Implement cache for bundle resources > > > Key: SLING-641 > URL: https://issues.apache.org/jira/browse/SLING-641 > Project: Sling > Issue Type: Bug > Components: Extensions >Affects Versions: Extensions Bundleresource 2.0.2 >Reporter: Felix Meschberger >Assignee: Felix Meschberger > > When accessing bundle resources, the BundleResourceProvider currently > accesses the bundle for each check, which in turn accesses and lock sthe > bundle jar file. > A simple cache should be built into the BundleResourceProvider to cache > resources found for faster access on future access. This cache should be > limited and on a per-bundle level, such that the cache may simply be dropped > if the bundle is stopped. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-641) Implement cache for bundle resources
[ https://issues.apache.org/jira/browse/SLING-641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger updated SLING-641: Fix Version/s: Extensions Bundleresource 2.1.0 > Implement cache for bundle resources > > > Key: SLING-641 > URL: https://issues.apache.org/jira/browse/SLING-641 > Project: Sling > Issue Type: Bug > Components: Extensions >Affects Versions: Extensions Bundleresource 2.0.2 >Reporter: Felix Meschberger >Assignee: Felix Meschberger > Fix For: Extensions Bundleresource 2.1.0 > > > When accessing bundle resources, the BundleResourceProvider currently > accesses the bundle for each check, which in turn accesses and lock sthe > bundle jar file. > A simple cache should be built into the BundleResourceProvider to cache > resources found for faster access on future access. This cache should be > limited and on a per-bundle level, such that the cache may simply be dropped > if the bundle is stopped. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: OSGi-fied JSR 223 JRuby engine
Hi Felix, Thanks for giving me an idea. Let me ask a couple questions since I'm sill struggling to get things work. I followed the instruction described at http://incubator.apache.org/sling/site/discover-sling-in-15-minutes.html to install and start sling. I could probably intall JRuby engine successfully by using the form in http://localhost:/system/console/list. When I looked at http://localhost:/system/console/list after restarting jetty server, I could see the entry "40 JRuby JSR223 Engine" showed up in the list. However, the status was "Installed" and not "Active." When I clicked on a start button on the left, an error.log said as follows: 03.09.2008 09:39:00.287 *ERROR* [btpool0-1] org.apache.felix.webconsole Cannot s tart (org.osgi.framework.BundleException: Unresolved package in bundle 40: packa ge; (package=org.jruby.runtime.builtin)) org.osgi.framework.BundleException: Unr esolved package in bundle 40: package; (package=org.jruby.runtime.builtin) at org.apache.felix.framework.Felix._resolveBundle(Felix.java:1728) at org.apache.felix.framework.Felix._startBundle(Felix.java:1591) at org.apache.felix.framework.Felix.startBundle(Felix.java:1544) at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:371) at org.apache.felix.webconsole.internal.core.StartAction.performAction(S tartAction.java:58) at org.apache.felix.webconsole.internal.servlet.OsgiManager.handleAction (OsgiManager.java:306) (skip) JSR 223 JRuby engine needes JRuby archives to get it start. How can I install jruby.jar into Sling or where to put ruby.jar in a directory tree? My another question is where /apps/sling/nonexisting/GET.erb should be in the sling directory tree? I tried curl command as in "Create some content" section of http://incubator.apache.org/sling/site/discover-sling-in-15-minutes.html. However, I don't have /apps/foo/bar directory anywhere under the sling directory tree. Am I missing something? My last question is what document should I read to know how to get JSR 223 scripting engines work? I googled but could not find any document available. Thanks -Yoko On Sun, Aug 31, 2008 at 3:02 PM, Felix Meschberger <[EMAIL PROTECTED]> wrote: > Hi Yoko, > > Yoko Harada schrieb: >> >> Hi, >> >> I've released JSR 223 JRuby engine independenly at >> >> https://scripting.dev.java.net/servlets/ProjectDocumentList?folderID=8848&expandFolder=8848&folderID=8848 >> expecially for JDK 1.5 users. >> >> I just released JRuby engine 1.1.5, which is JRuby 1.1.4 compliant >> version and should be OSGi-fied one. However, I'm not sure this >> release really fixes issue >> 37(https://scripting.dev.java.net/issues/show_bug.cgi?id=37) filed in >> the scripting project's issue tracker. How can I test released >> archives work with Apache Sling? > > It should be fairly easy: just install the required bundle(s) into sling (I > generally use the Apache Felix Web Console). The Sling scripting > infrastructure should recognize the JRuby bundle, which contains the > ScriptEngineFactory provided the factory is listed in the META-INF/services > folders as described by JSR-223. > > When the ScriptEngineFactory has been picked up, you should be able to write > scripts with the extension supported by the ScriptEngine. > > Unfortunately there is no other way yet, to find out whether the script > engine has been "accepted". > > > For example, you could do the following: > > - start Sling > - install the JRuby bundles > - look in the Sling log (logs/error.log) for any > errors during the installation > - open a web dav connect to Sling (e.g. if Sling is > started on por , open to http://host:/) > - create a script at /apps/sling/nonexisting/GET.erb > (given erb would be the JRuby extension) > - with your browser access http://host:/missing/page.html > > The last part causes a non existing resource of type sling:nonexisting to be > used for processing and the /apps/sling/nonexisting/GET.erb would be called > to process the request. > > Hope this helps. > > Regards > Felix >
[jira] Created: (SLING-642) ResourceProvider registered with a root path with a trailing slash cannot be unregistered
ResourceProvider registered with a root path with a trailing slash cannot be unregistered - Key: SLING-642 URL: https://issues.apache.org/jira/browse/SLING-642 Project: Sling Issue Type: Bug Components: JCR Resource Affects Versions: JCR Resource 2.0.2 Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: JCR Resource 2.0.4 If a ResourceProvider is registered with a path with a trailing slash, it is happily and correctly registered. Unregistration fails for such a root path. Actually root paths used for hooking ResourceProvider instances into the provider tree should never have a trailing slash. Therefore the JcrResourceResolverFactoryImpl.bindResourceProvider and unbindResourceProvider methods should remove any trailing slash from the root paths before using them for hooking the ResourceProvider up. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-642) ResourceProvider registered with a root path with a trailing slash cannot be unregistered
[ https://issues.apache.org/jira/browse/SLING-642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger closed SLING-642. --- Resolution: Fixed Fixed in Rev. 691792. > ResourceProvider registered with a root path with a trailing slash cannot be > unregistered > - > > Key: SLING-642 > URL: https://issues.apache.org/jira/browse/SLING-642 > Project: Sling > Issue Type: Bug > Components: JCR Resource >Affects Versions: JCR Resource 2.0.2 >Reporter: Felix Meschberger >Assignee: Felix Meschberger > Fix For: JCR Resource 2.0.4 > > > If a ResourceProvider is registered with a path with a trailing slash, it is > happily and correctly registered. Unregistration fails for such a root path. > Actually root paths used for hooking ResourceProvider instances into the > provider tree should never have a trailing slash. > Therefore the JcrResourceResolverFactoryImpl.bindResourceProvider and > unbindResourceProvider methods should remove any trailing slash from the root > paths before using them for hooking the ResourceProvider up. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-643) The LogSupport.fireLogEvent should deliver LogEvents to listeners asynchronously
The LogSupport.fireLogEvent should deliver LogEvents to listeners asynchronously Key: SLING-643 URL: https://issues.apache.org/jira/browse/SLING-643 Project: Sling Issue Type: Bug Components: Commons Log Affects Versions: Commons Log 2.0.2 Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: Commons Log 2.0.4 Currently the LogSupport.fireLogEvent notifies registered LogListeners synchronously during the call the to the LogService.log method. According to Section 101.4, Log Reader Service, of the OSGi Service Compendium specification, the delivery of events to LogListeners is recommended to be done asynchronously: "The delivery of LogEntry objects to the LogListener object should be done asynchronously" This should enhance the performance of the LogService.log calls dramatically. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-644) Add a Felix Web Console plugin the bundle resource provider
Add a Felix Web Console plugin the bundle resource provider --- Key: SLING-644 URL: https://issues.apache.org/jira/browse/SLING-644 Project: Sling Issue Type: Improvement Components: Extensions Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: Extensions Bundleresource 2.1.0 For easy overview of the state of the bundle resource provider services registered in the system, a simple plugin for the Felix Web Console should be developed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
