backward compatibility?

[Co...@trilogy.com]

I'm not sure if this has been addressed already (can't remember seeing it),
but do you guys anticipate Xerces 2 being a drop in replacement for the
1.1.x series?  Sure, it will provide a superset of 1.1's functionality, but
will it be backward compatible with 1.1 projects?  I'm wondering if moving
to 2.x (down the road) will be a painful process requiring a nontrivial
amount of code change, or if it will be very minor.  Any ideas on this?

---
Corbett J. Klempay
Trilogy Software, Inc.
512.532.5176 (W) | 512.750.1372 (C)
corbett.klempay@trilogy.com

Re: backward compatibility?

[Mikael St�ldal <d9...@d.kth.se>]

In article <39...@us.ibm.com>,
Arnaud Le Hors <le...@us.ibm.com> wrote:

>It all depends on what you're relying on. If you're only using the
>standard APIs SAX and/or DOM you'll be fine.

What about serialization?

-- 
/****************************************************************\
* You have just read a message from Mikael Ståldal.              *
*                                                                *
* Remove "-ingen-reklam" from the address before mail replying.  *
\****************************************************************/

Re: backward compatibility?

[Arnaud Le Hors <le...@us.ibm.com>]

It all depends on what you're relying on. If you're only using the
standard APIs SAX and/or DOM you'll be fine.
-- 
Arnaud  Le Hors - IBM Cupertino, XML Technology Group