Hi Jim,
The XMLSerializer is correct in throwing an error with (char)0 since
it's not a valid XML character. There is little we can do about that,
the character simply cannot exist in an xml document.
I've answered the question about vectors and references in a response to
your previous posting on the castor-user list.
Thanks,
--Keith
Jim Redman wrote:
>
> Apologies for what is essentially a cross posting. I'm either hitting
> a bunch of Castor bugs, or I'm doing something sadly wrong, perhaps
> this list can put me straight.
>
> There seems to be a problem with archiving characters that are not
> valid XML characters. For example, and object with this (and it's set
> sibling):
>
> [...]
> public char getCharValue () {
> return (char)0;
> }
> [...]
>
> generates and error from the XMLSerializer.
>
> I also hit an error that I notice has been reported elsewhere, where
> validation generates a NullPointerException (I'd get you the exact
> error, but non-Castor problems prevent me for running the app). If I
> can find more details, I'll pass them along.
>
> The biggest problem is that archiving Vectors seems to generate copies
> of the Objects rather than references when archiving Vectors that have
> common elements. I've seen hints that this is a bug, but couldn't find
> it in the bug database (after much searching). Can someone enlighten
> me as to whether this is a known bug or whether I'm doing something
> wrong?
>
> Thanks,
>
> Jim
>
> --
> Jim Redman
> (505) 662 5156 x85
> http://www.ergotech.com
>
> -----------------------------------------------------------
> If you wish to unsubscribe from this mailing, send mail to
> [EMAIL PROTECTED] with a subject of:
> unsubscribe castor-dev
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
