You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@jackrabbit.apache.org by "David B. Johnson" <DB...@eentertainment.com> on 2006/05/27 03:57:33 UTC

CND and Default Namespace

Does the Compact Node Definition work with the default namespace?  For
example, I can not get the following node type to work properly:

 

[eol:BodySegment] > eol:Base, mix:versionable

  orderable

  - body (string)

  - permalink (string)

- thumbnail (reference)

 

Note, properties are not fully qualified names - i.e., they are within
the default namespace.

 

Whereas the following works fine:

 

[eol:ContentItem] > eol:base, mix:referenceable, mix:versionable

  orderable

  - eol:publishDate (date) mandatory

  - eol:expireDate (date)

  - eol:lastModified (date) mandatory

  - eol:topics (reference) multiple

    < 'eol:Topic'

  - eol:keywords (string) multiple

  - eol:relatedContent (reference) multiple

    < 'eol:ContentItem'

- eol:relatedImages (reference) multiple

 

Do I need to do something special to get the properties defined within
the default namespace to work properly?

 

-David B. Johnson, Ph.D.

Manager of Software Engineering

E! Entertainment

 

dbjohnson@eentertainment.com

 


Re: CND and Default Namespace

Posted by Petr Pytelka <Pe...@lightcomp.com>.
I've had the same problem. To solve it I had to add default namespace 
declaration at the beginning of CND file.

Example:
/* orig.namespaces */
<mix = 'http://www.jcp.org/jcr/mix/1.0'>
<nt = 'http://www.jcp.org/jcr/nt/1.0'>
.... your declarations ...


Petr Pytelka

David B. Johnson wrote:
> Does the Compact Node Definition work with the default namespace?  For
> example, I can not get the following node type to work properly:
> 
>  
> 
> [eol:BodySegment] > eol:Base, mix:versionable
> 
>   orderable
> 
>   - body (string)
> 
>   - permalink (string)
> 
> - thumbnail (reference)
> 
>  
> 
> Note, properties are not fully qualified names - i.e., they are within
> the default namespace.
> 
>  
> 
> Whereas the following works fine:
> 
>  
> 
> [eol:ContentItem] > eol:base, mix:referenceable, mix:versionable
> 
>   orderable
> 
>   - eol:publishDate (date) mandatory
> 
>   - eol:expireDate (date)
> 
>   - eol:lastModified (date) mandatory
> 
>   - eol:topics (reference) multiple
> 
>     < 'eol:Topic'
> 
>   - eol:keywords (string) multiple
> 
>   - eol:relatedContent (reference) multiple
> 
>     < 'eol:ContentItem'
> 
> - eol:relatedImages (reference) multiple
> 
>  
> 
> Do I need to do something special to get the properties defined within
> the default namespace to work properly?
> 
>  
> 
> -David B. Johnson, Ph.D.
> 
> Manager of Software Engineering
> 
> E! Entertainment
> 
>  
> 
> dbjohnson@eentertainment.com
> 
>  
> 
> 

Re: CND and Default Namespace

Posted by Tobias Bocanegra <to...@day.com>.
well, it works fine for me with the default namespace aswell.
maybe it's a type in your first example, the 'eol:Base' is with a
uppercase 'B' whereas in the 2nd it's lowercase.

regards, toby

On 5/27/06, David B. Johnson <DB...@eentertainment.com> wrote:
> Does the Compact Node Definition work with the default namespace?  For
> example, I can not get the following node type to work properly:
>
>
>
> [eol:BodySegment] > eol:Base, mix:versionable
>
>   orderable
>
>   - body (string)
>
>   - permalink (string)
>
> - thumbnail (reference)
>
>
>
> Note, properties are not fully qualified names - i.e., they are within
> the default namespace.
>
>
>
> Whereas the following works fine:
>
>
>
> [eol:ContentItem] > eol:base, mix:referenceable, mix:versionable
>
>   orderable
>
>   - eol:publishDate (date) mandatory
>
>   - eol:expireDate (date)
>
>   - eol:lastModified (date) mandatory
>
>   - eol:topics (reference) multiple
>
>     < 'eol:Topic'
>
>   - eol:keywords (string) multiple
>
>   - eol:relatedContent (reference) multiple
>
>     < 'eol:ContentItem'
>
> - eol:relatedImages (reference) multiple
>
>
>
> Do I need to do something special to get the properties defined within
> the default namespace to work properly?
>
>
>
> -David B. Johnson, Ph.D.
>
> Manager of Software Engineering
>
> E! Entertainment
>
>
>
> dbjohnson@eentertainment.com
>
>
>
>
>


-- 
-----------------------------------------< tobias.bocanegra@day.com >---
Tobias Bocanegra, Day Management AG, Barfuesserplatz 6, CH - 4001 Basel
T +41 61 226 98 98, F +41 61 226 98 97
-----------------------------------------------< http://www.day.com >---