[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-8567) Add a dropdown list in JBoss ESB Editor/ESB Route To to pickup a predefined Service Category/Service Name

[Viacheslav Kabanovich (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-8567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12588720#comment-12588720 ] 

Viacheslav Kabanovich commented on JBIDE-8567:
----------------------------------------------

I have found the answer in sources and documentation.
1) In the case of SyncServiceInvoker, these properties are treated in the same way as in <route-to> in ContentBasedRouter;
2) In the case of BusinessRulesProcessor, attributes of <send-to> are treated in the same way if channel-class is default (org.jboss.soa.esb.services.rules.ServiceChannel). For a custom channel-class we have no way to know how attributes 'service-category' and 'service-name' are treated and if they are relevant at all, but it is reasonable to assume that developer who implemented Channel would not reuse this attributes for different meaning.

So I think, I will implement the proposed dropdown for all these cases.

> Add a dropdown list in JBoss ESB Editor/ESB Route To to pickup a predefined Service Category/Service Name
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-8567
>                 URL: https://issues.jboss.org/browse/JBIDE-8567
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: esb
>            Reporter: Joao Viragine
>            Assignee: Viacheslav Kabanovich
>             Fix For: 3.3.0.M1
>
>         Attachments: Add Route To.png
>
>   Original Estimate: 0 minutes
>  Remaining Estimate: 0 minutes
>
> Add a dropdown list in JBoss ESB Editor/ESB Route To to pickup a predefined Service Category/Service Name.
> JBDS should filter the available Services to populate the pickup list.
> Please, see attached screenshot.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira