<?xml version="1.0" encoding="UTF-8"?>
I am well aware of the fact that you are amongst the most talented people out there, so with due respect to your post,I would like to say that
I know of XML behavior in a browser, it simply looks like
<?xml version="1.0" encoding="ISO-8859-1" ?>
<body>this is a hello message</body>
when you click on the " - ", the note tag winds up and a + is displayed, clicking it collapses the tag and again the tree is displayed.
Please correct me if I am wrong
Thanks in advance
That actually made me laugh out loud - but thanks for believing in me...
I am well aware of the fact that you are amongst the most talented people out there
Perhaps i mis-understood your question (it's still pretty early here). I thought you were asking why an XML file might have a .jspa extension, and how the browser would know what to do with it. I was answering that question, not "why is the browser displaying what is XML in a non-xml kind of way".
can you provide a link to a specific example?
Keep in mind that just because a URL ends with "xml", that doesn't mean it's an XML file that will be sent to the browser. In this particular case it's obviously mapped to a server-side component that transforms it into HTML.
its great to see that special people like you bartenders/ sheriff's show willingness to answer even the most smallest of the questions
That is my most favorite part of the ranch
now Ulf's post cleared my confusion, although I had previously thought on similar grounds, but then I thought why would some do it that way, hence the confusion. Then came in the .jspa extension to add more confusion.
Then i felt like asp evolved into aspx, JSP's might have evolved into JSPA
And i was totally unaware of the new technology
now I guess its not like that
Although I am unable to get rid of some small percent of confusion remaining
Thanks for the help
[ April 17, 2008: Message edited by: Amit Ghorpade ]