Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 361820 - When BPEL process opened, using default target namespace instead of bpel prefix, the editor shows the process as dirty
Summary: When BPEL process opened, using default target namespace instead of bpel pref...
Status: CLOSED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: BPEL (show other bugs)
Version: unspecified   Edit
Hardware: All Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-24 11:30 EDT by Gary Brown CLA
Modified: 2022-10-03 11:11 EDT (History)
1 user (show)

See Also:


Attachments
A BPEL process without the bpel prefix defined (3.83 KB, application/octet-stream)
2011-10-24 11:33 EDT, Gary Brown CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Gary Brown CLA 2011-10-24 11:30:34 EDT
Build Identifier: 

When a BPEL process is defined using the default namespace for the BPEL namespace (xmlns="http://docs.oasis-open.org/wsbpel/2.0/process/executable"), the editor inserts the bpel prefix with the same namespace.


Reproducible: Always
Comment 1 Gary Brown CLA 2011-10-24 11:33:25 EDT
Created attachment 205835 [details]
A BPEL process without the bpel prefix defined

If the attached BPEL process is opened, it will automatically show the dirty flag on the editor.
Comment 2 Robert Brodt CLA 2011-11-01 15:49:58 EDT
Fixed. Gary, can you please verify & close?
Comment 3 Gary Brown CLA 2011-12-03 16:57:57 EST
Thanks Bob - sorry took a while to verify :)