cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benson Margulies (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (CXF-2094) Aegis schema generation doing arrays at two levels
Date Sat, 07 Mar 2009 19:40:56 GMT

     [ https://issues.apache.org/jira/browse/CXF-2094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Benson Margulies resolved CXF-2094.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 2.2

> Aegis schema generation doing arrays at two levels
> --------------------------------------------------
>
>                 Key: CXF-2094
>                 URL: https://issues.apache.org/jira/browse/CXF-2094
>             Project: CXF
>          Issue Type: Bug
>          Components: Aegis Databinding
>    Affects Versions: 2.2
>            Reporter: Benson Margulies
>            Assignee: Benson Margulies
>             Fix For: 2.2
>
>
> TypeClassInfo.getMinOccurs(QName) isn't really implemented, and getMaxOccurs(QName) doesn't
even exist!
> In an effort to work around this, I made the caller of this check directly for an element
of Array type and retrieve the bounds. However, that check does not manage to mirror the logic
that decides when to use an ArrayOf... type. So it ends up generating schema with maxOccurs
at both levels. Oops. The fix has to be to actually make getMinOccurs work right and add the
missing getMaxOccurs. 
> The real fun here seems to be that a parameter with maxOccurs doesn't trigger an ArrayOf
type correctly. Arggh.

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


Mime
View raw message