Issue with Flow Creation in SySON v2025.02

[imeneazouzi]

I developed a Spring Boot project that depends on SySON (v2025.02). However, I encountered an issue with flow creation. The flow is created in the project explorer, but graphically, an error appears, as shown in the attached image.

I look forward to your response.

[AxelRICHARD]

Hello,

Can you give more context please?
What are trying to do exactly?
To execute a tool between two graphical nodes? Between which nodes? In which diagram?

[imeneazouzi]

I'm creating a flow between two ports, and these ports are attached to nodes. The issue is that, while the flow is successfully created semantically, it doesn't appear graphically.

[AxelRICHARD]

Could you share the content of the getFlows method please?
I f you're absolutely certain that your semantic model is correct after the execution of your tool, then the problem should be located in this getFlows method.

[imeneazouzi]

[AxelRICHARD]

I don't know how extractNotifier and isTypedWith(LcaConstants.FLOW_QUALIFIED_NAME) are implemented but you could debug that getFlows method to see if its return value contains the InterfaceUsage you expect.

[imeneazouzi]

Please find attached the implementation of the two methods.

protected Predicate<? super org.eclipse.syson.sysml.Feature> isTypedWith(String qualifiedName) {
return element -> element.getType().stream().anyMatch(t -> t != null && qualifiedName != null && qualifiedName.equals(t.getQualifiedName()));
}

public List<Notifier> extractNotifier(EObject eObject) {
    ArrayList<Notifier> notifiersList = new ArrayList<>();
    eObject.eResource().getAllContents().forEachRemaining(notifiersList::add);
    return notifiersList;
}

[AxelRICHARD]

Ok so it means that in your createFlow method newInterfaceUsage.getSource().add(newSourcePortUsage); and newInterfaceUsage.getTarget().add(newTargetPortUsage); don't do what you expect.
When you create a new InterfaceUsage you can't just set the source and target as you did.
The data structure under the InterfaceUsage is quite complex, depending on the elements linked by this InterfaceUsage.
If I may suggest, you should dig in the SysMLv2 specification to see how is the data structure inside InterfaceUsage.

Regards,

[AxelRICHARD]

Obeo (https://www.obeosoft.com/en/contact) could also help you if you need professional support.

[imeneazouzi]

[AxelRICHARD]

Those changes have nothing to do with the SysMLv2 metamodel in SysON.
As already answered in my previous message, you should take a look at the SysMLv2 specification to see how is the data structure inside InterfaceUsage and try to reproduce the same when you create your own.

Regards,

[imeneazouzi]

Thank you for your feedback.
I’ll review the SysMLv2 specification more closely and ensure that my implementation of InterfaceUsage matches the expected structure.

Best regards,