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.

Messages - Uffe

Pages: 1 ... 55 56 [57] 58 59 ... 76
Bugs and Issues / Re: EA 11 RTF bork bork bork
« on: October 30, 2014, 03:05:54 am »
No, the existing thread is
It's EA that crashes, not Windows.

I'm on 1007, btw.


Bugs and Issues / EA 11 RTF bork bork bork
« on: October 30, 2014, 01:54:52 am »
Hi all,

Having very serious issues with EA 11 and RTF document generation. There is an earlier thread on this, but there's no resolution.
  • EA crashes during generation. No error message, just terminates.
  • EA crashes during template editing - sometimes simply from selecting a bit of text and hitting Ctrl-C.
  • I've even observed bit rot, where a template that was working suddenly stops working, after making non-template changes to the MDG Technology and regenerating the XML file.
My templates were originally written in EA 10 (some in EA 9). Does anyone have any magic recipe for fixing these and making sure they don't break again?



Bugs and Issues / Re: Apply Auto Naming and Security
« on: August 21, 2014, 08:14:18 pm »
Cool, thanks. My client is shifting to EA 11 next week, I should be able to hold them off with the ol' whip and chair till then. :)

Bugs and Issues / Apply Auto Naming and Security
« on: August 21, 2014, 06:55:37 pm »
Here's a weird one.

In a security-enabled repository, in order to apply auto names to elements the package must be locked - but the elements must be UNlocked. Yer what?

This is the behavior in 1009, and there's no mention of any changes in the version histories.

Is this really by design? If so, what's the reasoning behind it?


Bugs and Issues / Re: Problems with Baseline compare / restore
« on: August 20, 2014, 12:41:25 am »
To my astonishment :-? for even the simplest difference between 2 baselines (1 UC added) comparing or restoring always ends with the message "Query to complex".
My guess is that the comparison runs out of memory. The default EAP database manager is MS Jet 3.5, which is not the most powerful. Try JET 4.0 (Tools - Options - General) or, if you're on EA 11, Firebird. Or if you can, transfer to another database on the same server as your original project (you mention that you went to EAP for experimentation), that should work.

The .eap file after Project transfer is about 290 MB big. The .eap file after export / import of xmi about 50 MB. This difference puzzles me, too.
An XMI export contains only the package tree, what you see in the project browser. A project transfer duplicates the full database, which contains any number of things that are never shown in the browser -- notably the baselines themselves.

A baseline is stored in the t_document table as a zipped XMI file, so taking a couple of baselines on an entire package tree from the root node on down will soon have a significant impact on the project size.

Because the project contains a lot of secondary stuff besides the project browser content, my recommendation for branching is always to do a project transfer and then prune any contents that aren't needed in the branch, rather than exporting / importing XMI.

You should also make a habit of cleaning out obsolete baselines every once in a while. There's no need to keep them around "just in case" (this confuses version control with backup, which is a Big Bad Practice), as you can export baselines to files for backup purposes.

An empty EAP project on JET 3.5 is about 1 MB, so with 50 MB after XMI import it does sound to me like you're baselining too much in one unit. If you can identify separate parts of the model tree that do not refer to one another, you should baseline those rather than the whole project tree. This can be a very tall order if you haven't set the project up that way from the start.

Finally, the reusable asset functionality in EA 11 provides a somewhat better way to handle this stuff, so I'd advise you to take a look at that too.



Bugs and Issues / "No current project" when project is open
« on: August 12, 2014, 07:36:33 pm »
Hi all,

If you open a project by entering a connection string in the Open Project dialog, and that connection string omits a project name so it looks like EAConnectString:--- DBType=etc etc, EA 10 opens the project but displays "No current project" in the window title.

Probably just cosmetic, but there's always the possibility that some flag is set incorrectly in a way which affects other stuff. Can someone check if this has been found and fixed in EA 11?



Bugs and Issues / Re: Read EAP Files in Package
« on: June 26, 2014, 08:45:19 pm »
You can create a hyperlink of type File - Open (from the Common toolbox in any diagram) and specify the EAP file there. Double-clicking the hyperlink will then open the project.

Bugs and Issues / Re: Read EAP Files in Package
« on: June 26, 2014, 06:44:47 pm »
The content of an .EAP file is actually a database, so you can't reverse-engineer it like you would source code.

You can reverse-engineer databases (including EA's own) into EA with the Import DB Schema function, but you'll only get the structure this way -- not the contents.

Bugs and Issues / Re: Creating a Second Keystore
« on: June 26, 2014, 05:18:38 pm »
Terve Minna,

1. Yes, you can install floating licenses in a file-based keystore. The users just need write access to the file. Whether you can migrate existing licenses from a server-based keystore to a file-based one I don't know.

2. I think so. If I'm not mistaken you can specify the lease period and toggle auto-checkin-on-exit with a file-based keystore, just as you can with a server-based one -- the keystores work the same way from the administration side.

2. (sic) If I understand correctly, you're asking whether the keystore file is installed locally on the laptops. No. You place it on a network drive, and the laptop users connect, check out a non-auto-checkin license and then disconnect.



Bugs and Issues / Re: Execution environment and stereotypes
« on: February 19, 2014, 08:20:41 pm »
a-hAAAA! With you. Thanks! :)

Bugs and Issues / Execution environment and stereotypes
« on: February 19, 2014, 02:01:38 am »
Hi there!

The presentation of stereotypes for execution environment seems a bit screwy.

If I set my own stereotype on an execution environment the element is presented in diagrams as «executionEnvironment,myStereotype». This also applies if I create my own stereotype extending executionEnvironment in a profile.

By contrast, if I set my own stereotype on an interface, it is presented simply as «myStereotype», which is what I want. The «interface» stereotype is displayed only if there is no other stereotype on the element.

In fact, if I tell the diagram not to show element stereotypes, «executionEnvironment» is still shown (but «myStereotype» is not).

Is there some obscure passage in the UML spec to warrant this? Is there some even more obscure EA option I can jiggle with to work around it?

I tried writing a shape script and print the Stereotype field (not StereotypeEx). This resulted in only «myStereotype» being displayed, but surely there must be a better way?



Bugs and Issues / Adding metatype
« on: January 20, 2014, 09:02:43 pm »
Hi there!

In a recent release of a profile, I added the _metatype attribute to one of my stereotypes. I deployed it in the same MDG Technology as always.

In my target project, I have now observed that some of the pre-existing classes with this stereotype are labelled Class (in dialogs etc) while others have the specified metatype. I would like them all to have the metatype.

Does this sound familiar to anyone? Is there a simple trick I can do to force the metatype onto these elements? And what's the underlying reason for this behaviour (so I can avoid it next time I go fiddling with metatypes)?



Bugs and Issues / Re: Document Generator
« on: December 02, 2013, 11:38:53 pm »
Maybe you don't have a template named "ElementName"???

Bugs and Issues / Re: Classifier as attribute type
« on: October 30, 2013, 05:45:59 pm »
Thanks guys. A timing issue? Ouchie...

Would you like me to file it as a bug report?


Bugs and Issues / Classifier as attribute type
« on: October 29, 2013, 06:09:38 pm »

If you select a classifier as the type of an attribute, EA does two things: it writes the classifier's name into the attribute's type (which is shown in diagrams), and it stores a reference to the classifier's object ID in t_attribute.Classifier.

If you then change the classifier's name, the attribute type is not updated to reflect this. Is there a reason for this? It would make more sense to me if the attribute type reflected the classifier's name.



Pages: 1 ... 55 56 [57] 58 59 ... 76