I'd like to propose that the database type mappings database be added to
andromda.jar, with the default to get the type mapping from there. This will
facilitate Maven packaging, and since the it is simple to override the type
mapping in the build.xml, it should pose no problem to have a default in
all,
I have a Maven plugin itching for a checkin. There are a few things that
need to be done for this:
1) The jars for AndroMDA need to go up on ibiblio. This isn't a problem for
me to take care of, but I need to find out what versions that should go up.
It would be nice if there could be a re
Support Requests item #715387, was opened at 2003-04-04 08:39
Message generated for change (Comment added) made by nobody
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=536546&aid=715387&group_id=73047
Category: Code generation Problem
Group: v1.0 (example)
Status:
Title: Nachricht
Yep makes perfect sensethats what I ended up
doing. My question to you is in the way you might model any additional
information needed to execute tests, such as the initial load data, etc.
It would be nice to be able to automate them more than just generating a
skeleto
hi people,
I ran into a small issue during development and more specifically the
implementation of the validation methods.
currently the validate() method is called upon decorator constructor (by
the factory), while this seems a plausible approach it has a (IMO)
severe drawback
suppose you are
Hi Matthias,
thanks for your response!
thanks for contributing the idea but I'd like to avoid this indirection
- each indirection is one additional level of complexity.
yes this is true. A good example is the deployment descriptors of
EJB (2 files, one container independent and one container depe
> -Original Message-
> From: Matthias Bohlen [mailto:[EMAIL PROTECTED]
> Subject: RE: [Andromda-devel] Lower case stereotype names
>
> P.S.: We should solve the lowercase stereotype problem another way.
The patch I have:
cvs diff src\java\org\andromda\cartridges\mgmt\CartridgeDictionary.j
Hi Lofi,
thanks for contributing the idea but I'd like to avoid this indirection
- each indirection is one additional level of complexity.
> One more
> advantage: the user can see directly what kind of
> stereotypes, tagged values, etc. are used by the cartridge in
> one glance without having t
Matthias,
What do you think about a cartridge to generate
tests? Right now I'm thinking about testing webservices/session
ejbs I'm generating from a cartridge. I'd like to do it for my company,
and I've been trying to think about the best ways to model this. Do you
have any ideas?
Tha
personally I don't like that idea because 5 errors in one decorator
would still require 5 generation runs
We can optimize this. Each decorator has a field called "logger" so that
you could call
logger.error(Object)
on each issue that you find during validation. The output would go to
the
Hi Wouter,
my 2 cents below... :-)
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf
> Of Wouter Zoons
> Sent: Monday, January 26, 2004 6:19 PM
> To: Matthias Bohlen
> Cc: 'Developers AndroMDA'
> Subject: Re: [Andromda-devel] MMDs and validation
>
>
11 matches
Mail list logo
