Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Topics - Geert Bellekens

Pages: 1 ... 9 10 [11] 12 13 ... 16
151
Bugs and Issues / SQL error when saving sequence diagram
« on: November 30, 2009, 08:06:48 pm »
When saving a sequence diagram that contains some messages to operations with a long name and/or a lot of parameters I get an SQL server error: "Bynary data or string would be truncated"

this is apparently caused by the fact that EA stores the whole signature of the operation in the t_connector.Name field which is only 255 characters long.
Obviously this is not enough.

Reported to Sparx.

Geert

152
Bugs and Issues / Package.Elements doesn't return all elements
« on: April 16, 2010, 06:31:22 pm »
To my big surprise my validation tool returned less results in V8 then it did in V7.5.
After an intensive search I found out that Package.Elements doesn't return as much elements in V8 as it did in V7.5.
The reason is the parentID column in the t_object table.
Package.Elements doesn't return elements that have NULL as ParentID. (most of them have 0, but for some unknown reason others have NULL).

The project integrity check will not fix this.

Reported to Sparx

Geert

153
Bugs and Issues / Pre 8.0 triggers specifications broken in 8.0
« on: April 27, 2010, 04:45:46 pm »
In 7.5 you could specify a specification in the trigger field of a transition, without specifying the actual trigger.
In 8.0 that is not possible anymore.
This becomes an issue with the existing pre-8.0 trigger specifications of transitions.
These specifications cannot be edited anymore in 8.0
You can simulate the same situation in 8.0 by deleting a trigger that is used in a transition.

Reported as bug.

Geert

154
Bugs and Issues / Add New button creates elements in locked packages
« on: April 27, 2010, 05:04:19 pm »
We use the security feature with the option "Require User Lock to Edit"
In 8.0.855 I can add elements to package that are not locked by me using the select item dialog.
For instance if you select the behavior of a transition the "Add New" button of the select item dialog will allow me to create an activity in any package, regardless of the locking status.

Reported

Geert

155
Bugs and Issues / Element.Issues is very very slow
« on: April 16, 2010, 10:19:07 pm »
Traversing the Element.Issues collection is very very slow.
(I think I reported that once before, but I can't seem to find the topic )
I spent a little time with SQL profiler to find out what exactly was happening.
The code I used was a simple
Code: [Select]
               foreach (EA.Issue issue in this.wrappedElement.Issues)
                {
                    this.issues.Add(issue);
                }
Now when the this.wrappeElement.Issues get first initialized EA does following on the database:
Code: [Select]
Select 'problem=' + Problem + ';' + 'type=' + ProblemType + ';'  As Issue
from t_objectproblems where Object_ID=2146247310
Then each time the enumerator goes to the next issue another command is issued to get the details of that specific issue.
Code: [Select]
Select * from t_objectproblems
where 'problem=' + Problem + ';' + 'type=' + ProblemType + ';' = 'problem=ACVPackage¶ Geert Bellekens¶ Element should have comments_(13/04/2010 11:37:46.82);type=Defect;'
and Object_ID=2146247310
This is just ridiculous  :o
No other EA.Collection is managed that way!

If a developer on my team would pull one like that  :-X

I'll report it as a bug.

Geert

156
Bugs and Issues / v8 - Type dropdown box broken
« on: February 15, 2010, 11:22:15 pm »
The type dropdown gui element in the properties dialog of an attribute is of the type combobox.
That means that it allows both to type a value as to select one from the list.

In v8 they have managed to break this simple control. Once something has been selected previously you cannot type anything in the field anymore. Only if you select <none> (from somewhere in the middle of the list :-?) it allows you to type again.

Also in v7.5 this combobox allowed to simply start typing the name of a classifier, and it showed you the possibilities to choose from. This possibility has gone. I have to open a new dialog now if I want to select an existing class as type of my attribute >:(

In engineering there is a golden rule: if it aint broke, don't fix it!

Geert

157
Bugs and Issues / duplicate ea_guids in t_attribute
« on: February 17, 2010, 01:48:24 am »
Hi,

I'm trying to upgrade our model to use SQL server 2008 iso 2000.
To do so I though it would be wiser to start with a fresh database and do a project transfer.
So I created a database on the SQL2008 server with the script provided by Sparx, and I started the transfer.
After a while it stopped giving my an error on the t_attribute because of a violation of the ux_attribute_guid (the unique constraint on the t_attribute.ea_guid)

After running a query I found out that on my old sql2000 database I have ~150 guids who are shared by up to 6 attributes. (out of the 15.000 attributes).

Did anyone have this issue before (and knows a good way to solve it)?

Thanks

Geert

158
Bugs and Issues / SQLServer update script broken
« on: February 16, 2010, 01:19:01 am »
The MS SQLserver update script that can be downloaded from the website is broken.
1. It doesn't work on SQL 2000 because in that version it can't update columns of type ntext
2. There are some plain errors in the file like it tries to drop an non existing index:
Quote
           <PatchSQL>            
            IF EXISTS (SELECT 1 FROM dbo.sysindexes WHERE OBJECT_NAME(id) = 't_diagram' AND name = 'Diagram_Type')
            DROP INDEX [t_diagram].[t_diagramtypest_diagram]
            </PatchSQL>
or it tries to drop an index without checking if it exists:
Quote
<PatchSQL>
            DROP INDEX [t_object].[PD1]
        </PatchSQL>

Please make this work, it shouldn't be my job to test for such obvious errors.

Reported to Sparx

Geert


159
Bugs and Issues / EA crashes when Element.ApplyUserLock is called
« on: January 21, 2010, 06:12:42 pm »
We use the security feature with "require user lock to edit" option.
I've written an addin that allows me to edit the body of the postconditions in an external text editor and save it back to EA.

Before saving the changed postconditions to EA I check if the Element that owns the operation that owns the postcondition is editable. (the only way to test this is to try update() (without having changed anything) on the element and catch the exception if it isn't locked by the user)
Now when a user doesn't have a lock  I call Element.ApplyUserLock().
If that fails (either by throwing an exception, or returning false) I inform the user that somebody else has locked the element.

The problems happen when somebody else has a lock on the Element. The first time it is all fine, I can inform the user of the existing lock on the element. The second time I try this (the case where this or another element is locked by somebody else then the current user) EA crashes hard. No exceptions, no errors, it just plain disappears.

I have found a workaround for this by querying the seclocks table, but I would rather not have to do this.

Steps to reproduce

  • Setup security with option "require user lock to edit"
  • loging with user A
  • Lock element A
  • Login with user B
  • Call ApplyUserLock() on element A
  • notice all is still fine
  • Call ApplyUserLock() on element A
  • notice that EA is gone.

The code for the workaround looks like this:
Code: [Select]
       /// <summary>
        /// locks the element by the current user
        /// </summary>
        /// <returns>true if successful</returns>
        public override bool enableWrite()
        {
            //because of some nasty bug in EA the application will crash if the element is already locked
            // by another user.
            // therefore we check first if this element is locked before even trying.
            string SQLQuery = "select s.entityID from t_seclocks s where s.entityID = '" + this.wrappedElement.ElementGUID + "'";
            XmlDocument result = ((EAModel)this.model).SQLQuery(SQLQuery);
            XmlNode lockNode = result.SelectSingleNode("//entityID");
            if (lockNode == null)
            {
                //no lock found, go ahead and try to lock the element
                try
                {
                    return this.wrappedElement.ApplyUserLock();
                }
                catch (Exception)
                {
                    return false;
                }
            }
            else  
            {
                //lock found, don't even try it.
                return false;
            }
        }
(this.wrappedElement is the actual EA.Element)

The EAModel.SQLQuery method looks like this:
Code: [Select]
       /// <summary>
        /// generic query operation on the model.
        /// Returns results in an xml format
        /// </summary>
        /// <param name="sqlQuery">the query to execute</param>
        /// <returns>the results of the query in an xml format</returns>
        public XmlDocument SQLQuery(string sqlQuery)
        {
            XmlDocument results = new XmlDocument();
            results.LoadXml(this.wrappedModel.SQLQuery(sqlQuery));
            return results;
        }
(this.wrappedModel is the actual EA.Repository)

Reported to Sparx

Geert

160
Bugs and Issues / "StateFlow" connector type not documented
« on: December 21, 2009, 07:51:46 pm »
When looking at the help page about connectors the type "StateFlow" is not mentioned, yet that is the type you get when a transition between two states is selected.

Bug reported

Geert

161
Bugs and Issues / Template diagram copies author
« on: December 10, 2009, 11:14:20 pm »
When you create a template diagram in the "Templates" folder and someone else creates a new diagram of that type the "author" field is copied as well. The result is that all diagrams of that type have the same author: the one who created the template diagram.

Steps to recreate

- Use Security to enable the login
- Create a new package and set it to be the template package
- Create a new diagram in this template package (say ActivityDiagram)
- Login as another user
- Create a new ActivityDiagram somewhere else
- Notice that the author of this diagram is the user who created the template diagram.

Reported to Sparx

162
Bugs and Issues / BUG: Get All Latest not working with security
« on: November 05, 2009, 06:06:54 pm »
I have an issue when trying to do a "get All Latest" on my model.
We are using the EA security with the option "require user lock to edit" and we have a shared common model controlled in TFS.
When I try to do a "get All Latest" function I get an error saying that there are elements that are still locked by users.
That statement is true, but the locks are outside of my controlled packages, so it shouldn't matter.
I can do a get latest of each and every package manually, but I can't use the convenient "Get All Latest".
Sigh, why is this so difficult to get right? :'(

Reported to sparx

Geert

163
Bugs and Issues / BUG: Getlatest not working when using EA security
« on: October 09, 2009, 07:23:16 pm »
Hi,

We use the security feature in EA with the option "Require user lock to edit" option.
Recently I've controlled a part of the model in TFS.
One of the issues is that I can't do a "getLatest" because the package I try it on is not "locked" by me.
I also cannot lock the package since that option is greyed out when controlling a package in TFS.
The only option I have to get the latest version is to do a checkout, and then an "undo checkout".
EA should allow a getLatest on packages who are not locked by me.

Steps to reproduce:
- Setup EA using security and the option "Require user lock to edit"
- Control a package in TFS (or another VC I guess)
- Make sure the package is checked-in, and the lock are released.
- Select option "Package Control/Get latest..."
- Notice the error saying that the necessarry security is not available.

Reported

Geert

164
Bugs and Issues / BUG: Compare utility broken with nested packages
« on: October 09, 2009, 08:20:37 pm »
Hi,

Yet another bug regarding version control.
I've setup version control with TFS and used the option "Save nested version controlled packages to stubs only (recommended)"
Then I have controlled all packages in a model tree so that there are controlled nested packages.
Then I tried the option "Package Control/Compare with controlled version" on a package containing controlled subpackages.
This showed me a whole heap of of "Model only" attributes, links, tagged values etc...
When I try a Compare on the individual sub-packages then I don't get any differences.

Steps to reproduce
- Create package (packageA)
- Create package (packageB) as nested package of packageA
- control both packages in TFS (or another vc system I guess) using the option "nested packages as stubs"
- Compare packageA with the controlled version
- Notice all the "model only" differences.

Reported to Sparx

Geert

165
Bugs and Issues / BUG: Relations in XMI export messes up VC
« on: October 09, 2009, 06:57:02 pm »
Hi,

I've just setup version control with TFS and I've had some issues with relations showing up in the compare utility where they shouldn't.
Apparently EA includes relations in the XMI export even if these relations are owned by other classes/packages then the one being exported.
This really renders the compare utility useless because of all the noise. (not seeing the trees through the forest anymore)

Steps to reproduce:
- Create two packages (PackageA and PackageB) and create a class in each package (ClassA and ClassB)
- Create a diagram in PackageB and add ClassA and ClassB on the diagram
- Draw an association or dependency from ClassB to ClassA setting the sourceRole Non-Navigable and the targetrole navigable.
- Export the packageA to xmi (using the only the same settings as the version control: full EA roundtrip XMI 1.1)
- Open the XMI file and notice that both relations are defined in here.


Reported to Sparx

Geert

Pages: 1 ... 9 10 [11] 12 13 ... 16