[ 
http://galaxy.andromda.org:8080/jira/browse/JAVA-6?page=comments#action_11182 ]
     
Greg Holmberg commented on JAVA-6:
----------------------------------

Wouter, I've tried that, and it doesn't work--the "implements" clause is not 
generated.

I have however been successful with having a TreeSet class in package java.util 
and a Generalization association to it, causing AndroMDA to generate "extends 
java.util.TreeSet".

Which is good and useful, but I'd also like to be able to generate "implements 
java.util.Set".


Chad, I don't really want to model Java-specific classes, I want to continue 
the pattern you've already established of mapping at generation time.  In other 
words, just like datatype.Set maps to java.util.Set, I'd like an interface.Set 
for use in a <<realize>> Abstraction association that maps to java.util.Set at 
generation time (configured in some XML file, no doubt).

I'm saying I like the mapping idea, I just can't use a datatype in an 
Abstraction relationship in my UML editor.  MagicDraw literally won't let me 
draw that.  And I don't know any way other than an Abstraction relationship to 
indicate to AndroMDA to generate an "implements" clause.

Is there another way to diagram in MagicDraw that will trigger that behavour 
from AndroMDA?

Or are you just not in favor of generating explicit "implements" clauses at 
all?  (I mean, other than the implicit clauses, such as "implements 
java.io.Serializable", or "class FooDaoBase implements FooDao".) 

> Generate generic Java code
> --------------------------
>
>          Key: JAVA-6
>          URL: http://galaxy.andromda.org:8080/jira/browse/JAVA-6
>      Project: Java Cartridge
>         Type: New Feature
>     Reporter: Greg Holmberg
>     Assignee: Wouter Zoons

>
>
> I see that the Java cartridge can generate Services (operations, no 
> attributes) and ValueObjects (attributes, no operations), but how do I 
> generate a simple Java class with operations and attributes?
> I've found that if I use no stereotype at all, nothing gets generated.
> Similarly, how would I generate a simple interface?
> Suggestion: observe the "abstract", "interface", and "enumeration" keywords.  
> "enumeration" would generate a simple Java enum (either the usual convention 
> in Java 1.4 or real enums in 5.0), and not the Hibernate thing that the 
> <<Enumeration>> stereotype does.
> Could also generate the JavaDoc.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://galaxy.andromda.org:8080/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Andromda-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/andromda-devel

Reply via email to