Eclipse Community Forums - RDF feed
https://www.eclipse.org/forums/
Eclipse Community ForumsAdvantages of Static Profiles
https://www.eclipse.org/forums/index.php/mv/msg/151921/478255/#msg_478255
i've read the slides concerning static profiles in UML, but i didn't get
the idea behind it. What is the advantage of static profiles in contrast
to normal profiles?
Sorry, for that question, but if this community can't help, i don't know
how should be asked.
Thx
Timothy]]>Timothy Marc2009-03-26T10:00:05-00:00Re: Advantages of Static Profiles
https://www.eclipse.org/forums/index.php/mv/msg/151921/478261/#msg_478261
Originally posted by: give.a.damus.gmail.com
As I understand it, the principal advantages of statically defined
profiles are:
- convenient generated Java API for manipulation of stereotypes and
classes
in the profile (much better than Element::{get,set}Value(...)
methods)
- support for operations, derived attributes, supersets/subsets,
redefinition
in stereotypes
- generation of EValidator for the profile
- ability to use types from other profiles on stereotype
attributes/operations
(dynamic profiles replicate the EClasses for referenced stereotypes,
so they
end up with distinct identities in each profile's definition)
HTH,
Christian
On Thu, 2009-03-26 at 11:00 +0100, Timothy Marc wrote:
> Hey all,
>
> i've read the slides concerning static profiles in UML, but i didn't get
> the idea behind it. What is the advantage of static profiles in contrast
> to normal profiles?
>
> Sorry, for that question, but if this community can't help, i don't know
> how should be asked.
>
> Thx
> Timothy
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.24.1.1">
</HEAD>
<BODY>
Hi, Timothy,<BR>
<BR>
As I understand it, the principal advantages of statically defined profiles are:<BR>
<BR>
- convenient generated Java API for manipulation of stereotypes and classes<BR>
in the profile (much better than Element::{get,set}Value(...) methods)<BR>
- support for operations, derived attributes, supersets/subsets, redefinition<BR>
in stereotypes<BR>
- generation of EValidator for the profile<BR>
- ability to use types from other profiles on stereotype attributes/operations<BR>
(dynamic profiles replicate the EClasses for referenced stereotypes, so they<BR>
end up with distinct identities in each profile's definition)<BR>
<BR>
HTH,<BR>
<BR>
Christian<BR>
<BR>
<BR>
On Thu, 2009-03-26 at 11:00 +0100, Timothy Marc wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
Hey all,
i've read the slides concerning static profiles in UML, but i didn't get
the idea behind it. What is the advantage of static profiles in contrast
to normal profiles?
Sorry, for that question, but if this community can't help, i don't know
how should be asked.
Thx
Timothy
</PRE>
</BLOCKQUOTE>
</BODY>
</HTML>
--=-DTNvide+6vJ1FQ0IFGA7--]]>2009-03-26T13:08:07-00:00Re: Advantages of Static Profiles
https://www.eclipse.org/forums/index.php/mv/msg/151921/627452/#msg_627452
Originally posted by: give.a.damus.gmail.com
As I understand it, the principal advantages of statically defined
profiles are:
- convenient generated Java API for manipulation of stereotypes and
classes
in the profile (much better than Element::{get,set}Value(...)
methods)
- support for operations, derived attributes, supersets/subsets,
redefinition
in stereotypes
- generation of EValidator for the profile
- ability to use types from other profiles on stereotype
attributes/operations
(dynamic profiles replicate the EClasses for referenced stereotypes,
so they
end up with distinct identities in each profile's definition)
HTH,
Christian
On Thu, 2009-03-26 at 11:00 +0100, Timothy Marc wrote:
> Hey all,
>
> i've read the slides concerning static profiles in UML, but i didn't get
> the idea behind it. What is the advantage of static profiles in contrast
> to normal profiles?
>
> Sorry, for that question, but if this community can't help, i don't know
> how should be asked.
>
> Thx
> Timothy
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.24.1.1">
</HEAD>
<BODY>
Hi, Timothy,<BR>
<BR>
As I understand it, the principal advantages of statically defined profiles are:<BR>
<BR>
- convenient generated Java API for manipulation of stereotypes and classes<BR>
in the profile (much better than Element::{get,set}Value(...) methods)<BR>
- support for operations, derived attributes, supersets/subsets, redefinition<BR>
in stereotypes<BR>
- generation of EValidator for the profile<BR>
- ability to use types from other profiles on stereotype attributes/operations<BR>
(dynamic profiles replicate the EClasses for referenced stereotypes, so they<BR>
end up with distinct identities in each profile's definition)<BR>
<BR>
HTH,<BR>
<BR>
Christian<BR>
<BR>
<BR>
On Thu, 2009-03-26 at 11:00 +0100, Timothy Marc wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
Hey all,
i've read the slides concerning static profiles in UML, but i didn't get
the idea behind it. What is the advantage of static profiles in contrast
to normal profiles?
Sorry, for that question, but if this community can't help, i don't know
how should be asked.
I also wanted to mention that versioning of the profile is a key =
difference between static/dynamic use.
With dynamic profiles, when you "define" your profile you add a new =
ecore representation to the list of previously defined profiles. Older =
versions of the profile (the ecore representations) are maintained. =20
With static profiles, the "define" step is replaced by a code generation =
step. You would have to decide how you want to maintain older versions =
of your profile yourself.
... and by the way, Timothy, your question is exactly the kind of =
questions that this newsgroup is made for.
Never be afraid to ask a question here.
As I understand it, the principal advantages of statically defined =
profiles are:
- convenient generated Java API for manipulation of stereotypes and =
classes
in the profile (much better than Element::{get,set}Value(...) =
methods)
- support for operations, derived attributes, supersets/subsets, =
redefinition
in stereotypes
- generation of EValidator for the profile
- ability to use types from other profiles on stereotype =
attributes/operations
(dynamic profiles replicate the EClasses for referenced =
stereotypes, so they
end up with distinct identities in each profile's definition)
HTH,
Christian
On Thu, 2009-03-26 at 11:00 +0100, Timothy Marc wrote:=20
Hey all,
i've read the slides concerning static profiles in UML, but i didn't get =
the idea behind it. What is the advantage of static profiles in contrast =
to normal profiles?
Sorry, for that question, but if this community can't help, i don't know =
=EF=BB=BF<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; CHARSET=3DUTF-8">
<META content=3D"MSHTML 6.00.2900.3492" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>I also wanted to mention that=20
<U>versioning</U> of the profile is a key difference between<FONT=20
face=3D"Times New Roman" size=3D3> static/dynamic =
use.</FONT></FONT></DIV>
<DIV> </DIV>
<DIV>With dynamic profiles, when you "define" your profile you add a new =
ecore=20
representation to the list of previously defined profiles. Older =
versions=20
of the profile (the ecore representations) are maintained. =
</DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV>With static profiles, the "define" step is replaced by a code =
generation=20
step. You would have to decide how you want to maintain older =
versions of your profile yourself.</DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>.. and by the way, Timothy, your =
question is=20
exactly the kind of questions that this newsgroup is made =
for.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Never be afraid to ask a question=20
here.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Cheers,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>- James.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV>"Christian W. Damus" <<A=20
href=3D"mailto:give.a.damus@gmail.com">give.a.damus@gmail.com</A>> =
wrote in=20
message <A=20
href=3D"news:1238072887.6680.16.camel@cdamus-laptop">news:1238072887.6680= ..16.camel@cdamus-laptop</A>...</DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">Hi,=20
Timothy,<BR><BR>As I understand it, the principal advantages of =
statically=20
defined profiles are:<BR><BR> - convenient generated Java API =
for=20
manipulation of stereotypes and classes<BR> in the =
profile=20
(much better than Element::{get,set}Value(...) methods)<BR> - =
support=20
for operations, derived attributes, supersets/subsets,=20
redefinition<BR> in stereotypes<BR> - =
generation of=20
EValidator for the profile<BR> - ability to use types from other =
profiles on stereotype attributes/operations<BR> =
(dynamic=20
profiles replicate the EClasses for referenced stereotypes, so=20
they<BR> end up with distinct identities in each =
profile's=20
definition)<BR><BR>HTH,<BR><BR>Christian<BR><BR><BR >On Thu, 2009-03-26 =
at=20
11:00 +0100, Timothy Marc wrote:=20
<BLOCKQUOTE TYPE=3D"CITE"><PRE>Hey all,
i've read the slides concerning static profiles in UML, but i didn't get =
the idea behind it. What is the advantage of static profiles in contrast =
to normal profiles?
Sorry, for that question, but if this community can't help, i don't know =
I also wanted to mention that versioning of the profile is a key =
difference between static/dynamic use.
With dynamic profiles, when you "define" your profile you add a new =
ecore representation to the list of previously defined profiles. Older =
versions of the profile (the ecore representations) are maintained. =20
With static profiles, the "define" step is replaced by a code generation =
step. You would have to decide how you want to maintain older versions =
of your profile yourself.
... and by the way, Timothy, your question is exactly the kind of =
questions that this newsgroup is made for.
Never be afraid to ask a question here.
As I understand it, the principal advantages of statically defined =
profiles are:
- convenient generated Java API for manipulation of stereotypes and =
classes
in the profile (much better than Element::{get,set}Value(...) =
methods)
- support for operations, derived attributes, supersets/subsets, =
redefinition
in stereotypes
- generation of EValidator for the profile
- ability to use types from other profiles on stereotype =
attributes/operations
(dynamic profiles replicate the EClasses for referenced =
stereotypes, so they
end up with distinct identities in each profile's definition)
HTH,
Christian
On Thu, 2009-03-26 at 11:00 +0100, Timothy Marc wrote:=20
Hey all,
i've read the slides concerning static profiles in UML, but i didn't get =
the idea behind it. What is the advantage of static profiles in contrast =
to normal profiles?
Sorry, for that question, but if this community can't help, i don't know =
=EF=BB=BF<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; CHARSET=3DUTF-8">
<META content=3D"MSHTML 6.00.2900.3492" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>I also wanted to mention that=20
<U>versioning</U> of the profile is a key difference between<FONT=20
face=3D"Times New Roman" size=3D3> static/dynamic =
use.</FONT></FONT></DIV>
<DIV> </DIV>
<DIV>With dynamic profiles, when you "define" your profile you add a new =
ecore=20
representation to the list of previously defined profiles. Older =
versions=20
of the profile (the ecore representations) are maintained. =
</DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV>With static profiles, the "define" step is replaced by a code =
generation=20
step. You would have to decide how you want to maintain older =
versions of your profile yourself.</DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>.. and by the way, Timothy, your =
question is=20
exactly the kind of questions that this newsgroup is made =
for.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Never be afraid to ask a question=20
here.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Cheers,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>- James.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV>"Christian W. Damus" <<A=20
href=3D"mailto:give.a.damus@gmail.com">give.a.damus@gmail.com</A>> =
wrote in=20
message <A=20
href=3D"news:1238072887.6680.16.camel@cdamus-laptop">news:1238072887.6680= ..16.camel@cdamus-laptop</A>...</DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">Hi,=20
Timothy,<BR><BR>As I understand it, the principal advantages of =
statically=20
defined profiles are:<BR><BR> - convenient generated Java API =
for=20
manipulation of stereotypes and classes<BR> in the =
profile=20
(much better than Element::{get,set}Value(...) methods)<BR> - =
support=20
for operations, derived attributes, supersets/subsets,=20
redefinition<BR> in stereotypes<BR> - =
generation of=20
EValidator for the profile<BR> - ability to use types from other =
profiles on stereotype attributes/operations<BR> =
(dynamic=20
profiles replicate the EClasses for referenced stereotypes, so=20
they<BR> end up with distinct identities in each =
profile's=20
definition)<BR><BR>HTH,<BR><BR>Christian<BR><BR><BR >On Thu, 2009-03-26 =
at=20
11:00 +0100, Timothy Marc wrote:=20
<BLOCKQUOTE TYPE=3D"CITE"><PRE>Hey all,
i've read the slides concerning static profiles in UML, but i didn't get =
the idea behind it. What is the advantage of static profiles in contrast =
to normal profiles?
Sorry, for that question, but if this community can't help, i don't know =
------=_NextPart_000_0028_01C9AE2A.BEA602E0--]]>james bruck2009-03-26T19:51:36-00:00Re: Advantages of Static Profiles
https://www.eclipse.org/forums/index.php/mv/msg/151921/627456/#msg_627456
thanks for your answers. Is there a scenario where dynamic profiles are
mandatory? Because everything you stated is great stuff and if there is
no semanticall difference in the usage, i would ever create a static
profile in future.
And how can i find out, whether the profile.uml file, i got from my prof
for my prototype, is a static one?
Thx again
Timothy
ps: Okay, James, i will do so :-)
James Bruck schrieb:
> I also wanted to mention that _versioning_ of the profile is a key
> difference between static/dynamic use.
>
> With dynamic profiles, when you "define" your profile you add a new
> ecore representation to the list of previously defined profiles. Older
> versions of the profile (the ecore representations) are maintained.
>
> With static profiles, the "define" step is replaced by a code generation
> step. You would have to decide how you want to maintain older versions
> of your profile yourself.
>
>
> .. and by the way, Timothy, your question is exactly the kind of
> questions that this newsgroup is made for.
> Never be afraid to ask a question here.
>
> Cheers,
> - James.
>
>
>
>
> "Christian W. Damus" <give.a.damus@gmail.com
> <mailto:give.a.damus@gmail.com>> wrote in message
> news:1238072887.6680.16.camel@cdamus-laptop...
>
> Hi, Timothy,
>
> As I understand it, the principal advantages of statically defined
> profiles are:
>
> - convenient generated Java API for manipulation of stereotypes
> and classes
> in the profile (much better than Element::{get,set}Value(...)
> methods)
> - support for operations, derived attributes, supersets/subsets,
> redefinition
> in stereotypes
> - generation of EValidator for the profile
> - ability to use types from other profiles on stereotype
> attributes/operations
> (dynamic profiles replicate the EClasses for referenced
> stereotypes, so they
> end up with distinct identities in each profile's definition)
>
> HTH,
>
> Christian
>
>
> On Thu, 2009-03-26 at 11:00 +0100, Timothy Marc wrote:
>> Hey all,
>>
>> i've read the slides concerning static profiles in UML, but i didn't get
>> the idea behind it. What is the advantage of static profiles in contrast
>> to normal profiles?
>>
>> Sorry, for that question, but if this community can't help, i don't know
>> how should be asked.
>>
>> Thx
>> Timothy]]>Timothy Marc2009-03-26T20:00:07-00:00Re: Advantages of Static Profiles
https://www.eclipse.org/forums/index.php/mv/msg/151921/478265/#msg_478265
thanks for your answers. Is there a scenario where dynamic profiles are
mandatory? Because everything you stated is great stuff and if there is
no semanticall difference in the usage, i would ever create a static
profile in future.
And how can i find out, whether the profile.uml file, i got from my prof
for my prototype, is a static one?
Thx again
Timothy
ps: Okay, James, i will do so :-)
James Bruck schrieb:
> I also wanted to mention that _versioning_ of the profile is a key
> difference between static/dynamic use.
>
> With dynamic profiles, when you "define" your profile you add a new
> ecore representation to the list of previously defined profiles. Older
> versions of the profile (the ecore representations) are maintained.
>
> With static profiles, the "define" step is replaced by a code generation
> step. You would have to decide how you want to maintain older versions
> of your profile yourself.
>
>
> .. and by the way, Timothy, your question is exactly the kind of
> questions that this newsgroup is made for.
> Never be afraid to ask a question here.
>
> Cheers,
> - James.
>
>
>
>
> "Christian W. Damus" <give.a.damus@gmail.com
> <mailto:give.a.damus@gmail.com>> wrote in message
> news:1238072887.6680.16.camel@cdamus-laptop...
>
> Hi, Timothy,
>
> As I understand it, the principal advantages of statically defined
> profiles are:
>
> - convenient generated Java API for manipulation of stereotypes
> and classes
> in the profile (much better than Element::{get,set}Value(...)
> methods)
> - support for operations, derived attributes, supersets/subsets,
> redefinition
> in stereotypes
> - generation of EValidator for the profile
> - ability to use types from other profiles on stereotype
> attributes/operations
> (dynamic profiles replicate the EClasses for referenced
> stereotypes, so they
> end up with distinct identities in each profile's definition)
>
> HTH,
>
> Christian
>
>
> On Thu, 2009-03-26 at 11:00 +0100, Timothy Marc wrote:
>> Hey all,
>>
>> i've read the slides concerning static profiles in UML, but i didn't get
>> the idea behind it. What is the advantage of static profiles in contrast
>> to normal profiles?
>>
>> Sorry, for that question, but if this community can't help, i don't know
>> how should be asked.
>>
>> Thx
>> Timothy]]>Timothy Marc2009-03-26T20:00:07-00:00Re: Advantages of Static Profiles
https://www.eclipse.org/forums/index.php/mv/msg/151921/627458/#msg_627458
under the profile itself) it is dynamic.
If there is code generated from the profile, it is static.
The use of dynamic vs. static is an implementation distinction. From a UML
point of view, the two techniques are equivalent.
- James.
"Timothy Marc" <tmothymarc@freenet.de> wrote in message
news:gqgmsa$phu$1@build.eclipse.org...
> Hey Guys,
>
> thanks for your answers. Is there a scenario where dynamic profiles are
> mandatory? Because everything you stated is great stuff and if there is no
> semanticall difference in the usage, i would ever create a static profile
> in future.
>
> And how can i find out, whether the profile.uml file, i got from my prof
> for my prototype, is a static one?
>
> Thx again
> Timothy
>
> ps: Okay, James, i will do so :-)
>
> James Bruck schrieb:
>> I also wanted to mention that _versioning_ of the profile is a key
>> difference between static/dynamic use.
>> With dynamic profiles, when you "define" your profile you add a new
>> ecore representation to the list of previously defined profiles. Older
>> versions of the profile (the ecore representations) are maintained. With
>> static profiles, the "define" step is replaced by a code generation step.
>> You would have to decide how you want to maintain older versions of your
>> profile yourself.
>> .. and by the way, Timothy, your question is exactly the kind of
>> questions that this newsgroup is made for.
>> Never be afraid to ask a question here.
>> Cheers,
>> - James.
>> "Christian W. Damus" <give.a.damus@gmail.com
>> <mailto:give.a.damus@gmail.com>> wrote in message
>> news:1238072887.6680.16.camel@cdamus-laptop...
>>
>> Hi, Timothy,
>>
>> As I understand it, the principal advantages of statically defined
>> profiles are:
>>
>> - convenient generated Java API for manipulation of stereotypes
>> and classes
>> in the profile (much better than Element::{get,set}Value(...)
>> methods)
>> - support for operations, derived attributes, supersets/subsets,
>> redefinition
>> in stereotypes
>> - generation of EValidator for the profile
>> - ability to use types from other profiles on stereotype
>> attributes/operations
>> (dynamic profiles replicate the EClasses for referenced
>> stereotypes, so they
>> end up with distinct identities in each profile's definition)
>>
>> HTH,
>>
>> Christian
>>
>>
>> On Thu, 2009-03-26 at 11:00 +0100, Timothy Marc wrote:
>>> Hey all,
>>>
>>> i've read the slides concerning static profiles in UML, but i didn't
>>> get the idea behind it. What is the advantage of static profiles in
>>> contrast to normal profiles?
>>>
>>> Sorry, for that question, but if this community can't help, i don't
>>> know how should be asked.
>>>
>>> Thx
>>> Timothy]]>james bruck2009-03-27T16:07:00-00:00Re: Advantages of Static Profiles
https://www.eclipse.org/forums/index.php/mv/msg/151921/478267/#msg_478267
under the profile itself) it is dynamic.
If there is code generated from the profile, it is static.
The use of dynamic vs. static is an implementation distinction. From a UML
point of view, the two techniques are equivalent.
- James.
"Timothy Marc" <tmothymarc@freenet.de> wrote in message
news:gqgmsa$phu$1@build.eclipse.org...
> Hey Guys,
>
> thanks for your answers. Is there a scenario where dynamic profiles are
> mandatory? Because everything you stated is great stuff and if there is no
> semanticall difference in the usage, i would ever create a static profile
> in future.
>
> And how can i find out, whether the profile.uml file, i got from my prof
> for my prototype, is a static one?
>
> Thx again
> Timothy
>
> ps: Okay, James, i will do so :-)
>
> James Bruck schrieb:
>> I also wanted to mention that _versioning_ of the profile is a key
>> difference between static/dynamic use.
>> With dynamic profiles, when you "define" your profile you add a new
>> ecore representation to the list of previously defined profiles. Older
>> versions of the profile (the ecore representations) are maintained. With
>> static profiles, the "define" step is replaced by a code generation step.
>> You would have to decide how you want to maintain older versions of your
>> profile yourself.
>> .. and by the way, Timothy, your question is exactly the kind of
>> questions that this newsgroup is made for.
>> Never be afraid to ask a question here.
>> Cheers,
>> - James.
>> "Christian W. Damus" <give.a.damus@gmail.com
>> <mailto:give.a.damus@gmail.com>> wrote in message
>> news:1238072887.6680.16.camel@cdamus-laptop...
>>
>> Hi, Timothy,
>>
>> As I understand it, the principal advantages of statically defined
>> profiles are:
>>
>> - convenient generated Java API for manipulation of stereotypes
>> and classes
>> in the profile (much better than Element::{get,set}Value(...)
>> methods)
>> - support for operations, derived attributes, supersets/subsets,
>> redefinition
>> in stereotypes
>> - generation of EValidator for the profile
>> - ability to use types from other profiles on stereotype
>> attributes/operations
>> (dynamic profiles replicate the EClasses for referenced
>> stereotypes, so they
>> end up with distinct identities in each profile's definition)
>>
>> HTH,
>>
>> Christian
>>
>>
>> On Thu, 2009-03-26 at 11:00 +0100, Timothy Marc wrote:
>>> Hey all,
>>>
>>> i've read the slides concerning static profiles in UML, but i didn't
>>> get the idea behind it. What is the advantage of static profiles in
>>> contrast to normal profiles?
>>>
>>> Sorry, for that question, but if this community can't help, i don't
>>> know how should be asked.
>>>
>>> Thx
>>> Timothy]]>james bruck2009-03-27T16:07:00-00:00