cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "benson margulies (JIRA)" <>
Subject [jira] Updated: (CXF-987) Aegis schema does not match the actual situation
Date Fri, 21 Sep 2007 12:24:50 GMT


benson margulies updated CXF-987:

    Issue Type: Bug  (was: Sub-task)
        Parent:     (was: CXF-1037)

> Aegis schema does not match the actual situation
> ------------------------------------------------
>                 Key: CXF-987
>                 URL:
>             Project: CXF
>          Issue Type: Bug
>          Components: Aegis Databinding
>    Affects Versions: 2.0.1
>            Reporter: benson margulies
>         Attachments: aegis.xsd
> There are a number of problems with the aegis schema that is published.
> The big one is that it claims that the files are in a namespace. In XML schema, if there
is a targetNamespace, the files that conform to that schema have to have an xmlns for that
namespace in the top element. setting the defaultElementForm only effects what happens inside
the root element, it does not authorize the root element to have no namespace.
> The solution to this is to leave out the targetNamespace declaration altogether, but
put the XML schema glop in a prefix like 'xsd'.
> In addition, the 'method' element was missing, as were the 'flat' and 'maxOccurs' attributes.
> As you might guess from this writeup, I have come up with a working replacement, which
I will attach.
> I also have code to enable validation, but I'm attaching that to another JIRA.

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

View raw message