I think the hang might be the same issue as DAFFODIL-2586 [1], which causes a hang if attributes are not closed correctly. Around line 47 you have this:

  dfdl:textTrimKind='padChar"

which mixes single and double quotes for the attribute value, ultimately leading to this hang. If I change the single quote to a double quote then I get an expected error about "invalid content starting with simpleType", and some information about the namespace not being right.

[1]  https://issues.apache.org/jira/browse/DAFFODIL-2586


On 7/29/22 11:49 AM, Roger L Costello wrote:
Here ya go Steve. I am using version 3.2.1  /Roger

<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:dfdl="http://www.ogf.org/dfdl/dfdl-1.0/"; 
xmlns:xs="http://www.w3.org/2001/XMLSchema";>
     <xs:annotation xmlns:f="function" xmlns:fn="http://www.w3.org/2005/xpath-functions"; 
xmlns:regex="regex-functions">
         <xs:appinfo source="http://www.ogf.org/dfdl/";>
             <dfdl:format alignment="1"
                 alignmentUnits="bytes"
                 emptyValueDelimiterPolicy="none"
                 encoding="ASCII"
                 encodingErrorPolicy="replace"
                 escapeSchemeRef=""
                 fillByte="%SP;"
                 floating="no"
                 ignoreCase="yes"
                 initiatedContent="no"
                 initiator=""
                 leadingSkip="0"
                 lengthKind="delimited"
                 lengthUnits="characters"
                 nilValueDelimiterPolicy="none"
                 occursCountKind="implicit"
                 outputNewLine="%CR;%LF;"
                 representation="text"
                 separator=""
                 separatorSuppressionPolicy="anyEmpty"
                 sequenceKind="ordered"
                 textBidi="no"
                 textPadKind="none"
                 textTrimKind="none"
                 trailingSkip="0"
                 truncateSpecifiedLengthString="no"
                 terminator=""
                 textNumberRep="standard"
                 textStandardBase="10"
                 textStandardZeroRep="0"
                 textNumberRounding="pattern"
                 textStandardExponentRep="E"
                 textNumberCheckPolicy="strict"/>
         </xs:appinfo>
     </xs:annotation>
     <xs:element name="Test">
         <xs:complexType>
             <xs:sequence dfdl:separator="/" dfdl:separatorPosition="infix">
                 <xs:element name="A" type="xs:string" />
                 <xs:element name="Foo"
                     dfdl:lengthKind="explicit"
                     dfdl:length="10"
                     dfdl:textTrimKind='padChar"
                     dfdl:textPadKind="padChar"
                     dfdl:textStringPadCharacter="%SP;"
                     dfdl:textStringJustification="center">
                     <simpleType>
                         <restriction base="xs:string">
                             <pattern value="[A-Z]{10}|-"/>
                         </restriction>
                     </simpleType>
                 </xs:element>
                 <xs:element name="B" type="xs:string" />
             </xs:sequence>
         </xs:complexType>
     </xs:element>
</xs:schema>

-----Original Message-----
From: Steve Lawrence <slawre...@apache.org>
Sent: Friday, July 29, 2022 11:42 AM
To: users@daffodil.apache.org
Subject: [EXT] Re: Bug in Daffodil ... it hangs when the DFDL schema contains 
non-namespace-qualified XSD elements

Could you provide more context or the entire DFDL file is possible? I
can't reproduce this issue. Are you using the latest version of Daffodil?

- Steve

On 7/29/22 11:28 AM, Roger L Costello wrote:
Hi Folks,

I have a DFDL schema. I use xs: to namespace-qualify XSD elements.

Except, I forgot to namespace qualify this simpleType:

<simpleType>
      <restriction base="xs:string">
          <pattern value="[A-Z]{10}|-"/>
      </restriction>
</simpleType>

How did Daffodil behave with that DFDL schema? Answer: it did not report any 
error. It simply hung. I had to ctrl-c to terminate Daffodil.

/Roger

Reply via email to