Drop PropertyState?

Hi, An idea I had when waking up this morning: How about if we dropped the PropertyState class and related stuff like PropertyId and the per-property access methods in persistence managers and elsewhere? The rationale? See below: 1) Bundles are already the recommended way for storing content on

Re: Drop PropertyState?

hi jukka, generally i think this might be a good idea, at least for jsr283, where item.save() item.refresh() is dropped. it's hard to guess all implications, since the propertystate concept is widely used throughout the core. for example the changelog records all modifications of property states,

datastore question

hi .. i am testing the datastore (filedatastore) and i found that if i configure a workspace with the old org.apache.jackrabbit.core.state.obj.ObjectPersistenceManager the content are stored in the blob folder of the workspace and in the datastore. is this works as designed or is this a bug ?

[jira] Commented: (JCR-1604) NameImpl improvements

[ https://issues.apache.org/jira/browse/JCR-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12597392#action_12597392 ] Jukka Zitting commented on JCR-1604: I chatted with Stefan about this, and he mentioned

Re: Drop PropertyState?

Hi, On Fri, May 16, 2008 at 11:01 AM, Tobias Bocanegra [EMAIL PROTECTED] wrote: i think this will be a huge rewrite which will imply months of instability and testing, and i frankly don't know if it's worth it. additionally, wouldn't it compromise the NG data model? I think this would fit

[jira] Created: (JCR-1607) Add a NamespaceHelper in jcr-commons

Add a NamespaceHelper in jcr-commons Key: JCR-1607 URL: https://issues.apache.org/jira/browse/JCR-1607 Project: Jackrabbit Issue Type: New Feature Components: jackrabbit-core,

[jira] Created: (JCR-1608) JSR 283: Workspace Management

JSR 283: Workspace Management - Key: JCR-1608 URL: https://issues.apache.org/jira/browse/JCR-1608 Project: Jackrabbit Issue Type: Sub-task Reporter: Stefan Guggisberg Assignee: Stefan

Re: Memory use of item states

hi jukka, On Fri, May 16, 2008 at 3:44 PM, Jukka Zitting [EMAIL PROTECTED] wrote: Hi, I recently did some quick benchmarking and testing related to the memory requirements of large transient spaces. My main test case was: Node root = ...; for (int i = 0; i 100; i++) { Node

[jira] Closed: (JCR-1610) jsr170-0.12.pdf file referenes Object called Ticket not Session as seems to be coded in Jackrabbit

[ https://issues.apache.org/jira/browse/JCR-1610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke closed JCR-1610. --- Resolution: Invalid It appears you are looking at an ancient draft of the spec. I can't find the term

[jira] Commented: (JCR-1610) jsr170-0.12.pdf file referenes Object called Ticket not Session as seems to be coded in Jackrabbit

[ https://issues.apache.org/jira/browse/JCR-1610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12597537#action_12597537 ] Jukka Zitting commented on JCR-1610: Yeah, Ticket was abandoned way before JCR 1.0 became

[jira] Commented: (JCR-1571) DavMethodBase#getResponseException fails if the body is not (valid) XML

[ https://issues.apache.org/jira/browse/JCR-1571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12597597#action_12597597 ] Julio Castillo commented on JCR-1571: - Thank you Angela. The fix works. Thanks again for