[
https://issues.apache.org/jira/browse/JXPATH-80?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Benson resolved JXPATH-80.
-------------------------------
Resolution: Invalid
Hi--sorry it took me so long to get back to this issue. After much
tail-chasing I have come to the conclusion that this issue is a red herring.
Your test attachment isn't performing "boolean conversions" but equality
comparisons. A boolean conversion is accomplished by calling the built-in
boolean() function, and these seem to perform as expected. equality
comparisons do not automatically convert between types in the way you are
expecting. See http://www.w3.org/TR/xpath#booleans for more information about
how these comparisons are specified.
> boolean conversion of javabean getter values returning NULL fails
> -----------------------------------------------------------------
>
> Key: JXPATH-80
> URL: https://issues.apache.org/jira/browse/JXPATH-80
> Project: Commons JXPath
> Issue Type: Bug
> Affects Versions: 1.2 Final
> Environment: java.runtime.name=Java(TM) SE Runtime Environment
> java.runtime.version=1.6.0-b105
> java.specification.name=Java Platform API Specification
> java.specification.vendor=Sun Microsystems Inc.
> java.vm.info=mixed mode
> java.vm.name=Java HotSpot(TM) Client VM
> Reporter: Nico Max
> Priority: Minor
> Attachments: patch.patch, patch.patch, test.java
>
>
> According to the JXPath User Guide a Javabean Getter returning NULL,
> regadless of the type, will be converted bo Boolean FALSE. But trying to
> build a boolean expression from this fails as the attached testcase shows.
> It seems that the type the bean getter returns matters, as a NULL String for
> example works as expected.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
