Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 368262 - Setting target namespace on BPMN2 model with existing default namespace results in two default namespace attributes on the top level element
Summary: Setting target namespace on BPMN2 model with existing default namespace resul...
Status: RESOLVED WONTFIX
Alias: None
Product: BPMN2Modeler
Classification: SOA
Component: Tools (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: 0.0.1-M1   Edit
Assignee: Robert Brodt CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-10 10:19 EST by Gary Brown CLA
Modified: 2012-01-10 15:38 EST (History)
0 users

See Also:

Attachments
Original model, before setting the target namespace property (30.24 KB, application/octet-stream)
2012-01-10 10:20 EST, Gary Brown CLA 		no flags Details
Example of the model after target namespace set (25.56 KB, application/octet-stream)
2012-01-10 10:21 EST, Gary Brown CLA 		no flags Details
View All 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 Gary Brown CLA 2012-01-10 10:19:01 EST 
Build Identifier: 

I have a BPMN2 choreogaphy model that has a default namespace (the BPMN2 URI xmlns="http://www.omg.org/spec/BPMN/20100524/MODEL").

However when I set a value in the targetNamespace field (Properties->Definitions->Target Namespace) it results in the value being placed in the default namespace as well as the targetNamespace attribute - but the previous default namespace is also present, so the resulting XML is no longer valid.


Reproducible: Always

Steps to Reproduce:
1. Using the PurchaseGoodsOriginal.bpmn model, select the Properties->Definitions tab
2. Set the "Target Namespace" field to any non-empty value
3. View the XML, and you will see two 'xmlns=' attributes on the top level element.
Comment 1 Gary Brown CLA 2012-01-10 10:20:06 EST 
Created attachment 209265 [details]
Original model, before setting the target namespace property

Set the target namespace property on this model to see the duplicate xmlns (default namespace) created.
Comment 2 Gary Brown CLA 2012-01-10 10:21:29 EST 
Created attachment 209266 [details]
Example of the model after target namespace set

This cannot be opened in the editor as it is no longer valid xml.
Comment 3 Gary Brown CLA 2012-01-10 15:38:35 EST 
Looks like this is happening in the EMF/BPMN2 model, so will close the issue here.