Re: [Andromda-devel] model refactoring

[Doroszlai A. <da...@hs...>]

* Matthias Bohlen <mb...@mb...> [2003-10-26 01:21]:
> I'll comment the rest of your mail in detail, later...

OK, I'm looking forward to it.  Till then, I've posted the code as
a patch at [1].  It is against version 2.0.3., but I had taken
some recent changes from CVS, which I have summarized in [2].  So
if you want test my changes, you'll first have to apply the second
patch, then mine.  The dummy cartridge I mentioned is available at
[3].  Finally, two sample models for testing: [4] (one static and
one dynamic pair of models).

[1] http://www.inf.bme.hu/~eti/andromda-history.patch.gz
[2] http://www.inf.bme.hu/~eti/andromda-cvs.patch.gz
[3] http://www.inf.bme.hu/~eti/andromda-dummy-incremental.zip
[4] http://www.inf.bme.hu/~eti/history-sample.tar.gz

If you try it, and everything goes well, you should see something
like:

new value for association: A_incoming_target
	element: org.omg.uml.behavioralelements.activitygraphs.ActionState$Impl
	value: trans_6

which means that one state of the activity model has got a new
incoming transition, whose name is trans_6.  The cartridge has
access to the association and its two ends: the state and the
transition.  Is this amount of information enough for cartridges,
or do they need something more?

Of course the above is just an example, the test models contain
more elements.

Attila