[
https://issues.apache.org/jira/browse/SLING-3278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13852731#comment-13852731
]
Georg Henzler commented on SLING-3278:
--
1) maybe we should rather go run(String
hi *,
in SLING-3290 [0] I have started to write some performance test regarding long
startup time with many vanityPath or alias.
As you might see from the attached graph the startup time increases
considerably with the number of vanityPath.
The same should applies to aliases (I am writing
Tommaso Teofili created SLING-3295:
--
Summary: Add a scheduled replication rule
Key: SLING-3295
URL: https://issues.apache.org/jira/browse/SLING-3295
Project: Sling
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/SLING-3295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tommaso Teofili updated SLING-3295:
---
Attachment: SLING-3295.patch
Add a scheduled replication rule
Hi,
I thought a bit more about the SLING-3278 HealthCheckExecutor service,
and a fluent interface might be useful:
interface HealthCheckExecutor {
/** Select all HealthChecks for execution */
HealthCheckContext all();
/** Select a single HealthCheck for execution */
HealthCheckContext
[
https://issues.apache.org/jira/browse/SLING-3278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13852761#comment-13852761
]
Bertrand Delacretaz commented on SLING-3278:
I'm also for having an executor
[
https://issues.apache.org/jira/browse/SLING-3278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13852762#comment-13852762
]
Carsten Ziegeler edited comment on SLING-3278 at 12/19/13 9:33 AM:
[
https://issues.apache.org/jira/browse/SLING-3278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13852762#comment-13852762
]
Carsten Ziegeler commented on SLING-3278:
-
1) The class name is implementation
Hi Amit
thanks for the feedback - yes, good point with active vs available. I'll
change that.
Yes, as the implementation manages the contexts, it first calls isEnabled
on the providers to know which features are enabled and then only calls the
other methos like hideResource if the feature is
Bertrand Delacretaz created SLING-3296:
--
Summary: Occasional NPE in EstablishedClusterView
Key: SLING-3296
URL: https://issues.apache.org/jira/browse/SLING-3296
Project: Sling
Issue
[
https://issues.apache.org/jira/browse/SLING-3296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz updated SLING-3296:
---
Affects Version/s: Discovery Impl 1.0.2
Occasional NPE in EstablishedClusterView
[
https://issues.apache.org/jira/browse/SLING-3292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13852905#comment-13852905
]
Felix Meschberger commented on SLING-3292:
--
This sounds interesting.
Yet, we
[
https://issues.apache.org/jira/browse/SLING-3292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13852955#comment-13852955
]
Lars Trieloff commented on SLING-3292:
--
It looks like buffering is a common approach,
Hi,
although in general I like fluent APIs, in this case IMHO there is not
really a point in creating one. The HealthCheckExecutor is only to be
used by JMX and the web console (and maybe at some point by some
servlet), but not as part of a normal implementation project. However, I
think
[
https://issues.apache.org/jira/browse/SLING-3278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13852998#comment-13852998
]
Georg Henzler commented on SLING-3278:
--
Re Fluent API as well as The class name is
[
https://issues.apache.org/jira/browse/SLING-3281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tommaso Teofili updated SLING-3281:
---
Attachment: SLING-3281.5.patch
Expose more information on the replication queues
Hi,
I've published a page to the wiki about a concept I've been working on
to consolidate the various appproaches I have seen in the wild to
model object creation. I'm calling this YAMF for now, although ideally
we'll just call it Sling Models :)
Without repeating the whole contents of the wiki
HI Justin,
thank a lot for that. I am assuming a lot of developers were waiting for just
that. Could you extend the wiki page with an example on how the model bean
should then be used from within the view (i.e. the JSP) and also some words
about the scope of one instance?
One very good addition
Igor Bogomolov created SLING-3297:
-
Summary: Sling-based mail archive server sample contribution
Key: SLING-3297
URL: https://issues.apache.org/jira/browse/SLING-3297
Project: Sling
Issue
Hi Konrad,
Thanks for the feedback.
From a client perspective (i.e. a JSP), they are just using the
adapter framework. The fact that that adaption is annotation driven
isn't important to the client (or visible for that matter). I'll try
to make that more obvious.
Defaults are a good idea.
On Thursday, December 19, 2013, Georg Henzler wrote:
...The HealthCheckExecutor is only to be used by JMX and the
web console (and maybe at some point by some servlet), but not as part of
a
normal implementation project...
That's a very limiting view.
If you have spellchecking services for
Justin,
This seems like a really nice addition. I was working on something
similar using Java's Dynamic Proxy to allow injection from the
repository. The model is slightly different where instead of
annotating member variables, you annotate methods on an interface.
[
https://issues.apache.org/jira/browse/SLING-3297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Bogomolov updated SLING-3297:
--
Attachment: sling-mail-archive-server.zip
Sling-based mail archive server sample contribution
Hi Dan,
On Thu, Dec 19, 2013 at 12:37 PM, Daniel Klco dk...@apache.org wrote:
Justin,
This seems like a really nice addition. I was working on something
similar using Java's Dynamic Proxy to allow injection from the
repository. The model is slightly different where instead of
annotating
Hi Konrad,
Defaults have been implemented. Check the wiki.
Regards,
Justin
On Thu, Dec 19, 2013 at 12:21 PM, Konrad Windszus konra...@gmx.de wrote:
HI Justin,
thank a lot for that. I am assuming a lot of developers were waiting for just
that. Could you extend the wiki page with an example on
On 18.12.2013, at 21:44, Tobias Bocanegra tri...@apache.org 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
You have a good example here - I'm not sure though if you would really
call the health check before a spell check or if it is not better to
have good exception handling for the actual call of the spell checker if
things go wrong. What if the health check returns green and 20ms later
the
Hi Justin,
thanks a lot. I would like to see a section in the wiki where required
injections are described in detail. I guess in case for injected Sling values
which are not there the instantiation fails (i.e. adaptTo will return null).
What happens in case a default value is specified? In my
28 matches
Mail list logo
