Lists Home |
Date Index |
- From: "Sam Gentile" <firstname.lastname@example.org>
- To: "'David Brownell'" <db@Eng.Sun.COM>,"'XML Dev'" <email@example.com>
- Date: Wed, 5 Aug 1998 12:00:23 -0400
I don't have a month. I have a day. Our team leader has resolved it - use
Microsoft's Java classes to do it on both ends.
From: David Brownell [mailto:db@Eng.Sun.COM]
Sent: Wednesday, August 05, 1998 11:51 AM
To: Sam Gentile
Subject: Re: Help in picking a parser
Particularly if you'll be using Java, you should look at the
package Sun will be providing. It's not yet on the web, but
should be there later this month. Includes validating and
nonvalidating parsers ... very fast, robust, conformant.
Alternatively, I usually recomment XP. It has that same
set of technical advantages, though it doesn't offer any
validation option and is "just a parser".
Sam Gentile wrote:
> I am working on a E-Commerce Banking system and we have finally convinced
> people to use XML to transport our data from the browser front-end to the
> Web Server and out through our TUXEDO application servers. There is a need
> for XM parsers in several locations. On the browser side, we have DHTML
> Microsoft's Visual J++ WFC "Code Behind DHTML" Java classes. I thought
> was a WFC class to do parsing but it turns out that there is a
> com.ms.xml.parser in the Java SDK. So that side is taken care of.
> Our problem is more on the Web Server side. On the client, we are
> the Java classes into an XML buffer to go to the Web server. The Web
> will need to parse this XML and use a factory to dynamically instantiate
> re-create the Java class hierarchy.
> Then the data will be put in TUXEDO FML format for shipment to the Tuxedo
> servers. On the way back, I will have to take an FML buffer and convert to
> an XML buffer.
> They say they don't want to use DTDs and validating parsers and that we
> need the parser to be cross-platform. So I have been looking at
> Nonvalidating parsers like Lark and XP. I am new to XML. It seems like
> parsers are a maze of source code. Will I be better off having my code
> "spawn" an existing parser instead of integrating with this source code?
> Validating parsers be used even when DTDs are not used (like Microsoft's
> Any suggestions and thoughts would be greatly appreciated.
> Sam Gentile
> Senior Software Engineer
> Fundtech Corporation
> firstname.lastname@example.org <mailto:email@example.com>
> xml-dev: A list for W3C XML Developers. To post, mailto:firstname.lastname@example.org
> Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
> To (un)subscribe, mailto:email@example.com the following message;
> (un)subscribe xml-dev
> To subscribe to the digests, mailto:firstname.lastname@example.org the following
> subscribe xml-dev-digest
> List coordinator, Henry Rzepa (mailto:email@example.com)
xml-dev: A list for W3C XML Developers. To post, mailto:firstname.lastname@example.org
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:email@example.com the following message;
To subscribe to the digests, mailto:firstname.lastname@example.org the following message;
List coordinator, Henry Rzepa (mailto:email@example.com)