Sounds good to me. :-) I just checked in changes I've had laying
around on my local system, which fixed some obscure namespace issues
found by a company which was implementing XBIS for use with their XML
product (they've since been bought by Sun, so I suppose they'll switch
to the ASN.1 Infoset encoding...).
I can provide some limited help when you run into problem - you can just
email me directly to discuss.
- Dennis
Mark Pimentel wrote:
Hi everyone,
Chinthaka and I will likely move forward with trying to implement a
StAX parser for Dennis' XBIS format for Axis2, instead of sticking
with DFDL. Does that sound reasonable to everyone?
Thanks,
Mark
On 8/16/05, Sanjiva Weerawarana <[EMAIL PROTECTED]> wrote:
On Wed, 2005-08-17 at 07:01 +0600, Sanjiva Weerawarana wrote:
On Tue, 2005-08-16 at 12:16 -0700, Dennis Sosnoski wrote:
I'll just refer back to our earlier discussion on this topic:
http://marc.theaimsgroup.com/?l=axis-dev&m=112131569306784&w=2 ;-)
- Dennis
+1 to using some XML Infoset binary serialization format rather than
DFDL.
I forgot to mention .. I would like to introduce a typed pull API
(extending StAX) into Axis2 (and implement it the obvious way). When
data binding is in place and if the data is being serialized, for
non-string data this can make a big difference. A common use case is
using Axis2 to deal with large numerical data sets .. if we go with a
binary typed stax approach, there's no intrinsic reason that should be
any slower or memory intensive than any other binary protocol approach.
After v1.0, of course ;-).
Sanjiva.
