[ https://jira.jboss.org/jira/browse/JBIDE-5356?page=com.atlassian.jira.plu... ] Tom Fennelly updated JBIDE-5356: -------------------------------- Description: 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!! was: Bean value/wiring configs are added for all bean properties, even if no mappings were made onto the property e.g. <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 contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-5356?page=com.atlassian.jira.plu... ] Tom Fennelly updated JBIDE-5356: -------------------------------- Workaround Description: You can delete the property nodes from the bean in the Java Mapping window. This solves the immediate problem, but is not the right solution because you may want add a mapping on that property some time later. In this case, you wouldn't see the property on the bean (because you deleted it). Getting it back means using the "Add Value Binding" option on the right-click menu, which just drops in a "NULL" property... you have to rename it correctly etc... all very messy IMO. Fix Version/s: (was: 3.1.0.CR1) Moving to GA only - see workaround for the CR1 release. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-5356?page=com.atlassian.jira.plu... ] Tom Fennelly commented on JBIDE-5356: ------------------------------------- Outlined in the "Workaround Description" field at the top ;) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-5356?page=com.atlassian.jira.plu... ] Xue Peng commented on JBIDE-5356: --------------------------------- Brian is using Mylin :) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-5356?page=com.atlassian.jira.plu... ] Brian Fitzpatrick commented on JBIDE-5356: ------------------------------------------ Hey Tom... Does this need to be addressed for this release or can we push it to the next? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-5356?page=com.atlassian.jira.plugin... ] Tom Fennelly updated JBIDE-5356: -------------------------------- Assignee: Tom Fennelly (was: Xue Peng) Reassigning to me -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira