setString on JavaFMI generated FMUs is bugged

[Lars Ivar Hatledal]

setString does not seem to handle either one of or a combination of commas, spaces or newlines. Could be related to #102.

[Jose Evora]

Dear Lars,

Thanks for reporting. As commented in issue 102, I also agree with you about those characters. The implementation of the DLL communicates with the java application through a CLI so probably that kind of characters are messing up the communication. We will need to use a codification that avoid those characters (URL encoding sounds the best to me). We will work on it.

I guess you are not having these problems when using JavaFMI. When using JavaFMI, the communication is optimised by loading the Jar of the FMU in the same VM of the MA (no dll is used in this case).

As in 102, we will work on it and let you know when it is operative.

Best regards,

[Lars Ivar Hatledal]

Yes, I noticed that this is not an issue when loading the FMU with JavaFMI. Unfortunately we use FMI Library and FMI4j in our framework

[Jose Evora]

Fixed in builder 2.6.0 and framework 2.6.0. Let us know if you have any problem further.