gitgabrio opened a new issue, #6920:
URL: https://github.com/apache/incubator-kie/issues/6920

   Currently, 
[JITBPMNServiceImpl](https://github.com/kiegroup/kogito-apps/blob/11bd6d51868f5948211a8837cd00e6776dc59bf0/jitexecutor/jitexecutor-bpmn/src/main/java/org/kie/kogito/jitexecutor/bpmn/JITBPMNServiceImpl.java#L78)
 validation returns the following errors:
   
   1. "unparsable" errors (catched exception)
   2. "no process found"
   3. any other "ProcessValidation" error specific of BPMN
   
   As for the latter, they are gathered from 
`RuleFlowProcessValidator.validateProcess(Process) `
   
   This returns errors about missing nodes/edges, or others, but not other 
details, like "user task has no assignee" or "process variable has no type"
   
   
   Files from 
https://github.com/jomarko/kie-sandbox-process-validation-demo/tree/main/processes
 will be used for testing purpose.
   
   Proposed iteration
   
   1. make all modifications only inside jitexecutor, to keep core code/bpmn 
still and safe and to speed up testing with ui
   2. through iteration with UI requirement (i.e. what's best/easier to manage 
on UI side) finely tune the beans bringed along and exposed by rest endpoint
   3. after working and accepted solution, we may move/merge our modifications 
to core code (in a different ticket)
   
   
   Returned format:
   
   ```json{ 
     "mainURI": "string", 
     "results": [ 
       { 
         "errorLevel": "string (FINE | WARNING | SEVERE)", 
         "nodeId": "long", 
         "nodeName": "string", 
         "processId": "string", 
         "errorMessage": "string" 
       } 
     ] 
   } ```
   
   
   
   
   @jomarko 
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to