Hi Hari,

You can change the package structure of xerces and compile again: (e.g.
com.foo.org.apache...) I don't know what the legal implications are for
this, but I've seen it before. You probably won't be able to share
objects, but if your module is self-contained you would be able to use
the new version of Xerces in it.

This, of course, assumes it's impossible to simply change the rest of
the code to conform to the new interface. There also are some behavior
changes, e.g. schema locations must be valid URIs now. But your unit
tests will catch those, right? ;)

Chris

P.S. You could go the ClassLoader route, too, but that's prone to a
bunch of subtle errors...

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] 
Sent: Friday, December 10, 2004 00:36
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: xerces2 compatible with xerces 1.x



Hi,

Thanks for the response. This is still a hot issue for me, wondering if
I can somehow isolate the xerces 2.x impl for use by my part of the app
alone? Maybe by refactoring? I vaguely remember somebody mentioning
doing this sometime earlier on this group...any ideas would be greatly
appreciated!

Thanks,
-hari



 

                      "Michael

                      Glavassevich"            To:
[EMAIL PROTECTED]

                      <[EMAIL PROTECTED]        cc:       (bcc: Hari
Dhandapani/PeopleSoft)                                             
                      com>                     Subject:  Re: xerces2
compatible with xerces 1.x                                        
 

                      12/06/2004 02:54

                      PM

                      Please respond to

                      xerces-j-user

 

 






[EMAIL PROTECTED] wrote on 12/06/2004 05:23:42 PM:

> Hi,
>
> I uses Xerces2 for XML Schema API. However, there are other parts of 
> our system that are certified to work with only xerces 1.x. Wondering 
> if I switch out the 1.x with 2.x, will the old code that uses xerces 
> 1.x continue to work? In other words, is Xerces2 backward compatible?

If the code was only using standard APIs then you should be able to
switch out Xerces 1.x with 2.x. If it was relying on some internal
classes then migrating may be a bit of a challenge.

> Alternatively, is there a way I can use XML Schema API implementation
with
> Xerces 1.x?

The XML Schema API has only existed since Xerces 2.6.0. There is no
implementation for Xerces 1.x.

> Thanks for your help.
>
> -hari
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>

Michael Glavassevich
XML Parser Development
IBM Toronto Lab
E-mail: [EMAIL PROTECTED]
E-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]







---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to