Dependencies and release votes
Hi all, I have updated the jcr base, contentloader, and jackrabbit-server projects to refer to the next SNAPSHOT versions of the jcr api and jcr base modules to be able to build Sling in Rev. 993249. This can be reverted once the release artifacts are published. Regards Felix
[jira] Updated: (SLING-1708) contrib/scripting/velocity is missing suitable resourceloader for the JCR
[ https://issues.apache.org/jira/browse/SLING-1708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Müller updated SLING-1708: --- Fix Version/s: Scripting Velocity 2.0.0 contrib/scripting/velocity is missing suitable resourceloader for the JCR - Key: SLING-1708 URL: https://issues.apache.org/jira/browse/SLING-1708 Project: Sling Issue Type: Bug Components: Scripting Environment: Felix 1.4, Sling 2.0.7, Apache Velocity 1.6.2 Reporter: Olaf Otto Fix For: Scripting Velocity 2.0.0 Original Estimate: 4h Remaining Estimate: 4h Affects: Rev. 989119 of https://svn.apache.org/repos/asf/sling/trunk/contrib/scripting/velocity (2.0.0-SNAPSHOT) The velocity resource manager (org.apache.velocity.runtime.resource.ResourceManagerImpl) has, by default, only an org.apache.velocity.runtime.resource.loader.FileResourceLoader instance. This resourceloader cannot load resources JCR resources as it attempts to access the filesystem. To reproduce, simply create a .vlt script and add an include directive: template1.vlt: #include(/path/to/template2.vlt) This will fail: org.apache.velocity.exception.ResourceNotFoundException: Unable to find resource '/path/to/template2.vlt' at org.apache.velocity.runtime.resource.ResourceManagerImpl.loadResource(ResourceManagerImpl.java:483) at org.apache.velocity.runtime.resource.ResourceManagerImpl.getResource(ResourceManagerImpl.java:354) at org.apache.velocity.runtime.RuntimeInstance.getContent(RuntimeInstance.java:1445) at org.apache.velocity.runtime.directive.Include.renderOutput(Include.java:229) at org.apache.velocity.runtime.directive.Include.render(Include.java:155) at org.apache.velocity.runtime.parser.node.ASTDirective.render(ASTDirective.java:175) at org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:336) at org.apache.velocity.runtime.RuntimeInstance.render(RuntimeInstance.java:1277) at org.apache.velocity.runtime.RuntimeInstance.evaluate(RuntimeInstance.java:1216) A suitable resource loader should be provided to the VelocityEngine instance (perhaps in the VelocityTemplatesScriptEngine). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-1594) Support CommonJS Modules i.e. the require function
[ https://issues.apache.org/jira/browse/SLING-1594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-1594: Fix Version/s: Scripting JavaScript 2.0.8 Support CommonJS Modules i.e. the require function -- Key: SLING-1594 URL: https://issues.apache.org/jira/browse/SLING-1594 Project: Sling Issue Type: Improvement Components: Scripting Reporter: Lars Trieloff Assignee: Carsten Ziegeler Priority: Minor Fix For: Scripting JavaScript 2.0.8 Attachments: SLING-1594.patch SLING-320 already allows calling functions in external scripts, so implementing the full-blown modules spec to allow interoperability with other CommonJS modules should be possible. http://wiki.commonjs.org/wiki/Modules/1.1.1 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [VOTE] Release Apache Sling JCR API, JCR Base, JCR Content Loader, and Jackrabbit Server 2.1.0
+1 Regards Felix On 06.09.2010 17:10, Justin Edelson wrote: Hi, We solved a total of 33 issues in these releases: JCR API - 1 issue: https://issues.apache.org/jira/browse/SLING/fixforversion/12314564 JCR Base - 6 issues: https://issues.apache.org/jira/browse/SLING/fixforversion/12314768 JCR Content Loader - 16 issues: https://issues.apache.org/jira/browse/SLING/fixforversion/12314472 Embedded Jackrabbit Server - 10 issues: https://issues.apache.org/jira/browse/SLING/fixforversion/12314769 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-038/ You can use this UNIX script to download the release and verify the signatures: http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh Usage: sh check_staged_release.sh 038 /tmp/sling-staging Please vote to approve this release: [ ] +1 Approve the release [ ] 0 Don't care [ ] -1 Don't release, because ... This vote will be open for 72 hours. Justin
[jira] Commented: (SLING-1733) BundleResourceProvider fails to find resources when multiple bundles have the same Sling-Bundle-Resources path
[
https://issues.apache.org/jira/browse/SLING-1733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12906708#action_12906708
]
Felix Meschberger commented on SLING-1733:
--
Patch looks good for me with one comment for simplification: Instead of getting
the bundleId to compare, you can simply compare the bundle cache objects to
only use the parent bundle resource iff they are managed by the same
BundleCache instance.
if (((BundleResource)parent).getBundle() == this.bundle) {
return ((BundleResource) parent).listChildren();
}
BundleResourceProvider fails to find resources when multiple bundles have the
same Sling-Bundle-Resources path
--
Key: SLING-1733
URL: https://issues.apache.org/jira/browse/SLING-1733
Project: Sling
Issue Type: Bug
Components: Extensions
Affects Versions: Extensions Bundleresource 2.0.4
Reporter: Eric Norman
Assignee: Eric Norman
Fix For: Extensions Bundleresource 2.0.6
Attachments: SLING-1733.patch
If multiple bundles are providing Sling-Bundle-Resources with the same path,
the resources from the second bundle are not accessible.
.
For example:
Bundle 1 contains these scripts:
/libs/sling/servlet/default/script1.html.esp
/libs/sling/servlet/default/script2.html.esp
And the resource is provided as:
Sling-Bundle-Resources
/libs/sling/servlet/default
/Sling-Bundle-Resources
Bundle 2 contains these scripts:
/libs/sling/servlet/default/script2.html.esp
/libs/sling/servlet/default/script3.html.esp
And the resource is provided as:
Sling-Bundle-Resources
/libs/sling/servlet/default
/Sling-Bundle-Resources
With both bundles installed, you either see the scripts from bundle1 or the
scripts from bundle2 but not both.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SLING-1603) SlingServlet service
[ https://issues.apache.org/jira/browse/SLING-1603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger resolved SLING-1603. -- Resolution: Fixed Applied a modified version of the patch in Rev. 993280. The main change is the rename of the interface Engine to SlingRequestProcessor as proposed. Other modifications are related to fixes of bugs contained in the original patch. SlingServlet service Key: SLING-1603 URL: https://issues.apache.org/jira/browse/SLING-1603 Project: Sling Issue Type: Improvement Components: Engine Affects Versions: Engine 2.0.6 Reporter: Bertrand Delacretaz Assignee: Felix Meschberger Priority: Minor Fix For: Engine 2.1.2 Attachments: SLING-1603-fmeschbe.patch, SLING-1603.patch, SLING-1603.patch For SLING-550 I need to call the SlingMainServlet outside of the web container's request/response cycle. I'll attach a patch that introduces a new SlingServlet interface that SlingMainServlet implements. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SLING-1213) Filters to support servlet-API-level scope configuration
[ https://issues.apache.org/jira/browse/SLING-1213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger resolved SLING-1213. -- Fix Version/s: Engine 2.1.2 Resolution: Fixed Implemented support for the new filter scopes and defined respective constants in the EngineConstants class in Rev. 993280. The supported filter scopes are now: REQUEST -- request level filters INCLUDE -- filters only called on RequestDispatcher.include (also for jsp:include, and sling:include) FORWARD -- filters only called on RequestDispatcher.forward (also for jsp:forward, and sling:forward) ERROR -- filters only called handling status responses due to sendError and unhandled Throwables COMPONENT -- filters called after REQUEST level filters and upon RequestDispatcher.forward and include Filters to support servlet-API-level scope configuration Key: SLING-1213 URL: https://issues.apache.org/jira/browse/SLING-1213 Project: Sling Issue Type: Improvement Components: Engine Reporter: Mike Pfaff Assignee: Felix Meschberger Fix For: Engine 2.1.2 Currently the filter.scope supports either - component (comparable to dispatcherINCLUDE,FORWARD,ERROR/dispatcher of the servlet API) or - request (comparable to dispatcherREQUEST/dispatcher of the servlet API) In certain cases one wants to have finer control over the filter scopes, e.g. have a filter that would do dispatcherREQUEST,FORWARD/dispatcher, so that the filter is applied first for the request and then again when you do a requestDispatcher.forward(). Therefore i suggest that the filter.scope should be enhanced as follows: - Make filter.scope a multi-value property - Add filter scopes: include, forward and error - The existing filter scope component(quasi an alias for include,forward,error) should for backward-compatibility not change. - Add filter chains for the new filter scopes (don't know if this is needed internally?) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [VOTE] Release Apache Sling JCR API, JCR Base, JCR Content Loader, and Jackrabbit Server 2.1.0
On Mon, Sep 6, 2010 at 5:10 PM, Justin Edelson jus...@apache.org wrote: We solved a total of 33 issues in these releases: JCR API - 1 issue: https://issues.apache.org/jira/browse/SLING/fixforversion/12314564 JCR Base - 6 issues: https://issues.apache.org/jira/browse/SLING/fixforversion/12314768 JCR Content Loader - 16 issues: https://issues.apache.org/jira/browse/SLING/fixforversion/12314472 Embedded Jackrabbit Server - 10 issues: https://issues.apache.org/jira/browse/SLING/fixforversion/12314769 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-038/ You can use this UNIX script to download the release and verify the signatures: http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh Usage: sh check_staged_release.sh 038 /tmp/sling-staging Please vote to approve this release: [ ] +1 Approve the release [ ] 0 Don't care [ ] -1 Don't release, because ... This vote will be open for 72 hours. +1 -- Vidar S. Ramdal vi...@idium.no - http://www.idium.no Sommerrogata 13-15, N-0255 Oslo, Norway + 47 22 00 84 00 / +47 22 00 84 76 Quando omni flunkus moritatus!
[jira] Commented: (SLING-1603) SlingServlet service
[ https://issues.apache.org/jira/browse/SLING-1603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12906794#action_12906794 ] Felix Meschberger commented on SLING-1603: -- Fixed missing service registration of the SlingResourceProcessor service (as well as some minor cleanup) in Rev. 993307. SlingServlet service Key: SLING-1603 URL: https://issues.apache.org/jira/browse/SLING-1603 Project: Sling Issue Type: Improvement Components: Engine Affects Versions: Engine 2.0.6 Reporter: Bertrand Delacretaz Assignee: Felix Meschberger Priority: Minor Fix For: Engine 2.1.2 Attachments: SLING-1603-fmeschbe.patch, SLING-1603.patch, SLING-1603.patch For SLING-550 I need to call the SlingMainServlet outside of the web container's request/response cycle. I'll attach a patch that introduces a new SlingServlet interface that SlingMainServlet implements. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[DISCUSS] Registering filters with Sling
Hi all, Traditionally javax.servlet.Filter services were picked up by the Sling Main Servlet and used as filters regardless of any service registration properties. The filter.scope property could optionally be used to define a scope for the filter (request or component before SLING-1213, now also INCLUDE, FORWARD, and ERROR). To not pick up filters destined for the Apache Felix Http Service (registered with the pattern service property) we explicitly xclude those. I would like to go a step further and * define a new service property sling.filter.scope * deprecate the old filter.scope property * require services to either have the sling.filter.scope or the filter.scope (backwards compatibility) property set * optionally: support for a configuration option to cause filters without a scope property to still be picked up I consider renaming the official name to prevent any name collisions. WDYT ? Regards Felix
Re: [DISCUSS] Registering filters with Sling
+1 On 9/7/10 9:49 AM, Felix Meschberger wrote: Hi all, Traditionally javax.servlet.Filter services were picked up by the Sling Main Servlet and used as filters regardless of any service registration properties. The filter.scope property could optionally be used to define a scope for the filter (request or component before SLING-1213, now also INCLUDE, FORWARD, and ERROR). To not pick up filters destined for the Apache Felix Http Service (registered with the pattern service property) we explicitly xclude those. I would like to go a step further and * define a new service property sling.filter.scope * deprecate the old filter.scope property * require services to either have the sling.filter.scope or the filter.scope (backwards compatibility) property set * optionally: support for a configuration option to cause filters without a scope property to still be picked up I consider renaming the official name to prevent any name collisions. WDYT ? Regards Felix
Re: [DISCUSS] Registering filters with Sling
Ian Boston wrote On 7 Sep 2010, at 14:49, Felix Meschberger wrote: Hi all, Traditionally javax.servlet.Filter services were picked up by the Sling Main Servlet and used as filters regardless of any service registration properties. The filter.scope property could optionally be used to define a scope for the filter (request or component before SLING-1213, now also INCLUDE, FORWARD, and ERROR). To not pick up filters destined for the Apache Felix Http Service (registered with the pattern service property) we explicitly xclude those. I would like to go a step further and * define a new service property sling.filter.scope * deprecate the old filter.scope property * require services to either have the sling.filter.scope or the filter.scope (backwards compatibility) property set * optionally: support for a configuration option to cause filters without a scope property to still be picked up I consider renaming the official name to prevent any name collisions. WDYT ? Yes, makes sense to me. Might reqiure some patches for those downstream but it will be minor, and will generate a better distinction between Sling filters and httpservice filters. Sounds ok to me, but if we rename the scope prop we should rename the order prop as well to avoid collisions. Carsten -- Carsten Ziegeler cziege...@apache.org
Re: [DISCUSS] Registering filters with Sling
Felix Meschberger wrote The order property has already been deprecated in favor of the OSGi standard service.ranking property (as of FELIX-1213). Perfect :) Carsten -- Carsten Ziegeler cziege...@apache.org
Re: [DISCUSS] Registering filters with Sling
Hi all, Thanks for the feedback so far. I have created SLING-1734 [1] to track this change. Regards Felix [1] https://issues.apache.org/jira/browse/SLING-1734 On 07.09.2010 15:49, Felix Meschberger wrote: Hi all, Traditionally javax.servlet.Filter services were picked up by the Sling Main Servlet and used as filters regardless of any service registration properties. The filter.scope property could optionally be used to define a scope for the filter (request or component before SLING-1213, now also INCLUDE, FORWARD, and ERROR). To not pick up filters destined for the Apache Felix Http Service (registered with the pattern service property) we explicitly xclude those. I would like to go a step further and * define a new service property sling.filter.scope * deprecate the old filter.scope property * require services to either have the sling.filter.scope or the filter.scope (backwards compatibility) property set * optionally: support for a configuration option to cause filters without a scope property to still be picked up I consider renaming the official name to prevent any name collisions. WDYT ? Regards Felix
Re: [VOTE] Release Apache Sling JCR API, JCR Base, JCR Content Loader, and Jackrabbit Server 2.1.0
+1 On Sep 6, 2010 8:42 AM, Justin Edelson jus...@apache.org wrote: Hi, We solved a total of 33 issues in these releases: JCR API - 1 issue: https://issues.apache.org/jira/browse/SLING/fixforversion/12314564 JCR Base - 6 issues: https://issues.apache.org/jira/browse/SLING/fixforversion/12314768 JCR Content Loader - 16 issues: https://issues.apache.org/jira/browse/SLING/fixforversion/12314472 Embedded Jackrabbit Server - 10 issues: https://issues.apache.org/jira/browse/SLING/fixforversion/12314769 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-038/ You can use this UNIX script to download the release and verify the signatures: http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh Usage: sh check_staged_release.sh 038 /tmp/sling-staging Please vote to approve this release: [ ] +1 Approve the release [ ] 0 Don't care [ ] -1 Don't release, because ... This vote will be open for 72 hours. Justin
RE: [VOTE] Release Apache Sling JCR API, JCR Base, JCR Content Loader, and Jackrabbit Server 2.1.0
+1 Hi, We solved a total of 33 issues in these releases: JCR API - 1 issue: https://issues.apache.org/jira/browse/SLING/fixforversion/12314564 JCR Base - 6 issues: https://issues.apache.org/jira/browse/SLING/fixforversion/12314768 JCR Content Loader - 16 issues: https://issues.apache.org/jira/browse/SLING/fixforversion/12314472 Embedded Jackrabbit Server - 10 issues: https://issues.apache.org/jira/browse/SLING/fixforversion/12314769 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-038/ You can use this UNIX script to download the release and verify the signatures: http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh Usage: sh check_staged_release.sh 038 /tmp/sling-staging Please vote to approve this release: [ ] +1 Approve the release [ ] 0 Don't care [ ] -1 Don't release, because ... This vote will be open for 72 hours. Justin
CMIS
Has anyone looked at adding CMIS support to Sling? CMIS hasn't held a lot of interest for me, but it might be a good compliment to our array of integration options. I thought there was a CMIS-JCR wrapper in the Jackrabbit source tree, but I can't find it now. WDYT? Justin
[jira] Resolved: (SLING-1733) BundleResourceProvider fails to find resources when multiple bundles have the same Sling-Bundle-Resources path
[ https://issues.apache.org/jira/browse/SLING-1733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Norman resolved SLING-1733. Resolution: Fixed fixed in r993606. BundleResourceProvider fails to find resources when multiple bundles have the same Sling-Bundle-Resources path -- Key: SLING-1733 URL: https://issues.apache.org/jira/browse/SLING-1733 Project: Sling Issue Type: Bug Components: Extensions Affects Versions: Extensions Bundleresource 2.0.4 Reporter: Eric Norman Assignee: Eric Norman Fix For: Extensions Bundleresource 2.0.6 Attachments: SLING-1733.patch If multiple bundles are providing Sling-Bundle-Resources with the same path, the resources from the second bundle are not accessible. . For example: Bundle 1 contains these scripts: /libs/sling/servlet/default/script1.html.esp /libs/sling/servlet/default/script2.html.esp And the resource is provided as: Sling-Bundle-Resources /libs/sling/servlet/default /Sling-Bundle-Resources Bundle 2 contains these scripts: /libs/sling/servlet/default/script2.html.esp /libs/sling/servlet/default/script3.html.esp And the resource is provided as: Sling-Bundle-Resources /libs/sling/servlet/default /Sling-Bundle-Resources With both bundles installed, you either see the scripts from bundle1 or the scripts from bundle2 but not both. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-1735) Properly support service.ranking, service.id and filter.order for filter ordering
Properly support service.ranking, service.id and filter.order for filter ordering - Key: SLING-1735 URL: https://issues.apache.org/jira/browse/SLING-1735 Project: Sling Issue Type: Bug Components: Engine Affects Versions: Engine 2.1.2 Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: Engine 2.1.2 As of SLING-1213 the service.ranking registration property is primarily used for ordering services and filter.order is only used if present and service.ranking is not present. This change has not been fully and properly implemented, though: * filter.order was defined such that a lower value gives higher precedence, whereas service.ranking is defined to give higher values higher precedence * The default value for filter.order was Integer.MAX_VALUE (lowest precedence) while the default value for service.ranking is zero (medium precedence) * The OSGi spec states to fall back to comparing the service.id property if the service.ranking property is equal for two services to order. This is not considered at all yet. To fix this, the filter ordering must be extended such that: * the value of the filter.order property is negated (if stated and service.ranking is missing) * the service.id property is used as a fallback if the other ordering properties do not resolve ordering amongst services The fact that filter.order defaulted to Integer.MAX_VALUE is ignored. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: CMIS
Hi, On 07.09.2010 20:49, Justin Edelson wrote: Has anyone looked at adding CMIS support to Sling? CMIS hasn't held a lot of interest for me, but it might be a good compliment to our array of integration options. I thought there was a CMIS-JCR wrapper in the Jackrabbit source tree, but I can't find it now. WDYT? Hasn't this moved to the Chemistry poddling ? Whatever with my Sling hat on, I would assume that any CMIS integration for Sling should probably set up on-top of the Resource tree (and yes, I don't know too much about CMIS). Regards Felix
