Hi Joe:
>
>That appears to work for implementation classes, as long as everyone is
>very careful to _ONLY_ use APIs provided by the unchanging stuff in the
>core jarfiles.
>
>It doesn't directly address genuinely evolving standard APIs, where users
>might want to plug in a new release of the Interfaces along with the new
>implementation. (Consider the user who wants to start prototyping DOM
>Level 3, but is seeing DOM Level 2 on your extension classpath.)
>
I agree with you that the renaming of implementation classes would not help us
address the case of evolving standard APIs ( like DOM, SAX ). I hope as part of
JSR process, we can come up with some solution that addresses this issue.
Any ideas?
Thanks
-Ramesh
>______________________________________
>Joe Kesselman, IBM Next-Generation Web Technologies: XML, XSL and more.
>"may'ron DaroQbe'chugh vaj bIrIQbej" ("Put down the squeezebox and nobody
>gets hurt.")
>
