Hi,
(this might be more a question for the JSR283 people, but I'd like to
have this community's opinion)
I recently implemented a JCR-based audit trail module, and making
application-level sense of the Events that an EventListener receives
required quite some efforts (and lazyness is a virtue,
Hi,
This would probably really be worth it. I also think of somehow
tagging the operations for example to provide more information in case
of item removal, where very little is actually available in the event
leading to guessing or having to keep caches.
On the other hand, save operations may
hi bertrand,
i agree that this would be interesting, and could get us to a certain extent
out of the method events issue.
if you dont mind and others feel like this would be a valuable addition
you could eventually send this as a public review comment to
[EMAIL PROTECTED] so i can include it in
Hi,
Clustering: The Object needs to be Serializable. You need to define
what happens if the class does not exist in the 'receiving' end.
Maybe you want to think about operations that don't require save(),
for example Workspace.move(..).
Thomas
[
https://issues.apache.org/jira/browse/JCR-1049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12520187
]
Stefan Guggisberg commented on JCR-1049:
mysql4.dll and mysql.ddl should have:
create unique index
On 8/16/07, David Nuescheler [EMAIL PROTECTED] wrote:
...if you dont mind and others feel like this would be a valuable addition
you could eventually send this as a public review comment to
[EMAIL PROTECTED] so i can include it in our digest
Ok, I'll send this as a public review comment
[
https://issues.apache.org/jira/browse/JCR-1049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Guggisberg resolved JCR-1049.
Resolution: Fixed
added 'character set latin1' to 'create table' statement
fixed in svn
Hi,
On 8/16/07, Bertrand Delacretaz [EMAIL PROTECTED] wrote:
Maybe session.save() and other save() methods could take an optional
Object parameter, that is made available in the observation Event with
a new getCargo() method?
Sounds interesting. Have you considered how something like that
On 8/16/07, Jukka Zitting [EMAIL PROTECTED] wrote:
Have you considered how something like that could
be implemented already now as a Jackrabbit-specific extension?...
One idea (that might also be better than my former proposal for
JSR283) would be to add an additional setEventCargo(Object)
Hi,
On 8/16/07, Bertrand Delacretaz [EMAIL PROTECTED] wrote:
On 8/16/07, Jukka Zitting [EMAIL PROTECTED] wrote:
Have you considered how something like that could
be implemented already now as a Jackrabbit-specific extension?...
One idea (that might also be better than my former
Hi,
Am Donnerstag, den 16.08.2007, 15:01 +0300 schrieb Jukka Zitting:
For now I'd just put the extra methods directly on the SessionImpl and
EventImpl classes. We can formalize them in a jackrabbit-api (or
jackrabbit-jsr283) extension interface if they seem useful to a big
enough audience.
Hi devs
I am using Magnolia CMS (with Jackrabbit 1.3.1) and have set up clustered
instance of JR using Oracle bundle PM.
After publishing a page I get following exception:
INFO openwfe.org.embed.impl.engine.AbstractEmbeddedParticipant
MgnlParticipant.java(consume:88) 16.08.2007 08:08:07
Hi,
On 8/16/07, Felix Meschberger [EMAIL PROTECTED] wrote:
Am Donnerstag, den 16.08.2007, 15:01 +0300 schrieb Jukka Zitting:
For now I'd just put the extra methods directly on the SessionImpl and
EventImpl classes. We can formalize them in a jackrabbit-api (or
jackrabbit-jsr283) extension
[
https://issues.apache.org/jira/browse/JCR-1050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12520257
]
Stefan Guggisberg commented on JCR-1050:
discussion on the dev list:
-- Forwarded message --
[
https://issues.apache.org/jira/browse/JCR-1050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12520258
]
Stefan Guggisberg commented on JCR-1050:
discussion on the dev list:
-- Forwarded message --
[
https://issues.apache.org/jira/browse/JCR-1050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12520259
]
Stefan Guggisberg commented on JCR-1050:
discussion on the dev list:
-- Forwarded message --
Workspace{Copy|Move}VersionableTest assumptions on versioning
-
Key: JCR-1065
URL: https://issues.apache.org/jira/browse/JCR-1065
Project: Jackrabbit
Issue Type: Bug
Exclude system index for queries that restrict the result set to nodetypes not
availble in the jcr:system subtree
---
Key: JCR-1066
URL:
[
https://issues.apache.org/jira/browse/JCR-1066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christoph Kiehl updated JCR-1066:
-
Attachment: patch.txt
This is an initial patch. I'm not fully satisfied with it because
[
https://issues.apache.org/jira/browse/JCR-1050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12520275
]
Stefan Guggisberg commented on JCR-1050:
paddy,
thanks for the patch, i appreciate your efforts.
i have a
Stefan Guggisberg (JIRA) wrote:
[
https://issues.apache.org/jira/browse/JCR-1050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12520257
]
Stefan Guggisberg commented on JCR-1050:
discussion on the dev list:
[
https://issues.apache.org/jira/browse/JCR-1066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christoph Kiehl updated JCR-1066:
-
Attachment: (was: patch.txt)
Exclude system index for queries that restrict the result set to
[
https://issues.apache.org/jira/browse/JCR-1050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12520309
]
Padraic Hannon commented on JCR-1050:
-
That makes sense, I was trying to eliminate duplication of code and ensure
[
https://issues.apache.org/jira/browse/JCR-1067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Padraic Hannon updated JCR-1067:
Comment: was deleted
Referenced beans in an object graph should be persisted by the ocm
Hi,
Currently Jackrabbit uses one persistence manager per workspace, and
one for versioning. That means the same persistence manager is used
for all sessions (in a workspace).
there should be a new manager per session, ie per usage thread.
While the current architecture has advantages, the
25 matches
Mail list logo
