[esb-issues] [JBoss JIRA] Commented: (JBESB-1863) ConfigTree creates children with meaningless names

[Kevin Conner (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBESB-1863?page=comments#action_12420800 ] 
            
Kevin Conner commented on JBESB-1863:
-------------------------------------

There is already a way to handle the hierarchical naming with the current mapping, we are very unlikely to change this.  It is also desirable to support duplicate element names.

The only issue that I am aware of is JBESB-539

> ConfigTree creates children with meaningless names
> --------------------------------------------------
>
>                 Key: JBESB-1863
>                 URL: http://jira.jboss.com/jira/browse/JBESB-1863
>             Project: JBoss ESB
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Rosetta
>    Affects Versions: 4.2.1 CP3
>            Reporter: Mark Little
>            Priority: Minor
>
> When checking for children, ConfigTree calls getNodeName on subelements and uses the returned string as the name of the entry. This means children end up with names like "property" (non-unique) or "el" (again, not unique). I think most users will be expecting more meaningful names, such as:
> <action name="simplePropertyRouter" class="SimpleDynamicRouter"	>
> 	<property name="message.property.name" value="from" />
>         <property name="message.property.value" value="plus">
>   	   <service.name>PlusFileService</service.name>
>    	   <service.name>service99</service.name>
>         </property>
> </action>
> A child could be "message.property.name" rather than "property".

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira