Bug 1337369 - Fuse tooling route editor displays only error icon when 'to' route added that references .properties file uri
Summary: Fuse tooling route editor displays only error icon when 'to' route added that...
Status: NEW
Alias: None
Product: JBoss Fuse Service Works 6
Classification: JBoss
Component: Tooling
Version: unspecified
Hardware: All
OS: Windows
Target Milestone: ---
: ---
Assignee: Rob Cernich
QA Contact: Len DiMaggio
Depends On:
TreeView+ depends on / blocked
Reported: 2016-05-19 01:30 UTC by jeff.saul
Modified: 2016-05-19 01:31 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed:
Type: Bug

Attachments (Terms of Use)

Description jeff.saul 2016-05-19 01:30:50 UTC
Description of problem: Whilst building a route in the graphical Fuse route builder, the addition of a route that references an entry in a .properties file for the endpoint breaks the editor to the point it won't render the route at all.  However, the route can still be executed successfully and the message sent to the defined endpoint.

Version-Release number of selected component (if applicable):
JBoss Fuse Tooling Apache Camel Editor

How reproducible:
Add a 'to' route where the uri is solely a property, i.e. {{remote.endpoint}}
Where the properties file entry looks something like this:

Steps to Reproduce:
1. Create a new camel route
2. Add a 'to' route where the uri is solely a property, i.e. {{remote.endpoint}} (can be in the visual editor or added directly into the route manually like this: <to id="_to1" uri="{{remote.endpoint}}"/>)
3. Open the camel route in the visual editor

Actual results:
Visual route editor no longer renders the route, but instead displays only a Red dot with a white X inside.  A stack trace is also displayed when 'Details>>' is clicked.  Top of stack trace in additional info section below.

Expected results:
The visual route is rendered correctly

Additional info:
Top few lines of stack trace:

java.lang.IllegalStateException: The ContainerShape must have a valid GraphicsAlgorithm: org.eclipse.graphiti.mm.pictograms.impl.ContainerShapeImpl@5b59a244 (visible: true, active: true)
	at org.eclipse.graphiti.ui.internal.parts.ContainerShapeEditPart.createFigure(ContainerShapeEditPart.java:100)
	at org.eclipse.gef.editparts.AbstractGraphicalEditPart.getFigure(AbstractGraphicalEditPart.java:494)
	at org.eclipse.gef.editparts.AbstractGraphicalEditPart.addChildVisual(AbstractGraphicalEditPart.java:208)
	at org.eclipse.graphiti.ui.internal.parts.ContainerShapeEditPart.addChildVisual(ContainerShapeEditPart.java:170)
	at org.eclipse.gef.editparts.AbstractEditPart.addChild(AbstractEditPart.java:211)
	at org.eclipse.gef.editparts.AbstractEditPart.refreshChildren(AbstractEditPart.java:781)
	at org.eclipse.graphiti.ui.internal.parts.ShapeEditPart.refreshChildren(ShapeEditPart.java:682)

Note You need to log in before you can comment on or make changes to this bug.