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

Bug 368262

Summary:

Setting target namespace on BPMN2 model with existing default namespace results in two default namespace attributes on the top level element

Product:

[SOA] BPMN2Modeler

Reporter:

Gary Brown <gary>

Component:

Tools

Assignee:

Robert Brodt <bbrodt>

Status:

RESOLVED WONTFIX

QA Contact:

Severity:

normal

Priority:

Version:

unspecified

Target Milestone:

0.0.1-M1

Hardware:

OS:

Linux

Whiteboard:

Attachments:

Description	Flags
Original model, before setting the target namespace property	none
Example of the model after target namespace set	none

Description Gary Brown

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

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

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

2012-01-10 15:38:35 EST

Looks like this is happening in the EMF/BPMN2 model, so will close the issue here.