Connecting the 'workflow' standalone client with the 'tasklist' java server via websockets causes source file issue #1327
Replies: 1 comment
-
I was able to clearify some of my false assumptions and will ask more clear questions regarding the |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi everybody,
I want to connect the standalone client from the 'workflow' example with the java server from the 'tasklist' example via websockets. I already managed to get it to at least show me my Itempalette on the canvas. But it seems like it was not able to load the root container of the diagram, because it showed me 'unknown element' if I clicked into the empty diagram. Based on the server side error messages I understood that I first had to give the client a appropriate source file, which could be interpreted by my inserted Ecore-metamodel on the server side. So I exchanged the originally contained 'example1.wf' file, within the 'app' folder of the standalone client, with a XMI formated 'My.ooa_classdiagram' file from a Sirius editor (based on the same metamodel). Additionally I changed a little bit of code in the 'src/app.ts' file in line 37, where I inserted just the name of my source file. After doing this I got the server side error that it was not able to process the 'requestModel' action because of a 'FileNotFoundException'.
But before I go to deep into detail (which I already did tbh), I first wanted to ask which parts need to be additionally adjusted if the websocket connection itself already seems to work. Maybe You could explain it to me in generell and based on this I'll try to find the solution on myself. If this would fail, I will have to ask You for further help.
So I'm very thankfull for any kind of help.
Greetings Michael
Beta Was this translation helpful? Give feedback.
All reactions