If you just want to use standard W3C DOM features using a different XML
parser implementation, there are a number available. One of the most
popular is Apache Xerces: 

http://xml.apache.org/xerces2-j/index.html

Also, I would be surprised if there isn't an implementation already
included in the Websphere 5.0 distribution, but I haven't used WebSphere
so can't be certain. 

Another thing, if you haven't already done so, you might want to
consider using the JAXP API (included in Xerces & others) to obtain your
XML parser instances, since this allows you to make your code
vendor-agnostic, and specify the actual parser implementation externally
(e.g. as a system property). 

HTH. 

Al.


> -----Original Message-----
> From: Eli Edwards [mailto:[EMAIL PROTECTED]] 
> Sent: 28 January 2003 18:37
> To: JDJList
> Subject: [jdjlist] TXDocument replacement - XML parsing migration
> 
> 
> Hi all,
> 
> I have been searching high and low, and am getting nowhere fast...
> 
> Does anyone have any information on replacing the 
> com.ibm.xml.parser.TXDocument with an open source (or perhaps another
> vendor's) implementation of the org.w3c.dom.Document 
> Interface?  I can not find a replacement so far.
> 
> We are migrating our JDK 1.2 servlet application to J2EE 1.3 
> architecture.  (i.e. Currently we use WebSphere 3.5 and are 
> migrating to WebSphere 5.0)  IBM's com.ibm.xml library, 
> particularly the TXDocument class, is no longer available in 
> this new environment, so we have to replace it.
> 
> Thanks for any guidance.
> 
> Regards,
> Eli Edwards
> 
> ____________________________________________________
> To change your JDJList options, please visit: 
> http://www.sys-con.com/java/list.cfm
> 
> Be respectful! Clean up 
> your posts before replying 
> ____________________________________________________
> 

____________________________________________________
To change your JDJList options, please visit:
http://www.sys-con.com/java/list.cfm

Be respectful! Clean up your posts before replying
____________________________________________________

Reply via email to