Java 中的高效 XSLT 管道（或将结果重定向到源）
我有一系列相互馈送的 XSL 2.0 样式表，即样式表 A 的输出馈送 B 馈送 C。
最有效的方法是什么？重新表述的问题是：如何有效地将一种转换的输出路由到另一种转换中。
这是我的第一次尝试：
@Override
public void transform(Source data, Result out) throws TransformerException{
for(Transformer autobot : autobots){
if(autobots.indexOf(autobot) != (autobots.size()-1)){
log.debug("Transforming prelim stylesheet...");
data = transform(autobot,data);
}else{
log.debug("Transforming final stylesheet...");
autobot.transform(data, out);
}
}
}
private Source transform(Transformer autobot, Source data) throws TransformerException{
DOMResult result = new DOMResult();
autobot.transform(data, result);
Node node = result.getNode();
return new DOMSource(node);
}
正如您所看到的，我使用 DOM 来进行转换，虽然它很方便，但它的性能并不是最佳的。
有没有简单的方法可以将 SAXResult 路由到 SAXSource？ StAX 解决方案将是另一种选择。
我知道像 XProc 这样的项目，如果您还没有看过的话，这非常酷，但我没有不想投资整个框架。
I have a series of XSL 2.0 stylesheets that feed into each other, i.e. the output of stylesheet A feeds B feeds C.
What is the most efficient way of doing this? The question rephrased is: how can one efficiently route the output of one transformation into another.
Here's my first attempt:
@Override
public void transform(Source data, Result out) throws TransformerException{
for(Transformer autobot : autobots){
if(autobots.indexOf(autobot) != (autobots.size()-1)){
log.debug("Transforming prelim stylesheet...");
data = transform(autobot,data);
}else{
log.debug("Transforming final stylesheet...");
autobot.transform(data, out);
}
}
}
private Source transform(Transformer autobot, Source data) throws TransformerException{
DOMResult result = new DOMResult();
autobot.transform(data, result);
Node node = result.getNode();
return new DOMSource(node);
}
As you can see, I'm using a DOM to sit in between transformations, and although it is convenient, it's non-optimal performance wise.
Is there any easy way to route to say, route a SAXResult to a SAXSource? A StAX solution would be another option.
I'm aware of projects like XProc, which is very cool if you haven't taken a look at yet, but I didn't want to invest in a whole framework.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
我发现了这个：#3。链接转换展示了使用 TransformerFactory 链接转换的两种方法，将一个转换的结果提供给下一个转换，然后最终输出到系统输出。这避免了在转换之间对字符串、文件等进行中间序列化的需要。
I found this: #3. Chaining Transformations that shows two ways to use the TransformerFactory to chain transformations, having the results of one transform feed the next transform and then finally output to system out. This avoids the need for an intermediate serialization to String, file, etc. between transforms.
相关问题 Efficient XSLT pipeline, with params, in Java 澄清了正确的问题传递给此类变压器链的参数。
它还暗示了没有第三个变压器的稍微较短的解决方案：
Related question Efficient XSLT pipeline, with params, in Java clarified on correct parameters passing to such transformer chain.
And it also gave a hint on slightly shorter solution without third transformer:
最好的选择是坚持使用 DOM，因为 XSLT 处理器无论如何都必须构建一棵树 - 流式处理只是非常有限的转换类别的一个选项，而且很少有处理器能够自动找出并切换仅流式传输的实现；否则他们只是读取输入并构建树。
Your best bet is to stick to DOM as you're doing, because an XSLT processor would have to build a tree anyway - streaming is only an option for very limited category of transforms, and few if any processors can figure it out automatically and switch to a streaming-only implementation; otherwise they just read the input and build the tree.