[jbosstools-issues] [JBoss JIRA] (JBTIS-795) JBDSIS 9.0.0 beta1 / Early Access is giving an Id to Camel routes by default

[Rick Wagner (JIRA)]

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

Rick Wagner commented on JBTIS-795:
-----------------------------------

Hi Brian and Lars,

Yes, sure.  Attached please find 'A_camel_service.tar.gz', which shows the problem.

To make your own:
- Start a SwitchYard project, make sure it allows use of the Camel component.
- Add an XML Camel component.  (This should give you a route named 'route.xml' by default.)  Note that *immediately upon birth* the route is given an Id.  This is changed behavior from past versions-- it's the problem.

Note that this sample is based on the quickstart 'quickstarts/switchyard/camel-service'.  The vanilla quickstart has a route.xml already, but it does not have the route id attribute.   (It was not affected by the problem.)  But when we added a new Camel component (route), we got the second route.xml that *does* have the Id/problem.

Hope that helps,

Rick


> JBDSIS 9.0.0 beta1 / Early Access is giving an Id to Camel routes by default
> ----------------------------------------------------------------------------
>
>                 Key: JBTIS-795
>                 URL: https://issues.jboss.org/browse/JBTIS-795
>             Project: JBoss Tools Integration Stack
>          Issue Type: Bug
>          Components: Fuse IDE
>    Affects Versions: 9.0.0.Beta1
>         Environment: JBDS 9.1 with devstudio-integration-stack-9.0.0.Beta1-earlyaccess.zip
>            Reporter: Rick Wagner
>            Assignee: Brian Fitzpatrick
>         Attachments: A_camel_service.tar.gz
>
>
> A user has noted that Camel routes used in SwitchYard are now being given an Id without user input.  This is a changed behavior.
> The same user complains of very slow loading of SwitchYard/Camel component routes, but this is still under investigation in the cited support ticket.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)