Thanks Chad, that would be great.
-Vikram.
-----Original Message-----
From: Chad Brandon [mailto:[EMAIL PROTECTED]
Sent: Wed 8/18/2004 3:14 PM
To: Naik, Vikram; [EMAIL PROTECTED]
Cc:
Subject: RE: [Andromda-user] UML API for checking modeled element is Interface.
--- "Naik, Vikram" <[EMAIL PROTECTED]> wrote:
> Hello,
>
> We have a requirement of generating plain java
> objects. The element modelled can be a class,
> abstract class or an interface which are stereotyped
> as <<POJO>>. Now when an element modelled as
> interface I am not able to find a API which would
> indicate that the element is Interface and not
> Class. We are generating all the plain java objects
> using one stereotype. The current work around we
> have is we tag the element if its an Interface.
>
> So I ask , is there any API available which can
> indicate this difference of modeled API ?
>
> When we model an element as interface does the
> androMDA api instantiates a different meta-class
> then it does for a class. In that case I can use "
> instanceof " operator to know the difference.
AndroMDA instantiates a ClassifierFacade for
org.omg.uml.foundation.core.UmlClass,
org.omg.uml.foundation.core.Interface and
org.omg.uml.foundation.core.DataType. I'll add an
isInterfaceType() for you on the ClassifierFacade.
>
> -Vikram.
>
>
> -----Original Message-----
> From: Chad Brandon [mailto:[EMAIL PROTECTED]
> Sent: Wed 8/18/2004 2:53 PM
> To: Naik, Vikram;
> [EMAIL PROTECTED]
> Cc:
> Subject: Re: [Andromda-user] UML API for checking
> modeled element is Interface.
>
>
>
>
> --- "Naik, Vikram" <[EMAIL PROTECTED]> wrote:
>
> > Hello,
> >
> > How do we recognize, that a modelled element is
> of
> > type interface or class?
> > Simplest way would be to stereotype them. But say
> we
> > have a requirement of having both the types under
> > one stereotype <<POJO>>. I am not able to find
> any
> > uml API support like isInterface() etc...
>
> Why would you want to model both the class and the
> interface? Why don't you just generate both from
> the
> single modeled element stereotyped as <<POJO>>? If
> you're modeling both the class and interface then I
> would say you're getting a little too
> implementation
> specific. You shouldn't care whether or not the
> modeled element is a class or interface because it
> doesn't really provide any value.
>
> >
> > Please comment.
> >
> > Regards,
> > Vikram Naik.
> >
>
HS^ÃÂÃÂÃÂà XÃÂÃÂÃÂ'ÃÂà ÃÅuÃÂÃââÃâ Ã
xÃÂÃÂ!rÃâÂÃâÂÃÂÃÂÃÂÃÂÃÂqÃÂ'VÃÂÃÂÃâÃÂÃâÂÃÂtÃâÃâÂÃÂxÃâ
>
>
PÃâÃÂÃÂÃÂÃâÂÃÂÃâouÃâJdJÃâÂÃÂp5CÃÂÃÂÃÂÃâÂÃÂÃâ}ÃâjÃÂÃÂÃâÃâÂÃÅEÃÂZÃ
Z'"yÃÂwÃÂÃÂÃÂJÃÂÃÂ)à jwEÃÂÃÂÃâ ÃâÂÃÂaÃÂÃÅÃÂ
>
0ÃÂ)ÃÂÃâÃâÃâÂÃÅ&ÃÂ?ÃËÃÂHÃÅÃÂ&ÃÂÃÂÃÂÃÂÃÂÃÂ?ÃÂ]<ÃÂo9wkÃÂgZÃÂÃâÃÂÃâÂÃÂÃÂÃ
x%Ã [EMAIL PROTECTED]
ÃâlÃÂÃâÂÃÂqÃÂÃÂÃÂÃÂzÃËmÃÂÃâÂ?ÃÂXÃÂÃÂÃâ(ÃÂÃÂ~Ã
à zwÃÂÃÂXÃÂÃÂÃÂÃÂà ÃâbÃÂÃÂ?jwkÃÂgZÃÂÃâÃÂ
>
>
>
>
HS^µéX¬²'²Þu¼xµç!r£¬¶âqê'V§ÇtÒ¢x
PÑãèåËouÓJdJâp5CùèåË}Òj÷¹ÒßEëZZ'"y¢w«·J©¦)àjwEçûa¶Úÿ
0²)â×
Ê&ÿ?ÈHÞ&«¶¸ë?÷]<[EMAIL PROTECTED](º·~àzwþX¬¶ÏåËbú?jwk¢gZºÇ