jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jacco van Weert" <1111softw...@gmail.com>
Subject Re: null handling when a null is really needed
Date Tue, 29 May 2007 07:06:23 GMT
Hello Mark,

If your properties aren't mandatory you could write a method like;

  public Value getMyProperty( String pName ) {
    if (hasProperty( pName )) {
      return getProperty( pName );
    } else {

  }


On 5/28/07, Mark Waschkowski <mwaschkowski@gmail.com> wrote:
>
> Hi,
>
> I know that the JCR spec specifies that setting a property to null will
> result in the removal of a property, but we have a situation where this is
> problematic. We actually NEED properties that have no values to be stored.
> I
> could manually insert some dummy value for each of the different types,
> but
> if anyone knows of a better way I would really appreciate a suggestion.
>
> Thanks,
>
> Mark
>



-- 
-------------------------------------
Jacco van Weert -- 1111software@gmail.com
JCR Controller -- http://www.xs4all.nl/~weertj/jcr

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message