Eclipse Community Forums: UML2 » reuse the primitiveTypes package

Help

Home

Home » Modeling » UML2 » reuse the primitiveTypes package

Show: Today's Messages :: Show Polls :: Message Navigator

reuse the primitiveTypes package [message #474273]

Wed, 18 July 2007 10:23

Manar El-Kady

Messages: 78
Registered: July 2009

Member

Hi,

I notice in the InfrastructureLibrary that the Abstractions, Constructs,
and Basics packages import the primitiveTypes package, while in the
superstructure, the kernel package merge the primitiveTypes package.

I know that the package import allows visibility for the package
elements and the package merge allows extending its features. But, I
didn't get it clear for why the Abstraction and the Constructs import
the primitiveTypes package while the kernel package merge it?

Also, in which case, I can import the primitiveTypes package and in
which case I should merge it while building a new metamodel?

Thanks in advance,

Manar

Report message to a moderator

Re: reuse the primitiveTypes package [message #474387 is a reply to message #474273]

Thu, 19 July 2007 14:02

james bruck

Messages: 1724
Registered: July 2009

Senior Member

Hi Manar,

I spoke to Kenn about this so I'll try to regurgitate some of that
conversation.

The primitive types package is considered a building block and not a
language unit with its own namespace. If you want to create your own DSL
and use primitive types as defined in the primitve types package you should
merge it in.
Other packages like 'Constructs' import the primitiveTypes package because
'Constructs' also is not a language unit with its own namespace. Those
elements that want to use 'Constructs' as part of the definition of a
language (ie a DSL) (defining its own namesapce) would have to merge
PrimitiveTypes.

A quick search of open issues turned up these two.

http://www.omg.org/issues/uml2-rtf.open.html#Issue9878
http://www.omg.org/issues/uml2-rtf.open.html#Issue9180

Hope that helps.

- James.

"Manar El-Kady" <manar.elkady@gmail.com> wrote in message
news:f7kpnr$j2q$1@build.eclipse.org...
> Hi,
>
> I notice in the InfrastructureLibrary that the Abstractions, Constructs,
> and Basics packages import the primitiveTypes package, while in the
> superstructure, the kernel package merge the primitiveTypes package.
>
> I know that the package import allows visibility for the package
> elements and the package merge allows extending its features. But, I
> didn't get it clear for why the Abstraction and the Constructs import
> the primitiveTypes package while the kernel package merge it?
>
> Also, in which case, I can import the primitiveTypes package and in
> which case I should merge it while building a new metamodel?
>
>
> Thanks in advance,
>
> Manar

Report message to a moderator

Re: reuse the primitiveTypes package [message #474397 is a reply to message #474387]

Sat, 21 July 2007 06:30

Manar El-Kady

Messages: 78
Registered: July 2009

Member

Really, it helps me. Thanks for you and Kenn for this detailed reply.

Manar

James Bruck wrote:
> Hi Manar,
>
> I spoke to Kenn about this so I'll try to regurgitate some of that
> conversation.
>
> The primitive types package is considered a building block and not a
> language unit with its own namespace. If you want to create your own DSL
> and use primitive types as defined in the primitve types package you should
> merge it in.
> Other packages like 'Constructs' import the primitiveTypes package because
> 'Constructs' also is not a language unit with its own namespace. Those
> elements that want to use 'Constructs' as part of the definition of a
> language (ie a DSL) (defining its own namesapce) would have to merge
> PrimitiveTypes.
>
> A quick search of open issues turned up these two.
>
> http://www.omg.org/issues/uml2-rtf.open.html#Issue9878
> http://www.omg.org/issues/uml2-rtf.open.html#Issue9180
>
> Hope that helps.
>
> - James.
>
>
> "Manar El-Kady" <manar.elkady@gmail.com> wrote in message
> news:f7kpnr$j2q$1@build.eclipse.org...
>> Hi,
>>
>> I notice in the InfrastructureLibrary that the Abstractions, Constructs,
>> and Basics packages import the primitiveTypes package, while in the
>> superstructure, the kernel package merge the primitiveTypes package.
>>
>> I know that the package import allows visibility for the package
>> elements and the package merge allows extending its features. But, I
>> didn't get it clear for why the Abstraction and the Constructs import
>> the primitiveTypes package while the kernel package merge it?
>>
>> Also, in which case, I can import the primitiveTypes package and in
>> which case I should merge it while building a new metamodel?
>>
>>
>> Thanks in advance,
>>
>> Manar
>
>

Report message to a moderator