Georg Henzler created SLING-4767:
Summary: Optional sub models are logged as warn if they cannot be
adapted
Key: SLING-4767
URL: https://issues.apache.org/jira/browse/SLING-4767
Project: Sling
[
https://issues.apache.org/jira/browse/SLING-4767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus reassigned SLING-4767:
--
Assignee: Konrad Windszus
Optional sub models are logged as warn if they cannot be
[
https://issues.apache.org/jira/browse/SLING-4751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14567172#comment-14567172
]
Michael Dürig commented on SLING-4751:
--
Nothing really. Just saying that we've seen
See https://builds.apache.org/job/sling-trunk-1.8/1159/changes
See https://builds.apache.org/job/sling-contrib-1.7/135/
[
https://issues.apache.org/jira/browse/SLING-4751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14567013#comment-14567013
]
Stefan Egli commented on SLING-4751:
I see two problems with the previous (current)
See https://builds.apache.org/job/sling-contrib-1.7/changes
[
https://issues.apache.org/jira/browse/SLING-4767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated SLING-4767:
---
Fix Version/s: Sling Models Impl 1.2.0
Sling Models API 1.2.0
Optional
[
https://issues.apache.org/jira/browse/SLING-4767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14567010#comment-14567010
]
Konrad Windszus commented on SLING-4767:
Instead I fixed it by introducing a new
[
https://issues.apache.org/jira/browse/SLING-4751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14567160#comment-14567160
]
Carsten Ziegeler commented on SLING-4751:
-
Yes, one of the benefits of this
[
https://issues.apache.org/jira/browse/SLING-4751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14567162#comment-14567162
]
Carsten Ziegeler commented on SLING-4751:
-
What exactly do you have in mind here?
See https://builds.apache.org/job/sling-trunk-1.8/1160/changes
Changes:
[bdelacretaz] SLING-4757 - test invalid encoding
[bdelacretaz] SLING-4757 - remove duplicate test
[bdelacretaz] SLING-4757 - new tests for commons.contentdetection, contributed
by Petr Shypila, thanks!
[
https://issues.apache.org/jira/browse/SLING-4751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14567165#comment-14567165
]
Stefan Egli commented on SLING-4751:
With OAK-2829 the goal is to speed up external
On Sun, May 31, 2015 at 8:07 PM, Petr Shypila ikrump...@gmail.com wrote:
...After I changed
in my test class service's reference to interface type instead of concrete
realisation the problem has been disappeared...
Cool! And no problem for asking here and replying yourself, that
happens often
[
https://issues.apache.org/jira/browse/SLING-4755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14567073#comment-14567073
]
Stefan Egli commented on SLING-4755:
According to
See https://builds.apache.org/job/sling-contrib-1.7/134/
[
https://issues.apache.org/jira/browse/SLING-4751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14567030#comment-14567030
]
Michael Dürig commented on SLING-4751:
--
Does this new mechanism provide a way to
[
https://issues.apache.org/jira/browse/SLING-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14567107#comment-14567107
]
Bertrand Delacretaz commented on SLING-4757:
I have committed your unit tests
[
https://issues.apache.org/jira/browse/SLING-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14567455#comment-14567455
]
Bertrand Delacretaz commented on SLING-4757:
I have now committed your
See https://builds.apache.org/job/sling-trunk-1.7/1872/changes
[
https://issues.apache.org/jira/browse/SLING-4541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz updated SLING-4541:
---
Assignee: Petr Shypila
Provide an extensive test suite for the JCR content loader
One thing we have to think of is how to use pagination and sorting.
A search could go across the whole resource tree hitting different
resource providers. For example one use case is getting all vanity paths.
Sorting such a search is possible, the resource resolver implementation
always picks one
[
https://issues.apache.org/jira/browse/SLING-4751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14567464#comment-14567464
]
Stefan Egli commented on SLING-4751:
Maybe we can group all of this into different use
See https://builds.apache.org/job/sling-trunk-1.8/1162/changes
See https://builds.apache.org/job/sling-trunk-1.7/1873/changes
Hi,
Our summer of code student Petr is making good progress, see
SLING-4757 for example where he's helped improve the test coverage.
If people have suggestions about important modules that are in need of
more test coverage, let us know!
If there are no specific suggestions I'll suggest that
[
https://issues.apache.org/jira/browse/SLING-4751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14567318#comment-14567318
]
Carsten Ziegeler commented on SLING-4751:
-
I think hitting the queue limit is the
[
https://issues.apache.org/jira/browse/SLING-4710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14567286#comment-14567286
]
Konrad Windszus commented on SLING-4710:
In rev. 1682896 I made the
[
https://issues.apache.org/jira/browse/SLING-4737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus resolved SLING-4737.
Resolution: Fixed
Fix Version/s: Sling Models Impl 1.2.0
Add JSR305 nullness
[
https://issues.apache.org/jira/browse/SLING-4751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14567367#comment-14567367
]
Carsten Ziegeler commented on SLING-4751:
-
I also think, we should drop the event
See https://builds.apache.org/job/sling-trunk-1.7/1871/changes
Changes:
[bdelacretaz] SLING-4757 - factor out Pax config
[bdelacretaz] SLING-4757 - new integration tests for commons.contentdetection,
contributed by Petr Shypila, thanks!
--
[...truncated
[
https://issues.apache.org/jira/browse/SLING-4768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-4768.
-
Resolution: Fixed
Assignee: Carsten Ziegeler
Features, run modes, artifact groups
See https://builds.apache.org/job/sling-contrib-1.7/changes
See https://builds.apache.org/job/sling-trunk-1.8/changes
[
https://issues.apache.org/jira/browse/SLING-4768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14567607#comment-14567607
]
Carsten Ziegeler commented on SLING-4768:
-
The run modes for a feature should be
[
https://issues.apache.org/jira/browse/SLING-4768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14567607#comment-14567607
]
Carsten Ziegeler edited comment on SLING-4768 at 6/1/15 5:26 PM:
Stefan Seifert created SLING-4769:
-
Summary: Osgi Mock: Add support for bundle headers
Key: SLING-4769
URL: https://issues.apache.org/jira/browse/SLING-4769
Project: Sling
Issue Type:
See https://builds.apache.org/job/sling-contrib-1.7/138/
See https://builds.apache.org/job/sling-trunk-1.8/changes
See https://builds.apache.org/job/sling-contrib-1.7/139/
On 30.05.2015, at 01:31, Stefan Seifert sseif...@pro-vision.de wrote:
And this is a typical case where abstraction fails: performance. Which is
extremely important for queries.
Well, this is a broad statement and neither true nor wrong.
i'm the same opinion as carsten. i did a quick
[
https://issues.apache.org/jira/browse/SLING-4756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14567981#comment-14567981
]
Stefan Seifert commented on SLING-4756:
---
Completed: At revision: 1683002
i
Carsten Ziegeler created SLING-4770:
---
Summary: Create DTOs for state inspection
Key: SLING-4770
URL: https://issues.apache.org/jira/browse/SLING-4770
Project: Sling
Issue Type: Improvement
See https://builds.apache.org/job/sling-trunk-1.7/1877/changes
Changes:
[sseifert] SLING-4756 add support for filtering via felix.framework FilterImpl
implementation
[sseifert] SLING-4769 Osgi Mock: Add support for bundle headers
--
[...truncated 10791
But do you have queries across resource providers? Do you know the
implementation complexity and performance limitations you are asking for?
no, i never required searching across different providers in the past, it would
even be ok for me to not support cross-provider searching in the beginning
On 01.06.2015, at 08:50, Carsten Ziegeler cziege...@apache.org wrote:
So I think, we should support sorting across providers
This means sorting will be very slow. Since you have to re-sort the partial
results on the sling level without usage of an index.
Cheers,
Alex
[
https://issues.apache.org/jira/browse/SLING-4605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert updated SLING-4605:
--
Fix Version/s: Testing Sling Mock 1.3.2
cool, this was a simple adapter
Completed: At
See https://builds.apache.org/job/sling-contrib-1.7/140/
Am 01.06.15 um 13:58 schrieb Alexander Klimetschek:
But do you have queries across resource providers? Do you know the
implementation complexity and performance limitations you are asking for?
If you have different resource providers with their own search index, and you
have to aggregate
See https://builds.apache.org/job/sling-trunk-1.8/changes
See https://builds.apache.org/job/sling-trunk-1.8/changes
Am 01.06.15 um 14:00 schrieb Alexander Klimetschek:
On 01.06.2015, at 08:50, Carsten Ziegeler cziege...@apache.org wrote:
So I think, we should support sorting across providers
This means sorting will be very slow. Since you have to re-sort the partial
results on the sling level without
52 matches
Mail list logo
