You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/main/xar-resources/data/urlrewrite/urlrewrite.xml
+1-5Lines changed: 1 addition & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -422,11 +422,7 @@
422
422
throughout the entire pipeline, we need to clear the
423
423
<literal>xslt.input</literal>
424
424
with an explicit call to clear-attribute.</para>
425
-
<para>The benefit does to exchanging data through request attributes is that we save one serialization step.
426
-
<code>XQueryServlet</code>
427
-
directly passes the node tree of its output as a valid XQuery value, so
428
-
<code>XSLTServlet</code>
429
-
does not need to parse it again.</para>
425
+
<para>The benefit of exchanging data through request attributes is that we save one serialization step: <code>XQueryServlet</code> directly passes the node tree of its output as a valid XQuery value, so <code>XSLTServlet</code> does not need to parse it again.</para>
430
426
<para>The advantages become more obvious if you have two or more XQueries which need to exchange information: XQuery 1 can use the XQuery extension function
431
427
<code>request:set-attribute()</code>
432
428
to save an arbitrary XQuery sequence to an attribute. XQuery 2 then calls
0 commit comments