Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Message-ID: <720751708.1210249496108.JavaMail.jira@brutus>
Date: Thu, 8 May 2008 05:24:56 -0700 (PDT)
From: "Julian Reschke (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Subject: [jira] Commented: (JCR-1555) Add support for boolean values to
 QValue
In-Reply-To: <1132028508.1209135957635.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/JCR-1555?page=3Dcom.atlassian.j=
ira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D125952=
12#action_12595212 ]=20

Julian Reschke commented on JCR-1555:
-------------------------------------

I personally do not really care. If Mchael really wants it, let's add it :-=
)

That being said, we are just in the process of removing fluff elsewhere, wh=
ere the rational is to keep the API minimal. It seems adding the methods di=
scussed here is contrary to that goal :-)


> Add support for boolean values to QValue
> ----------------------------------------
>
>                 Key: JCR-1555
>                 URL: https://issues.apache.org/jira/browse/JCR-1555
>             Project: Jackrabbit
>          Issue Type: Improvement
>          Components: jackrabbit-spi, jackrabbit-spi-commons
>            Reporter: Michael D=C3=BCrig
>            Priority: Minor
>         Attachments: JCR-1555(2).patch, JCR-1555.patch
>
>
> I suggest to add support for reading and writing boolean values to QValue=
 and QValueFactory. I find it strange that there is such support for the ot=
her data types but booleans must be constructed via strings.=20

--=20
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.