IMPORTANT:
this is not a Support Forum! Experienced users might answer from time to time questions posted here. If you need a professional and reliable answer, or if you want to report a bug, please contact Altova Support instead.

visualizing mapping of enumerations Options · View
michel777
Posted: Wednesday, February 10, 2016 12:52:04 PM
Rank: Advanced Member

Joined: 1/23/2016
Posts: 54
Hi,

there is two classes car_old, car_new they use different enumerations for the colors (see below).

Question: how to visualize the mapping between the color enums ?

Thnaks a lot inadvance,

Michel

<xs:complexType name="Car_old">
<xs:sequence>
<xs:element name="manufacturer" type="string"/>
<xs:element name="color" type="integer"/>
</xs:sequence>
</xs:complexType>

uses enumeration:

<Color_Enumerations_Old>
<Enum>
<id>1</id>
<text>blue</text>
</Enum>
<Enum>
<id>2</id>
<text>red</text>
</Enum>
<Enum>
<id>3</id>
<text>yellow</text>
</Enum>
</Color_Enumerations_Old>

<xs:complexType name="Car_new">
<xs:sequence>
<xs:element name="manufacturer" type="string"/>
<xs:element name="color" type="integer"/>
</xs:sequence>
</xs:complexType>

uses

<Color_Enumerations_New>
<Enum>
<id>1</id>
<text>blue</text>
</Enum>
<Enum>
<id>2</id>
<text>red</text>
</Enum>
<Enum>
<id>3</id>
<text>yellow</text>
</Enum>
</Color_Enumerations_New>
island
Posted: Thursday, February 11, 2016 5:33:39 AM
Rank: Newbie

Joined: 10/28/2002
Posts: 1,283
Location: AT
Hi,

it is unclear:

a) whether this is a Mapforce question at all
b) what "visualize the mapping between the color enums" means.
c) what the schema fragment "Car_old" has to do with the "enumeration" "Color_Enumerations_Old "
d) what the schema fragment "Car_new" has to do with the "enumeration" "Color_Enumerations_New"

In short, it is unclear what you are asking.

If this is a Mapforce question, and if you are mapping from an xml source component to an xml target component but are not getting the desired results, then I would highly suggest attaching the following files to your post in an attempt to clarify what it is you are trying to convey:

1) your mapping design file (.mfd)
2) your source xsd file and source xml file.
3) your target xsd file and the DESIRED xml output that you wish to generate from your mapping (given the input source xml file)



michel777
Posted: Thursday, February 11, 2016 8:41:39 AM
Rank: Advanced Member

Joined: 1/23/2016
Posts: 54
Hi island,

you are right, the hole story is unclear.

In short form: for mapping enumeration is used the value-map construct and it works fine, no problem with it.

For seeing the mapping the value-map must be opened. My wish: a construct for maping, that is always "opened" - like the maping of elements.

Michel
island
Posted: Friday, February 12, 2016 5:30:32 AM
Rank: Newbie

Joined: 10/28/2002
Posts: 1,283
Location: AT
Hi michel777,

so you want the actual input and result values list of a value map to always be visible in the mapping design without having to actually double click on the value map to "open it" . Is this correct? If so, this is a feature request.
michel777
Posted: Friday, February 12, 2016 11:29:42 AM
Rank: Advanced Member

Joined: 1/23/2016
Posts: 54
Hi island,


yes, it is correct.


Warm regards, Michel
Users browsing this topic
guest

Forum Jump
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

Use of the Altova User Forum(s) is governed by the Altova Terms of Use.