Re: [VOTE] Moving SLING-2396 to trunk

2012-07-06 Thread Carsten Ziegeler
Coming back to the workspace support, which part do you think should be available? Specifying the workspace through a request attribute or as a value inside the authentication map? Regards Carsten 2012/6/14 Carsten Ziegeler cziege...@apache.org: Hi Justin, no, it isn't, I removed the whole

Re: [VOTE] Moving SLING-2396 to trunk

2012-06-18 Thread Pontus Amberg
Should the relativePath of parent really be ../../../parent/pom.xml ? Shouldn't it be ../../parent/pom.xml ? /Pontus On 2012-06-14 13:01, Carsten Ziegeler wrote: Thanks everyone - I've committed all the changes to trunk. So far noone complaint about missing workspace support... :) Regards

Re: [VOTE] Moving SLING-2396 to trunk

2012-06-15 Thread Felix Meschberger
Hi, Am 14.06.2012 um 08:13 schrieb Carsten Ziegeler: Hi Justin, no, it isn't, I removed the whole workspace support. But this could be re-added if required. We should maybe have an issue to track this. IIRC support for logging into a non-default workspace for a request is trivial.

Re: [VOTE] Moving SLING-2396 to trunk

2012-06-14 Thread Carsten Ziegeler
Thanks everyone - I've committed all the changes to trunk. So far noone complaint about missing workspace support... :) Regards Carsten 2012/6/12 Ian Boston i...@tfd.co.uk: Hi, Not using workspaces to any great extent I have to be +1 on this as it makes integration of other sources possible

Re: [VOTE] Moving SLING-2396 to trunk

2012-06-14 Thread Justin Edelson
Hi Carsten, I did not have a chance to review the code - been a busy week. One question - is the ability to select a non-default workspace on login still present? Justin On Jun 14, 2012, at 7:01 AM, Carsten Ziegeler cziege...@apache.org wrote: Thanks everyone - I've committed all the changes

Re: [VOTE] Moving SLING-2396 to trunk

2012-06-14 Thread Carsten Ziegeler
Hi Justin, no, it isn't, I removed the whole workspace support. But this could be re-added if required. However resources would not have the workspace name prefixed in the path anymore. Regards Carsten 2012/6/14 Justin Edelson justinedel...@gmail.com: Hi Carsten, I did not have a chance to

Re: [VOTE] Moving SLING-2396 to trunk

2012-06-12 Thread Carsten Ziegeler
] Moving SLING-2396 to trunk Hi, I really would like to move forward with SLING-2396 (Make ResourceResolverFactory independent from JCR) in order to implement other features (like CRUD support for the resource resolver) on top of this. Unfortunately this change introduces an incompatibility wrt

Re: [VOTE] Moving SLING-2396 to trunk

2012-06-12 Thread Vidar Ramdal
2012/6/10 Carsten Ziegeler cziege...@apache.org: I really would like to move forward with SLING-2396 (Make ResourceResolverFactory independent from JCR) in order to implement other features (like CRUD support for the resource resolver) on top of this. Unfortunately this change introduces an

Re: [VOTE] Moving SLING-2396 to trunk

2012-06-12 Thread Ian Boston
Hi, Not using workspaces to any great extent I have to be +1 on this as it makes integration of other sources possible without changes to the core Jackrabbit bundle, however I would like to hear how disruptive it really is for those using workspaces in a more traditional content management mode.

RE: [VOTE] Moving SLING-2396 to trunk

2012-06-11 Thread Mike Müller
- From: Carsten Ziegeler [mailto:cziege...@apache.org] Sent: Sunday, June 10, 2012 5:19 PM To: dev@sling.apache.org Subject: [VOTE] Moving SLING-2396 to trunk Hi, I really would like to move forward with SLING-2396 (Make ResourceResolverFactory independent from JCR) in order to implement

[VOTE] Moving SLING-2396 to trunk

2012-06-10 Thread Carsten Ziegeler
Hi, I really would like to move forward with SLING-2396 (Make ResourceResolverFactory independent from JCR) in order to implement other features (like CRUD support for the resource resolver) on top of this. Unfortunately this change introduces an incompatibility wrt workspaces, therefore I