comment on

I apologize. I just re-read the post and realized the formatting for the last paragraph was incorrect. It probably didn't make much sense. It should have read:

The problem is that I have to extract (inclusively) the data between each <Message>...</Message> section and write each chunk to its own file using the value in <MessageID>...</MessageID> for the file name. I understand that this module generates SAX events as a result of the query however, I was considering building a DOM tree and using XPath to extract the necessary text. Can anyone offer any advice on my purposed method of attack? I understand the benefits of using SAX with regards to performance however, the ease of the XPath syntax seems very appealing.

Thanks again,
Jay

In reply to Re: Design recommendation for parsing and creating XML files. by jmurphy
in thread Design recommendation for parsing and creating XML files. by jmurphy

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Your skill will accomplish what the force of many cannot
	PerlMonks