Hi
Am 25.02.2014 um 07:43 schrieb Carsten Ziegeler cziege...@apache.org:
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
[
https://issues.apache.org/jira/browse/SLING-3045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chetan Mehrotra resolved SLING-3045.
Resolution: Fixed
In some cases such logs would be observed and cannot be avoided. These
[
https://issues.apache.org/jira/browse/SLING-3364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chetan Mehrotra resolved SLING-3364.
Resolution: Fixed
Added support in http://svn.apache.org/r1571618
This fix would enable
[
https://issues.apache.org/jira/browse/SLING-3352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13911403#comment-13911403
]
Marius Petria commented on SLING-3352:
--
bquote. OTOH, you can already POST to the
[
https://issues.apache.org/jira/browse/SLING-3352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13911408#comment-13911408
]
Bertrand Delacretaz edited comment on SLING-3352 at 2/25/14 9:07 AM:
[
https://issues.apache.org/jira/browse/SLING-3352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13911408#comment-13911408
]
Bertrand Delacretaz commented on SLING-3352:
If the goal is only to provide
On Tue, Feb 25, 2014 at 2:41 AM, Andreas Schaefer Sr. schaef...@me.com wrote:
...it might a good idea to add the getSearchPathExtension() to the Tenant...
Shouldn't that rather be called getAdditionalSearchPaths?
In Sling, extension means the .html at the end of a URL, IMO we
should avoid
Hi Marius
Thanks for the patch. However, I think you misunderstood my
suggestion. The idea was that there is a well-defined property (e.g.
sling:osgiConfigPid), which can be set on a JCR node, this points to
the configuration that should be mounted on this node.
I'll try to illustrate it with an
Hi,
This is the vote to release
- Sling API 2.6.0
https://issues.apache.org/jira/browse/SLING/fixforversion/12325953
- Sling Engine 2.3.0
https://issues.apache.org/jira/browse/SLING/fixforversion/12325271
this vote is about the first release of the Resource Merger
Staging repository:
+1
Regards
Felix
Am 25.02.2014 um 10:38 schrieb Felix Meschberger fmesc...@adobe.com:
Hi,
This is the vote to release
- Sling API 2.6.0
https://issues.apache.org/jira/browse/SLING/fixforversion/12325953
- Sling Engine 2.3.0
+1
2014-02-25 10:41 GMT+01:00 Felix Meschberger fmesc...@adobe.com:
+1
Regards
Felix
Am 25.02.2014 um 10:38 schrieb Felix Meschberger fmesc...@adobe.com:
Hi,
This is the vote to release
- Sling API 2.6.0
https://issues.apache.org/jira/browse/SLING/fixforversion/12325953
[
https://issues.apache.org/jira/browse/SLING-3400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-3400.
-
Resolution: Fixed
Sling holds resource providers after they have been unregistered
[
https://issues.apache.org/jira/browse/SLING-3406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Egli reassigned SLING-3406:
--
Assignee: Stefan Egli
Stale item exception when concurrent topology change events
Got point, I've updated the javadocs in rev 1571670
Carsten
2014-02-25 9:20 GMT+01:00 Felix Meschberger fmesc...@adobe.com:
Hi
Am 25.02.2014 um 07:43 schrieb Carsten Ziegeler cziege...@apache.org:
Hi,
while thinking about the tenant stuff (see separate thread), I (again)
came
[
https://issues.apache.org/jira/browse/SLING-3352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13911552#comment-13911552
]
Tommaso Teofili commented on SLING-3352:
bq. OTOH, you can already POST to the
[
https://issues.apache.org/jira/browse/SLING-3352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13911554#comment-13911554
]
Bertrand Delacretaz commented on SLING-3352:
bq. ...we assume that things work
[
https://issues.apache.org/jira/browse/SLING-3352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13911626#comment-13911626
]
Carsten Ziegeler commented on SLING-3352:
-
I think we're throwing in many
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/329
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: osiris_ubuntu
Build Reason: scheduler
Build Source
This feels wrong to me. Not that it does not reflect the current state of
things but rather because it maybe limiting the tenant implementation.
I am still working through Sling to understand it inner workings because most
of what I know is based on CQ and not on using Sling directly.
- Andy
I still like my TenantAware approach :) as by this you explicitely mark
your component to handle things Tenant specific.
Do you mean with that that we place the Tenant on a Thread Local which then can
be obtained from the Servlet Resolver?
If so do you intent to place the Tenant into the
Ok, will adjust the wiki page.
- Andy
On Feb 25, 2014, at 1:11 AM, Bertrand Delacretaz bdelacre...@apache.org wrote:
On Tue, Feb 25, 2014 at 2:41 AM, Andreas Schaefer Sr. schaef...@me.com
wrote:
...it might a good idea to add the getSearchPathExtension() to the Tenant...
Shouldn't that
[
https://issues.apache.org/jira/browse/SLING-3413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13912029#comment-13912029
]
Francesco Mari commented on SLING-3413:
---
In my opinion is not a common idiom in
No, I don't think it does limit the Tenant implementation - at least as
long as we provide an additional way of providing the per tenant search
path than using getSearchPath of the resource resolver.
It's a fact that code in Sling and also in the code of client code using
Sling is assuming that
I think using a thread local is an implementation detail and TenantAware
has a single method like
TenantResolver getTenantResolver()
while TenantResolver has a single method
Tenant getCurrentTenant()
(Don't quote me on the names, its just the first option which came to my
mind)
And then
[
https://issues.apache.org/jira/browse/SLING-3417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-3417.
-
Resolution: Fixed
Search paths must end with a slash
Carsten Ziegeler created SLING-3417:
---
Summary: Search paths must end with a slash
Key: SLING-3417
URL: https://issues.apache.org/jira/browse/SLING-3417
Project: Sling
Issue Type: Bug
Carsten Ziegeler created SLING-3419:
---
Summary: Component name specified instead of component label
Key: SLING-3419
URL: https://issues.apache.org/jira/browse/SLING-3419
Project: Sling
Carsten Ziegeler created SLING-3418:
---
Summary: Wrong path handling wrt search paths
Key: SLING-3418
URL: https://issues.apache.org/jira/browse/SLING-3418
Project: Sling
Issue Type: Bug
Carsten Ziegeler created SLING-3420:
---
Summary: Implement ModifyingResourceProvider
Key: SLING-3420
URL: https://issues.apache.org/jira/browse/SLING-3420
Project: Sling
Issue Type: New
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/330
Buildbot URL: http://ci.apache.org/
Buildslave for this Build: osiris_ubuntu
Build Reason: scheduler
Build Source
30 matches
Mail list logo
