serialization

问题 I'm just starting out with Java serialization, and I'm not clear on how you are supposed to get objects from a source in a scenario with non-blocking I/O . All the documentation I can find suggests using ObjectInputStream is the proper way to read in serialized objects. However, as I mentioned I'm using java.nio and performing non-blocking operations. If readObject() will block until a new object is available, this can't help me Summary .. How do you do serialization when working with Java

问题 This is Jackson 2.2.x. I have a class implementing JsonSerializable; there are two methods to implement for this interface, serialize() and serializeWithType() . I want to test {de,}serialization of this class, and I can trigger calls to serialize() easily; not, however, serializeWithType() . The javadoc for this latter method says that this method is called [...] when additional type information is expected to be included in serialization, for deserialization to use. I just don't understand

问题 I am using DataContractSerializer to serialize an object to XML using DataMember attribute (only public properties are serialized). Is it possible to dynamically ignore some properties so that they won't be included in the XML output? For example, to allow user to select desired xml elements in some list control and then to serialize only those elements user selected excluding all that are not selected. Thanks 回答1: For the list scenario, maybe just have a different property, so instead of:

问题 My project is a java project over EJB3 using Hibernate and Weblogic server. For convenience sake (and as far as I understand, is typical to hibernate ), some of the entities contains circular dependency (Parent knows the child, child know the parent). Further, for some of the child classes - the hashCode() and equals() method depend on their parent (As it is a unique key). When working I saw an odd behavior - Some of the Sets that returned from the server to the client, although containing

问题 This is a really crazy bug. The following is throwing an OutOfMemoryException , for XML snippits that are very short and simple (e.g., <ABC def='123'/> ): public static T DeserializeXmlNode<T>(XmlNode node) { try { return (T)new XmlSerializer(typeof(T)) .Deserialize(new XmlNodeReader(node)); } catch (Exception ex) { throw; // just for catching a breakpoint. } } I read in this MSDN article that if I were using XmlSerializer with additional parameters in the constructor, I'd end up generating

问题 This is a really crazy bug. The following is throwing an OutOfMemoryException , for XML snippits that are very short and simple (e.g., <ABC def='123'/> ): public static T DeserializeXmlNode<T>(XmlNode node) { try { return (T)new XmlSerializer(typeof(T)) .Deserialize(new XmlNodeReader(node)); } catch (Exception ex) { throw; // just for catching a breakpoint. } } I read in this MSDN article that if I were using XmlSerializer with additional parameters in the constructor, I'd end up generating

问题 The following JSON is not deserializing. It's obviously because the DECIMALS in the saves JSON. How do I fix this? This initial JSON comes from the server and IS VALID: { "AppropriationAmount": 25000000, "AppropriationHours": 56300, "ArrThreshold": 11, "ClientKey": 24, "Description": 'Find and incarcerate the escaped prisoner', "DirectHours": 50000, "EndDate": '3/31/2011', "EngineeringHours": 4000, "IndirectHours": 2000, "Key": 1589, "Number": '0', "OtherHours": 300, "ProductivityCurveType":

问题 I have a class with a number of fields which are normally calculated in the constructor from other data in the class. They are not serialized to XML because any changes to the rest of the data will likely require their recalculation. Is there a way I can set up a function call to be triggered on deserialization? 回答1: What you are describing is [OnDeserialized] XmlSerializer does not support serialization callback methods (at least, not in MS .NET; mono may be different). Depending on your

问题 I have two lists (list1 and list2) containing references to some objects, where some of the list entries may point to the same object. Then, for various reasons, I am serializing these lists to two separate files. Finally, when I deserialize the lists, I would like to ensure that I am not re-creating more objects than needed. In other words, it should still be possible for some entry of List1 to point to the same object as some entry in List2. MyObject obj = new MyObject(); List<MyObject>

问题 I have two lists (list1 and list2) containing references to some objects, where some of the list entries may point to the same object. Then, for various reasons, I am serializing these lists to two separate files. Finally, when I deserialize the lists, I would like to ensure that I am not re-creating more objects than needed. In other words, it should still be possible for some entry of List1 to point to the same object as some entry in List2. MyObject obj = new MyObject(); List<MyObject>