Re: multi-workspace support in script resolution

2010-03-17 Thread Bertrand Delacretaz
Hi, On Wed, Mar 17, 2010 at 2:45 AM, Justin Edelson justinedel...@gmail.com wrote: Currently, although it's possible to log into different workspaces via AuthenticationInfo (even if httpauth and formauth don't support this); script resolution only happens against the default workspace. I don't

Re: multi-workspace support in script resolution

2010-03-17 Thread Carsten Ziegeler
Bertrand Delacretaz wrote Hi, On Wed, Mar 17, 2010 at 2:45 AM, Justin Edelson justinedel...@gmail.com wrote: Currently, although it's possible to log into different workspaces via AuthenticationInfo (even if httpauth and formauth don't support this); script resolution only happens

Re: multi-workspace support in script resolution

2010-03-17 Thread Bertrand Delacretaz
Hi, On Wed, Mar 17, 2010 at 9:41 AM, Carsten Ziegeler cziege...@apache.org wrote: ...In general I am not sure if it should be the authentication which defines what workspace is used. I rather could picture having a resource tree where workspaces are mounted at different locations in the tree.

Re: multi-workspace support in script resolution

2010-03-17 Thread Carsten Ziegeler
Bertrand Delacretaz wrote Hi, On Wed, Mar 17, 2010 at 9:41 AM, Carsten Ziegeler cziege...@apache.org wrote: ...In general I am not sure if it should be the authentication which defines what workspace is used. I rather could picture having a resource tree where workspaces are mounted at

Re: multi-workspace support in script resolution

2010-03-17 Thread Alexander Klimetschek
The question for one workspace per account / user / etc. pops up every now and then on the jackrabbit mailing lists and the general answer is to try to stay away from that as it just complicates things: why having to work with multiple workspaces when you can just create separate nodes? Workspaces

Re: multi-workspace support in script resolution

2010-03-17 Thread Carsten Ziegeler
Alexander Klimetschek wrote The question for one workspace per account / user / etc. pops up every now and then on the jackrabbit mailing lists and the general answer is to try to stay away from that as it just complicates things: why having to work with multiple workspaces when you can just

Re: multi-workspace support in script resolution

2010-03-17 Thread Justin Edelson
On 3/17/10 4:31 AM, Bertrand Delacretaz wrote: Hi, On Wed, Mar 17, 2010 at 2:45 AM, Justin Edelson justinedel...@gmail.com wrote: Currently, although it's possible to log into different workspaces via AuthenticationInfo (even if httpauth and formauth don't support this); script resolution

Re: multi-workspace support in script resolution

2010-03-17 Thread Bertrand Delacretaz
Hi, On Wed, Mar 17, 2010 at 1:55 PM, Justin Edelson justinedel...@gmail.com wrote: On 3/17/10 4:31 AM, Bertrand Delacretaz wrote: ...Assuming you use workspaces for multi-homed websites, one could imagine having a generic scripts workspace where the script resolution would look after looking

Re: multi-workspace support in script resolution

2010-03-17 Thread Justin Edelson
On 3/17/10 4:41 AM, Carsten Ziegeler wrote: I'm not sure what the best way is, but Sling is resource tree based. The resource resolver (factory) gets configured with resource search paths (/apps and /libs is default) for scripts. The script resolver uses these paths to search for scripts. The

Re: multi-workspace support in script resolution

2010-03-17 Thread Justin Edelson
On 3/17/10 7:05 AM, Alexander Klimetschek wrote: The question for one workspace per account / user / etc. pops up every now and then on the jackrabbit mailing lists and the general answer is to try to stay away from that as it just complicates things: why having to work with multiple

Re: multi-workspace support in script resolution

2010-03-17 Thread Bertrand Delacretaz
On Wed, Mar 17, 2010 at 2:08 PM, Justin Edelson justinedel...@gmail.com wrote: ... For example, if you think about how Google App Engine allows you to reference arbitrary versions of your application with a host name like version.appname.appspot.com (IIRC), one could imagine using the host

Re: multi-workspace support in script resolution

2010-03-17 Thread Justin Edelson
On 3/17/10 9:20 AM, Bertrand Delacretaz wrote: On Wed, Mar 17, 2010 at 2:08 PM, Justin Edelson justinedel...@gmail.com wrote: ... For example, if you think about how Google App Engine allows you to reference arbitrary versions of your application with a host name like

Re: multi-workspace support in script resolution

2010-03-17 Thread Felix Meschberger
Hi, On 17.03.2010 14:40, Justin Edelson wrote: On 3/17/10 9:20 AM, Bertrand Delacretaz wrote: On Wed, Mar 17, 2010 at 2:08 PM, Justin Edelson justinedel...@gmail.com wrote: ... For example, if you think about how Google App Engine allows you to reference arbitrary versions of your

Re: multi-workspace support in script resolution

2010-03-17 Thread Felix Meschberger
Hi, On 17.03.2010 02:45, Justin Edelson wrote: Currently, although it's possible to log into different workspaces via AuthenticationInfo (even if httpauth and formauth don't support this); script resolution only happens against the default workspace. I don't see any reason for this

Re: multi-workspace support in script resolution

2010-03-17 Thread Justin Edelson
On 3/17/10 9:49 AM, Felix Meschberger wrote: public class WorkspacePicker implements AuthenticationInfoPostProcessor { public void postProcess(AuthenticationInfo info, HttpServletRequest request, HttpServletResponse response) { String host = request.getHeader(Host); (NB this is

Re: multi-workspace support in script resolution

2010-03-17 Thread Felix Meschberger
Hi, On 17.03.2010 15:09, Justin Edelson wrote: On 3/17/10 9:49 AM, Felix Meschberger wrote: String host = request.getHeader(Host); (NB this is what request.getServerName() reports; I would prefer to use the API) (I seem to recall running into trouble with request.getServerName() and

Re: multi-workspace support in script resolution

2010-03-17 Thread Csákány Róbert
+1 I was in same situation - I can resolve that problem the resource will be selected as virtual domain, but for me it's little problematic that the scripts comes from default repository. (For security and versioning reasons sometimes some domain's repository better if separeted - for example

Re: multi-workspace support in script resolution

2010-03-17 Thread Justin Edelson
On 3/17/10 10:16 AM, Felix Meschberger wrote: Hi, On 17.03.2010 15:09, Justin Edelson wrote: On 3/17/10 9:49 AM, Felix Meschberger wrote: String host = request.getHeader(Host); (NB this is what request.getServerName() reports; I would prefer to use the API) (I seem to recall

Re: multi-workspace support in script resolution

2010-03-17 Thread Felix Meschberger
Hi, On 17.03.2010 15:27, Justin Edelson wrote: On 3/17/10 10:16 AM, Felix Meschberger wrote: Hi, On 17.03.2010 15:09, Justin Edelson wrote: On 3/17/10 9:49 AM, Felix Meschberger wrote: String host = request.getHeader(Host); (NB this is what request.getServerName() reports; I would

Re: multi-workspace support in script resolution

2010-03-17 Thread Justin Edelson
On 3/17/10 10:35 AM, Felix Meschberger wrote: Strange. This hints at a servlet container issue, because the getServerName method is defined to: Definitely possible. The app server was built pre-J2EE and plenty quirky. It's since been discontinued. Like I said, possible this was to workaround an

Re: multi-workspace support in script resolution

2010-03-17 Thread Justin Edelson
Felix- I know this probably isn't a great answer, but I think we just have to start somewhere. If the answer is that this should happen in a branch, I'm fine with that, but I personally don't think it's necessary - any change along these lines should be able to be fully backwards compatible. Two

Re: multi-workspace support in script resolution

2010-03-17 Thread Felix Meschberger
Hi, On 17.03.2010 15:46, Justin Edelson wrote: Felix- I know this probably isn't a great answer, but I think we just have to start somewhere. If the answer is that this should happen in a branch, I'm fine with that, but I personally don't think it's necessary - any change along these lines

[jira] Created: (SLING-1446) Scripts should be resolved against the current workspace

2010-03-17 Thread Justin Edelson (JIRA)
Scripts should be resolved against the current workspace Key: SLING-1446 URL: https://issues.apache.org/jira/browse/SLING-1446 Project: Sling Issue Type: Improvement

Re: multi-workspace support in script resolution

2010-03-17 Thread Justin Edelson
On 3/17/10 10:50 AM, Felix Meschberger wrote: Hi, On 17.03.2010 15:46, Justin Edelson wrote: Felix- I know this probably isn't a great answer, but I think we just have to start somewhere. If the answer is that this should happen in a branch, I'm fine with that, but I personally don't think

[jira] Created: (SLING-1447) jcr resource events are only created for the default workspace

2010-03-17 Thread Justin Edelson (JIRA)
jcr resource events are only created for the default workspace -- Key: SLING-1447 URL: https://issues.apache.org/jira/browse/SLING-1447 Project: Sling Issue Type: Improvement

[jira] Created: (SLING-1448) Sling-Initial-Content should be able to load content into non-default workspace

2010-03-17 Thread Justin Edelson (JIRA)
Sling-Initial-Content should be able to load content into non-default workspace --- Key: SLING-1448 URL: https://issues.apache.org/jira/browse/SLING-1448 Project: Sling

Re: multi-workspace support in script resolution

2010-03-17 Thread Carsten Ziegeler
Carsten Ziegeler wrote I still have the feeling that mounting other workspaces into the resource tree is the easier way. With that we wouldn't need to change content loading, resource events and maybe other things to come? Can we go a step back please and see what use cases we really have?

Re: AccessControlUtil.replaceAccessControlEntry

2010-03-17 Thread Ray Davis
On 3/17/10 5:27 AM, Ian Boston wrote: I just noticed that AccessControlUtil.replaceAccessControlEntry searches for a match on ACE within an ACL using the principal only. (and not the grant or deny as well) So if there was a grant acl and the replacement is a deny, then the grant is removed,

Re: multi-workspace support in script resolution

2010-03-17 Thread Justin Edelson
On 3/17/10 11:03 AM, Carsten Ziegeler wrote: I still have the feeling that mounting other workspaces into the resource tree is the easier way. With that we wouldn't need to change content loading, resource events and maybe other things to come? Can we go a step back please and see what use

Re: multi-workspace support in script resolution

2010-03-17 Thread Carsten Ziegeler
Carsten Ziegeler wrote Carsten Ziegeler wrote I still have the feeling that mounting other workspaces into the resource tree is the easier way. With that we wouldn't need to change content loading, resource events and maybe other things to come? Can we go a step back please and see what

Re: multi-workspace support in script resolution

2010-03-17 Thread Alexander Klimetschek
On Wed, Mar 17, 2010 at 16:07, Carsten Ziegeler cziege...@apache.org wrote: Carsten Ziegeler  wrote I still have the feeling that mounting other workspaces into the resource tree is the easier way. With that we wouldn't need to change content loading, resource events and maybe other things to

Build failed in Hudson: sling-contrib-1.5 » Apache Sling Launchpad Contrib Testing #410

2010-03-17 Thread Apache Hudson Server
See http://hudson.zones.apache.org/hudson/job/sling-contrib-1.5/org.apache.sling$org.apache.sling.launchpad.contrib-testing/410/ -- [...truncated 3480 lines...] br/ br/

Build failed in Hudson: sling-contrib-1.5 #410

2010-03-17 Thread Apache Hudson Server
See http://hudson.zones.apache.org/hudson/job/sling-contrib-1.5/410/ -- [...truncated 7060 lines...] br/ br/ /body /html ]

[jira] Created: (SLING-1449) jcr.jackrabbit-server is missing DynamicImport-Package

2010-03-17 Thread Justin Edelson (JIRA)
jcr.jackrabbit-server is missing DynamicImport-Package -- Key: SLING-1449 URL: https://issues.apache.org/jira/browse/SLING-1449 Project: Sling Issue Type: Bug Reporter: Justin

[jira] Updated: (SLING-1449) jcr.jackrabbit-server is missing DynamicImport-Package

2010-03-17 Thread Justin Edelson (JIRA)
[ https://issues.apache.org/jira/browse/SLING-1449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson updated SLING-1449: -- Component/s: JCR Fix Version/s: JCR Jackrabbit Server 2.0.8 jcr.jackrabbit-server is

[jira] Resolved: (SLING-1449) jcr.jackrabbit-server is missing DynamicImport-Package

2010-03-17 Thread Justin Edelson (JIRA)
[ https://issues.apache.org/jira/browse/SLING-1449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson resolved SLING-1449. --- Resolution: Fixed jcr.jackrabbit-server is missing DynamicImport-Package

Build failed in Hudson: sling-contrib-1.5 » Apache Sling Launchpad Contrib Testing #411

2010-03-17 Thread Apache Hudson Server
See http://hudson.zones.apache.org/hudson/job/sling-contrib-1.5/org.apache.sling$org.apache.sling.launchpad.contrib-testing/411/ -- [...truncated 3449 lines...] br/ br/

Re: AccessControlUtil.replaceAccessControlEntry

2010-03-17 Thread Eric Norman
Hi Ian, I am having trouble reproducing what you have described. I added a new unit test in r924618 to test the scenario you described and it appears to work correctly for me. Can you check the new unit test to see if there are some extra steps in your use case that I am missing? Regards,

Build failed in Hudson: sling-contrib-1.5 » Apache Sling Launchpad Contrib Testing #412

2010-03-17 Thread Apache Hudson Server
See http://hudson.zones.apache.org/hudson/job/sling-contrib-1.5/org.apache.sling$org.apache.sling.launchpad.contrib-testing/412/ -- [...truncated 3457 lines...] br/ br/

Build failed in Hudson: sling-contrib-1.5 #412

2010-03-17 Thread Apache Hudson Server
See http://hudson.zones.apache.org/hudson/job/sling-contrib-1.5/412/ -- [...truncated 7020 lines...] br/ br/ br/