...actually, as I struggle to get my little test case to break with that NullPointerException at org.exolab.castor.xml.MarshalFramework.searchInheritance (or alternately and even better to get the real code to NOT break), I realize: this whole project is intended to get the system to listen to commands via REST. As one coworker said when I asked him why we had setSuppressXSIType to true in the first place, "otherwise it puts in all kinds of stuff that we didn't think REST wanted to see."
In other words, people are going to want to send XML over the wire to create a new one of these objects, and apparently we don't want to have to ask them to specify XSI:type. I can push back on this if necessary, but: Is there in fact another way to go about taking the XML for a map and turning it into a Map with the correct objects inside it? I fantasize about something like <map> <key>some string here</key> <value> <cost>...</cost> </value> </map> ...such that it knows to map "cost" into a Cost object. (I guess the question of how to map the key into a String remains.) Am I headed in completely the wrong direction? Jessica ------------------------------------------------- If you wish to unsubscribe from this list, please send an empty message to the following address: [EMAIL PROTECTED] -------------------------------------------------
