Hi Bogdan,

2 questions:

1. Exactly what kind of elements can be a root element?

2. It may seem easy to add this functionality, but how do we make clear to the user that he can not create a connection (of any kind - association, dependency,...) between modelelements from different root models? Up until now, this problem did not exist, since having 2 root models would require different projects.
Hence, what is the relation with the Project, and zargo file?

Regards,
Michiel


----- Original Message ----- From: "Bogdan Ciprian Pistol" <[EMAIL PROTECTED]> To: "Tom Morris" <[EMAIL PROTECTED]>; "ArgoUML Developers" <[email protected]>
Sent: Friday, July 06, 2007 6:04 PM
Subject: [argouml-dev] UML model root


Hello,

The UML element: Model (defined in superstructure at page 610) can be
used inside a package.
It's possible to have hierarchies of Model elements and it's possible
to have Model elements as siblings (not contained in any container) in
a resource.

I tested this, and an example of the XMI serialization would be:

<?xml version="1.0" encoding="UTF-8"?>
<xmi:XMI xmi:version="2.1"
xmlns:xmi="http://schema.omg.org/spec/XMI/2.1";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xmlns:uml="http://schema.omg.org/spec/UML/2.1.1";
xsi:schemaLocation="http://schema.omg.org/spec/UML/2.1.1
http://www.eclipse.org/uml2/2.1.0/UML";>

 <uml:Model xmi:id="_Rsc0MCvZEdyBwvymrycfVw"/>

 <uml:Model xmi:id="_RsmlMCvZEdyBwvymrycfVw"/>

</xmi:XMI>

So it's possible to have more than one root Model element.

Also, it's possible to have any container as a root element: a
package, a profile, a model.

IMO, ArgoUML should be flexible and if the user wants it should model
any of these possibilities. Also, when we have package merge, it would
be very nice to use multiple resources with package increments and
then merge all of them in one package.
For this functionality ArgoUML should work with any container as the
root element.

What's your opinion about this?

The org.argouml.model.ModelManagementFactory uses one root model. One
solution would be to support as deprecated methods the
setRootMoel()/getRootModel() (not to break anything), but also support
multiple root containers and any kind of root container.

Bogdan,

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



--
No virus found in this incoming message.
Checked by AVG Free Edition. Version: 7.5.476 / Virus Database: 269.10.1/888 - Release Date: 6/07/2007 6:36


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to