Reorganize core test suite
--
Key: JCR-1203
URL: https://issues.apache.org/jira/browse/JCR-1203
Project: Jackrabbit
Issue Type: Improvement
Components: jackrabbit-core
Reporter: Jukka Zitting
[
https://issues.apache.org/jira/browse/JCR-1084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
fabrizio giustina updated JCR-1084:
---
Attachment: JCR-1084.diff
Very simple patch against current 1.4 trunk.
This small change
Marcel Reutegger wrote:
...
I'm working on a proposal that introduces a Subscription interface to
the SPI, which should solve the above issue.
here's a sneak preview:
http://people.apache.org/~mreutegg/spi-event/proposal.png
...
OK, as far as I understand this, we pass a Subscription
Redesign SPI observation
Key: JCR-1204
URL: https://issues.apache.org/jira/browse/JCR-1204
Project: Jackrabbit
Issue Type: Improvement
Components: SPI
Reporter: Marcel Reutegger
On 11/1/07, Padraic Hannon [EMAIL PROTECTED] wrote:
I have been reviewing the implementation I submitted for mixin support
in JCR-1100 and am struggling with how to proceed. On the one hand I
think the implementation that was submitted is nice since it has some
amount of type safety and
[
https://issues.apache.org/jira/browse/JCR-1204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger updated JCR-1204:
--
Attachment: JSR-1204.patch
Redesign SPI observation
[
https://issues.apache.org/jira/browse/JCR-1204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger updated JCR-1204:
--
Attachment: JSR-1204.patch
Redesign SPI observation
Hi,
On 11/2/07, Felix Meschberger [EMAIL PROTECTED] wrote:
If we are it, how about being able to stop a workspace or even destroy
it through API ?
That would be JCR-601.
Properly removing a workspace is quite tricky, especially if you want
to clean out the persistence store and query index
[
https://issues.apache.org/jira/browse/JCR-1201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12539650
]
Jukka Zitting commented on JCR-1201:
This seems like a recipe for complex bootstrapping issues... I see the use
[
https://issues.apache.org/jira/browse/JCR-1204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger updated JCR-1204:
--
Attachment: (was: JSR-1204.patch)
Redesign SPI observation
[
https://issues.apache.org/jira/browse/JCR-1195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting resolved JCR-1195.
Resolution: Won't Fix
Assignee: Jukka Zitting
Resolving as Won't Fix. You can have a dash in
[
https://issues.apache.org/jira/browse/JCR-1084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting resolved JCR-1084.
Resolution: Fixed
Resolved in revision 591404.
Maintan a stable ordering of properties in xml
[
https://issues.apache.org/jira/browse/JCR-1154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12539555
]
Thomas Mueller commented on JCR-1154:
-
In revision 591286, the DataStore throws DataStoreException instead of
Hi,
As described in JCR-1203, I'm modifying the test suite in jackrabbit-core.
As of revision 591280 all test cases have been moved from the normal
Maven test phase to the pre-integration-test and integration-test
phases. I'm planning to move real unit tests (i.e. tests that don't
require the
Jukka Zitting wrote:
Hi,
On 11/1/07, Julian Reschke [EMAIL PROTECTED] wrote:
Proposal: document that getEvents only needs to accept EventFilter
objects created by the same SPI implementation for the same SessionInfo
(this reflects reality in JCR2SPI)
+1 There's no guarantee that a remote
Workspace auto-create
-
Key: JCR-1205
URL: https://issues.apache.org/jira/browse/JCR-1205
Project: Jackrabbit
Issue Type: New Feature
Components: config, jackrabbit-core
Reporter: Jukka Zitting
Hi,
If we are it, how about being able to stop a workspace or even destroy
it through API ?
Regards
Felix
Am Freitag, den 02.11.2007, 09:28 -0700 schrieb Jukka Zitting (JIRA):
Workspace auto-create
-
Key: JCR-1205
URL:
Julian Reschke wrote:
Question: do we expect many cases in which a client stops listening for
events, but keeps the JCR session open? In this case it might be good if
we could indicate that an EventFilter is not going to be used anymore,
for instance using a dispose() method.
this is
Hi.
I think the issue I mentioned in
http://www.mail-archive.com/dev@jackrabbit.apache.org/msg08520.html
could be solved by integrating the data store with the current save mechanism,
so when you do a
save, you also get an atomic update on the timestamps of the transient items in
the data
[
https://issues.apache.org/jira/browse/JCR-1126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rama Krishna updated JCR-1126:
--
Attachment: workspace-v1.2.xml
repository.xml
jaas.config
Hi,
We are
[
https://issues.apache.org/jira/browse/JCR-1052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12539799
]
Filippo Fratoni commented on JCR-1052:
--
Sorry for very late answer.
I don't consider this request as Bug but
[
https://issues.apache.org/jira/browse/JCR-1161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrzej Zydron updated JCR-1161:
Attachment: azydron.vcf
Hi Roy,
The Mac OS X test failure is due to Xalan-*2.7.0.jar in
[
https://issues.apache.org/jira/browse/JCR-1161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrzej Zydron updated JCR-1161:
Attachment: azydron.vcf
Hi Julian,
I get th same error on Mac OS X 10.4.10 (8R2232) + Java
23 matches
Mail list logo
