Proposal sounds good to me. I would agree to move this to a plugin that gets
the accept header (is there anything else?) and can update any existing
selectors/extension/suffix (the PathInfo) parsed already.
void updatePathInfo(String[] accepts, PathInfo pathInfo);
Notes:
- accept header alr
On 02.04.2014, at 05:51, Justin Edelson wrote:
> Hi Carsten,
> Just curious - why do you prefer to remove the context path from the
> *result* of ResourceResolver.map() rather than removing it from the
> path passed *to* ResourceResolver.map()?
>
> Since ResourceResolver.map() does a resolve() c
If I read the javadoc for HttpServletResponse.encodeURL() [1] correctly, all it
does is to add the Java servlet Session ID. It isn't even supposed to encode
anything on the string level - "encode" seems to be used as a term for "include
session id" here.
OTOH, this discussion [2] - or better t
IIUC, a deep read is now done generically by fetching sub resources first and
each value map will from now on only read their "local" values.
I think this introduces overhead for a lot of common operations. For every
descendant node you now have to read and instantiate a resource and value map.
[
https://issues.apache.org/jira/browse/SLING-3439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13924673#comment-13924673
]
Alexander Klimetschek commented on SLING-3439:
--
FWIW: Works for me f
On 07.03.2014, at 02:53, Carsten Ziegeler wrote:
> Before I close the vote tomorrow, I just want to state that I will ignore
> the non binding -1 from Alex as the discussions he's referring cover
> additional functionality which we can add in a next release.
Fair enough.
Cheers,
Alex
[
https://issues.apache.org/jira/browse/SLING-3423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13923115#comment-13923115
]
Alexander Klimetschek edited comment on SLING-3423 at 3/6/14 9:4
[
https://issues.apache.org/jira/browse/SLING-3423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13923115#comment-13923115
]
Alexander Klimetschek commented on SLING-3423:
--
[~jsedding] Yes, you
[
https://issues.apache.org/jira/browse/SLING-3423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13923100#comment-13923100
]
Alexander Klimetschek commented on SLING-3423:
--
[~bdelacretaz] Gi
On 05.03.2014, at 09:13, Bertrand Delacretaz wrote:
> I'm not convinced by the ResourceMergerService API, reading it and its
> javadoc does not give me a clear picture of where and how to use it. I
> wouldn't be surprised if we have to change it later on.
-1 (non binding)
While the discussion o
On 05.03.2014, at 04:50, Carsten Ziegeler wrote:
> This is the vote to release
>
> - Sling I18N 2.2.8
+1 (non-binding, not verified)
Cheers,
Alex
[
https://issues.apache.org/jira/browse/SLING-3423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13921193#comment-13921193
]
Alexander Klimetschek commented on SLING-3423:
--
Would be ok, but it w
[
https://issues.apache.org/jira/browse/SLING-3423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13921053#comment-13921053
]
Alexander Klimetschek commented on SLING-3423:
--
The logic for getting
[
https://issues.apache.org/jira/browse/SLING-3423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13921023#comment-13921023
]
Alexander Klimetschek commented on SLING-3423:
--
Yes, as I wrote on the
[
https://issues.apache.org/jira/browse/SLING-3423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13920992#comment-13920992
]
Alexander Klimetschek commented on SLING-3423:
--
I disagree. Why would
On 03.03.2014, at 23:05, Carsten Ziegeler wrote:
> We should not return fake resources from a service which are not available
> using the same path (the resource returns) via the resoruce resolver.
If it's provided by a resource provider, that will be the case. Although I
don't think it's a bi
[
https://issues.apache.org/jira/browse/SLING-3420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13918654#comment-13918654
]
Alexander Klimetschek commented on SLING-3420:
--
Oh, yes, sorry for
On 02.03.2014, at 23:05, Carsten Ziegeler wrote:
> public MergeData merge(String[] paths)
But why not make it implement Resource then (as it already does)?
> Having a method which gets a relative path together with the search paths
The concept of "root path" plus "relative path" plus "list of
On 01.03.2014, at 01:56, Carsten Ziegeler wrote:
> It is not correct, that we added a merge() method which "completely misses
> the point".
No, you did not add that merge() method at all :)
It's basically now the getMergedResource(Resource) method, which is FIXED to
the sling search path. And
[
https://issues.apache.org/jira/browse/SLING-3420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13917032#comment-13917032
]
Alexander Klimetschek commented on SLING-3420:
--
That there is an autom
[
https://issues.apache.org/jira/browse/SLING-3420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13917013#comment-13917013
]
Alexander Klimetschek commented on SLING-3420:
--
But I think it gives
[
https://issues.apache.org/jira/browse/SLING-3420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13916491#comment-13916491
]
Alexander Klimetschek edited comment on SLING-3420 at 2/28/14 10:1
[
https://issues.apache.org/jira/browse/SLING-3420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13916491#comment-13916491
]
Alexander Klimetschek edited comment on SLING-3420 at 2/28/14 10:1
[
https://issues.apache.org/jira/browse/SLING-3420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13916491#comment-13916491
]
Alexander Klimetschek commented on SLING-3420:
--
-1 on making the me
I created https://issues.apache.org/jira/browse/SLING-3423
Cheers,
Alex
On 28.02.2014, at 13:54, Alexander Klimetschek wrote:
> Hi,
>
> looking at SLING-3420 [1] I noticed that the ResourceMergerService [2] fails
> to follow the intended design, and explains some of the misun
[
https://issues.apache.org/jira/browse/SLING-3420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13916478#comment-13916478
]
Alexander Klimetschek commented on SLING-3420:
--
Created SLING-
[
https://issues.apache.org/jira/browse/SLING-3423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Klimetschek updated SLING-3423:
-
Summary: ResourceMergerService API must allow custom merge paths (was
[
https://issues.apache.org/jira/browse/SLING-2986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13916475#comment-13916475
]
Alexander Klimetschek commented on SLING-2986:
--
The service is no
Alexander Klimetschek created SLING-3423:
Summary: ResourceMergerService API is wrong
Key: SLING-3423
URL: https://issues.apache.org/jira/browse/SLING-3423
Project: Sling
Issue Type
[
https://issues.apache.org/jira/browse/SLING-3420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13916470#comment-13916470
]
Alexander Klimetschek commented on SLING-3420:
--
I just note that
Hi,
looking at SLING-3420 [1] I noticed that the ResourceMergerService [2] fails to
follow the intended design, and explains some of the misunderstandings around
the /mnt/overlay servlet discussion and now the modifying resource merger
discussion.
The ResourceMergerService must have this one c
[
https://issues.apache.org/jira/browse/SLING-3420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13915014#comment-13915014
]
Alexander Klimetschek commented on SLING-3420:
--
But the point is that
[
https://issues.apache.org/jira/browse/SLING-3420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13913571#comment-13913571
]
Alexander Klimetschek commented on SLING-3420:
--
The resource merge
[
https://issues.apache.org/jira/browse/SLING-3352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13910846#comment-13910846
]
Alexander Klimetschek commented on SLING-3352:
--
Agree with [~bdelacr
[
https://issues.apache.org/jira/browse/SLING-3407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13910833#comment-13910833
]
Alexander Klimetschek commented on SLING-3407:
--
Yes, checking for
[
https://issues.apache.org/jira/browse/SLING-3407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Klimetschek updated SLING-3407:
-
Attachment: (was: SLING-3407.patch)
> ResourceBundleManager
[
https://issues.apache.org/jira/browse/SLING-3407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Klimetschek updated SLING-3407:
-
Attachment: SLING-3407.patch
> ResourceBundleManager
Hi,
wdyt about this proposal: https://issues.apache.org/jira/browse/SLING-3407
Patch attached. Some questions open, see issue.
Thanks,
Alex
[
https://issues.apache.org/jira/browse/SLING-3407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Klimetschek updated SLING-3407:
-
Attachment: SLING-3407.patch
Here is a quick patch (compiles & tests suc
Alexander Klimetschek created SLING-3407:
Summary: ResourceBundleManager API
Key: SLING-3407
URL: https://issues.apache.org/jira/browse/SLING-3407
Project: Sling
Issue Type: New
[
https://issues.apache.org/jira/browse/SLING-3403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13907165#comment-13907165
]
Alexander Klimetschek commented on SLING-3403:
--
Ok, it just seemed
[
https://issues.apache.org/jira/browse/SLING-3403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13907139#comment-13907139
]
Alexander Klimetschek commented on SLING-3403:
--
I guess the "Util&q
On 19.02.2014, at 23:46, Felix Meschberger wrote:
> Absolutely. There is a (presumably low level and simple) test case
> test_decode_query for this in [1]
Cool. Although the test is using "a=1&b=2&c=3", which wouldn't expose that
issue. You might want to test something like "a=1&b=2&a=3" as we
[
https://issues.apache.org/jira/browse/SLING-3392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13906735#comment-13906735
]
Alexander Klimetschek commented on SLING-3392:
--
Right, the path must be
On 17.02.2014, at 07:19, Felix Meschberger wrote:
> method and enance the API:
>
> RequestParameter:
>add String getName();
>
> SlingHttpServletRequest:
>add List getRequestParameterList();
+1 Looks great to me!
Just to be sure - this allows to iterate key-value pairs as in the or
[
https://issues.apache.org/jira/browse/SLING-3392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13906349#comment-13906349
]
Alexander Klimetschek commented on SLING-3392:
--
AFAICS, in the cur
On 13.02.2014, at 13:44, Tommaso Teofili wrote:
> I personally prefer the granular one as it's more resource oriented, which
> makes more sense in my opinion for an HTTP API (be it REST or not)
Regarding REST: It is closer to REST only once you send out links to the
various options/commands.
I
[
https://issues.apache.org/jira/browse/SLING-2393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Klimetschek updated SLING-2393:
-
Attachment: SLING-2393.patch
Attached a patch for the documentation.
> Upd
[
https://issues.apache.org/jira/browse/SLING-2393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13894208#comment-13894208
]
Alexander Klimetschek commented on SLING-2393:
--
Ping... this would be
[
https://issues.apache.org/jira/browse/SLING-3380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13893891#comment-13893891
]
Alexander Klimetschek commented on SLING-3380:
--
You might want to finish
[
https://issues.apache.org/jira/browse/SLING-2986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13881489#comment-13881489
]
Alexander Klimetschek commented on SLING-2986:
--
We have a use case alr
[
https://issues.apache.org/jira/browse/SLING-2986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13876962#comment-13876962
]
Alexander Klimetschek commented on SLING-2986:
--
I think the ResourceMe
On 20.01.2014, at 02:43, Felix Meschberger wrote:
> Ok, I have created a request parameter processing prototype in my whiteboard
> [1]:
>
> - Create new "parameters" bundle to reuse request parameter support
>independently of the Sling Engine
> - Added new ParameterSupport method to retriev
On 17.01.2014, at 05:52, Lars Krapf wrote:
> When I talk about trusted credentials, I refer only to the previous
> implementation that relied
> on an attribute (configured once for the login-module(s) and once for the
> authentication handler).
> which was stored in plain-text, and had a defaul
On 17.01.2014, at 05:10, Bertrand Delacretaz wrote:
>> Do you have a concrete use case for that ?
>
> Not me but I'm not running any Sling-based sites myself ;-)
>
> OTOH this is basic A/B testing, and also applies to soft launching a
> new feature (B) that replaces an existing one (A).
Appare
On 17.01.2014, at 01:54, Bertrand Delacretaz wrote:
> You might generate the "commands" parameter In a Filter, maybe? At
> least as a workaround until this is fixed in Sling, which might not be
> that simple (I haven't looked in detail).
If you mean Carsten's proposal of a osgi httpservice-level
On 16.01.2014, at 05:19, Carsten Ziegeler wrote:
> Eagerly waiting for a patch which implements this :)
He he :)
This isn’t meant as something we should have soon - it is meant as a goal to
guide around the jcr login mechanism discussion.
One opinion is: ah, don’t care, once code is running i
On 16.01.2014, at 06:49, Lars Krapf wrote:
> As long as reflection is still permitted I think you could get around most
> (all?) of these restrictions.
> I'm pretty sure this can only be solved properly on VM level
> (SecurityManager).
As I said, reflection is one of the things you have to dis
On 16.01.2014, at 02:15, Bertrand Delacretaz wrote:
> This looks like a mini language, so I'd say using multiple parameters
> for that is a bad idea, I'd rather have
>
> commands="layer 0 ; img mypic.jpg ; rotate 10 ; layer 1 ; img anotherpic.jpg"
>
> or something like that, as a single parame
On 15.01.2014, at 01:34, Carsten Ziegeler wrote:
> I think, that's already solved by the SecurityManager concept - so let's
> not reinvent the wheel
One solution would be to add a new interface to use that only gives access to
the allowed methods. For example, say you only want to allow
System
if the information is used.
>>
>> I'm wondering if its worth the effort - can't you simply register a servlet
>> filter (not a Sling servlet filter) which does the magic for you for those
>> URLs where it matters?
>>
>> Regards
>> Carsten
&
On 14.01.2014, at 18:05, Felix Meschberger wrote:
> Am 14.01.2014 um 18:44 schrieb Alexander Klimetschek :
>
>> /do?move=10steps&turnLeft=45deg&move=20steps
>>
>> [...]
>>
>> This could be easily solved by extending Sling's RequestParamete
I forgot 2 important points ;) (see below for responses to the existing
discussion)
(1)
Just using an ordered map instead of a hash map doesn't solve the problem, as
multi-value parameters still get merged and their invidual position lost. For
example, an URL like this (which is similar to my
[
https://issues.apache.org/jira/browse/SLING-1158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13871282#comment-13871282
]
Alexander Klimetschek commented on SLING-1158:
--
Ah, you are right. One c
[
https://issues.apache.org/jira/browse/SLING-1158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13871082#comment-13871082
]
Alexander Klimetschek commented on SLING-1158:
--
It should also be poss
On 13.01.2014, at 21:15, Chetan Mehrotra wrote:
> However the problem with sandboxing untrusted code in any form
> requires quite a bit of an effort. Just to start with
>
> a. Disable access to Java reflection API
> b. Limit access to OSGi service registry
> c. Limit access to JMX. You can invok
On 14.01.2014, at 09:59, Felix Meschberger wrote:
> How about we move the ParameterSupport into a separate bundle and expose the
> ParameterSupport class as a utility class. This can then be leveraged by the
> Sling Engine itself but also by other pieces not running inside the Sling
> Engine.
On 13.01.2014, at 21:17, Felix Meschberger wrote:
> Having said this, I could imagine taking a hybrid approach:
>
> (1) For url-encoded POST request, check whether InputStream is available
> (1a) if available:
> - decode query string
> - decode input stream
> (1b) if not available
> - take
Hi,
Sling currently does not allow to read request parameters in their original
order. I need this for a migrated servlet code that used to run on other
servlet containers and was able to preserve the order (see below), thus has URL
schemes where paramter order is crucial.
Actually it is the j
Hi,
an alternative to a trusted credentials mechanism is
1. to use loginByService in the authentication handler itself
2. impersonate to the desired user (and have a service user mapping that allows
the necessary impersonations)
3. put the resulting jcr session as "user.jcr.session" [0] into the
Right, good analysis! I have further important additions to #1 and #2:
#1 of course is difficult. It should be split up:
-
1a. malicious JSP/script code
Injecting a script that gets executed by Sling can be a lot easier (incorrect
ACLs on prod
Sling Models _could_ be slightly confusing if you look at Sling as MVC:
M = resources/jcr
V = scripts/servlets
C = sling engine
Just my 2 cents,
Alex
On 11.01.2014, at 04:47, Carsten Ziegeler wrote:
> I'm +1 on the move, I'm not sure if Sling Models is a good name - as a
> non-native speaker,
[
https://issues.apache.org/jira/browse/SLING-3179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13868903#comment-13868903
]
Alexander Klimetschek commented on SLING-3179:
--
{quote}this is how
[
https://issues.apache.org/jira/browse/SLING-2762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13868615#comment-13868615
]
Alexander Klimetschek commented on SLING-2762:
--
BTW, regarding the
[
https://issues.apache.org/jira/browse/SLING-3179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13868599#comment-13868599
]
Alexander Klimetschek edited comment on SLING-3179 at 1/11/14 2:1
Regarding:
https://issues.apache.org/jira/browse/SLING-3179
https://cwiki.apache.org/confluence/display/SLING/Solving+the+Authentication+Handler+Credential+Validation+Problem
I don't see how this is adding security other than reintroducing the
TrustedInfo again, just with different and more compl
[
https://issues.apache.org/jira/browse/SLING-3179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13868599#comment-13868599
]
Alexander Klimetschek commented on SLING-3179:
--
I don't see ho
On 10.01.2014, at 07:05, Konrad Windszus wrote:
> The general question is: Under which circumstances is it worth to cache a
> session (for a single thread) instead of just creating new ones and close
> them directly afterwards?
I guess there is another likely explanation:
4) a new session won
[
https://issues.apache.org/jira/browse/SLING-3285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13867158#comment-13867158
]
Alexander Klimetschek commented on SLING-3285:
--
Yes, good point. It coul
On 08.01.2014, at 06:41, Felix Meschberger wrote:
> I don't think pumping up the log tracker to extract information more easily
> is a way to go: Other than having some kind of defined line format, the
> actual messages are just strings with not defined format at all. So relying
> on the forma
[
https://issues.apache.org/jira/browse/SLING-3285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13866005#comment-13866005
]
Alexander Klimetschek commented on SLING-3285:
--
The problem seems to li
On 07.01.2014, at 11:19, Felix Meschberger wrote:
> The Sling Engine sets the "sling.core.current.servletName" request attribute
> to the name of the Servlet (absolut path in case of Scripts) before calling
> the servlet or script. In essence this means tha the name of the
> servlet/script to
On 20.12.2013, at 10:08, Tobias Bocanegra wrote:
> however, there are currently tools and UIs developed on top of the
> existing content based solution which assume the fine grained storage.
> so changing the structure would also impact those.
Yes, having written a few of those tools (all propie
On 18.12.2013, at 21:44, Tobias Bocanegra wrote:
> I don't really like the automatic upgrade, since we really don't know
> how to differentiate use of mix:language/sling:message in compact
> subtrees vs the sparse case. It might be to expensive to traverse the
> mix:language nodes for each bundle
On 17.12.2013, at 23:12, Carsten Ziegeler wrote:
> The bundle can either set a marker in the repository
That's probably something we should avoid. The question is where? And why?
> or a file in the
> bundle private date;
Sounds better.
> the repository is the better place as this can be used
On 18.12.2013, at 09:35, Tobias Bocanegra wrote:
> I don't think that the migration is straight forward. the way the
> provider currently works, it would allow message definitions like:
>
> /content/de [mix:language]
> /very/deep/structure/
>/hello [sling:Message]
> + sling:message "Ha
On 17.12.2013, at 22:03, Carsten Ziegeler wrote:
> What about if we add the migration code to the bundle?
Hmm, interesting :) Not sure though if we should modify content from such a
bundle. And how do we know that we already did the migration and don't run the
migration code over and over agai
On 17.12.2013, at 17:03, Tobias Bocanegra wrote:
> +1 I like the dictionary approach better as it reduces the amount of
> complex queries.
>
> for backward compatibility the resource bundle provider should
> initially do a query for the new dictionaries and if found, go into
> 'dictionary' mode.
[
https://issues.apache.org/jira/browse/SLING-3025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13851212#comment-13851212
]
Alexander Klimetschek commented on SLING-3025:
--
This has been fixed by S
On 17.12.2013, at 14:05, Tobias Bocanegra wrote:
> I was looking at SLING-2881 [0] and reading the docu at [1]. the i18n
> code has 1 queries, one is:
>
> 1) //element(*,mix:language)
Unfortunately this is too broad, mix:language can be many nodes, depending on
the application. That's why we e
On 16.12.2013, at 04:38, Dominik Süß wrote:
> There is currently a gap between the behavior of .resolve() and .getResource()
> where getResource would return null and .resolve() should return a
> NonExistingResource. I'm pretty sure there is a reason for that, but I
> couldn't find it.
Oh, yes,
[
https://issues.apache.org/jira/browse/SLING-3285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13848688#comment-13848688
]
Alexander Klimetschek commented on SLING-3285:
--
Thinking about b) furthe
[
https://issues.apache.org/jira/browse/SLING-3285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13848687#comment-13848687
]
Alexander Klimetschek commented on SLING-3285:
--
If the resource reso
Alexander Klimetschek created SLING-3285:
Summary: ResourceResolver.isResourceType() creates admin session
for every call with super type, slowing down processing
Key: SLING-3285
URL: https
Might be slightly OT, but still: there is always a
repository.loginAdminstrative() to do all kinds of things. So if you can deploy
code, you can do anything. To improve on that over the long term, I think we
should have configurability on the repository infra level, which can do what
login.
Wi
On 12.12.2013, at 19:40, Carsten Ziegeler wrote:
> I think you missunderstood me, or we're maybe talking about different
> things - as repeatedly stated we don't need to change the resource resolver
> - we have everything in place; and now we exactly need to define the use
> cases to know how the
On 11.12.2013, at 19:10, Carsten Ziegeler wrote:
> I think we're pretty clear now how we could implement this, basically
> everything is in place, so the resource resolver has all features we need
> in the way we need them. And we should now start defining the feature flags
> api.
Did you read m
From: Carsten Ziegeler
> Thanks Alex - should be fixed now
No, now it's in italic, which makes sense if this is Markdown, as underscores
make text italic there :)
I suggest to put it in back ticks to make it formatted as fixed-width font:
`_charset_`
Cheers,
Alex
From: Felix Meschberger
> For "hiding" resources I would really prefer hooking into the
> ResourceResolverImpl and make that be
> aware of FeatureFlags itself. (I seem to repeat myself here, but I seem to
> have a strong position on
> that :-) )
The problem of integrating that right into the r
Hi,
at the end of [0] in the section "Character Encoding" it currently says
/*charset*/
a few times in the text while it should probably be
_charset_
I assume it's just an issue with the markup language.
[0]
http://sling.apache.org/documentation/the-sling-engine/request-parameters.ht
301 - 400 of 884 matches
Mail list logo
