Same variant for different value in enumerations

Question

Hello.
Is it a bug?
I have this type in my schema:
<xs:simpleType name="VolumeUnit">
<xs:restriction base="xs:string">
<xs:enumeration value="ml"></xs:enumeration>
<xs:enumeration value="µl"></xs:enumeration>
</xs:restriction>
</xs:simpleType>
In the generated class I got:
static final Enum ML = Enum.forString("ml");
static final Enum ΜL = Enum.forString("µl");
static final int INT_ML = Enum.INT_ML;
static final int INT_ÎœL = Enum.INT_ÎœL;
What do you think about that?
How could we manage the generated code

Answer 1

Hi Advait,
From the below what I understand is that you are not able to do value mapping for the follwoing
1     A
2     A
3     B
As value mapping allow one to one mapping only. Please do it like as mentioned below
1     1*A
2     2*A
3     3*B
Then in the graphical mapping of Integration Repository do the mapping for the same as shown below
source field > VALUEMAPPING> UDF--> TARGET Field
In UDF suppress the value of  1* , 2* , 3* which can be done as follows
create one UDF with one input field
//write the code as below to suppress the field
return input.substring(2);
Here the davantage of using 1* , 2* , 3* etc is that you have the option to use value mapping for 100 values which I think is not normally the case for any Interface.
If you have same source you can do the same thing for that.
Hope this helps you to resolve your query.
Thanks & Regards
Prabhat