This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
I heard about the overhead of xml process in general and when I read about the JSP's internal XML representation of a page,
I wondered what could be the pros/cos or reasons to have this extra overhead.
Do you know the reasons? Is XML a overhead?
I have not heard of any conversion to XML. I am sure the spec does not ask a provider to convert to XML either. Converting something like HTML code to XML can be painful if you do not follow strict rules. For a container to actually enforce this rule or try to convert data that is not well formed to well formed XML, can be error prone and disastrous.
If you can point me to a quote from safari or a page number that would be great. I would be surprised if a spec demands well formed JSPs or conversion to well formed XML like JSPs.
ahhh Marcelo, I have misinterpreted your question. I see what you are pointing at. And yes the spec does define how page attributes / directives are converted into their respective XML elements with the JSP namespace.
As for your question itself, I am not aware of a overhead or a lack of it. I guess it would depend on how this XML is being processed. I have not heard of any XML specific degradation in performance for a JSP.
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com