[jdom-interest] Re: [jdom-commits] CVS Update: jdom/src/java/org/jdom/transform

[Elliotte Rusty Harold]

At 2:30 AM -0600 5/5/03, nobody wrote:
>****************************************
>Date:   Mon May  5, 2003 @02:30:23 MDT
>Author:
>
>Update of /home/cvs/jdom/src/java/org/jdom/transform
>In directory chimbo:/tmp/cvs-serv8192/src/java/org/jdom/transform
>
>Added Files:
>XSLTransformException.java XSLTransformer.java
>Removed Files:
>JDOMTransformer.java
>Log Message:
>Renaming JDOMTransformer to XSLTransformer which seems more accurate.
>Rusty, you had XSLTransform. Do you think that's better than with "er"?
>


6 of one, half dozen of another. OK, maybe 5 and 7. It depends on how 
you look at it. Since the object is configured with exactly one 
stylesheet, I think of it as a representation of a particular 
transform rather than a transformation engine. If the class provided 
methods that accepted both the stylesheet and the input dopcument as 
arguments, and thus could transform according to multiple different 
stylesheets, e.g.

public static List transform(Document stylesheet, Document input)

then I would say this is a transformer rather than a transform. So 
yes, I guess I do prefer XSLTransform. But neither really offends my 
sensibiliies.

>Also added an XSLTransformException (subtype of JDOMException) and changed
>the XSLTransformer class to throw this type. Rusty, you had XSLException.
>This name seems more specific, but I'm curious if you had a different more
>general vision?

What in your view would be the difference between an 
XSLTransformException and an XSLException? Is there some kind of 
XSLException that is not an XSLTransformException? If not, I prefer 
to have less typing. :-)
-- 

   Elliotte Rusty Harold
   elharo at metalab.unc.edu
   Processing XML with Java (Addison-Wesley, 2002)
   http://www.cafeconleche.org/books/xmljava
   http://www.amazon.com/exec/obidos/ISBN%3D0201771861/cafeaulaitA