Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 362923

Summary:	Project import issue
Product:	z_Archived	Reporter:	Sandrine Beauche <sandrine.beauche>
Component:	BPEL	Assignee:	Project Inbox <bpel.default-inbox>
Status:	NEW ---	QA Contact:
Severity:	minor
Priority:	P3	CC:	bbrodt, vincent.zurczak
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Windows 7
Whiteboard:

Description Sandrine Beauche

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

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

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.