Home » railML newsgroups » railML.infrastructure » [railML3] Proposal for removing "any" elements (this post just points to another post where the proposal is presented)
Re: [railML3] Proposal for removing "any" elements [message #3025 is a reply to message #3024] Mon, 04 July 2022 16:20 Go to previous messageGo to previous message
Milan Wölke is currently offline  Milan Wölke
Messages: 141
Registered: April 2007
Senior Member
Hi Jörgen,

sorry, but I havent had much experience with the EMF so far. So what you are saying is that the EMF will completely skip unknown subclasses of known ones if encountered during parsing? Do you evaluate a xsi:schemaLocation included in the document? Im asking because other generated parsers in the case you are describing fall back to the known base class.

Best regards, Milan

Milan Wölke – Timetable scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org

Report message to a moderator

[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: [railML3] LevelCrossing Best Practice Example
Next Topic: [railML 2] Semantic Constraint at trackBegin and trackEnd
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Thu May 09 10:49:16 CEST 2024