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 came to know the purpose of XMLs in application (as in many frameworks)that is even if any changes happens to the xml, the application need not be redeployed.
I have a question,But if the XML is in the application(say ear), after changes, the application has to be rebuilt(new ear) and then reployed and then the server has to be restarted.rite? Iam not clear here.
Yes Xmls are definitely preferred for configuring applications rather than hard coding them into your code.
when you deploy an app (.war or .ear) the app server extracts the files, you may change these configuration XMLs (which are now extracted) and just restart the server (in some cases like spring webflow xmls you don't have to restart the server) for your changes to be picked up. This saves you from rebuilding and redeploying your app.
Cheers, Joy [SCJP 1.4, SCBCD 5.0]
get high on alcohol, algorithm or both