Issue with XML Parsing

[Vishnu7185]

My process is returning an xml in the form of a string.I need to parse this XmlString and pull the values in it.

<Outer Tag
Data 1="wewe"
Data 2="1"
Data 3 ="13 Oct 2006"
Data 4="Sample">
<First Inner>
<First Inner. Inner 1
Data 1="28310615"
Data 2="Sample333"
Data 3 ="######Sample33###########hujjj#####">
</First Inner. Inner 1>
</First Inner>
</Outer Tag>

This is the sample xml.

I wanted to parse this string and pull out ######Sample33###########hujjj#####

which Parser should i be using and how? Since the xml is not well formed(may be i am unaware) i am stuck.

I tried with SAXParser but i am getting the following error
org.xml.sax.SAXParseException: Content is not allowed in trailing section.

[67726e]

That 'technically' isn't XML since it doesn't contain all of the necessary elements of an XML document. Perhaps you should learn XML first so you know how to create a well-formed document: XML Tutorial

As for a parser, it would depend on the application and the constraints you are working with but the easiest to use would be the DOM parser. If you are familiar with the DOM in web dev then it should be a snap to use.

[Tolls]

Yep, in fact nothing technical about it. It's not xml, so you can't parse it using any sort of xml parser. '<' and '>' does not xml make.

[Vishnu7185]

Hi

The xml had the top tags like the xml version and DOCTYPE which i have removed.

I tried using an XSLT processor and it worked. But I am encountering another issue when my out put i am trying to convert into an Json Array
######Sample33###########hujjj#####

[Tolls]

You have spaces in the tag names.
Or is that merely some example?

[67726e]

Your tags are also supposed to be in lower case <TAG STUFF=""> is not acceptable. Like I said, you must go over that tutorial and learn what you can and cannot do with XML.

[Tolls]

Are they?
Didn't think the spec precluded that?
They definition for a Name doesn't anyway.

Is that just a form of xml coding standard?

A lot of xml is camel cased, especially xsds for web services which get turned into Java classes.

[67726e]

I'm not actually sure about the 'names'. I mean I have always done it and everyone I know does it. I also know the XHTML spec states they must do that and the XHTML standard was made to make websites XML compliant.

[Tolls]

Well, I think the XHTML is like that because XML is case sensitive, and they defined the various tags as lower case. Then again, they're usually single words, or abbreviations.

If you look at web services you'll usually see camel case (to match Java, or other, naming conventions)