[
https://issues.apache.org/jira/browse/JCRRMI-7?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting reassigned JCRRMI-7:
--
Assignee: (was: Jukka Zitting)
> Use remote callbacks instead of polling for observat
[
https://issues.apache.org/jira/browse/JCR-3822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke closed JCR-3822.
---
> Observation tests sometimes time out
> -
>
>
[
https://issues.apache.org/jira/browse/JCR-3823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke closed JCR-3823.
---
> Observation tests sporadically fail
> ---
>
>
[
https://issues.apache.org/jira/browse/JCR-4046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke closed JCR-4046.
---
> Improve observation of files
>
>
> K
[
https://issues.apache.org/jira/browse/JCR-4293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated JCR-4293:
Labels: (was: candidate_jcr_2_8)
> jackrabbit-core: observation tests should not rely
http://svn.apache.org/r1830814]
2.16: [r1831734|http://svn.apache.org/r1831734]
2.14: [r1833902|http://svn.apache.org/r1833902]
2.12: [r1840939|http://svn.apache.org/r1840939]
> jackrabbit-core: observation tests should not rely on mix:lockable mix
[
https://issues.apache.org/jira/browse/JCR-4293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated JCR-4293:
Labels: candidate_jcr_2_8 (was: candidate_jcr_2_10)
> jackrabbit-core: observation tests should
[
https://issues.apache.org/jira/browse/JCR-4293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated JCR-4293:
Fix Version/s: 2.10.9
> jackrabbit-core: observation tests should not rely on mix:lockable mi
http://svn.apache.org/r1831734]
2.14: [r1833902|http://svn.apache.org/r1833902]
> jackrabbit-core: observation tests should not rely on mix:lockable mixin type
> -
>
> Key: JCR-4293
>
[
https://issues.apache.org/jira/browse/JCR-4293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated JCR-4293:
Fix Version/s: 2.12.10
> jackrabbit-core: observation tests should not rely on mix:lockable mi
[
https://issues.apache.org/jira/browse/JCR-4293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated JCR-4293:
Labels: candidate_jcr_2_10 (was: candidate_jcr_2_12)
> jackrabbit-core: observation tests sho
it-core: observation tests should not rely on mix:lockable mixin type
> -
>
> Key: JCR-4293
> URL: https://issues.apache.org/jira/browse/JCR-4293
> Project: Jackrab
[
https://issues.apache.org/jira/browse/JCR-4293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated JCR-4293:
Fix Version/s: 2.14.6
> jackrabbit-core: observation tests should not rely on mix:lockable mi
[
https://issues.apache.org/jira/browse/JCR-4293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated JCR-4293:
Labels: candidate_jcr_2_12 (was: candidate_jcr_2_14)
> jackrabbit-core: observation tests sho
0 PM:
--
trunk: [r1830814|http://svn.apache.org/r1830814]
2.16: [r1831734|http://svn.apache.org/r1831734]
was (Author: reschke):
trunk: [r1830814|http://svn.apache.org/r1830814]
> jackrabbit-core: observation tests should not rely on mix:lockable mix
[
https://issues.apache.org/jira/browse/JCR-4293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated JCR-4293:
Fix Version/s: 2.16.2
> jackrabbit-core: observation tests should not rely on mix:lockable mixin t
[
https://issues.apache.org/jira/browse/JCR-4293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated JCR-4293:
Labels: candidate_jcr_2_14 (was: candidate_jcr_2_16)
> jackrabbit-core: observation tests should
[
https://issues.apache.org/jira/browse/JCR-4293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke closed JCR-4293.
---
> jackrabbit-core: observation tests should not rely on mix:lockable mixin t
0814]
> jackrabbit-core: observation tests should not rely on mix:lockable mixin type
> -
>
> Key: JCR-4293
> URL: https://issues.apache.org/jira/browse/JCR-4293
>
[
https://issues.apache.org/jira/browse/JCR-4293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke resolved JCR-4293.
-
Resolution: Fixed
Fix Version/s: 2.17.3
> jackrabbit-core: observation tests should not r
[
https://issues.apache.org/jira/browse/JCR-4293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated JCR-4293:
Labels: candidate_jcr_2_16 (was: )
> jackrabbit-core: observation tests should not rely
[
https://issues.apache.org/jira/browse/JCR-4293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated JCR-4293:
Component/s: core
> jackrabbit-core: observation tests should not rely on mix:lockable mixin t
Julian Reschke created JCR-4293:
---
Summary: jackrabbit-core: observation tests should not rely on
mix:lockable mixin type
Key: JCR-4293
URL: https://issues.apache.org/jira/browse/JCR-4293
Project
was (Author: reschke):
trunk: [r1807244|http://svn.apache.org/r1807244]
2.14: [r1807346|http://svn.apache.org/r1807346]
2.12: [r1810005|http://svn.apache.org/r1810005]
2.10: [r1811792|http://svn.apache.org/r1811792]
2.8: [r1818268|http://svn.apache.org/r1818268]
> Unable to receive observation even
[
https://issues.apache.org/jira/browse/JCR-4173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated JCR-4173:
Labels: (was: candidate_jcr_2_6)
> Unable to receive observation events when connecting via Da
[
https://issues.apache.org/jira/browse/JCR-4173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated JCR-4173:
Fix Version/s: 2.6.10
> Unable to receive observation events when connecting via Da
http://svn.apache.org/r1807244]
2.14: [r1807346|http://svn.apache.org/r1807346]
2.12: [r1810005|http://svn.apache.org/r1810005]
2.10: [r1811792|http://svn.apache.org/r1811792]
> Unable to receive observation events when connecting vi
[
https://issues.apache.org/jira/browse/JCR-4173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated JCR-4173:
Fix Version/s: 2.8.7
> Unable to receive observation events when connecting via Da
[
https://issues.apache.org/jira/browse/JCR-4173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated JCR-4173:
Labels: candidate_jcr_2_6 (was: candidate_jcr_2_6 candidate_jcr_2_8)
> Unable to receive observat
candidate_jcr_2_8)
> Unable to receive observation events when connecting via DavEx
> --
>
> Key: JCR-4173
> URL: https://issues.apache.org/jira/browse/JCR-4173
> Project: Jackrabbit
http://svn.apache.org/r1807346]
2.12: [r1810005|http://svn.apache.org/r1810005]
> Unable to receive observation events when connecting via DavEx
> --
>
> Key: JCR-4173
> URL: https://issues.apache.
[
https://issues.apache.org/jira/browse/JCR-4173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated JCR-4173:
Fix Version/s: 2.10.7
> Unable to receive observation events when connecting via Da
receive observation events when connecting via DavEx
> --
>
> Key: JCR-4173
> URL: https://issues.apache.org/jira/browse/JCR-4173
> Project: Jackrabbit Content Repository
>
candidate_jcr_2_12 candidate_jcr_2_6 candidate_jcr_2_8)
> Unable to receive observation events when connecting via DavEx
> --
>
> Key: JCR-4173
> URL: https://issues.apache.org/jira/browse/JCR-4173
>
[
https://issues.apache.org/jira/browse/JCR-4173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated JCR-4173:
Fix Version/s: 2.12.8
> Unable to receive observation events when connecting via Da
[
https://issues.apache.org/jira/browse/JCR-4173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke closed JCR-4173.
---
> Unable to receive observation events when connecting via Da
7244]
2.14: [r1807346|http://svn.apache.org/r1807346]
> Unable to receive observation events when connecting via DavEx
> --
>
> Key: JCR-4173
> URL: https://issues.apache.org/j
ive observation events when connecting via DavEx
> --
>
> Key: JCR-4173
> URL: https://issues.apache.org/jira/browse/JCR-4173
> Project: Jackrabbit Content Repository
>
[
https://issues.apache.org/jira/browse/JCR-4173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated JCR-4173:
Fix Version/s: 2.14.3
> Unable to receive observation events when connecting via Da
: candidate_jcr_2_10 candidate_jcr_2_12
candidate_jcr_2_14 candidate_jcr_2_6 candidate_jcr_2_8)
> Unable to receive observation events when connecting via DavEx
> --
>
> Key: JCR-4173
> URL: https://is
[
https://issues.apache.org/jira/browse/JCR-4173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16153525#comment-16153525
]
Robert Munteanu commented on JCR-4173:
--
I can confirm that the observation events
> Unable to receive observation events when connecting via DavEx
> --
>
> Key: JCR-4173
> URL: https://issues.apache.org/jira/browse/JCR-4173
> Project: Jackrabbit Content Repositor
7244]
> Unable to receive observation events when connecting via DavEx
> --
>
> Key: JCR-4173
> URL: https://issues.apache.org/jira/browse/JCR-4173
> Project: Jackrab
[
https://issues.apache.org/jira/browse/JCR-4173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated JCR-4173:
Component/s: (was: jackrabbit-spi2dav)
> Unable to receive observation events when connecting
[
https://issues.apache.org/jira/browse/JCR-4173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke resolved JCR-4173.
-
Resolution: Fixed
Fix Version/s: 2.15.6
> Unable to receive observation events w
[
https://issues.apache.org/jira/browse/JCR-4173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated JCR-4173:
Fix Version/s: 2.16
> Unable to receive observation events when connecting via Da
(was: )
> Unable to receive observation events when connecting via DavEx
> --
>
> Key: JCR-4173
> URL: https://issues.apache.org/jira/browse/JCR-4173
> Project: Jackrabbit
2.8.5
2.14.2
> Unable to receive observation events when connecting via DavEx
> --
>
> Key: JCR-4173
> URL: https://issues.apache.org/jira/browse/JCR-4173
>
payload
being malformed. It also manages to roundtrip the jcr:primaryType information
provided by Oak.
But:
- missing unit test
- does not handle array values such as for mixinTypes in oak
- does not handle values that do not parse as JCR paths
> Unable to receive observation events w
red a separate issue.
For now I'll concentrate on just fixing the problem of invalid XML being
generated.
> Unable to receive observation events when connecting via DavEx
> --
>
> Key: JCR-41
ive observation events when connecting via DavEx
> --
>
> Key: JCR-4173
> URL: https://issues.apache.org/jira/browse/JCR-4173
> Project: Jackrabbit Content Repository
>
[
https://issues.apache.org/jira/browse/JCR-4173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated JCR-4173:
Affects Version/s: 2.15.5
> Unable to receive observation events when connecting via Da
[
https://issues.apache.org/jira/browse/JCR-4173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated JCR-4173:
Issue Type: Bug (was: Test)
> Unable to receive observation events when connecting via Da
fail if the path values contain elements in namespaces.
> Unable to receive observation events when connecting via DavEx
> --
>
> Key: JCR-4173
> URL: https://issues.apache.org/jira/browse/JC
ot
prefixed), but might fail if the path values contain elements in namespaces.
> Unable to receive observation events when connecting via DavEx
> --
>
> Key: JCR-4173
> URL: https:/
sing custom field names in the info
map; and these do not map properly to XML node names.
> Unable to receive observation events when connecting via DavEx
> --
>
> Key: JCR-4173
> URL: https:
able to receive observation events when connecting via DavEx
> --
>
> Key: JCR-4173
> URL: https://issues.apache.org/jira/browse/JCR-4173
> Project: Jackrabbit Content Repository
>
[
https://issues.apache.org/jira/browse/JCR-4173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated JCR-4173:
Affects Version/s: (was: 1.6.4)
> Unable to receive observation events when connecting via Da
Component/s: (was: remoting)
Workflow: no-reopen-closed, patch-avail (was: no-reopen-closed)
Key: JCR-4173 (was: OAK-6583)
Project: Jackrabbit Content Repository (was: Jackrabbit Oak)
> Unable to receive observation events when connecting via Da
[
https://issues.apache.org/jira/browse/JCR-4173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke reassigned JCR-4173:
---
Assignee: Julian Reschke
> Unable to receive observation events when connecting via Da
[
https://issues.apache.org/jira/browse/JCR-4012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated JCR-4012:
Fix Version/s: 2.14
> Include initial cost in stats for observation process
[
https://issues.apache.org/jira/browse/JCR-4046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Egli resolved JCR-4046.
--
Resolution: Duplicate
Will be handled in OAK-5021
> Improve observation of fi
ated and we should rather do
it based on OAK-5013
> Improve observation of files
>
>
> Key: JCR-4046
> URL: https://issues.apache.org/jira/browse/JCR-4046
> Project: Jackrabbit Content Repository
>
be achieved.
Based on OAK-5011 we could then, similarly as suggested in JCR-4044, implement
this aggregation feature request in the oak-jcr level, independent of
jackrabbit: attached [^JCR-4046.v2.patch] which illustrates this (this is based
on the patch attached
d to implement that. And as
discussed offline we could provide an oak-jcr utility class that hooks in this
functionality instead of 'dirtying' the JackrabbitEventFilter.
So the filtering can be done quite straight forward (with the oak-core
observation filter framework).
What's pe
so
wondering what would happen with {{nt:linkedFile}}..
> Improve observation of files
>
>
> Key: JCR-4046
> URL: https://issues.apache.org/jira/browse/JCR-4046
> Project: Jackrabbit Content Rep
ge should be reported on the parent. For add/remove this is
not needed as explained in the summary and for other node types it would be
wrong and break existing code.
> Improve observation of files
>
>
> Key: JCR-4046
>
Test#filterPropertyOfChild}}, which
demonstrates how to get events for nodes that have a property {{./b/c/foo=bar}}.
> Improve observation of files
>
>
> Key: JCR-4046
> URL: https://issues.apache.org/jira/browse/JCR-4046
&g
d path
'jcr:content' then root node for that path should be reindexed. This was solved
with a Matcher like pattern which transitions from one state to another as diff
editor traverse down the tree
> Improve observation of files
>
>
>
any change happens in aggregated path
'jcr:content' then root node for that path should be reindexed. This was solved
with a Matcher like pattern which transitions from one state to another as diff
editor traverse down the tree
> Improve obs
> Improve observation of files
>
>
> Key: JCR-4046
> URL: https://issues.apache.org/jira/browse/JCR-4046
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: c
> Improve observation of files
>
>
> Key: JCR-4046
> URL: https://issues.apache.org/jira/browse/JCR-4046
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: co
d by registering two listeners, one
eg for {{/a/**/*.file}} and one for {{/a/**/*.file/jcr:content}} ? The
advantage from an oak point of view would be that this is quite a special case
and perhaps not limited to nt:file but all its sub node types etc.
> Improve observation o
efit/be replaced with glob
support as suggested in JCR-4044
> extend path and property filtering of observation event
> ---
>
> Key: JCR-4016
> URL: https://issues.apache.org/jira/browse/JCR-4016
&g
s about a variation of the filter
of what one is interested in, while JCR-4046 is about reporting a change on a
different node than where it actually happened.
> Improve observation of files
>
>
> Key: JCR-4046
> URL: h
than JCR-4035 - it's true that the parent node
type plays a role, but the important thing is, the change should be reported on
the parent node, not the node (jcr:content node) that changed
> Improve observation of files
>
>
> Key: JCR-
sion) of JCR-4035. Perhaps
it's good enough to just allow having the filters be applied to grand-parent
and not further up the hierarchy.
> Improve observation of files
>
>
> Key: JCR-4046
> URL: https://issues.ap
Carsten Ziegeler created JCR-4046:
-
Summary: Improve observation of files
Key: JCR-4046
URL: https://issues.apache.org/jira/browse/JCR-4046
Project: Jackrabbit Content Repository
Issue Type
porting parentNodeTypes filtering in observation
>
>
> Key: JCR-4035
> URL: https://issues.apache.org/jira/browse/JCR-4035
> Project: Jackrabbit Content Repository
>
/ JCR-4017
> consider supporting parentNodeTypes filtering in observation
>
>
> Key: JCR-4035
> URL: https://issues.apache.org/jira/browse/JCR-4035
> Project: Jackrabbit Content Repo
onsider supporting parentNodeTypes filtering in observation
>
>
> Key: JCR-4035
> URL: https://issues.apache.org/jira/browse/JCR-4035
> Project: Jackrabbit Content Repository
rand-grandparent etc
hierarchy - afaics currently only the direct parent's node type counts?
> consider supporting parentNodeTypes filtering in observation
>
>
> Key: JCR-4035
> URL: h
s is how node type filtering is done. Filtering is per specification done on
the associated parent node. See also the Javadoc on
{{ObservationManager#addEventListener}}.
> consider supporting parentNodeTypes filtering in obse
Stefan Egli created JCR-4035:
Summary: consider supporting parentNodeTypes filtering in
observation
Key: JCR-4035
URL: https://issues.apache.org/jira/browse/JCR-4035
Project: Jackrabbit Content
Stefan Egli created JCR-4016:
Summary: extend path and property filtering of observation event
Key: JCR-4016
URL: https://issues.apache.org/jira/browse/JCR-4016
Project: Jackrabbit Content Repository
)}}.
Done in trunk: http://svn.apache.org/r1759270
> Include initial cost in stats for observation processing
>
>
> Key: JCR-4012
> URL: https://issues.apache.org/jira/browse/JCR-4012
>
[
https://issues.apache.org/jira/browse/JCR-4012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger updated JCR-4012:
--
Labels: observation (was: )
> Include initial cost in stats for observation process
er}} that allows client code to record
producer time outside of the tracker.
> Include initial cost in stats for observation processing
>
>
> Key: JCR-4012
> URL: https://issues.apache.
Marcel Reutegger created JCR-4012:
-
Summary: Include initial cost in stats for observation processing
Key: JCR-4012
URL: https://issues.apache.org/jira/browse/JCR-4012
Project: Jackrabbit Content
CI
> Observation tests sporadically fail
> ---
>
> Key: JCR-3823
> URL: https://issues.apache.org/jira/browse/JCR-3823
> Project: Jackrabbit Content Repository
> Issue Type: Bug
>
CI
> Observation tests sometimes time out
> -
>
> Key: JCR-3822
> URL: https://issues.apache.org/jira/browse/JCR-3822
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
ime series for observation processing
> --
>
> Key: JCR-3859
> URL: https://issues.apache.org/jira/browse/JCR-3859
> Project: Jackrabbit Content Repository
>
Michael Dürig created JCR-3859:
--
Summary: Extend EventListenerMBean to report time series for
observation processing
Key: JCR-3859
URL: https://issues.apache.org/jira/browse/JCR-3859
Project: Jackrabbit
[
https://issues.apache.org/jira/browse/JCR-3822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dürig updated JCR-3822:
---
Labels: observation test (was: observation)
> Observation tests sometimes time
[
https://issues.apache.org/jira/browse/JCR-3823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dürig updated JCR-3823:
---
Labels: observation test (was: observation)
> Observation tests sporadically f
ures with
{{testRenameEventHandling}}, which also used the {{EventResult}} class. After
[refactoring |
https://github.com/apache/jackrabbit-oak/commit/98eeebc5572ae4969a78dcc57ca589345a7cda51]
using latches and synchronized access to the shared {{events}} field things
improved considerably.
> Obser
pens-before relation. The JavaDoc of the class does not mention it, but
I'm pretty confident the memory consistency effects are the same as the
equivalent
[Semaphore|http://docs.oracle.com/javase/7/docs/api/java/util/concurrent/Semaphore.html]
in the JDK.
> Observation tests spora
Michael Dürig created JCR-3823:
--
Summary: Observation tests sporadically fail
Key: JCR-3823
URL: https://issues.apache.org/jira/browse/JCR-3823
Project: Jackrabbit Content Repository
Issue Type
Michael Dürig created JCR-3822:
--
Summary: Observation tests sometimes time out
Key: JCR-3822
URL: https://issues.apache.org/jira/browse/JCR-3822
Project: Jackrabbit Content Repository
Issue
eason why an implementation shouldn't
be allowed to pass more information than required.
I'd say we create an issue for JCR 2.1 and propose a weaker contract.
Regards
Marcel
On 08/07/14 17:52, "Michael Dürig" wrote:
Hi,
Often it would be helpful if observation eve
1 - 100 of 247 matches
Mail list logo
