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

Bug 326361

Summary:

[Diagram] Tigerstripe sometimes chooses a conflicting default name for an association

Product:

[Technology] Tigerstripe

Reporter:

Navid Mehregani <nmehrega>

Component:

Assignee:

Project Inbox <tigerstripe.ui-inbox>

Status:

VERIFIED FIXED

QA Contact:

Severity:

normal

Priority:

CC:

chrhartl, yuri

Version:

unspecified

Target Milestone:

0.5M0

Hardware:

OS:

Mac OS X - Carbon (unsup.)

Whiteboard:

Attachments:

Description	Flags
Error log	none
Patch with bug fix	none

Description Navid Mehregani

2010-09-27 18:33:57 EDT

Build Identifier: 

The diagrams don't take into account association class names when picking a default name for an association.

Reproducible: Always

Steps to Reproduce:
1. In an empty TS project, create to Entities
2. Create an Association Class between the Entities
3. Name the Association Class 'Association0'
4. Create a regular Association between the entities.  Notice that it picks the name 'Association0' for the newly created association!  This results in unpredictable behaviour.

Comment 1 Navid Mehregani

2010-09-27 18:34:29 EDT

Created attachment 179697 [details]
Error log

Comment 2 Chris Hartley

2010-09-27 23:16:37 EDT

I assume this is probably true for any artifact.

I have confirmed that if I rename an Entity Datatype0 then create a datatype I have a similar issue.

The only safe fix I can think of is for the 'default name method' to check if the FQN exists (not an issue if it exists in another package) and if it does, to increment and keep trying until it finds one not in use.

Comment 3 Anton Salnik

2010-11-19 05:16:58 EST

Created attachment 183458 [details]
Patch with bug fix

Comment 4 Yuri Strot

2010-11-19 06:22:40 EST

I've applied Anton's patch.

Comment 5 Navid Mehregani

2010-11-19 10:04:43 EST

Verified. Thanks!