Wednesday, December 10, 2014
I recently acquired a Kindle Fire tablet. It's been less than a week that I've had it, but I'm already annoyed by the amount of vendor tie-in that comes with the device. I'll be turning this tablet computer into the kind of device that I like over the next few weeks. I've started by looking over a few videos that advise on "rooting" or "jailbreaking" a Kindle Fire. For now, I'm distrustful of these and I'll be sticking to the use of official Android developer tools and a few others that seem useful.
Posted by Mark W. at 8:22 PM
Thursday, December 4, 2014
Lately, I was trying to resolve an issue with an xsl:import statement looking for a document in from the Tomcat servers base directory (/var/lib/tomcat7). Naturally, you have to tell the transformer how to resolve the the URI -- how would it know otherise?
The API provides a way for URIs referenced from within the stylesheet instructions or within the transformation to be resolved by the calling application. This can be done by creating a class that implements the URIResolver interface, with its one method, URIResolver.resolve(java.lang.String, java.lang.String), and use this class to set the URI resolution for the transformation instructions or transformation with TransformerFactory.setURIResolver(javax.xml.transform.URIResolver) or Transformer.setURIResolver(javax.xml.transform.URIResolver). The URIResolver.resolve method takes two String arguments, the URI found in the stylesheet instructions or built as part of the transformation process, and the base URI against which the first argument will be made absolute if the absolute URI is required. The returned Source object must be usable by the transformer, as specified in its implemented features.
Posted by Mark W. at 9:35 AM