You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "benson margulies (JIRA)" <ji...@apache.org> on 2007/09/11 03:04:30 UTC
[jira] Created: (CXF-987) flat attribute missing from Aegis XML
schema
flat attribute missing from Aegis XML schema
---------------------------------------------
Key: CXF-987
URL: https://issues.apache.org/jira/browse/CXF-987
Project: CXF
Issue Type: Bug
Components: Core
Affects Versions: 2.0.1
Reporter: benson margulies
Priority: Minor
Fix For: 2.1
The doc, and the xml schema, should include the 'flat' attribute.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CXF-987) Aegis schema does not match the actual
situation
Posted by "benson margulies (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
benson margulies updated CXF-987:
---------------------------------
Issue Type: Sub-task (was: Bug)
Parent: CXF-1037
> Aegis schema does not match the actual situation
> ------------------------------------------------
>
> Key: CXF-987
> URL: https://issues.apache.org/jira/browse/CXF-987
> Project: CXF
> Issue Type: Sub-task
> 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.
[jira] Closed: (CXF-987) Aegis schema does not match the actual
situation
Posted by "Dan Diephouse (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dan Diephouse closed CXF-987.
-----------------------------
Resolution: Fixed
Fix Version/s: 2.1
2.0.3
Applied as part of CXF-1054. Thanks!
> Aegis schema does not match the actual situation
> ------------------------------------------------
>
> Key: CXF-987
> URL: https://issues.apache.org/jira/browse/CXF-987
> Project: CXF
> Issue Type: Sub-task
> Components: Aegis Databinding
> Affects Versions: 2.0.1
> Reporter: benson margulies
> Fix For: 2.0.3, 2.1
>
> 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.
[jira] Updated: (CXF-987) Aegis schema does not match the actual
situation
Posted by "benson margulies (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
benson margulies updated CXF-987:
---------------------------------
Issue Type: Sub-task (was: Bug)
Parent: CXF-1054
> Aegis schema does not match the actual situation
> ------------------------------------------------
>
> Key: CXF-987
> URL: https://issues.apache.org/jira/browse/CXF-987
> Project: CXF
> Issue Type: Sub-task
> 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.
[jira] Updated: (CXF-987) Aegis schema does not match the actual
situation
Posted by "benson margulies (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
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: https://issues.apache.org/jira/browse/CXF-987
> 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.
[jira] Updated: (CXF-987) Aegis schema does not match the actual
situation
Posted by "benson margulies (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
benson margulies updated CXF-987:
---------------------------------
Attachment: aegis.xsd
This replaces 'mapping.xsd'.
> Aegis schema does not match the actual situation
> ------------------------------------------------
>
> Key: CXF-987
> URL: https://issues.apache.org/jira/browse/CXF-987
> 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.
[jira] Updated: (CXF-987) Aegis schema does not match the actual
situation
Posted by "benson margulies (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
benson margulies updated CXF-987:
---------------------------------
Fix Version/s: (was: 2.1)
Priority: Major (was: Minor)
Description:
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.
was:The doc, and the xml schema, should include the 'flat' attribute.
Summary: Aegis schema does not match the actual situation (was: flat attribute missing from Aegis XML schema )
> Aegis schema does not match the actual situation
> ------------------------------------------------
>
> Key: CXF-987
> URL: https://issues.apache.org/jira/browse/CXF-987
> 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.
[jira] Updated: (CXF-987) flat attribute missing from Aegis XML
schema
Posted by "benson margulies (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
benson margulies updated CXF-987:
---------------------------------
Component/s: (was: Core)
Aegis Databinding
Estimated Complexity: Novice
> flat attribute missing from Aegis XML schema
> ---------------------------------------------
>
> Key: CXF-987
> URL: https://issues.apache.org/jira/browse/CXF-987
> Project: CXF
> Issue Type: Bug
> Components: Aegis Databinding
> Affects Versions: 2.0.1
> Reporter: benson margulies
> Priority: Minor
> Fix For: 2.1
>
>
> The doc, and the xml schema, should include the 'flat' attribute.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CXF-987) Aegis schema does not match the actual
situation
Posted by "benson margulies (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
benson margulies updated CXF-987:
---------------------------------
Attachment: (was: mapping.xsd.diff)
> Aegis schema does not match the actual situation
> ------------------------------------------------
>
> Key: CXF-987
> URL: https://issues.apache.org/jira/browse/CXF-987
> 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.
[jira] Updated: (CXF-987) flat attribute missing from Aegis XML
schema
Posted by "benson margulies (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
benson margulies updated CXF-987:
---------------------------------
Attachment: mapping.xsd.diff
> flat attribute missing from Aegis XML schema
> ---------------------------------------------
>
> Key: CXF-987
> URL: https://issues.apache.org/jira/browse/CXF-987
> Project: CXF
> Issue Type: Bug
> Components: Aegis Databinding
> Affects Versions: 2.0.1
> Reporter: benson margulies
> Priority: Minor
> Fix For: 2.1
>
> Attachments: mapping.xsd.diff
>
>
> The doc, and the xml schema, should include the 'flat' attribute.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.