Author: Admin

I am using JAXB to generate the classes but the product classes are gettting generated as empty ( i.e. they don’t have any setters or getters ) any help would be appreciated! Regards

DeliveryDatesEnum (see xsd-enum-5-3.xsd) ” The “1stNearbyWeek” (and 52ndNearbyWeek added for Commodity Derivatives) enumerations are invalid – JAXB can’t have enumerations with leading numerals natively, so special-case bindings need to be written. As a minimum, when new enumerations use leading numerals there should be consistency applied – e.g. the new DeliveryDatesEnum: FourthNearby through EleventhNearby, ThirteenthNearby, FourteenthNearby, … Continued

Hello, I am getting below exception for the reporting view when i am trying to load all the classes along with schema. I used JAXB to generate the classes. Caused by: org.xml.sax.SAXParseException: cos-nonambig: “http://www.fpml.org/FpML-5/reporting”:definePosition and “http://www.fpml.org/FpML-5/reporting”:definePosition (or elements from their substitution group) violate “Unique Particle Attribution”. During validation against this schema, ambiguity would be created … Continued

When compliling with java 1.6 fpml-confirmation-processes-5-3.xsd its giving duplicate tradeId property. C:SrinivasCSDR Reportingrequiredxsd>C:SrinivasCjdk1.6.0_07binxjc.exe fpml-confirmation-processes-5-3.xsd Picked up JAVA_TOOL_OPTIONS: -agentlib:jvmhook Picked up _JAVA_OPTIONS: -Xrunjvmhook -Xbootclasspath/a:C:PROGRA~1HPQUICKT~1binJAVA_S~1classes;C:PROGRA~1HPQUICKT~1binJAVA_S~1classesjasmine .jar parsing a schema… [ERROR] Element “{http://www.fpml.org/FpML-5/confirmation}tradeId” shows up in more than one properties. line 1262 of file:/C:/SrinivasC/SDR%20Reporting/requiredxsd/fpml-doc-5-3.xsd [ERROR] The following location is relevant to the above error line 1254 of file:/C:/SrinivasC/SDR%20Reporting/requiredxsd/fpml-doc-5-3.xsd … Continued

The rule is intended for the interest leg of an equity swap but the test case is based on an interest rate swap and can never be triggered.

The swap stream reference at the end of the file needs to point to something other than the ‘Fixed’ or ‘Float’ leg of the product, like a party.

The test case defines forward points on both the near and far legs of the swap so the rule is not triggered. Comment out the forwardPoints element on the far leg.

The wrong set of spotRate and forwardPoints elements where adjusted (i.e. not the ones for the crossRate structure. Change the example to match this: MXN GBP Currency1PerCurrency2 21.3766 21.2531 0.1235 MXN USD Currency2PerCurrency1 10.7145 1.0 2.0 USD EUR Currency1PerCurrency2 1.9951 1.0 0.9951

Shared-22 appears to test exactly the same thing as shared-10. Compare .. shared-10 (Mandatory) English Description: Context: CalculationAgent (complex type) The values of calculationAgentPartyReference/@href attributes shall be unique. XPath Description: Context: CalculationAgent count(distinct-values(calculationAgentPartyReference/@href)) eq count(calculationAgentPartyReference/@href) Comment: It does not make sense for a party to be listed more than once as calculation agent to a … Continued

shared-19 detects cases where two account structures exist for the same logical instance. In the test case the two accounts have unique Ids (differing in thier scheme URI) so can not trigger the rule. 12345PartyA 12345PartyAB Change the scheme URI for the second account to match the first.