Defining base tools for classes

[LeventKent]

Hi everyone,

we just upgraded form EA7.5 to 9.2 and I am very happy with the bug fixes.

I now have one question:

We have a Java application with strict types of components with predefined interfaces.

For example every component in business layer needs to be annotated with @Service such as:

@Service
public class MyBusinessBean {}

I want to specify some class templates, which the technical designers would use (through drag&drop) to model such components.

For example they would select the element BusinessBean and drag&drop to the class diagram and the stereotype would be there automatically.

Is there a convenient&easy way to sepcify such customized tools for modeling in EA?

Thanks in advance,

Levent

[qwerty]

You should define a MDG for that purpose. I have written a tutorial here: http://community.sparxsystems.com/tutorials/extensibility/intro-creating-mdg-file and some additional info here: http://community.sparxsystems.com/resources/mdg-technologies/improved-mdg-creation

q.

[LeventKent]

Hi,

thanks for your advice. MDG looks cool, however I tried yesterday the "UML Pattern" way.

I did define some patterns, which includes the necessary classes for our components. However, I have one problem:

The binding expressions of the classes are not created when the technical designers drag & drop the UML patterns to the class diagram.

For example an interface like:
public interface IWagenRDataAccess extends IReadDataAccess<Wagen>
is modeled in EA through Binding expressions.
After I model the pattern in a class diagram and save it as a pattern, I can see through the preview of the pattern that the bindings are still there. On the otherhand, if someone tries to apply the pattern the bindings disappear.

Is this a bug of EA? Are there any work arounds?

[LeventKent]

Hi again,

I found the workaround for bining expressions. You need to put the paramterized class (to which you bind your other classes) to the template diagram (not create just put a drag&drop a link to the diagram). Just referencing to it through binding expressions does not help for UML patterns.

Thanks for the replies...