You are viewing a plain text version of this content. The canonical link for it is here.
Posted to xbean-dev@geronimo.apache.org by "Alan Cabrera (JIRA)" <ji...@apache.org> on 2015/03/04 16:56:04 UTC
[jira] [Commented] (XBEAN-278) Blueprint Namespace Handler
improperly parsed flat-collections
[ https://issues.apache.org/jira/browse/XBEAN-278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14347049#comment-14347049 ]
Alan Cabrera commented on XBEAN-278:
------------------------------------
Dan, I saw the pull request. I thought you had the karma to commit this yourself.
> Blueprint Namespace Handler improperly parsed flat-collections
> --------------------------------------------------------------
>
> Key: XBEAN-278
> URL: https://issues.apache.org/jira/browse/XBEAN-278
> Project: XBean
> Issue Type: Bug
> Affects Versions: 4.1
> Reporter: Daniel Kulp
>
> When parsing a flat collections, the fist item is processed correctly creating the MutableColectionMetadata and setting the childeMetadata to the listMeta which is then added to the bean.
> For subsequent items, item is added to the list correctly. However, the childeMetadata remains null (which is likely proper). However, at the end of the 'if/else' chain in XBeanNamespaceHandler, if childMeta is null, it creates another childMeta with the "value" of the element (likely an empty string). This causes beans to fail to be created.
> Patch coming soon.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)