Thanks for the changes. They were merged.
Paul Sandoz wrote:
> The implementations are currently very specific to the Base64Data class
> and will not scale very well when supporting a number of different data
> types. We will need a better way to supports types (single instances and
> in certain cases arrays of) for both serializing and parsing in the future
Right.
> The FastInfosetConnector class is currently FI StAX specific. In the
> future it does not have to be. I can see how to optimize specifically
> for JAXB e.g. to avoid buffering until the end of the element, and not
> to decode stuff like comments and PI which can be just skipped.
I'm not sure if I follow this. Are you saying that you can do those
optimizations with any StAX parser?
> The serializing side of things should be quite stable as most code is
> rused. The parsing side may be less so because it is new code. I am not
> sure how best we can test both the parser and serializer. Can existing
> JAXB tests be used with FI?
If we have instance documents, I think we can. Is there any "FI encoder"
tool?
--
Kohsuke Kawaguchi
Sun Microsystems kohsuke.kawaguchi_at_sun.com