Quote:
Thanks for your quick replies,



gratulations joelkoz, that it is compiling for you. But all the steps you 
described i have allready done, as i wrote in my initial Posting (i mean the 
creating of my own 'DataTypes', in a Namespace called datatype.)



but it still brings up the failure with "no UML DataType". Can you give me a 
step by step solution to creating valid UML Datatypes in Poseidon?


(end of quote)




I really had to fiddle with it to get it to work.  I tried so many things, but 
I THINK I ended up doing something like this which should work for an EXISTING 
diagram:



Assumption: For a modeled class named MyClass:



<<Entity>>

MyClass

-----------

+id: long

+myString: String

+myDate: Date





1) Switch the "Navigation pane" to be "Model Centric", and insure all of your 
data types show up there underneath the "Datatypes" node. By this, I mean the 
"Datatypes" node with the "DataType" icon, and NOT a node underneath the 
"Classes" node or the "Packages" node.  For my first attempt, the "String" type 
was NOT in the "Datatypes" node - it was in the "Classes" node (even though it 
was in a "namespace" I created named "datatypes"). I couldn't figure out a way 
to create my own datatypes using Poseindon, so I did this (warning: serious 
KLUDGE):



a) changed the data type in my model of "myString" to "short" (which is a data 
type that IS listed in the "Datatypes section" and was one that I was not 
using). "short" should now show up as a node in the "Datatypes" in the "Model 
Centric" view



b) Highlight the "short" node in your "Model Centric" view, which should make 
it appear in the "Details" pane in the lower right.  Then, under the Properties 
tab, change the name from "short" to "String".  Insure the "Namespace" of the 
"new" String datatype is "datatype."  (If you don't have a "datatype" package 
created in your model, create one.



I did the same steps above for "myDate", hijacking ANOTHER type listed in the 
Poseidon "Data types" list.



That seemed to cure all of the problems.



Now, knowing that is not a very clean way to do things, I turned my attention 
to "the process." What SHOULD have worked was to open "andromda-profile-30.xmi" 
and start modeling.  Problem is, the andromda-profile-30.xmi was generated with 
MagicDraw, and Poseidon chokes on it (at least my version of Poseidon 2.x 
does).  When I try to read in that file, Poseidon generates a nasty error box.



I ended up creating a NEW file named "poseidon-andromda-profile.xmi".  Its one 
that Poseidon CAN read. I created it by making a blank .xmi file CREATED BY 
POSEIDON, then I merged <XMI:UML> elements from the original 
andromda-profile-30.xmi, one by one, testing each merge with Poseidon to try to 
identify what it could and could not read.



Along the way, I discovered a few things:



1) Poseidon was choking on  any <UML:TagDefinition> tag nested INSIDE of a 
<UML:Stereotype> tag.  So, I believe Poseidon does NOT support tags on 
stereotypes, and because of that, it does not know to read the MagicDraw XMI 
file (because MagicDraw DOES support tags on stereotypes? Or is the 
<UML:TagDefinition> tag used so specify which tags ALLOW the stereotype to be 
attached to?).  In any event, after deleting those nested tags, I was able to 
create an XMI file that Poseidon can read.



2) The "File_Merge project into current" menu option does nothing - at least, 
does nothing with the data types in my new "poseidon-andromda-profile-30.xmi"  
I tried to use the file directly, and well as create a "native" Poseidon file 
out of it (.zuml).  In neither case was I able to "merge" the "new" AndroMDA 
data types in with a pre-existing project in need of the new data types.



3) On the advice of wouter, I took a second look at MagicDraw.  I spent about 
another hour with it, and I did discover that its not as bad as I originally 
thought.  While I can model quicker with Poseidon, the delta is not nearly as 
bad as I first suspected.  I MAY end up simply switching to MagicDraw so I'm 
not constantly paddling upstream.  It seems obvious that the developers of 
AndroMDA use it, so by default, IT seems to work with new stuff, while other 
modeling tools "may or may not" depending on their quirks and your ability to 
overcome them.



If your interested in my copy of poseidon-andromda-profile-30.xmi, send me an 
email ([EMAIL PROTECTED]).  I'd attach it to this post, but it appears this 
board does not support file attachments?
_________________________________________________________
Reply to the post : http://galaxy.andromda.org/forum/viewtopic.php?p=1404#1404
Posting to http://forum.andromda.org/ is preferred over posting to the mailing 
list!


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Andromda-user mailing list
Andromda-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/andromda-user

Reply via email to