dm2e / dm2e-ws Goto Github PK

@d0rg0ld in DM2E/dm2e-gui#42:

If I "Run" a config, I am directed to the Job page where the Job has some hex-string as name. Would it be possible to auto-create some label for it based on the involved workflow, config and timestamp?

Right now, the workflowservice just iterates the positions which isn't correct and renders the dataflow into a pipeline.

The WorkflowService should have a logic similar to the validate methods in WorkflowConfigPojo, traversing the graph spanned by positions as nodes and connectors as edges and manage the webservices and assign parameterassignments accordingly

... so we can sort the job list in dm2e-gui by start time

Reproduce:

• Create a workflow with XSLT service as only position
• Connect xmlInput and xslInput to Workflow input
• Connect xmlOuput of pos#1 to workflow output
• Create a Config from the workflow
• Assign xmlInput and xslInput valid file URLs
• Run the Config

Result:

• One output assignment parameter (completeLog)

Expected Result:

• Two output assignment parameters (completeLog and xmlOutput)

With the current set of properties it is impossible to get from a running WorkflowJob to the jobs that run the positions in that workflow.

WorkflowJob needs:

• omnom:currentPosition
• omnom:currentJob
• omnom:finishedPosition -> omnom:finishedJob

Ideally some sort of associative mapping between the two. Then the GUI can query the jobs pertaining to specific positions and retrieve from the job:

• log
• created files

GET -H $AC_JSON $SRV/api/job/..../relatedJobs

Result

• Array of a single job

Expected result

• Array of all jobs, running, finished, failed

When omitting metadata in a POST to /api/file, sensible defaults should be used:

dcterms:modified: now
omnom:fileOwner: anonymous?
omnom:fileType: by file extension?