[
https://issues.apache.org/jira/browse/SLING-3407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13910135#comment-13910135
]
Bertrand Delacretaz commented on SLING-3407:
+1 in general.
If
Felix Meschberger created SLING-3409:
Summary: URL form encoded request parsing fails if charset is set
on Content-Type header
Key: SLING-3409
URL: https://issues.apache.org/jira/browse/SLING-3409
[
https://issues.apache.org/jira/browse/SLING-2986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler updated SLING-2986:
Fix Version/s: Resource Merger 1.0.0
Merged Resource Provider
[
https://issues.apache.org/jira/browse/SLING-2986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler updated SLING-2986:
Fix Version/s: (was: Resource Merger 1.0.0)
Merged Resource Provider
I've no idea - I removed the version from the issue and applied it again -
and now it's in the list...
2014-02-22 18:54 GMT+01:00 Justin Edelson jus...@justinedelson.com:
+1
Sorry for the delay...
One question - https://issues.apache.org/jira/browse/SLING-2986 is not
listed under issues
The vote passes with four binding +1 votes from Ian Boston, Justin Edelson,
Mike Müller, and Carsten Ziegeler and one non binding +1 vote from GIlles
Knobloch
Thanks everyone for voting
Carsten
--
Carsten Ziegeler
cziege...@apache.org
The vote passes with four binding +1 votes from Justin Edelson, Ian Boston,
Mike Müller, and Carsten Ziegeler
Thanks everyone for voting
Carsten
--
Carsten Ziegeler
cziege...@apache.org
[
https://issues.apache.org/jira/browse/SLING-3409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger resolved SLING-3409.
--
Resolution: Fixed
Assignee: Felix Meschberger
fixed in Rev. 1571220.
Also
[
https://issues.apache.org/jira/browse/SLING-3370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amit Gupta reassigned SLING-3370:
-
Assignee: Amit Gupta
Bootdelegation support for third party library
The Buildbot has detected a new failure on builder sling-trunk while building
ASF Buildbot.
Full details are available at:
http://ci.apache.org/builders/sling-trunk/builds/316
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: osiris_ubuntu
Build Reason: scheduler
Build Source
Chetan Mehrotra created SLING-3410:
--
Summary: Log the Logback initialization related logs to normal log
for transient errors
Key: SLING-3410
URL: https://issues.apache.org/jira/browse/SLING-3410
On Fri, Feb 21, 2014 at 5:19 PM, Andreas Schaefer Sr. schaef...@me.com wrote:
...My confluence name is ‘schaefera’
Ok, I have added you to the sling-contributors group, you should now
have write access to https://cwiki.apache.org/confluence/display
BTW I saw that there is a page called
The Buildbot has detected a restored build on builder sling-trunk while
building ASF Buildbot.
Full details are available at:
http://ci.apache.org/builders/sling-trunk/builds/317
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: osiris_ubuntu
Build Reason: scheduler
Build Source
[
https://issues.apache.org/jira/browse/SLING-3352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marius Petria updated SLING-3352:
-
Attachment: SLING-3352.2.patch
Adding implementation of a resource provider that exposes osgi
[
https://issues.apache.org/jira/browse/SLING-3410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13910302#comment-13910302
]
Chetan Mehrotra commented on SLING-3410:
Added support in r1571283 and r1571284
[
https://issues.apache.org/jira/browse/SLING-3410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chetan Mehrotra updated SLING-3410:
---
Fix Version/s: Commons Log 4.0.0
Log the Logback initialization related logs to normal log
Hi,
I have provided an initial implementation in a patch for [1]. It allows to
customize the resource provider so that downstream users can choose which
property should be used as the friendly name (as Julian suggested). We can add
also a customization option to specify a resource type.
[
https://issues.apache.org/jira/browse/SLING-3352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13910304#comment-13910304
]
Bertrand Delacretaz commented on SLING-3352:
I haven't followed all
[
https://issues.apache.org/jira/browse/SLING-3352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13910301#comment-13910301
]
Marius Petria edited comment on SLING-3352 at 2/24/14 1:43 PM:
Chetan Mehrotra created SLING-3411:
--
Summary: Enable configuring the maxCallerDataDepth in Logback
LoggerContext
Key: SLING-3411
URL: https://issues.apache.org/jira/browse/SLING-3411
Project: Sling
Felix Meschberger created SLING-3412:
Summary: Create parmater support configurer component
Key: SLING-3412
URL: https://issues.apache.org/jira/browse/SLING-3412
Project: Sling
Issue
[
https://issues.apache.org/jira/browse/SLING-3412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger resolved SLING-3412.
--
Resolution: Fixed
Created the new RequestParameterSupportConfigurer class as a
[
https://issues.apache.org/jira/browse/SLING-3403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger resolved SLING-3403.
--
Resolution: Fixed
I think we can resolve this issue fixed. Separate issues to be
[
https://issues.apache.org/jira/browse/SLING-3403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13910393#comment-13910393
]
Felix Meschberger commented on SLING-3403:
--
[~alexander.klimetschek] I have
[
https://issues.apache.org/jira/browse/SLING-3403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13910396#comment-13910396
]
Felix Meschberger commented on SLING-3403:
--
oh, and finally removed the Jetty
[
https://issues.apache.org/jira/browse/SLING-3275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chetan Mehrotra resolved SLING-3275.
Resolution: Fixed
Added support in [r1571319|http://svn.apache.org/r1571319]
LogWriter
[
https://issues.apache.org/jira/browse/SLING-3275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chetan Mehrotra updated SLING-3275:
---
Fix Version/s: Commons Log 4.0.0
Add Buffered Logging Configuration in Apache Sling Logging
[
https://issues.apache.org/jira/browse/SLING-3411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chetan Mehrotra resolved SLING-3411.
Resolution: Fixed
Added support in [r1571318|http://svn.apache.org/r1571318].
One can set
Justin Edelson created SLING-3413:
-
Summary: add support for getName() and getChildren() to JS
Resource API
Key: SLING-3413
URL: https://issues.apache.org/jira/browse/SLING-3413
Project: Sling
[
https://issues.apache.org/jira/browse/SLING-3413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13910461#comment-13910461
]
Justin Edelson commented on SLING-3413:
---
proposed patch here:
[
https://issues.apache.org/jira/browse/SLING-3413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13910461#comment-13910461
]
Justin Edelson edited comment on SLING-3413 at 2/24/14 5:00 PM:
[
https://issues.apache.org/jira/browse/SLING-3413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13910505#comment-13910505
]
Felix Meschberger commented on SLING-3413:
--
Sounds reasonable, except for
Andreas Schaefer created SLING-3414:
---
Summary: Mutlitenancy Support Integration
Key: SLING-3414
URL: https://issues.apache.org/jira/browse/SLING-3414
Project: Sling
Issue Type: Improvement
Hi
Thanks. I’ll created the page here:
https://cwiki.apache.org/confluence/display/SLING/Multitenancy+Support+Integration
and also created a ticket for it here:
https://issues.apache.org/jira/browse/SLING-3414
- Andy
On Feb 24, 2014, at 5:08 AM, Bertrand Delacretaz bdelacre...@apache.org
Marius Petria created SLING-3415:
Summary: The ResourceAccessGateHandler does not parse correctly
multiple operations
Key: SLING-3415
URL: https://issues.apache.org/jira/browse/SLING-3415
Project:
[
https://issues.apache.org/jira/browse/SLING-3415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marius Petria updated SLING-3415:
-
Attachment: resourcesecurity-multipleoperations-bugfix.patch
Fixing by retrieving an object and
Hi Carsten
Even if a Search Path Extension is not used outside of the Tenants I still
think it would be great to keep things separate. Based on my tests if the
Search Path Extension is set when the Resource Resolver of a request is created
and the Servlet resolver’s own Resource Resolver is
Amit Gupta created SLING-3416:
-
Summary: Some tests in
o.a.s.m.projectsupport.BundleListContentProviderTest fails on windows
Key: SLING-3416
URL: https://issues.apache.org/jira/browse/SLING-3416
Project:
[
https://issues.apache.org/jira/browse/SLING-3416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13910589#comment-13910589
]
Amit Gupta commented on SLING-3416:
---
fix Completed: At revision: 1571375
Some tests
The Buildbot has detected a new failure on builder sling-trunk while building
ASF Buildbot.
Full details are available at:
http://ci.apache.org/builders/sling-trunk/builds/322
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: osiris_ubuntu
Build Reason: scheduler
Build Source
[
https://issues.apache.org/jira/browse/SLING-3415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler updated SLING-3415:
Fix Version/s: Resource Access Gate 1.0.0
The ResourceAccessGateHandler does not parse
[
https://issues.apache.org/jira/browse/SLING-3415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-3415.
-
Resolution: Fixed
Thanks for reporting, I've fixed the issue slightly different.
Fixed
The Buildbot has detected a restored build on builder sling-trunk while
building ASF Buildbot.
Full details are available at:
http://ci.apache.org/builders/sling-trunk/builds/323
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: osiris_ubuntu
Build Reason: scheduler
Build Source
If you want the method to get the search paths extensions to be on the
resource resolver and make it independent of a tenant, then why do we need
this method at all?
In the case of a tenant getSearchPath would return the normal search path
with the tenant specific one prepended.
Carsten
[
https://issues.apache.org/jira/browse/SLING-3407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13910833#comment-13910833
]
Alexander Klimetschek commented on SLING-3407:
--
Yes, checking for null should
[
https://issues.apache.org/jira/browse/SLING-3352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13910846#comment-13910846
]
Alexander Klimetschek commented on SLING-3352:
--
Agree with [~bdelacretaz],
If we have the search path extension separate and it is settable we do the
following with it:
1) We can set it with a Servlet Filter instead of having it to hook into the
Engine
2) In the Servlet Resolver the Search Path that did deliver the Servlet can be
used in order to manage the cache.
[
https://issues.apache.org/jira/browse/SLING-3413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Edelson updated SLING-3413:
--
Summary: add support for getName() and listChildren() to JS Resource API
(was: add support
[
https://issues.apache.org/jira/browse/SLING-3413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13911151#comment-13911151
]
Justin Edelson commented on SLING-3413:
---
bq. Sounds reasonable, except for
[
https://issues.apache.org/jira/browse/SLING-3413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Edelson updated SLING-3413:
--
Description: The JS API used to wrap Resources doesn't support getting a
list of children or
[
https://issues.apache.org/jira/browse/SLING-3416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amit Gupta resolved SLING-3416.
---
Resolution: Fixed
Some tests in o.a.s.m.projectsupport.BundleListContentProviderTest fails on
Right, 2) and also 3) are good reasons to keep it separate. I think it
makes sense to link the search path extension somehow to the tenant.
In the old proposal (
https://cwiki.apache.org/confluence/display/SLING/Multitenancy+Support) we
suggested to have a special method on the resource resolver
Hi,
while thinking about the tenant stuff (see separate thread), I (again) came
across the fact, that we
don't say anything whether ResourceResolver#getSearchPath is static or
dynamic (if the value might change at runtime for the same resource
resolver).
Looking at code using the resource
53 matches
Mail list logo
