Chad Brandon wrote:
Guess what :-) No errors any more! It was so much fun resolving those issues with you at hand, that I am almost sorry that there are no issues any more. Now I may go to bed happily.Actually one last problem persists :)))
I have one Exception class modelled which should be used four times (I
drew dependencies from four different entities/service to the
Exception...). The result is that AndroMDA generates four times a file
with the great name .java (no name, just the extension) - AND it keeps
the placeholders in the file instead of replacing those with the chosen
class name (I did give the class a name, I am sure of that. It is empty
otherwise, tho...). Still it correctly places that noname class in the
correct package :-).
Do you have the exception stereotyped with <<Exception>> as well as adding a dependency to it with <<ExceptionRef>>? If so try getting rid of the <<ExceptionRef>> and just have the plain dependency to the class with <<Exception>>. Or if its your own exception that you aren't generating, then you'd want to have the <<ExceptionRef>> and NOT the <<Exception>> on your class (however that does need to be fixed so that it does handle both stereotypes).
Thanks again!
Daniel
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Andromda-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/andromda-user
