[
https://issues.redhat.com/browse/DROOLS-5009?page=com.atlassian.jira.plug...
]
Jozef Marko commented on DROOLS-5009:
-------------------------------------
[~manstis] [~dadossan] actually I think a little bit more about this. I haven't
written the expected behavior. Do we all agree that informing user about an error after
clicking the button is too late? If no, then we can close jira. If yes, we should agree on
one options bellow:
- Import is not possible if such field is present, user is informed
- Import omits particular fields that are not DMN valid, user is informed
- Import adapts particular fields to be DMN valid, user is informed
*User is informed* in all cases above is question for UX I guess.
DMN Designer convert java class with invalid DMN identiefier
------------------------------------------------------------
Key: DROOLS-5009
URL:
https://issues.redhat.com/browse/DROOLS-5009
Project: Drools
Issue Type: Bug
Components: DMN Editor
Affects Versions: 7.33.0.Final
Reporter: Jozef Marko
Assignee: Daniel José dos Santos
Priority: Minor
Labels: drools-tools
Attachments: Screenshot from 2020-02-05 16-21-10.png
There is an issue if user convert java class to DMN data type while the java class
contains field name, that is invalid identifier for DMN.
for example assume this java class and try to convert it into DMN data type, you will get
an error as attached.
{code:java}
public class Address {
private int number;
}
{code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)