[
https://issues.apache.org/jira/browse/SLING-3392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13906735#comment-13906735
]
Alexander Klimetschek commented on SLING-3392:
--
Right, the path must be the
On 19.02.2014, at 23:46, Felix Meschberger fmesc...@adobe.com 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=1b=2c=3, which wouldn't expose that
issue. You might want to test something like
[
https://issues.apache.org/jira/browse/SLING-3383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-3383.
-
Resolution: Fixed
Non stopping thread in AbstractJobQueue causes classloader leak
Another idea was proposed to generally solve access to OSGI objects (configs
and services).
1. OSGI configs need to be managed (CRUD) over HTTP and access should be
controlled at factory and config level.
URL hierarchy:
- /system/osgiconfigs/factoryPid/{configFriendlyName}
-
[
https://issues.apache.org/jira/browse/SLING-3400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13906786#comment-13906786
]
Carsten Ziegeler commented on SLING-3400:
-
It seems this is really caused by long
Hi,
as noted in SLING-3400 we have a problem when a resource provider factory
is unregistered and a resource resolver is currently using a provider from
this factory. In that case, that reference is never cleared.
This problem occurs due to long running resource resolvers.
I looked at solving
Felix Meschberger created SLING-3403:
Summary: Improve Parameter Support
Key: SLING-3403
URL: https://issues.apache.org/jira/browse/SLING-3403
Project: Sling
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/SLING-3403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13906850#comment-13906850
]
Felix Meschberger commented on SLING-3403:
--
Defined new API in Rev. 1570135:
*
[
https://issues.apache.org/jira/browse/SLING-3403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13906851#comment-13906851
]
Felix Meschberger commented on SLING-3403:
--
Updated the launchpad bundle list to
[
https://issues.apache.org/jira/browse/SLING-3401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger resolved SLING-3401.
--
Resolution: Fixed
Fix Version/s: Maven Launchpad Plugin 2.2.2
Assignee:
Hi
Am 20.02.2014 um 10:19 schrieb Carsten Ziegeler cziege...@apache.org:
Hi,
as noted in SLING-3400 we have a problem when a resource provider factory
is unregistered and a resource resolver is currently using a provider from
this factory. In that case, that reference is never cleared.
Hi Marius,
2014-02-20 9:58 GMT+01:00 Marius Petria mpet...@adobe.com:
Another idea was proposed to generally solve access to OSGI objects
(configs and services).
1. OSGI configs need to be managed (CRUD) over HTTP and access should be
controlled at factory and config level.
URL hierarchy:
Only ResourceProviderFactories are affected - simple resourceProviders like
the servlet ones can't keep state. Those appear/disappear silently. I agree
that service registration modifications are rather expensive, on the other
hand there are only a few provider factories and those are usually not
Hi
I see.
Can this be easily solved by just making the ResourceProviderFactory
reference in the ResourceResolverFactoryActivator a static reference with eager
policyOption?
Regards
Felix
Am 20.02.2014 um 13:21 schrieb Carsten Ziegeler cziege...@apache.org:
Only ResourceProviderFactories
Good point. I have updated the test
Regards
Felix
Am 20.02.2014 um 09:03 schrieb Alexander Klimetschek aklim...@adobe.com:
On 19.02.2014, at 23:46, Felix Meschberger fmesc...@adobe.com wrote:
Absolutely. There is a (presumably low level and simple) test case
test_decode_query for this in
[
https://issues.apache.org/jira/browse/SLING-3401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler reopened SLING-3401:
-
Assignee: Carsten Ziegeler (was: Felix Meschberger)
I think this patch is currently
[
https://issues.apache.org/jira/browse/SLING-3404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tommaso Teofili updated SLING-3404:
---
Description:
JobHandlingReplicationQueue currently logs an INFO message when a Job is
[
https://issues.apache.org/jira/browse/SLING-3404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13906924#comment-13906924
]
Tommaso Teofili commented on SLING-3404:
trivial fix for
[
https://issues.apache.org/jira/browse/SLING-3401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-3401.
-
Resolution: Fixed
I've added the support for the lifecycle participant (reading the
[
https://issues.apache.org/jira/browse/SLING-3401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13906934#comment-13906934
]
Felix Meschberger commented on SLING-3401:
--
Good catch. Thank you very much.
The Buildbot has detected a new failure on builder sling-trunk-oak while
building ASF Buildbot.
Full details are available at:
http://ci.apache.org/builders/sling-trunk-oak/builds/246
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: osiris_ubuntu
Build Reason: downstream
Build
Yes, that sounds like the easiest option - it would mean that the resource
resolver factory is re-registered with every change to a resource provider
factory - which doesn't sound too bad to me
Carsten
2014-02-20 13:25 GMT+01:00 Felix Meschberger fmesc...@adobe.com:
Hi
I see.
Can this be
Bertrand Delacretaz created SLING-3405:
--
Summary: SLING2094Test fails with java 8: JSP compiler does not
find java.util.Arrays
Key: SLING-3405
URL: https://issues.apache.org/jira/browse/SLING-3405
[
https://issues.apache.org/jira/browse/SLING-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13906960#comment-13906960
]
Carsten Ziegeler commented on SLING-3405:
-
Maybe we need to update our embedded
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/305
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: osiris_ubuntu
Build Reason: scheduler
Build Source
[
https://issues.apache.org/jira/browse/SLING-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13906981#comment-13906981
]
Bertrand Delacretaz commented on SLING-3405:
I don't know much about our
[
https://issues.apache.org/jira/browse/SLING-3356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tommaso Teofili updated SLING-3356:
---
Attachment: SLING-3356.3.patch
new version of Marius patch adapted to latest trunk
Expose
[
https://issues.apache.org/jira/browse/SLING-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz updated SLING-3405:
---
Attachment: jasper-upgrade.patch
I have tried upgrading the jasper-jdt compiler and
[
https://issues.apache.org/jira/browse/SLING-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13907078#comment-13907078
]
Carsten Ziegeler commented on SLING-3405:
-
Yepp, looks like the right way to
[
https://issues.apache.org/jira/browse/SLING-3406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jörg Hoh updated SLING-3406:
Summary: Stale item exception when concurrent topology change events (was:
Stale item exception
Jörg Hoh created SLING-3406:
---
Summary: Stale item exception concurrent topology change events
Key: SLING-3406
URL: https://issues.apache.org/jira/browse/SLING-3406
Project: Sling
Issue Type: Bug
[
https://issues.apache.org/jira/browse/SLING-3406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jörg Hoh updated SLING-3406:
Attachment: SLING-3406-stacktrace.txt
Stale item exception when concurrent topology change events
[
https://issues.apache.org/jira/browse/SLING-3403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13907139#comment-13907139
]
Alexander Klimetschek commented on SLING-3403:
--
I guess the Util class now
[
https://issues.apache.org/jira/browse/SLING-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13907155#comment-13907155
]
Bertrand Delacretaz commented on SLING-3405:
It looks like it's the
[
https://issues.apache.org/jira/browse/SLING-3403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13907158#comment-13907158
]
Felix Meschberger commented on SLING-3403:
--
The Util class being a component is
[
https://issues.apache.org/jira/browse/SLING-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13907155#comment-13907155
]
Bertrand Delacretaz edited comment on SLING-3405 at 2/20/14 4:42 PM:
[
https://issues.apache.org/jira/browse/SLING-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13907162#comment-13907162
]
Felix Meschberger edited comment on SLING-3405 at 2/20/14 4:44 PM:
[
https://issues.apache.org/jira/browse/SLING-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13907155#comment-13907155
]
Bertrand Delacretaz edited comment on SLING-3405 at 2/20/14 4:45 PM:
[
https://issues.apache.org/jira/browse/SLING-3403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13907165#comment-13907165
]
Alexander Klimetschek commented on SLING-3403:
--
Ok, it just seemed very
+1
2014-02-18 13:39 GMT+01:00 Carsten Ziegeler cziege...@apache.org:
Hi,
this vote is about the release of
Apache Sling Servlets Resolver 2.3.0
https://issues.apache.org/jira/browse/SLING/fixforversion/12324330
Staging repository:
[
https://issues.apache.org/jira/browse/SLING-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13907162#comment-13907162
]
Felix Meschberger commented on SLING-3405:
--
Java 8 support for the JDT compiler
[
https://issues.apache.org/jira/browse/SLING-3142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz updated SLING-3142:
---
Labels: java8 (was: )
NullPointerException with Java8 in AbstractUsingBundleList
[
https://issues.apache.org/jira/browse/SLING-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz updated SLING-3405:
---
Assignee: (was: Bertrand Delacretaz)
SLING2094Test fails with java 8: JSP
[
https://issues.apache.org/jira/browse/SLING-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13907181#comment-13907181
]
Bertrand Delacretaz commented on SLING-3405:
I have unassigned this issue as I
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
Hi
I started to look into how to add tenant support to Sling.
This is my test scenario:
I have an /apps/foo/bar/html.esp and a /apps/tenant1/foo/bar/html.esp and a
/content/mynode entry. The title of the second html.esp is different so that I
know which one is loaded.
Changes to the code:
Sorry, I forgot to mention that the Search Path Extension is prepended to the
Search Path when it is requested (in the Resource Resolver).
- Andy
On Feb 20, 2014, at 10:20 PM, Andreas Schaefer Sr. schaef...@me.com wrote:
Hi
I started to look into how to add tenant support to Sling.
This
Hi Andy,
this sounds interesting - and I guess a patch would be great. Now I just
would like to present my idea again - just for the sake of discussion :)
I think over time there will be more components than just the servlet
resolver which make use of the tenant and the extended search path, so
Anyone?
2014-02-18 13:26 GMT+01:00 Carsten Ziegeler cziege...@apache.org:
+1
Carsten
2014-02-18 11:37 GMT+01:00 Carsten Ziegeler cziege...@apache.org:
Hi,
this vote is about the first release of the Resource Merger
https://issues.apache.org/jira/browse/SLING/fixforversion/12326149
Anyone?
2014-02-20 17:53 GMT+01:00 Carsten Ziegeler cziege...@apache.org:
+1
2014-02-18 13:39 GMT+01:00 Carsten Ziegeler cziege...@apache.org:
Hi,
this vote is about the release of
Apache Sling Servlets Resolver 2.3.0
https://issues.apache.org/jira/browse/SLING/fixforversion/12324330
[
https://issues.apache.org/jira/browse/SLING-3356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tommaso Teofili resolved SLING-3356.
Resolution: Fixed
fixed by applying Marius's patch (with slight modifications) in r1570484
[
https://issues.apache.org/jira/browse/SLING-3404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tommaso Teofili resolved SLING-3404.
Resolution: Fixed
JobHandlingReplicationQueue reports failed Job.toString
52 matches
Mail list logo
