Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 362923 - Project import issue
Summary: Project import issue
Status: NEW
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: BPEL (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 minor (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-04 12:48 EDT by Sandrine Beauche CLA
Modified: 2022-10-03 11:12 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Sandrine Beauche CLA 2011-11-04 12:48:28 EDT 
Build Identifier: 20110913-1707

When I import a BPEL Petals studio project that have been built from another installation of petals studio or by hand for example, the BPEL file is not readable in the bpel visual editor. But I can read the source. I can also read the wsdl or jbi file in their visual editors. 

To be able to read correctly the bpel, I have to delete the petals studio project configuration files, and then import the folder as a petals structure. If I don't check "copy in the workspace", I have the same problem. I have to copy and then it is OK.

Reproducible: Always
Comment 1 Robert Brodt CLA 2011-11-04 12:53:36 EDT 
Can you please attach a sample project (zipped) so we can repro this?
Thanks!
Comment 2 Vincent Zurczak CLA 2011-11-04 13:02:35 EDT 
Hi,

At first glance, I did not think this problem was about the Eclipse BPEL Designer itself. IMO, this was more a problem with the studio. 

But after thinking about it, I see the source of the problem.
The BPEL Designer can only read resources which are located in the workspace. BPEL files located outside the workspace cannot be edited graphically.

So, this is indeed a bug with the BPEL Designer.