I have the following XSD template for the following:
<xsd:choice>
<xsd:element name="NilReport" type="ftc:CorrectableNilReport_Type">
<xsd:annotation>
<xsd:documentation xml:lang="en">Nil Report indicates that financial institution does not have accounts to report</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:sequence >
<xsd:element name="AccountReport" type="ftc:CorrectableAccountReport_Type" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation>Detailed information for account report, such as account number and account balance</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="PoolReport" type="ftc:CorrectablePoolReport_Type" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation>Information about the pool of account holders with similar characteristics</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
But the result so far doesn't go as it supposes to be.
Unexpected result
Here is my wanted result:
Expected result
How could i archive the expected result ? Please advice me.
Please note that both and are optional in this case.
Currently your choice lets you pick between the NilReport element and the sequence with the other two elements.
If you want to have the two other elements as children of the "sequence" you will have to create a containing element, and you need to define them as children of that element as follows.
<xsd:choice>
<xsd:element name="NilReport" type="ftc:CorrectableNilReport_Type">
<xsd:annotation>
<xsd:documentation xml:lang="en">Nil Report indicates
that financial institution does not have accounts to report</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="NotNilReport">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="AccountReport" type="ftc:CorrectableAccountReport_Type"
minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation>Detailed information for account report, such
as account number and account balance</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="PoolReport" type="ftc:CorrectablePoolReport_Type"
minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation>Information about the pool of account holders
with similar characteristics</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:choice>
Related
I am trying to marshall and unmarshal gpx files with an extension. The gpx schema allows to have extension added in the extensions tag example:
<trkpt lat="51.219983" lon="6.765224">
<ele>52.048584</ele>
<time>2009-06-19T10:13:04Z</time>
<extensions>
<gpxdata:hr>164</gpxdata:hr>
<gpxdata:cadence>99</gpxdata:cadence>
</extensions>
</trkpt>
The GPX file is correct and passes unmarshalling like this:
JAXBContext jaxbContext = JAXBContext.newInstance(GpxType.class, com.cluetrust.xml.gpxdata._1._0.ObjectFactory.class);
Unmarshaller unmarshaller = jaxbContext.createUnmarshaller();
File file = new File("src/test/resources/gpx-example.gpx");
JAXBElement<GpxType> unmarshal = (JAXBElement<GpxType>) unmarshaller.unmarshal(file);
GpxType gpx = unmarshal.getValue();
Two things for me are odd. First off all I have to unmarshal to a JAXBElement and cannot go straight to GpxType, I have to go to the JAXBElement first.
Second of all and that is (for me the biggest problem) once I have the GpxType object. Part is indeed done, but the extensions are not:
ExtensionsType extensions = gpx.getExtensions();
List<Object> extensionsAny = extensions.getAny();
for (Object object : extensionsAny){
System.out.println(object.getClass());
if (object instanceof JAXBElement) {
JAXBElement element = (JAXBElement) object;
LapType lapType = (LapType) element.getValue();
System.out.println(lapType.getStartTime());
}
It seems I have to jump through some hoops here. I have setup a very small project on github where this is shown jaxbproblem. The complete example GPX file i am using is there too. The namespaces in it are correct:
<gpx xmlns="http://www.topografix.com/GPX/1/1"
xmlns:gpxdata="http://www.cluetrust.com/XML/GPXDATA/1/0"
creator="pytrainer http://sourceforge.net/projects/pytrainer" version="1.1">
EDIT:
Relevant part in the schema is :
<xsd:element name="lap" type="lapType">
<xsd:annotation>
<xsd:documentation>
Lap is used to contain information about an individual lap of activity.
Depending upon the device, this may contain a variety of additional information.
Depending upon the device, this may be contained within a run or course.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
and:
<xsd:complexType name="lapType">
<xsd:sequence>
<xsd:element name="index" type="xsd:int" minOccurs="0" maxOccurs="1">
<xsd:annotation><xsd:documentation>The index of the lap in the internal list.</xsd:documentation></xsd:annotation>
</xsd:element>
<xsd:element name="startPoint" type="locationType" minOccurs="0" maxOccurs="1">
<xsd:annotation><xsd:documentation>The starting point of the lap in Lat/Long</xsd:documentation></xsd:annotation>
</xsd:element>
<xsd:element name="endPoint" type="locationType" minOccurs="0" maxOccurs="1">
<xsd:annotation><xsd:documentation>The ending point of the lap in Lat/Long</xsd:documentation></xsd:annotation>
</xsd:element>
<xsd:element name="startTime" type="xsd:dateTime" minOccurs="0" maxOccurs="1">
<xsd:annotation><xsd:documentation>The starting time of the lap</xsd:documentation></xsd:annotation>
</xsd:element>
<xsd:element name="elapsedTime" type="xsd:float" minOccurs="0" maxOccurs="1">
<xsd:annotation><xsd:documentation>The total elapsed time of the lap in seconds</xsd:documentation></xsd:annotation>
</xsd:element>
<xsd:element name="calories" type="xsd:nonNegativeInteger" minOccurs="0" maxOccurs="1">
<xsd:annotation><xsd:documentation>The number of calories burned during the lap</xsd:documentation></xsd:annotation>
</xsd:element>
<xsd:element name="distance" type="xsd:float" minOccurs="0" maxOccurs="1">
<xsd:annotation><xsd:documentation>Distance (in m) covered during the lap</xsd:documentation></xsd:annotation>
</xsd:element>
<xsd:element name="trackReference" type="trackReferenceType" minOccurs="0" maxOccurs="1">
<xsd:annotation><xsd:documentation>Reference information for the track which corresponds to this lap</xsd:documentation></xsd:annotation>
</xsd:element>
<xsd:element name="summary" type="summaryType" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation><xsd:documentation>Performance summary elements summarizing different performance measurements, such as cadence, hr, etc.</xsd:documentation></xsd:annotation>
</xsd:element>
<xsd:element name="trigger" type="triggerType" minOccurs="0" maxOccurs="1">
<xsd:annotation><xsd:documentation>The trigger of the lap. On some devices, the lap may be manual or automatic based on attributes known by the device.</xsd:documentation></xsd:annotation>
</xsd:element>
<xsd:element name="intensity" type="intensityKind" minOccurs="0" maxOccurs="1">
<xsd:annotation><xsd:documentation>The intensity of the lap (whether resting or active)</xsd:documentation></xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
This is just one of the many types that are being introduced with this schema that can be found here
What am I doing wrong?
I'm looking at the feasibility of using an Excel file for loading data into the EPA GHG schema (ghg_subpartp_inputs_v1.0.xsd) for defining the XML Subpartp Inputs data.
I'm not well versed or practiced in using Excel and xml-schemas.
The SubpartP schema has nested complex elements, and it won't be accepted into Excel via the XML Maps facility.
Error message: "Cannot Load the specified XML or schema source."
I'm thinking it is because it is a partial schema that is meant to be included in others?
Here is the schema itself:
Schema Name : ghg_subpartp_inputs_v1.0.xsd
Description : Inputs Verifier Tool - XML schema for Subpart P inputs
<xsd:complexType name="SubpartPInputsType">
<xsd:sequence>
<xsd:element name="SubpartPUnitInputs" minOccurs="0" maxOccurs="unbounded">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="UnitName" type="xsd:string"/>
<xsd:element name="Values">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EquationP1FeedstockInputs" type="EquationP1FeedstockInputsType" minOccurs="0" maxOccurs="unbounded" />
<xsd:element name="EquationP2FeedstockInputs" type="EquationP2FeedstockInputsType" minOccurs="0" maxOccurs="unbounded" />
<xsd:element name="EquationP3FeedstockInputs" type="EquationP3FeedstockInputsType" minOccurs="0" maxOccurs="unbounded" />
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:unique name="UniqueSubpartPFeedstockName">
<xsd:selector xpath="Values/*"/>
<xsd:field xpath="FeedstockName"/>
</xsd:unique>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="EquationP1FeedstockInputsType">
<xsd:sequence>
<xsd:element name="FeedstockName" type="xsd:string"/>
<xsd:element name="Values">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="MassOrVolume" type="MassOrVolumeIndicatorType"/>
<xsd:element name="EquationP1MonthlyInputs" minOccurs="0" maxOccurs="12">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="MonthName" type="MonthNameList"/>
<xsd:element name="Values">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Mass" type="xsd:decimal" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Required units of measure for this equation input: kg of fuel or feedstock</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="Volume" type="xsd:decimal" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Required units of measure for this equation input: scf (at standard conditions of 68 degrees F and atmospheric pressure) of fuel or feedstock</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="CarbonContent" type="xsd:decimal" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Required units of measure for this equation input: kg C per kg of fuel or feedstock</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="MolecularWeight" type="xsd:decimal" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Required units of measure for this equation input: kg/kg-mole</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:unique name="UniqueEquationP1MonthName">
<xsd:selector xpath="*"/>
<xsd:field xpath="MonthName"/>
</xsd:unique>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="EquationP2FeedstockInputsType">
<xsd:sequence>
<xsd:element name="FeedstockName" type="xsd:string"/>
<xsd:element name="Values">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="MassOrVolume" type="MassOrVolumeIndicatorType"/>
<xsd:element name="EquationP2MonthlyInputs" minOccurs="0" maxOccurs="12">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="MonthName" type="MonthNameList"/>
<xsd:element name="Values">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Mass" type="xsd:decimal" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Required units of measure for this equation input: kg of fuel or feedstock</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="Volume" type="xsd:decimal" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Required units of measure for this equation input: gallons of fuel or feedstock</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="CarbonContent" type="xsd:decimal" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Required units of measure for this equation input: kg C per kg of fuel or feedstock if measured as mass, or kg C per gallon of fuel or feedstock if measured as volume</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:unique name="UniqueEquationP2MonthName">
<xsd:selector xpath="*"/>
<xsd:field xpath="MonthName"/>
</xsd:unique>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="EquationP3FeedstockInputsType">
<xsd:sequence>
<xsd:element name="FeedstockName" type="xsd:string"/>
<xsd:element name="Values">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EquationP3MonthlyInputs" minOccurs="0" maxOccurs="12">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="MonthName" type="MonthNameList"/>
<xsd:element name="Values">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Mass" type="xsd:decimal" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Required units of measure for this equation input: kg of fuel and feedstock</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="CarbonContent" type="xsd:decimal" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Required units of measure for this equation input: kg C per kg of fuel and feedstock</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:unique name="UniqueEquationP3MonthName">
<xsd:selector xpath="*"/>
<xsd:field xpath="MonthName"/>
</xsd:unique>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
What should I be doing to create the Excel file that will create an acceptible XML for this schema?
I have a task where I need to create an element "Worker" which has 0 or more subelements "subordinate". I have to use key and keyref to create the references. I can't figure out how make the references "work". Here's what I've written so far:
<xsd:element name="Workers">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Worker" maxOccurs="unbounded">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="name" type="xsd:string"/>
<xsd:element name="subordinate" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
<xsd:attribute name="identyfikator" type="PESEL" use="required"/>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:key name="id">
<xsd:selector xpath="Worker"/>
<xsd:field xpath="#identyfikator"/>
</xsd:key>
<xsd:keyref name="subordinate_ref" refer="id">
<xsd:selector xpath="Worker/subordinate"/>
<xsd:field xpath="#identyfikator"/>
</xsd:keyref>
</xsd:element>
PESEL is my own type and the key restriction works well as I am unable to create two workers with the same key in XML document. However, I can create anything as "subordinate" element and no warnings will be displayed. As I understand, in case of such reference I should be only able to add workers as subordinates if they already exist, right? How do I create proper reference?
This is my first time working with XMLSchema so sorry if the code is messy.
Thanks in advance!
Make a Worker ComplexType and have Worker and Subordinate both be of that type.
Approximately like so:
<!-- Define the below where appropriate. -->
<xsd:element name="Worker" type="WorkerType" />
<xsd:complexType name="WorkerType">
<xsd:sequence>
<xsd:element name="name" type="xsd:string"/>
<xsd:element name="subordinate" type="WorkerType" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
<xsd:attribute name="identyfikator" type="PESEL" use="required"/>
</xsd:complexType>
Also, if you want items to have a unique id, then consider using (or extending) the xsd:ID datatype. This gives you free uniqueness and referential checks using xsd:IDREF.
<xsd:attribute name="identyfikator" type="xsd:ID" use="required"/>
How do I use jaxb bindings to fix multiple group references in a schema?
Part of fpml 5.3 has the following in the schema
<xsd:complexType name="Price">
<xsd:annotation>
<xsd:documentation xml:lang="en">A type describing the strike price.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="commission" type="Commission" minOccurs="0">
<xsd:annotation>
<xsd:documentation xml:lang="en">This optional component specifies the commission to be charged for executing the hedge transactions.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:choice minOccurs="0">
<xsd:sequence>
<xsd:element name="determinationMethod" type="DeterminationMethod">
<xsd:annotation>
<xsd:documentation xml:lang="en">Specifies the method according to which an amount or a date is determined.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:group ref="EquityPrice.model" minOccurs="0"></xsd:group>
</xsd:sequence>
<xsd:element name="amountRelativeTo" type="AmountReference">
<xsd:annotation>
<xsd:documentation xml:lang="en">The href attribute value will be a pointer style reference to the element or component elsewhere in the document where the anchor amount is defined.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:group ref="EquityPrice.model"></xsd:group>
</xsd:choice>
<xsd:element name="cleanNetPrice" type="xsd:decimal" minOccurs="0">
<xsd:annotation>
<xsd:documentation xml:lang="en">The net price excluding accrued interest. The "Dirty Price" for bonds is put in the "netPrice" element, which includes accrued interest. Thus netPrice - cleanNetPrice = accruedInterest. The currency and price expression for this field are the same as those for the (dirty) netPrice.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="quotationCharacteristics" type="QuotationCharacteristics" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Allows information about how the price was quoted to be provided.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
This results in
* <p>
* You are getting this "catch-all" property because of the following reason:
* The field name "GrossPrice" is used by two different parts of a schema. See:
* line 1361 of file:/C:/fpml-jaxb/src/main/xsd/fpml-asset-5-3.xsd
* line 1361 of file:/C:/fpml-jaxb/src/main/xsd/fpml-asset-5-3.xsd
* <p>
The error is misleading. EquityPrice.model starts with this and line 1361 is the grossPrice. The issue stems from above where there are 2 group references to EquityPrice.model in the Price complex type.
<xsd:group name="EquityPrice.model">
<xsd:sequence>
<xsd:element name="grossPrice" type="ActualPrice" minOccurs="0">
<xsd:annotation>
<xsd:documentation xml:lang="en">Specifies the price of the underlyer, before commissions.</xsd:documentation>
</xsd:annotation>
</xsd:element>
The same thing applies for TradeNovationContent where it has multiple references to NewTrade.model.
I also had this same problem, the solution was to enable simple binding mode.
Add the following into your external bindings file.
xmlns:xjc="http://java.sun.com/xml/ns/jaxb/xjc"
...
<jxb:globalBindings>
<xjc:simple />
</jxb:globalBindings>
Error is caused by the way JAXB is handling groups, as you've seen yourself.
I have a complex type defined which doesn't currently contain any minOccurs restrictions. When I use this comlpex type as an element type I sometimes want the elements to have minOccurs 0, other times 1. E.g.
<xsd:complexType name="Identifier">
<xsd:sequence>
<xsd:element name="Id" type="xsd:string"/>
<xsd:element name="Version" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="Wibble">
<xsd:sequence>
<xsd:element name="Id" type="Identifier"/> <!-- I want all elements of Identifier to be mandatory when used as part of a 'Wibble' -->
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="Wobble">
<xsd:sequence>
<xsd:element name="Id" type="Identifier"/> <!-- I want all elements of Identifier to be optional when used as part of a 'Wobble' -->
</xsd:sequence>
</xsd:complexType>
Is this possible?
Thanks in advance.
Groups are your friend, e.g.
<xsd:group name="IdentifierGroup">
<xsd:sequence>
<xsd:element name="Id" type="Identifier"/>
</xsd:sequence>
</xsd:group>
<xsd:complexType name="Wibble">
<xsd:sequence>
<xsd:group ref="IdentifierGroup" minOccurs="1"/>
<!-- more elements for Wibble here -->
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="Wobble">
<xsd:sequence>
<xsd:group ref="IdentifierGroup" minOccurs="0"/>
<!-- more elements for Wobble here -->
</xsd:sequence>
</xsd:complexType>