You could also replace <br/> with 
 and add a linefeed-treatment=”preserve” attribute to your <fo:block>. Something like: <fo:block linefeed-treatment=”preserve”>This is an example Description.
List item 1
List item 2
List item 3
List item 4</fo:block> Edit Some users may need to use \n instead of 
 depending on how they are creating the XML. See Retain the 
 during … Read more
The value of the match attribute of the <xsl:template> instruction must be a match pattern. Match patterns form a subset of the set of all possible XPath expressions. The first, natural, limitation is that a match pattern must select a set of nodes. There are also other limitations. In particular, reverse axes are not allowed … Read more
You can use this XPath: //a[b/c/@d = ‘text1’ and b/c/@d = ‘text4’]/b/c[@d = ‘text5’]/@e It will select e=”text15″ and e=”text35″ of 1st and 3rd a/b XSLT: <xsl:template match=”//a[b/c/@d = ‘text1’ and b/c/@d = ‘text4’]/b/c[@d = ‘text5’]”> <xsl:value-of select=”@e”/> </xsl:template>
Try JOLT. It is a JSON to JSON transformation library written in Java. It was created on a project that was transforming lot of JSON from an ElasticSearch “backend” to a frontend api. For the JSON transform you have listed in your problem, the Jolt “shift” spec would be : // Jolt “shift” spec { … Read more
This is a pretty common pattern: <xsl:for-each select=”*”> <xsl:value-of select=”.”/> <xsl:if test=”position() != last()”> <xsl:text>,</xsl:text> </xsl:if> </xsl:for-each>
You can define a template to match on script/command and eliminate the xsl:for-each concat() can be used to shorten the expression and save you from explicitly inserting so many <xsl:text> and <xsl:value-of> elements. The use of an entity reference 
 for the carriage return, rather than relying on preserving the line-break between your <xsl:text> element … Read more
There are multiple ways to do this (in order of lookup precedence): Direct Instantiation Explicitly instantiate the Saxon factory (with a nod to Michael’s comment above): TransformerFactory fact = new net.sf.saxon.TransformerFactoryImpl() This approach means that your code is locked into using Saxon at compile time. This can be seen as an advantage (no risk of … Read more
There are three reasons for getting unwanted whitespace in the result of an XSLT transformation: whitespace that comes from between nodes in the source document whitespace that comes from within nodes in the source document whitespace that comes from the stylesheet I’m going to talk about all three because it can be hard to tell … Read more
Try either of these :: Amazon JSON API – This is a ruby webservice to pass through requests and translate the responses to JSON. Try any of these Javascript functions to convert the XML you already have into JSON : http://goessner.net/download/prj/jsonxml/ http://davidwalsh.name/convert-xml-json http://www.fyneworks.com/jquery/xml-to-json/ http://www.thomasfrank.se/xml_to_json.html I’ve tried thomasfrank myself. Its easy and works well 🙂
<xsl:if test=”$var=”ab” | $var=”bc” | $var=”ca” “> This is wrong — you are using the XPath union operator | on boolean values. Solution: use the XPath or operator: <xsl:if test=”$var=”ab” or $var=”bc” or $var=”ca” “> The above XPath expression (the value of the test attribute) can be optimized, so that only one comparison is made … Read more