[jira] Created: (XERCESC-1621) ##targetNamespace results in a bogus UPA violation error

##targetNamespace results in a bogus UPA violation error
--------------------------------------------------------

                 Key: XERCESC-1621
                 URL: http://issues.apache.org/jira/browse/XERCESC-1621
             Project: Xerces-C++
          Issue Type: Bug
          Components: Validating Parser (Schema) (Xerces 1.5 or up only)
    Affects Versions: 2.7.0
         Environment: all
            Reporter: Boris Kolpackov


The following schema fragment:

  <complexType name="AnyTargetNamespace">
    <sequence maxOccurs="unbounded">
      <element name="apple" type="string"/>
      <any namespace="##targetNamespace" processContents="skip" minOccurs="1" maxOccurs="unbounded"/>
    </sequence>
  </complexType>

causes Xerces-C++ to fail with the following (bogus) error:

:0:0: error: Complex type 'AnyTargetNamespace' violates the Unique Particle Attribution rule in its components 'apple' and '##any'

There is no UPA violation in the above fragment. Xerces-J, Jing and MSV agree.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@...
For additional commands, e-mail: c-dev-help@...

     [ http://issues.apache.org/jira/browse/XERCESC-1621?page=all ]

Boris Kolpackov updated XERCESC-1621:
-------------------------------------

    Attachment: bug.xsd

Complete XML Schema that reproduces the bug.

> ##targetNamespace results in a bogus UPA violation error
> --------------------------------------------------------
>
>                 Key: XERCESC-1621
>                 URL: http://issues.apache.org/jira/browse/XERCESC-1621
>             Project: Xerces-C++
>          Issue Type: Bug
>          Components: Validating Parser (Schema) (Xerces 1.5 or up only)
>    Affects Versions: 2.7.0
>         Environment: all
>            Reporter: Boris Kolpackov
>         Attachments: bug.xsd
>
>
> The following schema fragment:
>   <complexType name="AnyTargetNamespace">
>     <sequence maxOccurs="unbounded">
>       <element name="apple" type="string"/>
>       <any namespace="##targetNamespace" processContents="skip" minOccurs="1" maxOccurs="unbounded"/>
>     </sequence>
>   </complexType>
> causes Xerces-C++ to fail with the following (bogus) error:
> :0:0: error: Complex type 'AnyTargetNamespace' violates the Unique Particle Attribution rule in its components 'apple' and '##any'
> There is no UPA violation in the above fragment. Xerces-J, Jing and MSV agree.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@...
For additional commands, e-mail: c-dev-help@...

    [ http://issues.apache.org/jira/browse/XERCESC-1621?page=comments#action_12422425 ]
           
Boris Kolpackov commented on XERCESC-1621:
------------------------------------------

It appears that maxOccurs="unbounded" is causing this somehow.

> ##targetNamespace results in a bogus UPA violation error
> --------------------------------------------------------
>
>                 Key: XERCESC-1621
>                 URL: http://issues.apache.org/jira/browse/XERCESC-1621
>             Project: Xerces-C++
>          Issue Type: Bug
>          Components: Validating Parser (Schema) (Xerces 1.5 or up only)
>    Affects Versions: 2.7.0
>         Environment: all
>            Reporter: Boris Kolpackov
>         Attachments: bug.xsd
>
>
> The following schema fragment:
>   <complexType name="AnyTargetNamespace">
>     <sequence maxOccurs="unbounded">
>       <element name="apple" type="string"/>
>       <any namespace="##targetNamespace" processContents="skip" minOccurs="1" maxOccurs="unbounded"/>
>     </sequence>
>   </complexType>
> causes Xerces-C++ to fail with the following (bogus) error:
> :0:0: error: Complex type 'AnyTargetNamespace' violates the Unique Particle Attribution rule in its components 'apple' and '##any'
> There is no UPA violation in the above fragment. Xerces-J, Jing and MSV agree.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@...
For additional commands, e-mail: c-dev-help@...

    [ http://issues.apache.org/jira/browse/XERCESC-1621?page=comments#action_12422427 ]
           
Boris Kolpackov commented on XERCESC-1621:
------------------------------------------

##targetNamespace can be replaced with ##any, ##local or ##other with the same result.

> ##targetNamespace results in a bogus UPA violation error
> --------------------------------------------------------
>
>                 Key: XERCESC-1621
>                 URL: http://issues.apache.org/jira/browse/XERCESC-1621
>             Project: Xerces-C++
>          Issue Type: Bug
>          Components: Validating Parser (Schema) (Xerces 1.5 or up only)
>    Affects Versions: 2.7.0
>         Environment: all
>            Reporter: Boris Kolpackov
>         Attachments: bug.xsd
>
>
> The following schema fragment:
>   <complexType name="AnyTargetNamespace">
>     <sequence maxOccurs="unbounded">
>       <element name="apple" type="string"/>
>       <any namespace="##targetNamespace" processContents="skip" minOccurs="1" maxOccurs="unbounded"/>
>     </sequence>
>   </complexType>
> causes Xerces-C++ to fail with the following (bogus) error:
> :0:0: error: Complex type 'AnyTargetNamespace' violates the Unique Particle Attribution rule in its components 'apple' and '##any'
> There is no UPA violation in the above fragment. Xerces-J, Jing and MSV agree.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@...
For additional commands, e-mail: c-dev-help@...

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

Boris Kolpackov updated XERCESC-1621:
-------------------------------------

    Fix Version/s: 2.9.0
                   3.0.0

> ##targetNamespace results in a bogus UPA violation error
> --------------------------------------------------------
>
>                 Key: XERCESC-1621
>                 URL: https://issues.apache.org/jira/browse/XERCESC-1621
>             Project: Xerces-C++
>          Issue Type: Bug
>          Components: Validating Parser (XML Schema)
>    Affects Versions: 2.7.0
>         Environment: all
>            Reporter: Boris Kolpackov
>             Fix For: 3.0.0, 2.9.0
>
>         Attachments: bug.xsd
>
>
> The following schema fragment:
>   <complexType name="AnyTargetNamespace">
>     <sequence maxOccurs="unbounded">
>       <element name="apple" type="string"/>
>       <any namespace="##targetNamespace" processContents="skip" minOccurs="1" maxOccurs="unbounded"/>
>     </sequence>
>   </complexType>
> causes Xerces-C++ to fail with the following (bogus) error:
> :0:0: error: Complex type 'AnyTargetNamespace' violates the Unique Particle Attribution rule in its components 'apple' and '##any'
> There is no UPA violation in the above fragment. Xerces-J, Jing and MSV agree.

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


---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@...
For additional commands, e-mail: c-dev-help@...

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

Boris Kolpackov closed XERCESC-1621.
------------------------------------

       Resolution: Invalid
    Fix Version/s:     (was: 2.9.0)
                       (was: 3.0.0)
         Assignee: Boris Kolpackov

This is actually a case of UPA violation and is correctly reported by Xerces-C++. See http://lists.w3.org/Archives/Public/xmlschema-dev/2008Jun/0038.html for more information.

> ##targetNamespace results in a bogus UPA violation error
> --------------------------------------------------------
>
>                 Key: XERCESC-1621
>                 URL: https://issues.apache.org/jira/browse/XERCESC-1621
>             Project: Xerces-C++
>          Issue Type: Bug
>          Components: Validating Parser (XML Schema)
>    Affects Versions: 2.7.0
>         Environment: all
>            Reporter: Boris Kolpackov
>            Assignee: Boris Kolpackov
>         Attachments: bug.xsd
>
>
> The following schema fragment:
>   <complexType name="AnyTargetNamespace">
>     <sequence maxOccurs="unbounded">
>       <element name="apple" type="string"/>
>       <any namespace="##targetNamespace" processContents="skip" minOccurs="1" maxOccurs="unbounded"/>
>     </sequence>
>   </complexType>
> causes Xerces-C++ to fail with the following (bogus) error:
> :0:0: error: Complex type 'AnyTargetNamespace' violates the Unique Particle Attribution rule in its components 'apple' and '##any'
> There is no UPA violation in the above fragment. Xerces-J, Jing and MSV agree.

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


---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@...
For additional commands, e-mail: c-dev-help@...