| Summary: | CR: Provide Save As command for workflows | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Nadine Ausländer <nadine.auslaender> |
| Component: | BPEL | Assignee: | Project Inbox <bpel.default-inbox> |
| Status: | NEW --- | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | igor.novakovic, nadine.auslaender, vincent.zurczak |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
|
Description
Nadine Ausländer
+1 Hi, Is it enough to save the process as a new file *in the workspace*? We could imagine to save it as a new name anywhere on the disk, but the BPEL Designer does not support edition of external processes (located outside the workspace). Saving a copy in the workspace is quite easy to implement. Another question: what should be the edited file after the "save as"? The previously edited file or the new copy? Hi, 1st question: IMO, saving the process within the workspace will do. That was just what I intended to do when I posted this CR. ;-) 2nd question: Well, preferably, it should conform with Eclipse's default behavior (if there is any). I tried it with a text file in the Text Editor: When I change the original file and select "Save As" to create a new file, I end up with the copy in the Text Editor showing the new input. The original file is left unchanged then. This seems to be a reasonable behavior. So, IMO, "the new copy" is the answer to your question. |