You are viewing a plain text version of this content. The canonical link for it is here.
Posted to j-users@xerces.apache.org by "Timothy W. Cook" <ti...@mlhim.org> on 2014/11/02 12:31:20 UTC

assert validation error

using oXygen 16.1 with embedded Xerces.

I have a failure on a simple regex (yes I know it could be performed using
a pattern facet) used to demonstrate/test assertions.  It passes with
SaxonEE but fails with Xerces.

The complexType:

    <xs:complexType name="ct-9c65478e-5cdf-413b-aa54-ce0574e48374"
xml:lang="en-US"> <!-- Telephone Number (US) -->
        <xs:annotation>
            <xs:documentation>
      A US telephone number. Exactly 12 characters; 111-111-1111 with a
pattern match of "[0-9]{3}-[0-9]{3}-[0-9]{4}"
    </xs:documentation>
            <xs:appinfo>
            </xs:appinfo>
        </xs:annotation>
        <xs:complexContent>
            <xs:restriction base="mlhim245:DvStringType">
                <xs:sequence>
                    <xs:element maxOccurs="1" minOccurs="1"
name="data-name" type="xs:string" fixed="Telephone Number (US)"/>
                    <xs:element maxOccurs="1" minOccurs="0"
ref="mlhim245:ExceptionalValue"/>
                    <xs:element maxOccurs="1" minOccurs="0"
name="valid-time-begin" type="xs:dateTime"/>
                    <xs:element maxOccurs="1" minOccurs="0"
name="valid-time-end" type="xs:dateTime"/>
                    <xs:element maxOccurs="1" minOccurs="1"
name="DvString-dv" type="xs:string" default="111-111-1111"/>
                    <xs:element maxOccurs="1" minOccurs="0" name="language"
type="xs:language"/>
                </xs:sequence>
                <xs:assert test="matches(DvString-dv,
'[0-9]{3}-[0-9]{3}-[0-9]{4}')"/>
            </xs:restriction>
        </xs:complexContent>
    </xs:complexType>

The instance:
                    <ccd:el-9c65478e-5cdf-413b-aa54-ce0574e48374> <!--
DvString -->
                        <data-name>Telephone Number (US)</data-name>

<valid-time-begin>2015-01-04T21:28:24Z</valid-time-begin>

<valid-time-end>2012-09-09T06:33:19Z</valid-time-end>
                        <DvString-dv>111-111-1111</DvString-dv>
                        <language>en-US</language>
                    </ccd:el-9c65478e-5cdf-413b-aa54-ce0574e48374>

The element el-9c65478e-5cdf-413b-aa54-ce0574e48374 is declared as a type
ct-9c65478e-5cdf-413b-aa54-ce0574e48374 in the schema.

Should I file a bug report or is there an error in my code and Saxon
ignores it?

Thanks,
Tim





-- 

============================================
Timothy Cook
LinkedIn Profile:http://www.linkedin.com/in/timothywaynecook
MLHIM http://www.mlhim.org

Re: assert validation error

Posted by "Timothy W. Cook" <ti...@mlhim.org>.
Awesome!

On Mon, Nov 3, 2014 at 8:18 AM, Octavian Nadolu <oc...@sync.ro>
wrote:

>  Hello Tim,
>
> You reported a similar problem in "XERCESJ-1640", that was fixed by Mukul.
> It seems that the fix resolves also the your current validation problem.
> We did not integrate this fix in the Xerces build that is distributed in
> oXygen 16.1. This fix will be available in the next oXygen release.
>
> Do not hesitate to contact us you need further assistance or any other
> information.
>
> Best Regards,
> Octavian
>
> --
> Octavian Nadolu
> <oXygen/> XML Editorhttp://www.oxygenxml.com
>
>
>
> On 02.11.2014 13:31, Timothy W. Cook wrote:
>
>  using oXygen 16.1 with embedded Xerces.
>
>  I have a failure on a simple regex (yes I know it could be performed
> using a pattern facet) used to demonstrate/test assertions.  It passes with
> SaxonEE but fails with Xerces.
>
>  The complexType:
>
>      <xs:complexType name="ct-9c65478e-5cdf-413b-aa54-ce0574e48374"
> xml:lang="en-US"> <!-- Telephone Number (US) -->
>         <xs:annotation>
>             <xs:documentation>
>       A US telephone number. Exactly 12 characters; 111-111-1111 with a
> pattern match of "[0-9]{3}-[0-9]{3}-[0-9]{4}"
>     </xs:documentation>
>             <xs:appinfo>
>             </xs:appinfo>
>         </xs:annotation>
>         <xs:complexContent>
>             <xs:restriction base="mlhim245:DvStringType">
>                 <xs:sequence>
>                     <xs:element maxOccurs="1" minOccurs="1"
> name="data-name" type="xs:string" fixed="Telephone Number (US)"/>
>                     <xs:element maxOccurs="1" minOccurs="0"
> ref="mlhim245:ExceptionalValue"/>
>                     <xs:element maxOccurs="1" minOccurs="0"
> name="valid-time-begin" type="xs:dateTime"/>
>                     <xs:element maxOccurs="1" minOccurs="0"
> name="valid-time-end" type="xs:dateTime"/>
>                     <xs:element maxOccurs="1" minOccurs="1"
> name="DvString-dv" type="xs:string" default="111-111-1111"/>
>                     <xs:element maxOccurs="1" minOccurs="0"
> name="language" type="xs:language"/>
>                 </xs:sequence>
>                 <xs:assert test="matches(DvString-dv,
> '[0-9]{3}-[0-9]{3}-[0-9]{4}')"/>
>             </xs:restriction>
>         </xs:complexContent>
>     </xs:complexType>
>
>  The instance:
>                      <ccd:el-9c65478e-5cdf-413b-aa54-ce0574e48374> <!--
> DvString -->
>                         <data-name>Telephone Number (US)</data-name>
>
> <valid-time-begin>2015-01-04T21:28:24Z</valid-time-begin>
>
> <valid-time-end>2012-09-09T06:33:19Z</valid-time-end>
>                         <DvString-dv>111-111-1111</DvString-dv>
>                         <language>en-US</language>
>                     </ccd:el-9c65478e-5cdf-413b-aa54-ce0574e48374>
>
>  The element el-9c65478e-5cdf-413b-aa54-ce0574e48374 is declared as a
> type ct-9c65478e-5cdf-413b-aa54-ce0574e48374 in the schema.
>
>  Should I file a bug report or is there an error in my code and Saxon
> ignores it?
>
>  Thanks,
> Tim
>
>
>
>
>
>  --
>
> ============================================
> Timothy Cook
> LinkedIn Profile:http://www.linkedin.com/in/timothywaynecook
> MLHIM http://www.mlhim.org
>
>
>
>


-- 

============================================
Timothy Cook
LinkedIn Profile:http://www.linkedin.com/in/timothywaynecook
MLHIM http://www.mlhim.org

Re: assert validation error

Posted by Octavian Nadolu <oc...@sync.ro>.
Hello Tim,

You reported a similar problem in "XERCESJ-1640", that was fixed by 
Mukul. It seems that the fix resolves also the your current validation 
problem.
We did not integrate this fix in the Xerces build that is distributed in 
oXygen 16.1. This fix will be available in the next oXygen release.

Do not hesitate to contact us you need further assistance or any other 
information.

Best Regards,
Octavian

-- 
Octavian Nadolu
<oXygen/> XML Editor
http://www.oxygenxml.com



On 02.11.2014 13:31, Timothy W. Cook wrote:
> using oXygen 16.1 with embedded Xerces.
>
> I have a failure on a simple regex (yes I know it could be performed 
> using a pattern facet) used to demonstrate/test assertions. It passes 
> with SaxonEE but fails with Xerces.
>
> The complexType:
>
>     <xs:complexType name="ct-9c65478e-5cdf-413b-aa54-ce0574e48374" 
> xml:lang="en-US"> <!-- Telephone Number (US) -->
>         <xs:annotation>
> <xs:documentation>
>       A US telephone number. Exactly 12 characters; 111-111-1111 with 
> a pattern match of "[0-9]{3}-[0-9]{3}-[0-9]{4}"
>     </xs:documentation>
>             <xs:appinfo>
>             </xs:appinfo>
>         </xs:annotation>
>         <xs:complexContent>
>             <xs:restriction base="mlhim245:DvStringType">
>                 <xs:sequence>
>                     <xs:element maxOccurs="1" minOccurs="1" 
> name="data-name" type="xs:string" fixed="Telephone Number (US)"/>
>                     <xs:element maxOccurs="1" minOccurs="0" 
> ref="mlhim245:ExceptionalValue"/>
>                     <xs:element maxOccurs="1" minOccurs="0" 
> name="valid-time-begin" type="xs:dateTime"/>
>                     <xs:element maxOccurs="1" minOccurs="0" 
> name="valid-time-end" type="xs:dateTime"/>
>                     <xs:element maxOccurs="1" minOccurs="1" 
> name="DvString-dv" type="xs:string" default="111-111-1111"/>
>                     <xs:element maxOccurs="1" minOccurs="0" 
> name="language" type="xs:language"/>
> </xs:sequence>
>                 <xs:assert test="matches(DvString-dv, 
> '[0-9]{3}-[0-9]{3}-[0-9]{4}')"/>
>             </xs:restriction>
>         </xs:complexContent>
>     </xs:complexType>
>
> The instance:
> <ccd:el-9c65478e-5cdf-413b-aa54-ce0574e48374> <!-- DvString -->
> <data-name>Telephone Number (US)</data-name>
> <valid-time-begin>2015-01-04T21:28:24Z</valid-time-begin>
> <valid-time-end>2012-09-09T06:33:19Z</valid-time-end>
> <DvString-dv>111-111-1111</DvString-dv>
> <language>en-US</language>
> </ccd:el-9c65478e-5cdf-413b-aa54-ce0574e48374>
>
> The element el-9c65478e-5cdf-413b-aa54-ce0574e48374 is declared as a 
> type ct-9c65478e-5cdf-413b-aa54-ce0574e48374 in the schema.
>
> Should I file a bug report or is there an error in my code and Saxon 
> ignores it?
>
> Thanks,
> Tim
>
>
>
>
>
> -- 
>
> ============================================
> Timothy Cook
> LinkedIn Profile:http://www.linkedin.com/in/timothywaynecook
> MLHIM http://www.mlhim.org <http://www.mlhim.org/>
>