I am curious why there is a null return value for the getEncoderFactory() method in IEEE1516eRtiFactory as of OHLA 0.6. Does this indicate there are no implementations yet of the IEEE 1516e data types yet checked in?
I have yet to implement those. I will add them to the list of things for 0.7.
I'm almost done with 0.6.1 which fixed a few things and changed the serialization to use Google Protocol Buffers in preparation for the C++ interface.
I have some completed implementations based in part on the 1516 jlc classes (with appropriate additions). I haven't verified the implementation against the standard but it appears to work in practice and I'd be happy to contribute them. Thanks for your continued work on this project, I've been using it off-and-on over the past couple of years.
You can send me the files you want to contribute and I'll add them in for the next release.
Glad to hear that you are making some use of the project!
I've attached the files here... it was actually a while ago that I did a bulk of the transplanting from the jlc classes. There are a couple new methods required for the 1516e interface and a couple new data types. I referenced the standard to get the correct encoding structure, however I don't recall the extent to which I actually tested the code. Anyways, hope it's helpful!
Log in to post a comment.
Sign up for the SourceForge newsletter:
You seem to have CSS turned off.
Please don't fill out this field.