StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
11047610
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-06-15T09:03:44.170
FavoriteCount
0
LastActivityDate
2012-06-15T09:03:44.170
LastEditDate
LastEditorUserId
0
OwnerUserId
1156561
ParentId
11016477
PostTypeId
2
Score
4
ViewCount
0
LastEditorDisplayName
text
Body
Instead of going directly for the UML2EcoreConverter, take a look at org.eclipse.uml2.uml.util.UMLUtil.convertToEcore(Package, Map) It takes a package and a Map of options and returns the converted EPackage(s). The options map can be fed the options from UMLUtil.UML2EcoreConverter.OPTION__* as keys. Possible values are UMLUtil.OPTION_DISCARD/OPTION_IGNORE/OPTION_PROCESS/OPTION_REPORT. All options default to OPTION__IGNORE. Most of these options are for processing concepts of UML2 class diagrams that don't map cleanly to Ecore, so you can control how they should be handled. For extended feature mapping (subset/union, redefines ...), see OPTION_REDEFINING*, OPTION_SUBSETTING*, OPTION__UNION_PROPERTIES, OPTION_DUPLICATE*. It should be okay to set all of these to OPTION_PROCESS. One option you might want to disable is OPTION__SUPER_CLASS_ORDER. This will reorder the generalizations and interface realizations in alphabetical order, which might cause implementation concerns when you want to inherit a specific super implementation. Another one is OPTION__CAMEL_CASE_NAMES, which will process class and feature names to force a strict camel case scheme. This only makes sense in cases where your UML artifacts don't have valid java names. Just set them to OPTION_IGNORE, or, to see where they would change something, to OPTION_REPORT. There's also a convertFromEcore(...) for the reverse. In case you would like to understand the inner workings of UML2EcoreConverter better: It's basically a simple recursive visitor that traverses the UML model, converting each artifact to its Ecore equivalent and doing some cleaning up. It extends UMLSwitch to handle the different metaclasses. So to see for example how a UML Property is converted to an EStructuralFeature, have a look at caseProperty(...)
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POEclipse: how to programmatically convert UML to ecore
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USCarsten
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POEclipse: how to programmatically convert UML to ecore
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.