This content has been marked as final.
Show 5 replies
-
1. Re: xml export
kukeltje May 20, 2007 6:01 AM (in response to msandoz)regarding the deprecated class: correct, since the core-engine now stores the process in xml format as well when deploying, converting back is no longer needed
regarding the manipulation of the domain objects, isn't that you design choise if you beuild a new editor? -
2. Re: xml export
msandoz May 20, 2007 10:02 PM (in response to msandoz)"kukeltje" wrote:
regarding the deprecated class: correct, since the core-engine now stores the process in xml format as well when deploying, converting back is no longer needed
regarding the manipulation of the domain objects, isn't that you design choise if you beuild a new editor?
hi thanks for the info. My motivation is that I'd like to concentrate on programmatically creating process definitions and then having them exported from my editor as xml for later submission. is there a way to do that?
Here's my understanding of the use case:
1. Create process definitions in GUI editor, complete with actions, etc.
2. Store on local file system in xml while its being worked on
3. When ready to instantiate, submit the xml to the engine.
4. Get feedback from the engine on run state etc.
if my assumption is correct, it seems theres a step needed to create the xml. does the engine do that? That seems to be how the existing editor works. Is that correct?
Thank You,
Matthew -
-
4. Re: xml export
msandoz May 22, 2007 4:40 PM (in response to msandoz)"kukeltje" wrote:
the editor creates the xml
Does the source come with the existing editor? I'd just like to use whats already there instead of having to reinvent the wheel. -