[ https://issues.jboss.org/browse/JBIDE-20136?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich edited comment on JBIDE-20136 at 7/2/15 8:33 PM: ----------------------------------------------------------------------- For "Next" the behaviour is ok, there can be no way to connect source to a target with no id. Connection service for Next is our custom implementation, and we did it as it should be. For "next on" we used standard Sapphire connection service, its implementation is internal and it does what they think is best - when id attribute is not available, instead of forbidding connection they reference target by an internal id of diagram node. Of course, it makes no sense. I still cannot find if we can prevent it. was (Author: scabanovich): For "Next" the behaviour is ok, there can be no way to connect source to a target with no id. Connection service for Next is our custom implementation, and we did it as it should be. For "next on" we used standard Sapphire connection service, its implementation is internal and it does what they think is best - when id attribute is not available, instead of forbidding connection they reference target by an internal id of diagram node. I still cannot find if we can prevent it. -- This message was sent by Atlassian JIRA (v6.3.15#6346)