I probably found a bug in IEEE1516e xml-parser code (IEEE1516eFDDParser.java) which restricts the use of scaffolding ineraction classes. An interaction class is created when SAX parser handles the "</order>" tag. But there is only the "<name>" tag in scaffolding class impelementation so it doesn't event make an attempt to create an interaction class hierarchy. Application crashes with null poiner exception when RTI tries to merge FDDs and finds null instead of interaction root in loaded FDDs.
I think the XSD requires the name, transportation, and order tags (in that order). I create the InteractionClass when I get the order tag because it is last.
I should probably add schema validation. I think that would help with identifying problems.
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.