XMI Import: Error: Unknown Package Connector Sourc

[DBRN]

Hello. How do you find out where exactly the problem is when the XMI import file looks like this:

Add Classifier... [a few hundred times]

Resolving Classifiers
Resolving Owners
Resolving Attribute Types
Resolving Parameter Types
Error: Unknown Package Connector Source or Target
Error: Unknown Package Connector Source or Target
Error: Unknown Package Connector Source or Target
Error: Unknown Package Connector Source or Target
Error: Unknown Package Connector Source or Target
Error: Unknown Dependency Source or Target
Error: Unknown Package Connector Source or Target
Error: Unknown Dependency Source or Target
Error: Unknown Package Connector Source or Target
Error: Unknown Package Connector Source or Target
Error: Unknown Package Connector Source or Target
[... a few hundres similar lines]
Resolving Association-Classes
Resolving DiagramIDs
Resolving Note links
Fixup external references
Import Complete!


Is there any way to find out which package connector or dependency exactly has been tried?
[original message]

[qwerty]

No way (I know). There is a dangling connector into some (not yet) loaded XMI of some other package. As soon as you load that (good luck in finding it) the links are resolved.

q.
[original message]

[DBRN]

I think I figured out what exactly is not being resolved:
the parameters and return types of Collection<SomeType>.

SomeType, be it from Java API or my own libraries, is being imported; when I have String or MyOwnClass as parameters for example, they are being shown in the import, but as soon as I want a List/Set/Collection of them, I get method names like getAll(?).

Now how do deal with it?

Is there any way to show Collection<SomeType> in the Project Browser (ie without reducing it to a single SomeType), but make it link to SomeType instead of java.util.List in the diagram? (maybe it happens automatically, I have not tried out yet, I better ask before changing lots of code).
[original message]

[qwerty]

Use a Search. You need to ex-/import the whole package (at least the sub-package where it's located). Eventually you can create a temp folder, move the element therein and ex-/import that before moving it back.

q.
[original message]

[DBRN]

393F2D3A3C31480 wrote:

Use a Search. You need to ex-/import the whole package (at least the sub-package where it's located). Eventually you can create a temp folder, move the element therein and ex-/import that before moving it back. q.

Thanks for the reply, but what do you mean by moving things in temp folder and back? You mean putting all needed standard java libraries into one <packagedElement>and reference that? I thought you can reference those without <elementImport ...> because they are saved in the EA and you are able to simply identify them by EA_Java_StandardJavaApiType.

Right now the code I am working on uses <ownedParameter xmi:id="..." name="..." direction="return" type="EA_Java_CollectionType_TypeInsideCollection_"> for example. So you are telling me this is correct and only the <elementImport ...> of CollectionType for the <packagedElement> is missing?

And I did try to search for a guide. Google barely gives any results. If you can link me to one, that would be really helpful.
[original message]

[qwerty]

If you have dangling references from an exported package which go into multiple elements in different packages and you just need them for reference then you can move all those into a single temporary package. This temp package can be ex-/imported as usual and will help to resolve the dangling references in the model where you imported your main package. Afterwards you can move the elements back to where they were first.

I do not look into XMI and don't try to understand it. So I can't help with that.

What kind of guide are you looking for?

q.
[original message]