[jbosstools-issues] [JBoss JIRA] (JBIDE-5356) Unmapped Java bindings being added to to <bean> configs
Max Rydahl Andersen (JIRA)
jira-events at lists.jboss.org
Tue Jun 18 10:17:36 EDT 2013
[ https://issues.jboss.org/browse/JBIDE-5356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Max Rydahl Andersen closed JBIDE-5356.
--------------------------------------
Resolution: Out of Date
Thank you for reporting the issue but this is being closed as out-of-date since the 'smooks' component is not currently being developed and have been removed for 1+ year. Thus it no longer makes sense to keep these issues around.
If you feel this issue was closed for the wrong reason then please open a new issue.
> Unmapped Java bindings being added to to <bean> configs
> -------------------------------------------------------
>
> Key: JBIDE-5356
> URL: https://issues.jboss.org/browse/JBIDE-5356
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: smooks
> Reporter: Tom Fennelly
> Assignee: Tom Fennelly
> Fix For: LATER
>
>
> Bean value/wiring configs are added for all bean properties, even if no mappings were made onto the property.
> Example... the <value> config in the following should have a data attribute if a mapping was made onto the property. No mapping => no data attribute => we should just omit that <value> config.
> <jb:bindings beanId="header" class="example.model.Header" createOnElement="json">
> <jb:value property="date"/>
> </jb:bindings>
> Note... it is not mandatory for a mapping to be made onto a bean property!!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jbosstools-issues
mailing list