I understand, that these streams aren't necessarily XML? If so, I have
implemented a similar thing in the JaxMe predecessor, called Parselets.
See
http://jaxme.sf.net/docs/api/de/ispsoft/jaxme/Parselet.html
for a rough idea. Basically, the generator converts the schema into a
set of Parselets.
This hasn't done with JaxMe 2. However, the main ideas are so comparable
and the extensibility of JaxMe 2 is even better than it has been for the
predecessor.
Correct, the streams would be generic ascii or binary data. I will
certainly take a look at these.
> type objects should be easily extensible, our biggest concern is that
> it doesn't support the full schema yet.
That's right. Since this week, we have support for nested groups with
multiplicity <= 1. More to come, hopefully.
That is good news. Do you have any idea of a time frame for nested
groups with multiplicity? Weeks/months/year?
> When marshalling does it use lazy binding?
Can you explain what you mean by that?
I think that you do this. By lazy binding I basically mean that the
marshaller doesn't store the data unless it is actually being used.
Unlike dom which I think stores all of the data with the object. It
appears that the serializers only retrieve the data when it is actually
being written out, is this correct?
Thanks for all your help!
Tara
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
