fixtradingcommunity / fix-sbe-utilities Goto Github PK

View Code? Open in Web Editor NEW

6.0 10.0 4.0 893 KB

Utilities and demonstration code for FIX Simple Binary Encoding

License: Apache License 2.0

XSLT 60.05% Java 39.95%

sbe fixprotocol

fix-sbe-utilities's Introduction

FIX Simple Binary Encoding Utilities

This project contains resources and sample code for FIX Simple Binary Encoding.

orchestra2sbe

This utility generates a Simple Binary Encoding (SBE) message schema from an Orchestra file.

sbe-validator

Validates that an SBE message schema conforms to its XML schema.

License

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

fix-sbe-utilities's People

Contributors

Stargazers

Watchers

Forkers

david-gibbs-ig dendisuhubdy loveen johngreenan

fix-sbe-utilities's Issues

orchestra2sbe: test should validate that result conforms to SBE schema

Add a test step to validate the generated SBE file.

Unknown node type: name=sbe:type

The SBE tool throws an exception while trying to parse the schema file as in FIX SBE Examples.
The schema file is derived from Orchestra using the FIX SBE Utilities.

Please see https://github.com/IG-Group/ig-orchestrations/tree/FIXAPI-2296

Could this be related to #1 ?

I am using <real-logic.version>1.20.3</real-logic.version> see https://github.com/IG-Group/ig-orchestrations/blob/FIXAPI-2296/ig-us-rfed/sbe/codec/pom.xml

The exception is

Java.lang.IllegalStateException: Unknown node type: name=sbe:type
    at uk.co.real_logic.sbe.xml.CompositeType.processType (CompositeType.java:470)
    at uk.co.real_logic.sbe.xml.CompositeType.<init> (CompositeType.java:84)
    at uk.co.real_logic.sbe.xml.CompositeType.<init> (CompositeType.java:55)
    at uk.co.real_logic.sbe.xml.XmlSchemaParser.lambda$findTypes$1 (XmlSchemaParser.java:200)
    at uk.co.real_logic.sbe.xml.XmlSchemaParser.forEach (XmlSchemaParser.java:464)
    at uk.co.real_logic.sbe.xml.XmlSchemaParser.findTypes (XmlSchemaParser.java:199)
    at uk.co.real_logic.sbe.xml.XmlSchemaParser.parse (XmlSchemaParser.java:137)
    at uk.co.real_logic.sbe.SbeTool.parseSchema (SbeTool.java:297)
    at uk.co.real_logic.sbe.SbeTool.main (SbeTool.java:204)
    at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke (Method.java:498)
    at org.codehaus.mojo.exec.ExecJavaMojo$1.run (ExecJavaMojo.java:282)
    at java.lang.Thread.run (Thread.java:748)

Namespace for fixr is obsolete

xmlns:fixr="http://fixprotocol.io/2016/fixrepository" is an obsolete location. Should be
xmlns:fixr="http://fixprotocol.io/2020/orchestra/repository"

Unexpected XML namespaces in orchestra2sbe

The XML namespaces in the output of XSL Transforms are not as expected. Either the prefixes are not as expected or extra namespace nodes are included in output.

SBE to and from Orchestra

We want to use Orchestra to drive and version our SBE templates. Having XSLT as a requirement is challenging as XSLT adoption and availability of XSLT processors waning. These tools would be much better implemented as Python programs, especially given the wide use of Python for DevOps and DevSecOps automation. Would it be possible to port these over to Python and then as we use them - put feedback, issues, and enhancement requests against the Python versions instead of the XSLT versions.

orchestra2sbe: name too long for SBE

Some element names in Orchestra may be long for SBE. The SBE schema restricts names to 64 characters. How to deal with this? At minimum there should be a validation error. Alternatively, the translator could truncate names to the SBE limit.

New module - SBE message schema validator

An SBE message schema validator would validate that a file conforms to the XML schema, but it could also apply other rules that are not enforced by the schema itself.

It should validate SBE version 1.0 Standard as well as latest release candidate.