Re: why always rely on Externalizable
- Hello Nicolas,
I sent you a jar with what you needed, and a couple of followup
But I haven't had a reply from you. That was all a few weeks ago.
Perhaps this reply on the email list will reach you.
--- In JSXfirstname.lastname@example.org, "nicolascorreard"
> I've been using a trial version of JSX, as part of an IT project
> in Paris.ugly
> First thought: great! It does many things that other tools like
> skaringa were not able to do.
> Then, we changed most of our objects to Externalizable to speed up
> serialization. The XML we got was completely different: one big
> byte array. Suprising, but logical: since we broke down the wholeif
> serialization all the way to the native type.
> Hence, my suggestion: provide a way to ignore Externalizable,
> in the constructors for example:
> ObjectWriter out = new ObjectWriter(false);
> ObjectReader in = new ObjectReader(false);
> This is critical to us: we cannot use JSX as is. If you provide us
> with a fix to this, we'll use JSX and buy a site (maybe enterprise
> I convince my boss) distribution license.