[jira] Commented: (SLING-848) Support getting versioned resources by using uri path parameters
[ https://issues.apache.org/jira/browse/SLING-848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12670273#action_12670273 ] Bertrand Delacretaz commented on SLING-848: --- I think /content/home/tobi.html;v=1.5 breaks existing logic, as IMHO programmers assume that things that affect the representation come at the end of the URL. I much prefer /content/home/tobi;v=1.5.selector.html Where the URI parameters (which affect the selected content) come first, and the selectors and extensions (which affect the representation) last. Also, why not change the API? If we start supporting URI parameters as specified, the least surprising way would be to add a (backwards-compatible) getURIParameters method to the SlingHttpServletRequest interface. Hacking the content path downstream feels wrong. > Support getting versioned resources by using uri path parameters > > > Key: SLING-848 > URL: https://issues.apache.org/jira/browse/SLING-848 > Project: Sling > Issue Type: New Feature > Components: JCR Resource >Affects Versions: JCR Resource 2.0.2 >Reporter: Carsten Ziegeler > > Getting versioned content should be support thorough uri path parameters, > like /something/hello;v=1.1 > For jcr based resources the value of the version should either point to a > version name or label. > In order to not change our existing apis, we introduce a new utility method > which removes all uri path parameters > and returns a map of these. Every resource provider could use this utility > method and then decide to act on these > parameters. > If a requested version does not exists, a 404 is returned. > If the requested node does not directly point to a versionable node, the > algorithm checks the parent hierarchy until a versionable node is found, and > tries to get the version of this node and then goes down the path again. If > the versionable node does not have the requested version or the child, a 404 > is returned. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Is there any easy method to backup and restore data in sling
Hi everyone: Is there any smooth way to backup and restore data in sling ? Thanks. 2009-02-04 yanjie
[jira] Commented: (SLING-848) Support getting versioned resources by using uri path parameters
[ https://issues.apache.org/jira/browse/SLING-848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12670281#action_12670281 ] Marc commented on SLING-848: Supporting versions is a great feature. Just for the record of future bug hunters: Mac OS 10.4 + HTTP Basic Authentication cannot handle these links [1]. BTW this was also one of the reasons Rails dropped using ; in URLs [2]. One of the other reasons was caching but I'm not sure if this still applies. [1] https://bugs.webkit.org/show_bug.cgi?id=10073 [2] http://dev.rubyonrails.org/changeset/6485 > Support getting versioned resources by using uri path parameters > > > Key: SLING-848 > URL: https://issues.apache.org/jira/browse/SLING-848 > Project: Sling > Issue Type: New Feature > Components: JCR Resource >Affects Versions: JCR Resource 2.0.2 >Reporter: Carsten Ziegeler > > Getting versioned content should be support thorough uri path parameters, > like /something/hello;v=1.1 > For jcr based resources the value of the version should either point to a > version name or label. > In order to not change our existing apis, we introduce a new utility method > which removes all uri path parameters > and returns a map of these. Every resource provider could use this utility > method and then decide to act on these > parameters. > If a requested version does not exists, a 404 is returned. > If the requested node does not directly point to a versionable node, the > algorithm checks the parent hierarchy until a versionable node is found, and > tries to get the version of this node and then goes down the path again. If > the versionable node does not have the requested version or the child, a 404 > is returned. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Is there any easy method to backup and restore data in sling
Hi Yanjie, On Wed, Feb 4, 2009 at 09:44, yanshaozhiGmail wrote: > Hi everyone: > > Is there any smooth way to backup and restore data in sling ? Sling stores its data in a Jackrabbit repository (a JCR[1] implementation). The JCR spec covers content exporting and importing in the paragraphs 6.4, 6.5 and 7.3. I strongly advise you to take a look in those topics, if you haven't done yet. In summary, you can export your content to XML using the method 'exportSystemView' [2] and import it back using the method 'importXML' [3], both belonging to the javax.jcr.Session class. Another option is to persist your repository in a RDBMS, and then all you need to concern is about the database backup. If you're interested in know more about it, the Jackrabbit users list [4] is the most appropriate place. Kindly, -- Douglas Jose http://douglasjose.com - "Use free software. Help us make a free world." [1] http://jcp.org/en/jsr/detail?id=170 [2] http://www.day.com/maven/jsr170/javadocs/jcr-1.0/javax/jcr/Session.html#exportSystemView(java.lang.String,%20java.io.OutputStream,%20boolean,%20boolean) [3] http://www.day.com/maven/jsr170/javadocs/jcr-1.0/javax/jcr/Session.html#importXML(java.lang.String,%20java.io.InputStream,%20int) [4] http://jackrabbit.apache.org/mailing-lists.html
[jira] Commented: (SLING-848) Support getting versioned resources by using uri path parameters
[ https://issues.apache.org/jira/browse/SLING-848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12670288#action_12670288 ] Tobias Bocanegra commented on SLING-848: that's was i feared. using the ; parameters is not widely used, and causes problems, as marc pointed out. i think it's ok to use the parameters for the resource resolver - but then you can also extend the api. i would avoid using them on the URI from the request, especially, because the generation of such links is a bit special. i'd rather see a "global" query parameter or cookie that controls the version selection. > Support getting versioned resources by using uri path parameters > > > Key: SLING-848 > URL: https://issues.apache.org/jira/browse/SLING-848 > Project: Sling > Issue Type: New Feature > Components: JCR Resource >Affects Versions: JCR Resource 2.0.2 >Reporter: Carsten Ziegeler > > Getting versioned content should be support thorough uri path parameters, > like /something/hello;v=1.1 > For jcr based resources the value of the version should either point to a > version name or label. > In order to not change our existing apis, we introduce a new utility method > which removes all uri path parameters > and returns a map of these. Every resource provider could use this utility > method and then decide to act on these > parameters. > If a requested version does not exists, a 404 is returned. > If the requested node does not directly point to a versionable node, the > algorithm checks the parent hierarchy until a versionable node is found, and > tries to get the version of this node and then goes down the path again. If > the versionable node does not have the requested version or the child, a 404 > is returned. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Groovlets and Groovy Server Pages
Hi all, Starting with Groovy 1.6 RC1, the groovy-all.jar may directly be installed in to the Sling OSGi framework to enable Groovy scripting. This is great and works perfectly. Now, there are also Groovlets and Groovy Server Pages. These are not supported yet, directly. How about creating a ScriptEngineFactory, which supports these by treating scripts with the ".groovlet" extension as Groovlets and scripts with the ".gsp" extension as Groovy Server Pages. Is this something, which has a place here at Sling or should we get the Groovy people to include that ? Regards Felix
Re: Groovlets and Groovy Server Pages
Hi, On Wed, Feb 4, 2009 at 10:51 AM, Felix Meschberger wrote: > ...How about creating a ScriptEngineFactory, which supports these by > treating scripts with the ".groovlet" extension as Groovlets and scripts > with the ".gsp" extension as Groovy Server Pages +1 > ...Is this something, which has a place here at Sling or should we get the > Groovy people to include that ?... If they have to do it, does it just mean that they need to list the gsp and groovlet extensions in their script engine bundle, or is there more to that? If the changes are of general interest, I think it would be better for them to make those changes. -Bertrand
[Poll] What are you using Sling/Jackrabbit for?
Hello JCR community, in response to the discussion around posting (commercial) products and job offers related to Jackrabbit or Sling on the mailing list [1], some mentioned an interest in knowing what Sling and/or Jackrabbit are used for, and I think this is a good idea! That should give a level playing field for everyone and relieve the discussion a bit... [1] http://markmail.org/message/nv2375hdfbijks3g So, let's have some small "poll" - if you'd like, you can present your cool JCR-based software in this thread. Interesting facts would be: - Name of the Tool/Library/Product + Website - Use case - Cool features - System environment (eg. those nasty enterprise integrations ;-)) - What features gained most (or where simple to do) because of JCR and/or Sling's built-in functionality? - Interesting technical challegens - etc. I can't wait for your answers! Regards, Alex -- Alexander Klimetschek alexander.klimetsc...@day.com
Re: CRX 1.4.1 released - powered by Apache Jackrabbit & Sling - thanks!
Hi, > I myself would be > interested in how Jackrabbit (and Sling) is used in other companies' > products. > > Cheers > Greg > Absolutely agree. It´s very important to know as many Sling/Jackrabbit case estudies as possible. Congratulations!. BR, Juanjo.
