After looking through the documents on the site, I'm seeing some behavior that would seem to qualify as a "feature" - I'd like an opinion on it. While the docs agree that this behavior exists, I'm not sure it _should_.
Concrete mappings are, the docs state, one-per-class. For marshalling purposes, you need to be able to link the class to an expected name. Okay. Makes sense. Until I start working with a direction="input" binding. At this point, the only "unique" I should need to worry about for a binding is the name in the XML, and not the class, itself - after all, I don't need to marshal to XML, so the name of the incoming XML element should be sufficient identification of the unmarshaller. Right? So, the question... Is this something I need to find a way to hack around, or would it be worth investigating a behavioral alteration in JiBX, itself? -- The cake is a lie! ------------------------------------------------------------------------------ Nokia and AT&T present the 2010 Calling All Innovators-North America contest Create new apps & games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev _______________________________________________ jibx-users mailing list jibx-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jibx-users
