[jira] Commented: (SLING-1455) Impossible to refer to same-name-siblings when doing internal redirect to another protocol
[
https://issues.apache.org/jira/browse/SLING-1455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12898094#action_12898094
]
Felix Meschberger commented on SLING-1455:
--
Since SLING-1218 we are using a copy of the HTTP Client URI class in the
JCRResourceResolver to work around escaping issues in the mapped paths. Maybe
we could hack this class up to account for bracket indices ??
Impossible to refer to same-name-siblings when doing internal redirect to
another protocol
--
Key: SLING-1455
URL: https://issues.apache.org/jira/browse/SLING-1455
Project: Sling
Issue Type: Bug
Components: JCR
Affects Versions: JCR Resource 2.0.6
Reporter: Vidar S. Ramdal
Fix For: JCR Resource 2.0.8
Attachments: content.xml, etc.xml
Consider the following repository contents:
/etc/map/general-redirect
- sling:internalRedirect = protocol://$1
- sling:match = http/(.*)\.\d+
/etc/map/protocol
- sling:internalRedirect = /content
/content/localhost.80
/content/localhost.80/child
/content/localhost.80/child[2]
The domain mappings (under /etc/map) are then set up so that:
1) A request to http://localhost:8080 should internally redirect to
protocol://localhost.80. This, again, causes the request to resolve to
/content/localhost.80, which is what is intended.
2) Thus, a request to http://localhost:8080/child.html should resolve to
/content/localhost.80/child.
Both 1) and 2) works as intended. However, when including indexes for
same-name siblings, the resolution fails:
http://localhost:8080/child[2].html
.. causes a NPE: *ERROR* [0:0:0:0:0:0:0:1%0 [1269213415402] GET
/child%5B2%5D.html HTTP/1.1] org.apache.sling.engine.impl.SlingMainServlet
service: Uncaught Problem handling the request java.lang.NullPointerException
at
org.apache.sling.engine.impl.SlingHttpServletRequestImpl.getResource(SlingHttpServletRequestImpl.java:90)
at
org.apache.sling.servlets.resolver.internal.SlingServletResolver.getErrorResource(SlingServletResolver.java:368)
at
org.apache.sling.servlets.resolver.internal.SlingServletResolver.handleError(SlingServletResolver.java:259)
This is because resolution in JcrResourceResolver has failed when trying to
construct a URL for the string protocol://localhost/child[2].html:
try {
URI uri = new URI(mappedPath[0]);
... throws a URISyntaxException because the string argument contains
unescaped brackets (for [2]).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SLING-1646) Expose subset of authentication info properties as ResourceResolver attributes
[ https://issues.apache.org/jira/browse/SLING-1646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger resolved SLING-1646. -- Resolution: Fixed This has been implemented and passes the tests. Thus resolving. Expose subset of authentication info properties as ResourceResolver attributes -- Key: SLING-1646 URL: https://issues.apache.org/jira/browse/SLING-1646 Project: Sling Issue Type: Improvement Components: API, JCR Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: JCR Resource 2.0.8, API 2.1.0 The properties of the authentication info (or credentials map) provided to the ResoureResolverFactory to create a new ResourceResolver should be exposed by the ResourceResolver. Exceptions apply to any passwords or JCR Credentials or other identifiable sensitive information, which should of course not be exposed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
RE: extending jQuery JCR Resource explorer
will I be able to update/add/delete the values of multivalued properties through the Sling REST API (SlingPostServlet?)? -Original Message- From: Clemens Wyss [mailto:clemens...@mysign.ch] Sent: Friday, August 13, 2010 7:22 AM To: 'dev@sling.apache.org' Subject: RE: extending jQuery JCR Resource explorer 2, 4, 5, 6, 10 ok, so you think/say mixin types is not that much a topic? ACL view/edit good point, though this mandates 10) ;-) Reference/Path property support Links? dragdrop? I need to make some modifications to the explorer to support non-default workspaces, but hopefully that change will be minor (keeps slipping off my list). is there a jira entry for this task? Is esp the right serverside approach? Or would groovy (me, coming from Ruby), or even Java be helpful? Clemens -Original Message- From: Justin Edelson [mailto:justinedel...@gmail.com] Sent: Thursday, August 12, 2010 9:07 PM To: dev@sling.apache.org Subject: Re: extending jQuery JCR Resource explorer Nice of you to ask about prioritization... 2, 4, 5, 6, 10 Would be the highest priority items for me. I'd also add these to your list: ACL view/edit Reference/Path property support I need to make some modifications to the explorer to support non-default workspaces, but hopefully that change will be minor (keeps slipping off my list). Justin On Aug 12, 2010, at 10:26 AM, Clemens Wyss clemens...@mysign.ch wrote: As promised, I (actually it's we, MySign) intend to extend the jQuery JCR Resource (contrib/explorers/jQuery) explorer in order to make it more valuable for developers. Features currently available (as of May 17th 2010, rev 945149): + login + browse JCR + add node (name, sling:resourceType and jcr:primaryType have to be entered manually (input field)) + delete node + view properties (multivalue properties are shown inline in an input field) + modify/update property (single value properties only) + delete property desirable features: 1) jcr:primaryNodeType properties should be selectable 2) view/add/edit/delete multivalued properties 3) view/add/edit/delete mixin types, mixin types should be selectable 4) simplified input for known types, such as date (see also 1) and 3) ) 5) search/filter functionality (SQL2, JQOM?) 6) nt:file - file upload 7) import/export subtrees, format to be defined 8) input validation 9) ajax'ify the client 10) usermanagement more to come... WDYT? Anything important/fancy missing? How would you priorize these features?
[jira] Resolved: (SLING-983) Add sling.properties file to configuration status page
[ https://issues.apache.org/jira/browse/SLING-983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-983. Fix Version/s: Extensions Settings 0.1.0 (was: Engine 2.1.0) Resolution: Fixed Moved to the new settings module and removed from engine Add sling.properties file to configuration status page -- Key: SLING-983 URL: https://issues.apache.org/jira/browse/SLING-983 Project: Sling Issue Type: Improvement Components: Engine Affects Versions: Launchpad Base 2.1.0 Reporter: Felix Meschberger Assignee: Carsten Ziegeler Fix For: Extensions Settings 0.1.0, Launchpad Base 2.2.0 It would be good, if the sling.properties file could be provided through a Felix Web Console ConfigurationPrinter to include it into the Configuration Status output to ease support. Maybe this would be part of the Sling Engine bundle, which is the core engine of Sling. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SLING-1651) Integrate RunMode module into new Settings Module
[ https://issues.apache.org/jira/browse/SLING-1651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-1651. - Resolution: Fixed Added run mode stuff to the settings service and added web configuration printer and shell command Integrate RunMode module into new Settings Module - Key: SLING-1651 URL: https://issues.apache.org/jira/browse/SLING-1651 Project: Sling Issue Type: Task Components: Engine Affects Versions: Extensions Settings 0.1.0 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Extensions Settings 0.1.0 To keep all settings related stuff in a single central place, we should merge the current run mode module into the settings module -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-1560) Improve and clean up code
[ https://issues.apache.org/jira/browse/SLING-1560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12898197#action_12898197 ] Carsten Ziegeler commented on SLING-1560: - Merge installer impl and thread, make registered resources comparable Improve and clean up code - Key: SLING-1560 URL: https://issues.apache.org/jira/browse/SLING-1560 Project: Sling Issue Type: Improvement Components: Installer Affects Versions: OSGi Installer 3.0.0, JCR Installer 3.0.0 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: OSGi Installer 3.0.0, JCR Installer 3.0.0 In order to fix some outstanding bugs and to add new features, a code review and clean up seems to be a good idea :) This bug will keep track of all changes to the code that don't add new features -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (SLING-1650) Move commons auth to extensions
[ https://issues.apache.org/jira/browse/SLING-1650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger reassigned SLING-1650: Assignee: Felix Meschberger Move commons auth to extensions --- Key: SLING-1650 URL: https://issues.apache.org/jira/browse/SLING-1650 Project: Sling Issue Type: Task Components: Commons, Extensions Affects Versions: Commons Auth 1.0.0 Reporter: Carsten Ziegeler Assignee: Felix Meschberger Fix For: Commons Auth 1.0.0 As the commons auth uses the Sling API it is by definition no commons module :) Therefore it should be moved to the extensions part -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: extending jQuery JCR Resource explorer
On Aug 13, 2010, at 1:22 AM, Clemens Wyss clemens...@mysign.ch wrote: 2, 4, 5, 6, 10 ok, so you think/say mixin types is not that much a topic? Hmm. I'm not aware that you can't set a mixin type today, but yes... in my usage of this explorer, I've never found myself wanting to add a mixin. But YMMV. ACL view/edit good point, though this mandates 10) ;-) Yes Reference/Path property support Links? dragdrop? Display should be links. To add a value, I'd love a browse/search popup, but that's just me. I need to make some modifications to the explorer to support non-default workspaces, but hopefully that change will be minor (keeps slipping off my list). is there a jira entry for this task? No. Is esp the right serverside approach? Or would groovy (me, coming from Ruby), or even Java be helpful? I think esp is used currently, so there's that to consider. Also, you can use (J)Ruby if you want; the jruby-all JAR just needs to installed. Mostly, I imagine the amount of new server side code to be minimal. Justin Clemens -Original Message- From: Justin Edelson [mailto:justinedel...@gmail.com] Sent: Thursday, August 12, 2010 9:07 PM To: dev@sling.apache.org Subject: Re: extending jQuery JCR Resource explorer Nice of you to ask about prioritization... 2, 4, 5, 6, 10 Would be the highest priority items for me. I'd also add these to your list: ACL view/edit Reference/Path property support I need to make some modifications to the explorer to support non-default workspaces, but hopefully that change will be minor (keeps slipping off my list). Justin On Aug 12, 2010, at 10:26 AM, Clemens Wyss clemens...@mysign.ch wrote: As promised, I (actually it's we, MySign) intend to extend the jQuery JCR Resource (contrib/explorers/jQuery) explorer in order to make it more valuable for developers. Features currently available (as of May 17th 2010, rev 945149): + login + browse JCR + add node (name, sling:resourceType and jcr:primaryType have to be entered manually (input field)) + delete node + view properties (multivalue properties are shown inline in an input field) + modify/update property (single value properties only) + delete property desirable features: 1) jcr:primaryNodeType properties should be selectable 2) view/add/edit/delete multivalued properties 3) view/add/edit/delete mixin types, mixin types should be selectable 4) simplified input for known types, such as date (see also 1) and 3) ) 5) search/filter functionality (SQL2, JQOM?) 6) nt:file - file upload 7) import/export subtrees, format to be defined 8) input validation 9) ajax'ify the client 10) usermanagement more to come... WDYT? Anything important/fancy missing? How would you priorize these features?
Re: extending jQuery JCR Resource explorer
On Aug 13, 2010, at 3:55 AM, Clemens Wyss clemens...@mysign.ch wrote: will I be able to update/add/delete the values of multivalued properties through the Sling REST API (SlingPostServlet?)? Yes. You need to set the property as a whole, i.e. pass all values for a property in a same post. There's no way to say delete the third value from the baz property /content/foo/bar. -Original Message- From: Clemens Wyss [mailto:clemens...@mysign.ch] Sent: Friday, August 13, 2010 7:22 AM To: 'dev@sling.apache.org' Subject: RE: extending jQuery JCR Resource explorer 2, 4, 5, 6, 10 ok, so you think/say mixin types is not that much a topic? ACL view/edit good point, though this mandates 10) ;-) Reference/Path property support Links? dragdrop? I need to make some modifications to the explorer to support non-default workspaces, but hopefully that change will be minor (keeps slipping off my list). is there a jira entry for this task? Is esp the right serverside approach? Or would groovy (me, coming from Ruby), or even Java be helpful? Clemens -Original Message- From: Justin Edelson [mailto:justinedel...@gmail.com] Sent: Thursday, August 12, 2010 9:07 PM To: dev@sling.apache.org Subject: Re: extending jQuery JCR Resource explorer Nice of you to ask about prioritization... 2, 4, 5, 6, 10 Would be the highest priority items for me. I'd also add these to your list: ACL view/edit Reference/Path property support I need to make some modifications to the explorer to support non-default workspaces, but hopefully that change will be minor (keeps slipping off my list). Justin On Aug 12, 2010, at 10:26 AM, Clemens Wyss clemens...@mysign.ch wrote: As promised, I (actually it's we, MySign) intend to extend the jQuery JCR Resource (contrib/explorers/jQuery) explorer in order to make it more valuable for developers. Features currently available (as of May 17th 2010, rev 945149): + login + browse JCR + add node (name, sling:resourceType and jcr:primaryType have to be entered manually (input field)) + delete node + view properties (multivalue properties are shown inline in an input field) + modify/update property (single value properties only) + delete property desirable features: 1) jcr:primaryNodeType properties should be selectable 2) view/add/edit/delete multivalued properties 3) view/add/edit/delete mixin types, mixin types should be selectable 4) simplified input for known types, such as date (see also 1) and 3) ) 5) search/filter functionality (SQL2, JQOM?) 6) nt:file - file upload 7) import/export subtrees, format to be defined 8) input validation 9) ajax'ify the client 10) usermanagement more to come... WDYT? Anything important/fancy missing? How would you priorize these features?
[jira] Updated: (SLING-1650) Move commons auth to another location
[ https://issues.apache.org/jira/browse/SLING-1650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger updated SLING-1650: - Summary: Move commons auth to another location (was: Move commons auth to extensions) Description: As the commons auth uses the Sling API it is by definition no commons module :) Therefore it should be moved to some other location e.g. bundles/extensions or a new location bundles/auth where also the OpenID and Form authentication handlers could be moved to keep them together. was: As the commons auth uses the Sling API it is by definition no commons module :) Therefore it should be moved to the extensions part Component/s: (was: Extensions) Move commons auth to another location - Key: SLING-1650 URL: https://issues.apache.org/jira/browse/SLING-1650 Project: Sling Issue Type: Task Components: Commons Affects Versions: Commons Auth 1.0.0 Reporter: Carsten Ziegeler Assignee: Felix Meschberger Fix For: Commons Auth 1.0.0 As the commons auth uses the Sling API it is by definition no commons module :) Therefore it should be moved to some other location e.g. bundles/extensions or a new location bundles/auth where also the OpenID and Form authentication handlers could be moved to keep them together. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Moving the Commons Auth Bundle
Hi all, We are in the end game of releasing the Sling Authenticator Bundle (aka Commons Auth). Carsten an I have been discussing about this bundle and are considering moving this bundle out of the commons area. The reason for this is, that the commons area has once been designated to be a location with usefull helper stuff but with not API dependency to Sling. Since we moved part of Commons Auth to the API, this does not hold any longer for the Commons Auth bundle. As a consequence, we would have to rename the packages from o.a.s.commons.auth to o.a.s.auth (probably). This is mainly an issue because the exported packages ...auth and ...auth.spi are being used elsewhere (e.g. for implementing authentication handlers). I suggest we create a new location bundles/auth where we move the Authenticator bundle along with the OpenID and Form authentication handlers (currently below bundles/extensions). As a consequence the API packages o.a.s.commons.auth and o.a.s.commons.auth.spi would be renamed to o.a.s.auth and o.a.s.auth.spi, resp. Moving the bundle is tracked in SLING-1650. WDYT ? Regards Felix [1] https://issues.apache.org/jira/browse/SLING-1650
Re: Moving the Commons Auth Bundle
+1 to moving auth out of commons and moving the other auth bundles to bundles/auth. Not loving the package change, but I agree it is a good idea and better to be done now than later. On Aug 13, 2010, at 10:01 AM, Felix Meschberger fmesc...@gmail.com wrote: Hi all, We are in the end game of releasing the Sling Authenticator Bundle (aka Commons Auth). Carsten an I have been discussing about this bundle and are considering moving this bundle out of the commons area. The reason for this is, that the commons area has once been designated to be a location with usefull helper stuff but with not API dependency to Sling. Since we moved part of Commons Auth to the API, this does not hold any longer for the Commons Auth bundle. As a consequence, we would have to rename the packages from o.a.s.commons.auth to o.a.s.auth (probably). This is mainly an issue because the exported packages ...auth and ...auth.spi are being used elsewhere (e.g. for implementing authentication handlers). I suggest we create a new location bundles/auth where we move the Authenticator bundle along with the OpenID and Form authentication handlers (currently below bundles/extensions). As a consequence the API packages o.a.s.commons.auth and o.a.s.commons.auth.spi would be renamed to o.a.s.auth and o.a.s.auth.spi, resp. Moving the bundle is tracked in SLING-1650. WDYT ? Regards Felix [1] https://issues.apache.org/jira/browse/SLING-1650
[jira] Resolved: (SLING-1652) Upgrade Felix Framework to latest release
[ https://issues.apache.org/jira/browse/SLING-1652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger resolved SLING-1652. -- Resolution: Fixed Done in Rev. 985208 Upgrade Felix Framework to latest release - Key: SLING-1652 URL: https://issues.apache.org/jira/browse/SLING-1652 Project: Sling Issue Type: Task Components: Launchpad Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: Launchpad Base 2.2.2 Richard Hall hall published a 3.1.0-SNAPSHOT release to give the framework exposure before the 3.0.2 release to come in the short time frame. The Base module should be upgraded to this snapshot to test the snapshot and as soon as 3.0.2 is released, upgrade to that release. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-1652) Upgrade Felix Framework to latest release
Upgrade Felix Framework to latest release - Key: SLING-1652 URL: https://issues.apache.org/jira/browse/SLING-1652 Project: Sling Issue Type: Task Components: Launchpad Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: Launchpad Base 2.2.2 Richard Hall hall published a 3.1.0-SNAPSHOT release to give the framework exposure before the 3.0.2 release to come in the short time frame. The Base module should be upgraded to this snapshot to test the snapshot and as soon as 3.0.2 is released, upgrade to that release. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Reopened: (SLING-1652) Upgrade Felix Framework to latest release
[ https://issues.apache.org/jira/browse/SLING-1652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger reopened SLING-1652: -- Reopen. This issue should only be resolved when the final version is actually referred to Upgrade Felix Framework to latest release - Key: SLING-1652 URL: https://issues.apache.org/jira/browse/SLING-1652 Project: Sling Issue Type: Task Components: Launchpad Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: Launchpad Base 2.2.2 Richard Hall hall published a 3.1.0-SNAPSHOT release to give the framework exposure before the 3.0.2 release to come in the short time frame. The Base module should be upgraded to this snapshot to test the snapshot and as soon as 3.0.2 is released, upgrade to that release. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (SLING-1652) Upgrade Felix Framework to latest release
[ https://issues.apache.org/jira/browse/SLING-1652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12898252#action_12898252 ] Felix Meschberger edited comment on SLING-1652 at 8/13/10 10:36 AM: Upgraded to 3.1.0-SNAPSHOT in in Rev. 985208 was (Author: fmeschbe): Done in Rev. 985208 Upgrade Felix Framework to latest release - Key: SLING-1652 URL: https://issues.apache.org/jira/browse/SLING-1652 Project: Sling Issue Type: Task Components: Launchpad Reporter: Felix Meschberger Assignee: Felix Meschberger Fix For: Launchpad Base 2.2.2 Richard Hall hall published a 3.1.0-SNAPSHOT release to give the framework exposure before the 3.0.2 release to come in the short time frame. The Base module should be upgraded to this snapshot to test the snapshot and as soon as 3.0.2 is released, upgrade to that release. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Preparing for a 3.0.2 release of framework
Hi all, I have updated Sling Launchpad base to this SNAPSHOT version in anticipation of this release and to give it some exposure. Please report any problems you might run into. Thanks. Regards Felix On 13.08.2010 16:23, Richard S. Hall wrote: We're going to do a 3.0.2 release of the framework, since we have a fair number of reasonably minor, but worthwhile changes in trunk. The biggest change is in some locking code around our installed bundle data structures, which was done to try to resolve FELIX-2437. I've published snapshot (including the framework distro), so go ahead and play with it. Thanks. - richard
[HEADSUP] Sling API 2.1 Release
Hi all, Looking at [1] there are no more open issues for the Sling API. I have published a mvn site run to my people folder [2]. So please quickly check this and your portfolios for any missing links. If I hear nothing to the contrary I will cut the release on Monday. Regards Felix [1] https://issues.apache.org/jira/browse/SLING/fixforversion/12314252 [2] http://people.apache.org/~fmeschbe/sling6/api/
[jira] Updated: (SLING-1513) allow host-specific rendering for virtual hosts. Multitenancy Support
[ https://issues.apache.org/jira/browse/SLING-1513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-1513: Component/s: API allow host-specific rendering for virtual hosts. Multitenancy Support --- Key: SLING-1513 URL: https://issues.apache.org/jira/browse/SLING-1513 Project: Sling Issue Type: New Feature Components: API Reporter: Markus Blaurock Currently we have the need to run multiple websites on the same sling-instance. That is, serving the same or similar content in different ways (layouts), defined by the hostname. Reason behind this is we would like to have a single pool of sling-app-servers and each one should be possible to serve all websites. Otherwise we would need to have one pool for each (small) site, which is not feasible. e.g. Content a/b/c should be accessible with http://www.one/a/b/c.html and http://www.two/a/b/c.html and looking differently. https://cwiki.apache.org/SLING/multitenancy-support.html would solve the problem easily. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-1648) Node move with :replace fails
[ https://issues.apache.org/jira/browse/SLING-1648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-1648: Affects Version/s: Servlets Post 2.0.4 Component/s: Servlets Node move with :replace fails - Key: SLING-1648 URL: https://issues.apache.org/jira/browse/SLING-1648 Project: Sling Issue Type: Bug Components: Servlets Affects Versions: Servlets Post 2.0.4 Reporter: daniel parry Following docs at http://sling.apache.org/site/manipulating-content-the-slingpostservlet-servletspost.html In trunk, Revision: 984520, steps to reproduce error: curl -uadmin:admin -Ftitle=test -Ftext=test http://localhost:8080/test1 curl -uadmin:admin -Ftitle=test -Ftext=test http://localhost:8080/test2 curl -uadmin:admin -F:operation=move -F:dest=/test2 http://localhost:8080/test1 (Not allowed to move without :replace as expected) curl -uadmin:admin -F:operation=move -F:replace=true -F:dest=/test2 http://localhost:8080/test1 (This should work with :replace specified) However, error encountered: html head titleError while processing /test1/title /head body h1Error while processing /test1/h1 table tbody tr tdStatus/td tddiv id=Status500/div/td /tr tr tdMessage/td tddiv id=Messagejavax.jcr.PathNotFoundException: /test2/div/td /tr tr tdLocation/td tda href=/test1 id=Location/test1/a/td /tr tr tdParent Location/td tda href=/ id=ParentLocation//a/td /tr tr tdPath/td tddiv id=Path/test1/div/td /tr tr tdReferer/td tda href= id=Referer/a/td /tr tr tdChangeLog/td tddiv id=ChangeLogpre/pre/div/td /tr /tbody /table pa href=Go Back/a/p pa href=/test1Modified Resource/a/p pa href=/Parent of Modified Resource/a/p /body /html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SLING-1488) Move EventHelper from JCRInstall to Commons Testing
[ https://issues.apache.org/jira/browse/SLING-1488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-1488. - Resolution: Fixed Removed class from jcr install in revision 985245 Move EventHelper from JCRInstall to Commons Testing --- Key: SLING-1488 URL: https://issues.apache.org/jira/browse/SLING-1488 Project: Sling Issue Type: Improvement Components: Commons, Installer Reporter: Justin Edelson Assignee: Justin Edelson Priority: Minor Fix For: JCR Installer 3.0.0, Commons Testing 2.0.6 Original Estimate: 0h Remaining Estimate: 0h There's an EventHelper class in JCRInstall's test directory which is of general use. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SLING-1295) JcrInstall should only observe configured folders
[ https://issues.apache.org/jira/browse/SLING-1295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-1295. - Resolution: Invalid This issue is invalid JcrInstall should only observe configured folders - Key: SLING-1295 URL: https://issues.apache.org/jira/browse/SLING-1295 Project: Sling Issue Type: Improvement Components: Installer Reporter: Carsten Ziegeler Currently jcr install listens for all modifications in the repository - however only changes to the configured locations are of interest, therefore jcr install should register more specific listeners for the various configured paths. This can be done by registering event listener proxy that all forward the events to a single listener -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-1438) GSoC 2010: create a mini-CMS to demonstrate Sling
[ https://issues.apache.org/jira/browse/SLING-1438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Federico Paparoni updated SLING-1438: - Attachment: david.rar Submit of David Mini CMS. GSoC 2010: create a mini-CMS to demonstrate Sling - Key: SLING-1438 URL: https://issues.apache.org/jira/browse/SLING-1438 Project: Sling Issue Type: Task Components: Documentation Reporter: Bertrand Delacretaz Assignee: Federico Paparoni Attachments: david.rar This is a suggested project for Google Summer of Code 2010. The goal is to create a mini-CMS with Sling, that demonstrates Sling best practices. The emphasis is on the quality and readability of the demo code, and we expect to have to go through several iterations to refine it and the corresponding JCR content model so that they demonstrate Sling best practices. We will not necessarily create a full-fledged CMS, the goal is for the result to be educational and help Sling newcomers understand how to create web applications with it. Suggested technologies: jQuery for the front-end, ESP and/or JSP for server-side scripting, and Java code in OSGi bundles for back-end functionality. See http://tinyurl.com/asfgsoc for the full list of GSoC 2010 projects at the ASF, and http://community.apache.org/gsoc for general GSoC information. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
where is the esp-syntax described?
e.g. is there an else if or elsif? How about a switch/case? Thx
Re: where is the esp-syntax described?
ESP is Embedded ECMAScript (Javascript). Inside % and % you can use any ECMAScript statement you want, including if, else if, switch and case. Lars On Fri, Aug 13, 2010 at 11:59 AM, Clemens Wyss clemens...@mysign.ch wrote: e.g. is there an else if or elsif? How about a switch/case? Thx -- Lars Trieloff - http://lars.mp - Day Software - http://www.day.com
[jira] Updated: (SLING-1653) Donation of enhanced explorer
[ https://issues.apache.org/jira/browse/SLING-1653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Moulton updated SLING-1653: Attachment: sling-explorer.tar.gz Donation of enhanced explorer - Key: SLING-1653 URL: https://issues.apache.org/jira/browse/SLING-1653 Project: Sling Issue Type: Improvement Reporter: Mike Moulton Attachments: sling-explorer.tar.gz I was reading the recent thread [1] about extending the current explorer stubs available in the contrib. section. A while back when I was first learning Sling I extended what was the existing explorer at the time to teach myself the inner workings of Sling. The project was never complete, however a decent amount of work was done to produce a complete explorer. Given the conversation and the renewed interest in development, I wanted to offer up my explorer to Sling. I'm not sure if this version is a better starting point to accomplish Clemens goals, but if so, you are welcome to build off it. Most of the code is my own, however their are some third party libraries that are used. It looks like they all have ASF friendly licensing, however this is obviously something that will need to be investigated. To use this explorer you can build the bundle, then install it. The explorer will then be available at .explorer.html e.g., http://localhost:8080/.explorer.html [1] http://apache-sling.73963.n3.nabble.com/VOTE-Grant-Jean-Christophe-write-access-to-the-docs-was-Re-Scheduler-service-problem-tp1028822p405.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-1653) Donation of enhanced explorer
Donation of enhanced explorer - Key: SLING-1653 URL: https://issues.apache.org/jira/browse/SLING-1653 Project: Sling Issue Type: Improvement Reporter: Mike Moulton I was reading the recent thread [1] about extending the current explorer stubs available in the contrib. section. A while back when I was first learning Sling I extended what was the existing explorer at the time to teach myself the inner workings of Sling. The project was never complete, however a decent amount of work was done to produce a complete explorer. Given the conversation and the renewed interest in development, I wanted to offer up my explorer to Sling. I'm not sure if this version is a better starting point to accomplish Clemens goals, but if so, you are welcome to build off it. Most of the code is my own, however their are some third party libraries that are used. It looks like they all have ASF friendly licensing, however this is obviously something that will need to be investigated. To use this explorer you can build the bundle, then install it. The explorer will then be available at .explorer.html e.g., http://localhost:8080/.explorer.html [1] http://apache-sling.73963.n3.nabble.com/VOTE-Grant-Jean-Christophe-write-access-to-the-docs-was-Re-Scheduler-service-problem-tp1028822p405.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: extending jQuery JCR Resource explorer
I'm a little late to this thread but I wanted to bring this up anyway. A while back when I first was learning Sling I created an extended explorer based on the original version in the contrib. section. My explorer uses jQuery and accomplished most of the items of the current jQuery explorer. Before an extended set of work started on enhancements I wanted to donate this codebase in case it's of any use in this effort. I would love to see a mature explorer ship as a part of Sling, and any work I can do to help that, I will do. I created SLING-1653 [1] with the codebase in it. [1] https://issues.apache.org/jira/browse/SLING-1653 On Aug 13, 2010, at 9:21 AM, Bertrand Delacretaz wrote: On Thu, Aug 12, 2010 at 4:26 PM, Clemens Wyss clemens...@mysign.ch wrote: ...Anything important/fancy missing? How would you priorize these features?.. A nice thing would be to use the Sling script resolution to plugin custom content editors based on resource types. Maybe just use .explorer.edit selectors to generate a composite UI where users can plugin their own editing components, and define a simple set of guidelines/constraints that those components must follow. -Bertrand
RE: extending jQuery JCR Resource explorer
Hi Mike, cool. If you don't mind, I will take your code base and build upon this Thx Clemens -Original Message- From: Mike Moulton [mailto:m...@meltmedia.com] Sent: Saturday, August 14, 2010 12:00 AM To: dev@sling.apache.org Subject: Re: extending jQuery JCR Resource explorer I'm a little late to this thread but I wanted to bring this up anyway. A while back when I first was learning Sling I created an extended explorer based on the original version in the contrib. section. My explorer uses jQuery and accomplished most of the items of the current jQuery explorer. Before an extended set of work started on enhancements I wanted to donate this codebase in case it's of any use in this effort. I would love to see a mature explorer ship as a part of Sling, and any work I can do to help that, I will do. I created SLING-1653 [1] with the codebase in it. [1] https://issues.apache.org/jira/browse/SLING-1653 On Aug 13, 2010, at 9:21 AM, Bertrand Delacretaz wrote: On Thu, Aug 12, 2010 at 4:26 PM, Clemens Wyss clemens...@mysign.ch wrote: ...Anything important/fancy missing? How would you priorize these features?.. A nice thing would be to use the Sling script resolution to plugin custom content editors based on resource types. Maybe just use .explorer.edit selectors to generate a composite UI where users can plugin their own editing components, and define a simple set of guidelines/constraints that those components must follow. -Bertrand
RE: extending jQuery JCR Resource explorer
I had a first look at your explorer. If I get this right: + new, more appealing, GUI + new js-tree + properties are no more being edited inline, which makes sense + privileges, minimal did I miss a hidden feature? -Original Message- From: Clemens Wyss [mailto:clemens...@mysign.ch] Sent: Saturday, August 14, 2010 7:20 AM To: 'dev@sling.apache.org' Subject: RE: extending jQuery JCR Resource explorer Hi Mike, cool. If you don't mind, I will take your code base and build upon this Thx Clemens -Original Message- From: Mike Moulton [mailto:m...@meltmedia.com] Sent: Saturday, August 14, 2010 12:00 AM To: dev@sling.apache.org Subject: Re: extending jQuery JCR Resource explorer I'm a little late to this thread but I wanted to bring this up anyway. A while back when I first was learning Sling I created an extended explorer based on the original version in the contrib. section. My explorer uses jQuery and accomplished most of the items of the current jQuery explorer. Before an extended set of work started on enhancements I wanted to donate this codebase in case it's of any use in this effort. I would love to see a mature explorer ship as a part of Sling, and any work I can do to help that, I will do. I created SLING-1653 [1] with the codebase in it. [1] https://issues.apache.org/jira/browse/SLING-1653 On Aug 13, 2010, at 9:21 AM, Bertrand Delacretaz wrote: On Thu, Aug 12, 2010 at 4:26 PM, Clemens Wyss clemens...@mysign.ch wrote: ...Anything important/fancy missing? How would you priorize these features?.. A nice thing would be to use the Sling script resolution to plugin custom content editors based on resource types. Maybe just use .explorer.edit selectors to generate a composite UI where users can plugin their own editing components, and define a simple set of guidelines/constraints that those components must follow. -Bertrand
RE: extending jQuery JCR Resource explorer
A nice thing would be to use the Sling script resolution to plugin custom content editors based on resource types. sounds interesting -Original Message- From: Bertrand Delacretaz [mailto:bdelacre...@apache.org] Sent: Friday, August 13, 2010 6:22 PM To: dev@sling.apache.org Subject: Re: extending jQuery JCR Resource explorer On Thu, Aug 12, 2010 at 4:26 PM, Clemens Wyss clemens...@mysign.ch wrote: ...Anything important/fancy missing? How would you priorize these features?.. A nice thing would be to use the Sling script resolution to plugin custom content editors based on resource types. Maybe just use .explorer.edit selectors to generate a composite UI where users can plugin their own editing components, and define a simple set of guidelines/constraints that those components must follow. -Bertrand
