This week's book giveaway is in the OCAJP 8 forum. We're giving away four copies of OCA Java SE 8 Programmer I Study Guide and have Edward Finegan & Robert Liguori on-line! See this thread for details.
hi all , i m just trying to develop a simple database management application following the mvc pattern . for presentation part i m bit confused to use either jsp or xsl. i just need to know the difference between the two in their performance ,scalability , simplicity . so accordingly i could choose the language to use. if someone could help me out .
I have done applications both ways. I don't know about performance or scalability because they weren't high-volume applications. I would suggest that JSP is more intuitive for web applications than XSLT is, and also that you will find more people who are proficient in JSP than in XSLT to do the work.
Even I prefer to go the jsp way as using XSL for big sized projects or mid sized projects can become messy over a period of time.
SCJP 1.4, SCWCD 1.4 - Hints for you, Certified Scrum Master
Did a rm -R / to find out that I lost my entire Linux installation!
Joined: Jan 02, 2007
hi first thanks all for your replies . i m totally amazed that everyone is for jsp and in fact feel that coding in xsl is going to be the toughest job. but is there any one good reason for using xsl. because i have heard that some people still use xsl in their application for their presentation part by rendering the xml returned by controller or model. is that any particular feature that xsl could do but not jsp . and what could have made this people to choose xsl rather than jsp.
The "model" in a web application typically contains information stored either as session attributes or as request attributes. A JSP has access to those attributes built in, whereas XSLT does not, so you would need extra work to allow XSLT to access the model. So that's something specific in favour of JSP.
What could be an application where XSLT would be not a bad choice? In the application I wrote using XSLT, all of the pages had a common structure. This makes it easy to write a transformation per page, because xsl:include can be used a lot. But such applications are uncommon; they are visually boring and so they can only really be used in places where the users have no choice but to use them.
Joined: Jan 02, 2007
hey paul as you said i was just trying some sample program in xsl . all my pages have got same structure like drawing header , result table , placing buttons . i just wrote a common xsl code and using import i could call the particular template for header,table & buttons. and for specific behavior for particular page i just overridden the template in that page alone . so in this case as you said xsl coding is easy and less coding is to be done. but i just want to know if this could be done in jsp or is this kind of coding is not appreciated to do in jsp.