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.
Hi Giselle, I have used xmlc for a couple of years now and to tell you the truth I am not impressed. The concept of it seems pretty cool, a unique way of separating data from presentation etc, but in reality unless you are serving up very simple HTML, things become complex very quickly. It also does not scale well and suffers from performance issues. For those who don't know what xmlc is: - code up HTML with HTML 4.0 "id" attributes - compile the HTML using the xmlc compiler into a Java class, the ids, become static members of the class - from a servlet you then instantiate the above class and use DOM manipulation to produce the dynamic HTML (adding/removing nodes etc) - and then essensially perform an out.println(document.toString()) So my advice would be to avoid it and stick with servlets/jsps/taglibs, or even go down the servlets/xml/xslt route.
Joined: Apr 20, 2003
Thanks James, I had a feeeling I was going to hear that. Unfortunatelly, I was told to prepare this demo that today uses jsps/servlets on xmlc. So I have to do kind of a migration. Hope I got this right: 1) Transform my jps on pure htmls 2) compile them with xmlc 3) create servlets for whatever functionalities I had on my jsps 4) call them from the .java files my compilation produced ?
Joined: Jun 26, 2001
Yep that's pretty much the steps: here's a simple xmlc example: - it should compile assuming you have your environment setup (xmlc jars etc) - also assuming you know how to invoke the xmlc compiler the html
James. [ November 11, 2003: Message edited by: James Swan ]