+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 if some script not secure enough some cases can access another user's nodes for example ), and I think the performance also can be better (maybe I'm not right but as I know the Path filtering differs from another's property - and the path filtering is a performance bottleneck of jackrabbit). I prefer that the scripts uses same repository as resources - in some situation this feature can be very usefull.
Regards, Robert On Mar 17, 2010, at 2:20 PM, Bertrand Delacretaz wrote: > On Wed, Mar 17, 2010 at 2:08 PM, Justin Edelson <[email protected]> > 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 >> header to select the workspace which corresponds to the requested >> version (and according to David's Model, this is a totally valid use of >> workspaces).... > > I like the idea of using an HTTP header to select workspaces - and the > name of the "default scripts" workspace to use might be stored as a > property at the root node of the "private" workspace, or defined by > configuration of the script resource resolver. > > -Bertrand
