[jira] Created: (CXF-1763) Possible type name conflicts in Aegis related to arrays and nillable

["Benson Margulies (JIRA)" <ji...@apache.org>]

Possible type name conflicts in Aegis related to arrays and nillable
--------------------------------------------------------------------

                 Key: CXF-1763
                 URL: https://issues.apache.org/jira/browse/CXF-1763
             Project: CXF
          Issue Type: Bug
          Components: Aegis Databinding
    Affects Versions: 2.1.2, 2.0.8
            Reporter: Benson Margulies


Aegis makes complex types for arrays. For example, a SEI function like 'void x(String[])' will result in a complex type named ArrayOfString.

Classically, as in back in XFire, the code could get into trouble if it had conflicting types afoot. This can happen if the application uses a .aegis.xml file to specify minOccurs, maxOccurs, or nillable.

Some time ago, the present writer modified the code to avoid conflicts in case of minOccurs and maxOccurs by creating multiple distinct complex types with names like ArrayOfString-2-50. However, there's no provision to avoid name conflicts for 'nillable'. Worse yet, in the AbstractTypeCreator, the 'nillable' fact doesn't live in the same place as minOccurs and maxOccurs, ao it's not quite trivial to add it to the mixture.

This whole business madly needs someone to digest it and try to refactor all of this into some rational condition.


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.