||The State of JAXB: Availability, Suitability, Analysis, and Architecture|
Response to: java.beans.XMLEncoder/Decoder
Thanks for the input. I haven't looked into XMLEncoder and Decoder. Perhaps as you have suggested they could be use for light weight uses which in my mind are quite a few. Again thanks for the pointers. Nevertheless it is interesting that we separate these XML data binding needs as serialization needs and data exchange needs although what is produced is XML in both cases. I think XML serialization is much more loose and lossy and problem domain specific and can cover more than object persistence. I don't think lumping this kind of serialization for XML generation doesn't suit the problem space either. We need a ground between this and JAXB. It would have been nice to see such a facility as part of JAXB. In fact there are suggestions in the JAXB architecture that perhaps it is possible to provide JAXB implementations without requiring an XSD or an alternative schema.