"Dirk P. Fromhein" wrote:
>
> Why is that?
>
> I can think of one reason (that I hope is not the reason - applet
> compatibility with "old" browsers, not a feature I care about at all).
>
How about, because our sponsors want us to keep JDK 1.1 compatability.
Do you think that's a good enough reason? I think it's a great
reason...they make it possible for Castor to remain free of charge and
open source.
> In the area of Collections, 1.2 added some very important functionality.
> Why not support it? (I for one feel it is essential)
I never said we wouldn't support 1.2...AND WE DO have support for 1.2 in
both the source code generator and the mapping framework.
I simply said, we need to maintain JDK 1.1 compatability. JDK 1.2
compatability needs to be added in a way that it doesn't break JDK 1.1
compatability, that's all.
Castor-XML needs to remain JDK agnostic. This simply means we need to be
creative when we add support for JDK 1.2, such as using collection
handlers and wrapper classes, etc.
Glenn is maintaining his changes and has made them available. So if you
wish to use them, feel free to do so. That's why he made them available.
For people like you, who feel it's essential.
Thanks,
--Keith
>
> Keith Visco wrote:
>
> >Hi Glenn,
> >
> >We can't use your patch. Castor XML is maintaining JDK 1.1
> >compatability. The Marshaller cannot include JDK 1.2+ collections.
> >
> >Thanks,
> >
> >--Keith
> >
> >[munch]
> >
>
> -----------------------------------------------------------
> 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
