Skip Menu |

This queue is for tickets about the XML-Pastor CPAN distribution.

Report information
The Basics
Id: 53827
Status: resolved
Priority: 0/
Queue: XML-Pastor

People
Owner: aulusoy [...] cpan.org
Requestors: JHANNAH [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: Normal
Broken in: 1.0.3
Fixed in: (no value)



Subject: Pastor : Element 'CurrencyCodeGroup' found where unexpected!
I don't know the underlying problem, but here's an example .xsd which fails. The full specification is here: http://www.opentravel.org/Specifications/Default.aspx I attached OTA_VehResRQ.xsd. Below, my program and results. Thanks! j use XML::Pastor; my $pastor = XML::Pastor->new(); $pastor->generate( mode => 'offline', style => 'multiple', schema => '../OTA/OpenTravel2009A_XML/OTA_VehResRQ.xsd', class_prefix => 'MyApp::Data::', destination => '/home/jhannah/tmp/OTA_XML_Pastor/out/', ); jhannah@dev:~/tmp/OTA_XML_Pastor> perl j.pl Pastor : Element 'CurrencyCodeGroup' found where unexpected! <attributeGroup name="AcceptablePaymentCardGroup" > <annotation > <documentation xml:lang="en" /> </annotation> <attribute name="CardType" type="OTA_CodeType" use="optional" > <annotation > <documentation xml:lang="en" /> </annotation> </attribute> <attribute name="CardName" type="StringLength1to32" use="optional" > <annotation > <documentation xml:lang="en" /> </annotation> </attribute> <attribute name="UsagePercentage" type="Percentage" use="optional" > <annotation > <documentation xml:lang="en" /> </annotation> </attribute> <attribute name="UsageAmount" type="Money" use="optional" > <annotation > <documentation xml:lang="en" /> </annotation> </attribute> <attributeGroup ref="CurrencyCodeGroup" > <annotation > <documentation xml:lang="en" /> </annotation> </attributeGroup> </attributeGroup>
Subject: OTA_VehResRQ.xsd
Download OTA_VehResRQ.xsd
application/xml 4.8k

Message body not shown because it is not plain text.

This seems to be a due to an "attributeGroup ref" within an "attributeGroup", which failed as outlined in the bug report #39691 and which is now fixed for the upcoming version 1.0.4.