[jira] Subscription: open issues

2006-04-15 Thread jira
Issue Subscription Filter: open issues (49 issues) Open Issues for Apache Jackrabbit Subscriber: jackrabbitdev Key Summary JCR-402 release module jackrabbit-bdb 1.0 http://issues.apache.org/jira/browse/JCR-402 JCR-401 contrib/bdb-persistence: update berkeleydb version

[jira] Commented: (JCR-402) release module jackrabbit-bdb 1.0

2006-04-15 Thread Alexandru Popescu (JIRA)
[ http://issues.apache.org/jira/browse/JCR-402?page=comments#action_12374660 ] Alexandru Popescu commented on JCR-402: --- I added my vote for it (I'm one of those users :-) ). ./alex -- .w( the_mindstorm )p. > release module jackrabbit-bdb 1.0 > -

[jira] Commented: (JCR-401) contrib/bdb-persistence: update berkeleydb version

2006-04-15 Thread Alexandru Popescu (JIRA)
[ http://issues.apache.org/jira/browse/JCR-401?page=comments#action_12374659 ] Alexandru Popescu commented on JCR-401: --- I've been using 2.0.90 for a few months already without any problems. ./alex -- .w( the_mindstorm )p. > contrib/bdb-persistence:

[jira] Subscription: open issues

2006-04-15 Thread jira
Issue Subscription Filter: open issues (46 issues) Open Issues for Apache Jackrabbit Subscriber: jackrabbitdev Key Summary JCR-399 DBFileSystem database connections strings stored in database http://issues.apache.org/jira/browse/JCR-399 JCR-398 maven2 repository

Re: residual definition xml implementation

2006-04-15 Thread Jukka Zitting
Hi, On 4/15/06, Greg Kick <[EMAIL PROTECTED]> wrote: > well, i'm glad that jackrabbit behaves correctly internally. the > reason i brought this up originally was because NodeTypeWriter > creates documents with the *. i had wanted to create an xml schema > to check that a node definition was vali

Re: residual definition xml implementation

2006-04-15 Thread Greg Kick
well, i'm glad that jackrabbit behaves correctly internally. the reason i brought this up originally was because NodeTypeWriter creates documents with the *. i had wanted to create an xml schema to check that a node definition was valid (i needed xml, not cnd). so, i figured that i would

[jira] Created: (JCR-402) release module jackrabbit-bdb 1.0

2006-04-15 Thread fabrizio giustina (JIRA)
release module jackrabbit-bdb 1.0 - Key: JCR-402 URL: http://issues.apache.org/jira/browse/JCR-402 Project: Jackrabbit Type: Wish Components: contrib PMs Versions: 1.0 Reporter: fabrizio giustina The berkeydb persist

[jira] Created: (JCR-401) contrib/bdb-persistence: update berkeleydb version

2006-04-15 Thread fabrizio giustina (JIRA)
contrib/bdb-persistence: update berkeleydb version -- Key: JCR-401 URL: http://issues.apache.org/jira/browse/JCR-401 Project: Jackrabbit Type: Improvement Components: contrib PMs Versions: 1.0 Reporter:

Re: residual definition xml implementation

2006-04-15 Thread Jukka Zitting
Hi, On 4/15/06, Greg Kick <[EMAIL PROTECTED]> wrote: > your response actually outlines the reason i brought it up. although > the spec uses the * notation in its definitions, it pretty clearly > states: You are right. However, the "*" in the item definitions is rather treated as a special marker

Re: residual definition xml implementation

2006-04-15 Thread Greg Kick
your response actually outlines the reason i brought it up. although the spec uses the * notation in its definitions, it pretty clearly states: "...to indicate that a property or child node definition is residual, the value returned by ItemDefinition.getName() is “*”. However, “*” is not

Re: residual definition xml implementation

2006-04-15 Thread Jukka Zitting
Hi, On 4/15/06, Greg Kick <[EMAIL PROTECTED]> wrote: > i have a quick question about node type definitions. jackrabbit > consistently (NodeTypeWriter, custom_nodetypes.xml, etc.) uses > name="*" for residual definitions in the xml format. however, p. 144 > of the jsr170 spec says that * is not a