-
Notifications
You must be signed in to change notification settings - Fork 526
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Import common encodings #624
Comments
Can you provide an example of how to do an include before validation? |
I've pushed a change for this and it was way more than a trivial change. Namespace handling with XInclude is a can of worms. Those references did not come even close to providing a sample of what was involved. |
@billsegall Can you check that the samples work OK from your perspective? |
Is there way to set the path for the includes?
|
…se include so that the path is relative to the running process. Issue #624.
@billsegall The include path is relative to where the parser runs and that seems to be the only way XInclude works. I've updated the Java and C++ samples to reflect this by changing the working directory. |
… SbeTool in the resource directory. Issue #624.
@billsegall Do things work correctly for you now? |
In the FIX SBE Standard 1.0 it is suggested to use imports for common encodings. (see: https://github.com/FIXTradingCommunity/fix-simple-binary-encoding/blob/master/v1-0-STANDARD/doc/04MessageSchema.md#importing-encodings)
Issue #556 was closed with the reason that it is not possible to use both imports and schema validation with a link to a StackOverflow question. In that same SO question it is also stated that the imports should be handled before validation, so it should be possible.
Can I ask why it is not possible for the SBE-tool to support this? I would rather have the tool that does the processing do all of the processing, instead of requiring yet another tool to do the pre-processing.
The text was updated successfully, but these errors were encountered: