xom-interest AT lists.ibiblio.org
Subject: XOM API for Processing XML with Java
List archive
- From: Wolfgang Hoschek <whoschek AT lbl.gov>
- To: xom-interest AT lists.ibiblio.org
- Subject: [XOM-interest] XSLTransform(Templates templates)
- Date: Mon, 6 Sep 2004 21:01:12 -0700
Perhaps another (fourth) option would be to add a XSLTransform(import javax.xml.transform.Templates) constructor similar in spirit to Builder(XMLReader). That way the other discussed methods could possibly go away, yet advanced/fully configured usage would become possible (for those who make sure that things works as intended in their context). Such stuff is needed to configure variables, functions and other transformer specific options. Currently the XOM XSLTransform really can't be used if such configuration is required by the app.
That sounds like a separate issue, though one worth considering. I don't think I'll address it for 1.0, but I will add it to the list to be considered for future releases.
With b4 it's as simple as adding a constructor along the following lines:
public XSLTransform(Templates templates) {
if (templates == null) throw new IllegalArgumentException();
this.templates = templates;
}
-
[XOM-interest] Re: XSLTransform constructors are flawed,
Wolfgang Hoschek, 09/02/2004
-
[XOM-interest] Re: XSLTransform constructors are flawed,
Elliotte Rusty Harold, 09/02/2004
-
[XOM-interest] Re: XSLTransform constructors are flawed,
Wolfgang Hoschek, 09/02/2004
- [XOM-interest] Re: XSLTransform constructors are flawed, Elliotte Rusty Harold, 09/03/2004
-
[XOM-interest] XSLTransform(Templates templates),
Wolfgang Hoschek, 09/07/2004
- [XOM-interest] Re: XSLTransform(Templates templates), Wolfgang Hoschek, 09/07/2004
-
[XOM-interest] Re: XSLTransform constructors are flawed,
Wolfgang Hoschek, 09/02/2004
-
[XOM-interest] Re: XSLTransform constructors are flawed,
Elliotte Rusty Harold, 09/02/2004
Archive powered by MHonArc 2.6.24.