[
https://issues.apache.org/jira/browse/JXPATH-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927659#action_12927659
]
Zhongxian Gu commented on JXPATH-143:
-------------------------------------
Hi,
I think this bug is duplicate to JXPATH-128.
I am building a tool to analyse bugs. The tool is aimed at finding similar bugs
so that we can make use of this information. One possibility would be that
similar bugs are actually duplicate bugs. With this information, programmers
need not to explore these bug reports one by one, instead can view them as one
bug, thus saving the efforts.
I input some bugs in this project. According to my tool's analysis, JXPATH-143
is very likely to related to JXPATH 128. I tried to resolve 143 based on fix
patch of 128. Finally it turns out that JXPATH-143 is duplicate to 128. The
patch to 128 is the essential code to resolve 143. With jxpath-1.3 patched the
128's patch, 143 will run smoothly without any runtime exception.
I am new to JXPATH, and not 100% sure of it.
Best
Zhongxian
> JXPathContext.iterate does not work with null value in LazyDynaBean
> -------------------------------------------------------------------
>
> Key: JXPATH-143
> URL: https://issues.apache.org/jira/browse/JXPATH-143
> Project: Commons JXPath
> Issue Type: Bug
> Affects Versions: 1.3
> Reporter: Mikael Nordenberg
>
> The following code fails with a NoSuchElementException:
> LazyDynaBean bean = new LazyDynaBean();
> bean.set("test", null);
> JXPathContext context = JXPathContext.newContext(bean);
> context.iterate("test").next();
> Replacing the value in the bean for anything but null works as expected.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
