[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] RE: use cases for d-o-e
Joerg, > Poll: Who does agree we can drop d-o-e without making too much > customers unhappy? Who does not, and why not? > NAG members are not allowed to invoke case three to thwart > the proposal! > :-) :-) I disagree, although I guess I will get relegated to the "bad" users of d-o-e camp. :-) I use XSLT to generate JSP pages, which I believe falls into your second category. However, I am not willing to accept the notion that I should simply use "text" as the output method. If I do that, it makes it much more difficult to retain all of the HTML tags on the JSP page. Things should get better when more containers support the XML compliant JSP specification (i.e. <jsp:scriptlet></jsp:scriptlet> rather than <% %>), etc.). That would avoid alot of the d-o-e hoops I am forced to use in order to get <% %>, <%= %>, and <%@ %> into the output. Now it is time for true confessions. I use the saxon:d-o-e extension frequently in the <xsl:attribute> tag, because I often want to use JSP scriptlets and/or expressions to set HTML attribute values (width, onClick, etc.). I would imagine that even using JSP XML tags would cause a problem for HTML attribute values (e.g. <td width="<jsp:expression>myJavaWidthVariable</jsp:expression>">). What do you suggest as the long-term solution in this case. I need further convincing that the pain of using "text" as the output method is merited. Regards, Dave XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|