|
XMLC vs. JAVA TEMPLATE METHOD: msg#00016java.enhydra.xmlc
Hi, I am considering using XMLC for a large J2EE project. I currenlty create HTML pages which are doctored to include the XSLT commands. From this perspective, I definitely see the advantage of a simple HTML page without page designers having to know XSLT. What I do not like, is seeing a bunch of new Java classes for every HTML page in my design. I currently use a template base class to do all of the XML document generation using Metadata to link the XML tags to variable names in a Java list object. I only have a single class that is used to generate all of the documents for every HTML page. Can I hear some arguments as to how I can do this with XMLC and why using XMLC would be a better approach? Thanks! John Westerkamp Productivity Network Innovations, LLC
|
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | Re: XMLCDeferredParsingFactory and classpaths, Jacob Kjome |
|---|---|
| Next by Date: | Re: XMLC vs. JAVA TEMPLATE METHOD, David H. Young |
| Previous by Thread: | XMLCDeferredParsingFactory and classpaths, James Carnegie |
| Next by Thread: | Re: XMLC vs. JAVA TEMPLATE METHOD, David H. Young |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |