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 - «Midnight»

Pages: 1 ... 372 373 [374] 375 376 377
Automation Interface, Add-Ins and Tools / Re: BPMN event icons
« on: May 11, 2006, 03:59:59 am »

Not sure about indicators, but I think there is a way to do the event icons as you require. Search the forum in the last couple of months, although I think 30 days might be enough. I don't remember which section.

If there is not a similar way to handle the indicators - but first experiment when you find the above solution - try submitting this via the Help / On-line Resources / Request a Feature menu.


I think you should be able to change your collegues all you want without affecting the shapes...  ;D

Seriously though, can we protect this particular metadata without changing the settings elsewhere? [Nara_c, I simply have not tried and am not working in a shared environment right now; perhaps you have the answer at hand.]

The second option has all kinds of issues. You my find that the overhead of managing separate projects for this quickly outweighs the benefits (if any). However, my experience is that it is easy to get reference data in different projects out of synch with each other, and this area is particularly prone to problems. It might save you some hair pulling to have a private 'reference' project for your shape scripts, from which you can reload from time to time. This would allow you to 'refresh' your scripts and stereotypes (which you will also want to keep in synch) as needed.


In the case of shape scripts Sparx has been extending the range of elements that can be modified (or at least decorated). Check the release notes for the last few builds.

I do not know if they have been making similar inroads with assignment of alternate graphics (the 'old' way).

This is an area I'd like to see expanded. Paolo doubtless say this should be consistent across the board; I would doubtless agree. Worth starting a "Suggestions" thread folks?

Hi again Frisky,

What are your settings in the diagram properties?

Also, just to be absolutely sure, what exactly do you mean when you say:
apply the sterotype on the diagram
Are you applying the stereotype to an element you have placed on the diagram? If so, is the element the correct base type - from the Settungs / UML / Stereotypes dialog? And, are you absolutely sure you have saved the stereotype before you exited the above dialog (or even changed to another stereotype)? [I know the last question is rather pedantic, but I seem to fail on this at least half the time, and the dialog is very fragile regarding this point.]


Hi Frisky,

Here's the answer you don't want, but also a ray of hope.

I've been asking shape scripts for a while. They are a fairly new feature, and the documentation is not up to date as yet, but they are definitely working on it. My (uneducated) guess is that this will likely synchronize with the product about the time version 6.5 is released. My best guess is that this will be quite soon.

Do a search on forum messages with ShapeScript (or "Shape Script" with the space). Also, try searching my messages on this subject over the last 60 - 75 days or so. Those threads will give you some ideas.

Also, take a look at the BPMN add-in. They have used shape scripts for several of the stereotypes, although they do not cover all the bases.

Let me know how you do on this. I'm still hanging up on a few things and we can compare notes.


BTW, I think I remember from someplace that if you search on - or otherwise use or expect - the stereotypes to be separated by a 'comma space' pair, you will fail. EA will consider the space to be the first character of the latter stereotype and act accordingly, something you likely do not want.

Given that users or other software may format or expect lists for readability it is often worth running the stereotype lists through something like a regular expression filter in either or both directions.

Just thought I'd save you a bit of hair pulling when the time came.


Actually I think it is, although if I remember correctly I needed to try it out before the documentation made sense. With the benefit of hindsight the docs improved somewhat...

Then why not have a "Save as EAX" / "Open as EAX" options

This function - and its analogue at the package level - provides one of the mechanisms for sharing models in a distributed team. Thus, saving and opening entire files was not quite what they were looking for. As well, XMI provides a standard mechanism for communicating UML information (versus a standard interchange, which is still a ways off) that EA, like other products, uses to write and read this type of info. Note that EA can read some other 'dialects' of XMI.

I don't want to "Select anything"

You have to select - as in highlight - the top node (the model itself) before you call up the menu so EA knows that you want to export the entire model (which you say you want to do) instead of just a given package tree. Follow the directions as stated and you should get the result you are looking for.

Not a problem.

Do the following:
  • Open your source model in EA as usual.
  • Select the model itself (i.e. the root element) in the Project View tree.
  • Either: right-click the model element you just selected and use the context menu, or use the Ctrl-Alt-E hot key to get the Export Model to XML dialog. (This is the same hot key that exports a package, but when you select the model root it acts differently.)
  • Set the options you want in the dialog and export.
  • Open or create your target model (remembering that it will be completely overwritten).
  • Select the model root element in the Project View tree.
  • Right click and use the context menu, or use the Ctrl-Alt-I hot key to access the Import Model from XML dialog. (Once again this is a variant of the import package function that works on entire models.
  • Set the options as appropriate and import the file - you will have to confirm that you will be overwriting the target model.
This should solve your problem.

[Note that if you have multiple roots (i.e. several models in one EA project, this applies to each one separately. This is probably a rare enough case that you would have mentioned it if it applied to you. If you want to handle this case you can either export and import each one separately - in this case you will have to create 'dummy' project roots in the target model that will be overwritten; or create a short add-in or external automation program to interate through the source models.]


If I understand you, in essence you are somehow 'hooking' EXEC_ADD_IN when it would normally be time to do a transformation. The add-in then takes over and does whatever it is you want - which may be quite a bit more detailed than an EA transformation script. Finally, you and control back and things continue from the point where your 'transformation' was invoked.

Am I reading you correctly Thomas?

Unfortunately that's where all the hard work, and possible and potential pitfalls, will be found.

Once (if) you can get the information into EA you can get it to where you want - possibly with the aid of an add-in or something.

You may be faced down the line with issues relating to delivering the procedures (with or without Oracle packages) back into a database, but I think there are other options for that.

Oracle seems of late to be producing more tools, or at least richer feature sets, for developers. They've continued their work in the Java world, and some really nifty stuff is coming out for .Net integration - particularly in the 10g world. This could ease some of your downstream workload.

I don't (yet) have a feel for whether these tools could help here. A possibility would be something that could expose Oracle Package structure and internals to (say) Visual Studio (or perhaps one of the Java development environments, perhaps Eclipse). Then perhaps you could somehow grab the information with EA through one of the MDG links. Some unknowns here, and definitely some work involved even in the best case... Who knows?



There's not much on this so far, but take a look at these threads:;action=display;num=1133465934;start=1#1
Particularly near the end,
Note that much of this relates to EA 6.0; perhaps 6.1 goes further than just the root package.

You may have to build an add-in, or some kind of preprocessor, or whatever.


Automation Interface, Add-Ins and Tools / Re: BPMN -> BPEL
« on: February 10, 2006, 08:52:43 am »
And me too!

Also, I think several large projects my clients are contemplating could well use this. One influential client group uses another product, but IMHO it has limited support in this area, and seems more brittle than EA with regard to evolution. It's also somewhat more costly.

Perhaps they (or those around them) would be amenable to adopting EA, although without good support for this (and related) feature it's probably a lost cause.


I take it that "the effect we were looking for" is only available in some external (to EA) application that consumes the EMF files. Is this correct?

And, regardless of the above, what, if anything, are you doing to the EMF files to get the alpha component? Are you tweaking them from the external app?


With a prefix, which must be just right. If you've got this under control fine, otherwise let me know and I'll give you the format.

Or, just copy it from the start menu. Punctuation and spaces are important and must be preserved.


Pages: 1 ... 372 373 [374] 375 376 377