Hi folks, today, I have integrated log4j in AndroMDA. Now, each cartridge generates its own logfile, e.g. andromda-ejb.log, andromda-hibernate.log, etc. There is no velocity.log any more because that file was too confusing to read. With the new logfile format, you can see exactly which model element caused the Velocity messages.
I also upgraded to Velocity 1.3.1 which caused a strange effect in the new ejb cartridge. The method getAttributesAsList() was called in the wrong class with the wrong signature (ScriptHelper instead of EjbScriptHelper). So, I renamed it slightly to make the name unique. This bug has to be reproduced and reported to the Velocity team. The logging feature will help me with the migration to metamodel decorators. That way, I can see which decorators function correctly and which don't. BTW, the ejb cartridge generates a lot of Velocity error messages (see the attached log output). Richard, is there a way to optimize this? Cheers... Matthias --- Matthias Bohlen "Consulting that helps project teams to succeed..." http://www.mbohlen.de/
andromda-ejb-log.zip
Description: Zip compressed data
