Re: [Andromda-user] Interface generation

2005-04-07 Thread Guillaume Lederrey
Could you be more specific as to where in the Spring HowTo is the advice ? I reread the Spring HowTo and I could not find what you are talking about. I'm probably not looking for the right thing ... but I would be very happy to understand this point ! Thanks ! Guillaume On Apr 1, 2005 11:

AW: [Andromda-user] Interface generation

2005-04-05 Thread =?iso-8859-1?Q?Rahn=2C_R=E9gine?=
: [Andromda-user] Interface generation how ? by writing your own cartridge AndroMDA there's no support for that at this point, although there is an issue for it in JIRA: http://jira.andromda.org/browse/JAVA-6 -- Wouter here's some advice: read the AndroMDA Spring howto what you are

Re: [Andromda-user] Interface generation

2005-04-01 Thread Wouter Zoons
[Greg] I wanted this too. I understand the point of view that AndroMDA is for modeling Spring/Hibernate/Struts/etc, but there are also classes and interfaces I want to design in my system that have nothing to do with Spring/Hibernate/Struts/etc. So it would be nice to model general Java class

RE: [Andromda-user] Interface generation

2005-04-01 Thread Greg Holmberg
> I have an interface(there is a "realize" link between this > interface and the abstract class), an abstract class(with Entity stereotype, I don´t if this > is the right stereotype for an abstract class) and some persistence classses (with Entity > stereotypes),I run the andromda with m

Re: [Andromda-user] Interface generation

2005-04-01 Thread Wouter Zoons
how ? by writing your own cartridge AndroMDA there's no support for that at this point, although there is an issue for it in JIRA: http://jira.andromda.org/browse/JAVA-6 -- Wouter here's some advice: read the AndroMDA Spring howto what you are trying to do is not needed at all! you do NOT need

[Andromda-user] Interface generation

2005-04-01 Thread Rahn, Régine
I am using MDv9.0, andromda 3.0-RCI and the hibernate cartridge. I know hibernate is to deal with persistence classes. I have an interface(there is a "realize" link between this interface and the abstract class), an abstract class(with Entity stereotype, I don´t if this is the right stereotype f