Hi Sarada,
I'd say the issues you're concerned about apply to any set of APIs you
might code to. There's always a tension between evolving the API based
on experience and new requirements and maintaining backward
compatibility with existing applications. In the case of JAXB (and all
JCP-developed APIs), evolution of the API is controlled by a group of
experts sensitive to this tension.
Regards,
--
Ed Mooney |Sun Microsystems, Inc.|Time flies like
Java Web Services |UBUR02-201 |an arrow, but
Ed.Mooney_at_Sun.COM |1 Network Drive |fruit flies like
781-442-0459 |Burlington, MA 01803 |a banana. Groucho
Lakhamraju, Sarada (UMC-Student) wrote:
> Hello All,
>
>
> I have a question regarding the application development and JAXB API. If I develop an application with JAXB using the API available now and later after some years if the API changes or gets upgraded then many of the methods may become deprecated and my application will be obsolete and I have to rewrite the whole binding code in accordance to new API.
>
> How can this issue be answered? Will such a case may arise or not? Can JAXB be used for developing robust applications? Will JAXB be an issue in the stability of the application developed??
>
> Please answer by questions....
>
>
> Regards & Thanks,
> Sarada
>