Or, a non-parser way, read the xml file to a buffer, send the buffer to
a jsp, using jstl's xml parsing capability (<x:parse xml="${your xml
file} var=...) to do that. This can be done within 24 hours :-)


Saul


> -----Original Message-----
> From: Mark Galbreath [mailto:[EMAIL PROTECTED]
> Sent: Thursday, August 28, 2003 5:31 PM
> To: 'Struts Users Mailing List'; [EMAIL PROTECTED]
> Subject: RE: XML Parsing Dilemma
> 
> 
> 
> 
> 
> This is my real dilemma.  I think an XML parsing engine should be able
to
> take a validated XML file and output:
> 
> tag_name = tag_value
> 
> and understand where one record stops and another record begins.  For
> crying
> out loud, I can write the thing myself in a few hours, but I want to
> remain
> open-source standard.  Is there an XML parser that simply reads the
tags
> and
> puts them into a collection indexed by record?
> 
> Mark
> 
> -----Original Message-----
> From: Greg Reddin [mailto:[EMAIL PROTECTED]
> Sent: Thursday, August 28, 2003 12:07 PM
> To: Struts Users Mailing List
> Subject: Re: XML Parsing Dilemma
> 
> 
> > The front-runners on my list is Castor and JDOM.  Any (related)
> > suggestions are greatly appreciated.
> 
> I've used both of these, though not JDOM enough to comment on it.  My
> favorite XML tool right now is Digester.  To me, it has a smaller
> development footprint than Castor and gives you at least the same XML
> parsing capability.
> 
> I used both Castor and Digester to parse configuration files.  To use
> Castor I had to write a schema and the castor "client" code, which was
> pretty big and I had to put up with the objects it generated.  For
> Digester I wrote a RuleSet class, some value objects and a very small
> amount of "client" code.  I didn't write (but should've written) a
DTD.
> 
> Greg
> 
> 
> 
> DISCLAIMER:
> This email message is for the sole use of the intended recipient(s)
and
> may
> contain confidential and privileged information.  Any unauthorized
review,
> use, disclosure or distribution is prohibited.  If you are not the
> intended
> recipient, please contact the sender by reply email and destroy all
copies
> of the original message and attachments.
> 
> ---------------------------------------------------------------------
> 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