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 ... 5 6 [7] 8 9 ... 14
General Board / 7.1 beta status
« on: January 29, 2008, 10:55:19 pm »

I've just noticed the release of version 7.1 (beta). Wow, there are some really nice new features in there. Especially the formatting will make the crowd wild in this organisation.
Anyone know the average time between beta status and general available status?
We are on the brink of rolling out EA and I might consider postponing if the general version is coming very soon.

General Board / Object attributes unreachable
« on: January 17, 2008, 12:15:31 am »
I have noticed some weird behaviour in EA regarding object diagram.
Follow the following steps
- Create Class "Class1"
- add attribute to Class1 "ClassAtt"
- Create object diagram
- Create object on the object diagram "object1"
- Add attribute to object1 "ObjectAtt"
- set the classifier of object1 to Class1
- Try to edit ObjectAtt

There seems to be no way to edit the attribute of the object. I only get the dialog for the attributes of the class. I also haven't found a way to break the link between the object and the class.
Does anyone have a solution for this?

General Board / Version control puzzle
« on: August 24, 2007, 04:30:43 am »

Another one on the version control.
I'm using EA 7.0.815 with an oracle repository (although for this problem I tested with a .eap file as well)
I'm testing the integration with PCVS (versions 8 (Merant) and 10 (Serena) through the scc interface.
First we tested Serena with two users userA and userB
We did following:
- A packageA is checked in in the VC
- UserA nor UserB can modify packageA
- UserA checks out a packageA from VC
- UserA can now modify packageA
- UserB cannot modify packageA

So far so good, works exactly as expected. Now I did the same test with PVCS8

- A packageA is checked in in the VC
- UserA nor UserB can modify packageA
- UserA checks out a packageA from VC
- UserA can now modify packageA
- UserB can ALSO modify packageA :o

No I'm really puzzled. It seems like the settings for PVCS8 and PVCS10 are exaclty the same. In EA I don't see a difference... I really don't know anymore.  ???
Anyone that can shed some light on it?

General Board / "String literal too long" importing XMI
« on: August 03, 2007, 12:26:17 am »
When I import a unisys xmi file directly into my Oracle repository I get several errors: "ORA-01704: string literal too long".
The importing screen is indicating that is is "Adding notes"
Importing that same xmi file in a local eap or MySQL repository works fine.
I'm using EA corporate v 7.0.815 and Oracle

General Board / Build 816 zip file misconfigured
« on: August 30, 2007, 08:55:28 pm »
Just downloaded the 816 build zip file, and unzipped it over my install directory. Instead of overwriting all the files in my EA install directory it created a sub-directory called EA70_816 and put all the files there.
I needed to copy them over my install directory to get the latest version.
I'll send an email to sparx support as well.

General Board / BUG: Strip GUID's corrupts database
« on: August 16, 2007, 09:58:48 pm »
I found a major bug in EA (7.0.815)
When importing an xmi file that was created using version control and selecting the option "Strip GUID's", the database gets corrupted someway. It crashes EA (windows application error: The instruction at "0x09bacd3d" referenced memory at "0x0000000c". The memory could not be "read".)
After restarting EA the model is no longer accessible, when trying to load the model EA crashes with the same message.
This bug is not related to the repository type. (I reproduced the error on Oracle, Mysql and .eap file)
It does seem to be related to the version control settings. We have Serena Dimensions (PVCS 10) setup as version control system through the scc interface. It is only when the version control is configured that it has this problem. When using a new project, without the version control setup, it imports fine.
I'll submit a bug report for this issue.

General Board / Tagged values content lost on XMI import
« on: August 03, 2007, 04:49:47 am »

Another one on the unisys XMI import.
I'm converting my Rational Rose model to EA. In that RR model I had a lot of information in the so-called properties. (like preconditions, purpose etc).
I exported this RR model using the unisys xmi export, and I have imported that into my EA model. That works fine. (as long as you're not working on an Oracle rep; see other post)
The XMI import will nicely create tagged values and copy the content into the "value" field of the tagged value. Unfortunately it will also cut-off the text at 255 chr's without warning! I've had a look into the db-schema and the value field of t_objectproperties is only varchar(255). There is another field (note) that has TEXT (MysQL) datatype, but that is not used.
Another bug report?

General Board / "Value too large" when importing XMI
« on: August 05, 2007, 09:49:09 pm »

Another one on the XMI import/export.
When exporting an object to XMI (EA xmi export) that has a tagged value, I get an error importing that same XMI file.
This only seems to be happening when you have special characters in the tagged value (tabs, CR-LF,???) and when the total of 255 charachters is used in the tagged value.
I tested this with a plain '123456...' and that was fine.
Tested with the text:
Er wordt een nieuw mfa record aangemaakt met invulling van de volgende velden
MFA-TYPERECORDA037.Type de record

and when trying to import the xmi I got a database error: "ORA-12899: value too large for column "D00ARCH01"."T_OBJECTPROPERTIES"."VALUE" (actual: 262, maximum: 255)"
I'm very worried about this since the version control add-ins use this xmi import/export principle; and i'm afraid it is going to be a problem there too. (I'm testing version control integration in the next weeks)

I'll be submitting a bug report for this issue.

General Board / Best practices on branching?
« on: August 16, 2007, 10:19:10 pm »

I was wondering what would be the best practice in handling branching.
We have EA 7.0.815, a central (oracle) repository and a version control system (Serena Dimensions) integrated using the scc interface.
Imagine following situation:
We have released our application with version 1.0
We are now working on towards version 2.0
We get a major bug report that requires a patch on version 1.0 (so 1.1).
Now what is the best way to branch (a part of) the model to create this 1.1?
I tried getting the xml file (v 1.0) from the version control system, and importing that into a new root model (selecting "strip GUID's") to create an alternative copy, but that resulted in corrupting my whole project. (see post;action=display;num=1187333928)

General Board / Compare utility evaluation
« on: August 09, 2007, 11:14:32 pm »

I'm evaluating EA (7.0.815 on Oracle repository) and I'm currently looking at the compare utility. I found some weird things, and I would like your thoughts.
- I started trying to compare a package with a generated xmi file. So logically I used the context menu option "export package to xmi file..." on a test package to create the xmi file. I did not change any of the default settings, so it created an xmi 2.1 file. I then tried to compare the created xmi file with my (unchanged) package. To my surprise the compare utility gave the [sarcasm] very usefull [/sarcasm] message: "An error has occured during the compare process"
- After some fiddling about I found the option to control my package and thus exporting it to an xmi file. (xmi 1.1). I did the same thing, compare the created xmi file with my unchanged package; and to my surprise I still got a lot of changes, and even some deletes ?!?

Do any of you have any experience with the compare utility? Because, like it is now, reporting changes without changing anything, this seems totally useless to me.

Bugs and Issues / Formatted fields in SQL Fragments
« on: December 02, 2015, 09:23:43 pm »
In v12.1 it should be possible to use formatted notes in SQL fragments.
According to the help it says:
It is possible to force a field to be processed as formatted notes, by providing a column in this format:
    custom >
     <fieldname>-Formatted     (for .eap (JET) repositories, or <fieldname>.Formatted for other types of repository)
     < custom
In your custom SQL Query statement, you must use an alias matching the template field name; for example (in MySQL):
     SELECT ea_guid AS CLASSGUID, Object_Type AS CLASSTYPE, Name, Note as "Note.Formatted" FROM t_object
     Where Object_ID=#OBJECTID#

I tried to do that on .eap file, but it doesn't seem to work:
Code: [Select]
Custom Query:
Code: [Select]
select c.[SourceCard] AS SMultiplicity, o.[Name] AS Source, c.[Name] AS ConnectorName,
c.[DestCard] AS TMultiplicity, ot.[Name] as Target, c.[Notes] AS [Description-Formatted]
from (( t_object o
inner join t_connector c on c.[Start_Object_ID] = o.Object_ID)
inner join t_object ot on ot.Object_ID = c.[End_Object_ID])                      
where o.Object_ID = #OBJECTID#
and c.[Connector_Type] in ('Association', 'Aggregation')

The in the output I only get the text Description-Formatted, not the formatted notes I was after.

A) what am I doing wrong?

B) Who decided to use a . notation that isn't compatible between JET and the SQL databases, and in doing so making my templates dependent on the database type?

C) Why is the documentation partially for Jet and partially for MySQL? Is it too much to ask to make a complete example for both?


Bugs and Issues / V12: can't check attribute's type
« on: October 21, 2015, 05:58:44 pm »
Before v12 you could click on the [...] button next to the type field of an attribute to select a classifier to serve as datatype for the attribute.
If the attribute was already linked to a datatype the elementpicker dialog would already select this dataype in the tree view.

This was AFAIK the only native way to check which datatype was linked to your attribute. (I never used this for myself since I have this build into the EA Navigator)

But now since v12 the [...] has been replace with the drowdown option Select type.... This also opens up the element picker dialog, but it no longer selects the existing datatype if that was already linked.

So now the EA Navigator is the only way I can see if an attribute is linked to a datatype, or if the datatype was simply typed in.


Bugs and Issues / Addins broken in Lite edition v12
« on: October 08, 2015, 12:22:46 am »
The lite edition of v12 broke all of my addins >:(

I am not amused.

Example code:
Code: [Select]
this.navigatorControl = this.model.addWindow("Navigate", "TSF.UmlToolingFramework.EANavigator.NavigatorControl") as NavigatorControl;The addWindow returns null for the lite version.

This used to work perfectly fine in version 10.

bug reported


Bugs and Issues / Extending ActivityInitial/Final doesn't work
« on: September 15, 2015, 11:47:00 pm »
I'm making a UML profile, and I have created stereotype that extends ActivityInitial and one that extends ActivityFinal.
After adding attributes tot he stereotype I expected to see them as tagged values in my model.
But some some reason the tagged values don't appear. If I change the extend to Action then the tagged values appear without a problem.

Has anyone experienced this?
Have I missed something?



Bugs and Issues / Bugs will be fixed in the next release
« on: June 11, 2015, 03:58:01 pm »
The last two days I got two emails from Sparx support stating that the bugs I reported would be fixed in the next release.

I must say I really appreciate that, and it makes me more inclined to report bugs in the future.

Keep up the good work guys!


Pages: 1 ... 5 6 [7] 8 9 ... 14