[castor-dev] Refactoring of FieldMappingCollectionType breaks backward compability

Hi all,=0A=0AI hope this is allright to post here. Between 1.3.1 and 1.3.3 =
of castor the class org.exolab.castor.mapping.xml.types.FieldMappingCollect=
ionType seems to have changed a bit. =0A=0AIn my case - the class org.exola=
b.castor.xml.XMLMappingLoader.createFieldDesc (around line 620) the code st=
arts mapping a collection type. In my case a files typeName derived on 626 =
is "collection". But then colType is looked for by using=0A=0AcolType =3D F=
ieldMappingCollectionType.valueOf(typeName); //(typeName =3D "collection" i=
n my case).=0A=0AThis returns an error about that there is no such entry in=
 the enumeration. If the line on the other hand would use =0A=0AcolType =3D=
 FieldMappingCollectionType.fromValue(typeName); =0A=0Ait works. Now I'm no=
t sure if both cases could be true or if it's just a mistake in the refacto=
ring of the enum. Right now I have just made a silly patch which tries both=
 in case one of them works. But I would like this to be solved in the offic=
ial branch naturally.=0A=0ARegards=0AMattias Bogeblad=0A

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email