You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@xalan.apache.org by bu...@apache.org on 2002/09/06 21:45:27 UTC

DO NOT REPLY [Bug 12377] - TCK: Output method is not set to html when it should

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12377>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12377

TCK: Output method is not set to html when it should





------- Additional Comments From santiago.pericasgeertsen@sun.com  2002-09-06 19:45 -------
Morris: 

 There was a long discussion about this TCK a few months ago. The conclusion 
was that the test is *incorrect*. There is not way for an XSLT processor to 
determine the output type "without running the transformation". Thus, creating 
a Templates object and then getting the property is not enough. 

 Notice that the paragraph you pasted from the spec talks about the "result 
tree" and not the "stylesheet". It is easy to show that this TCK is bogus: 
just write a stylesheet (with no xsl:output) that depending on the value of a 
parameter outputs HTML or XML (e.g. using an xsl:if). What would be the value 
of getProperty("method") in that case? 

 The solution to this problem is (i) drop this TCK test (ii) update the JAXP 
documentation explaining why this information cannot be obtained from a 
Templates object.