book

Java and XSLT

by Eric M. Burke

September 2001

Intermediate to advanced

528 pages

13h 46m

English

O'Reilly Media, Inc.

Read now

Unlock full access

Audience
Java, XSLT, and the WebWhat’s Wrong with HTML?Keeping Data and Presentation SeparateThe XSLT Solution
SGML, XML, and Markup LanguagesXML SyntaxValidationJava and XMLSAXDOMJDOMJDOM and DOM interoperability
Web Development ChallengesWeb ApplicationsNonbrowser ClientsSOAPWireless

Java XSLT Processor ChoicesXTLotusXSLSAXONJAXP
XSLT IntroductionAn XSLT ExampleTrying It Out
XML Tree Data StructureRecursive Processing with TemplatesBuilt-in Template RulesA Skeleton Stylesheet
How XSLT Uses XPathAxesLocation StepsLocation PathsAbbreviated Syntax
Looping with <xsl:for-each>SortingLooping and Sorting Examples
<xsl:attribute>Attribute Value Templates<xsl:attribute-set>
Conditional Processing<xsl:if><xsl:choose>, <xsl:when>, and <xsl:otherwise>
<xsl:variable>Defining variablesUsing variables<xsl:call-template> and Named Templates<xsl:param>and <xsl:with-param>Incrementing VariablesTemplate Modes<xsl:template> Syntax Summary
<xsl:include><xsl:import>
Number FormattingText Formatting
An Example XML FileThe Identity TransformationTransforming Elements and AttributesThe Result File
Ant BasicsStylesheet FunctionalityThe Complete ExampleSpecifying XHTML outputCreating the dependency graphCleaning up dependency lists
Traditional ApproachesCGIServlets as CGI ReplacementsJSPTemplate EnginesThe Hybrid Approach
Web FrameworksModel-View-ControllerXSLT ImplementationDevelopment and Maintenance Benefits of XSLT
Tradeoffs
A Simple ExampleThe DesignXalan 1 ImplementationSAXON ImplementationSAXON, Xalan, or TrAX?
JAXP 1.1 ImplementationXSLT Plugability LayerThe Transformer ClassJAXP XSLT Design
System Identifiers, Files, and URLsJAXP I/O DesignJAXP Stream I/OJAXP DOM I/OJAXP SAX I/OThe approachDetailed CSV to SAX designWriting the custom parserUsing the parserConclusionFeeding JDOM Output into JAXPJDOM to SAX approachJDOM to DOM approachJDOM to text approach
Templates APIA Stylesheet Cache
Servlet SyntaxSplash Screen Servlet Example
WAR FilesDeployment DescriptorDeploying SplashScreenServlet to TomcatServlet API Highlights
DesignXML and StylesheetsSource CodeDeploymentHow to Compile, Deploy, and RunLocating Stylesheets with Initialization Parameters
Integration with the Stylesheet Cache
Servlet Threading ModelThread Safety TipsTip 1: Local variables are thread-safeTip 2: Immutable objects are thread-safeTip 3: Provide a single point of entryTip 4: Understand the Templates interface
Overall ProcessRequirementsScreen Flow
XHTML PrototypesXML SamplesXSLT Stylesheets
Domain ClassesData Adapter LayerJDOM XML Production
DeploymentIdeas for Enhancements
XSLT Page Layout Templates
Servlet Session-Tracking APISession Tracking with Java and XSLT
Filter OverviewXSLT Transformation FilterClosing Thoughts on Filters
XSLT Stylesheet DesignEncodingsCreating the XML and XSLTPutting It All TogetherXML dataXSLT stylesheetsWeb page and servletI18n Troubleshooting Checklist
Development EnvironmentCLASSPATH IssuesJAR hell?Sealing violationsOther exceptions and errorsJava optional packagesJava IDEsAntInstalling AntA typical Ant build fileTransforming using Ant’s style taskTomcatConfiguring Tomcat 3.2.xConfiguring Tomcat 4.0.x
JUnitAn example unit testRunning the testJAXP 1.1 Error ListenersA Custom XSLT Transformer GUIScreen shotsSource code
Stress Testing with JMeterMore Detailed MeasurementsCommercial optionsJVMPIUnit testingUsing XSLT Processors EffectivelyStylesheet cachingResult cachingWriting Effective XSLTInteracting with EJBSending XML from EJBsSending objects from EJBs
Wireless TechnologiesWhy Not HTML?Problems with HTMLLimitations of current devices
A WML ExampleWMLScript and WBMPServlets and WMLIdentifying the clientSetting the content typeMovie Theater ExampleStoryboardXML dataWML prototypes and screen shotsServlet implementationXSLT stylesheets

Content preview from Java and XSLT

The Future of Wireless

Looking toward the future, two things are inevitable. First, device capabilities will improve. Color displays, increased screen resolution, increased memory, and faster processors can be expected. Second, bandwidth will improve. Migration to Third Generation (3G) wireless networks is already underway in many countries, offering bandwidth anywhere from 128Kbps to 2Mbps.

Partly because of these two advancements, the WAP Forum and NTT DoCoMo have agreed to migrate towards XHTML Basic for future devices. XHTML Basic uses a subset of XHTML. Therefore, it is far more familiar to web developers than WML. Existing web browsers can already display XHTML Basic, which is not the case with WML or cHTML. XHTML Basic also utilizes CSS to define colors, fonts, and other presentation styles. Newer, more capable devices should be able to take advantage of far more style instructions than currently available devices.

The migration to XHTML Basic will not eliminate the need for technologies such as XSLT, however. Even though normal web browsers can display the same XHTML Basic web pages that wireless devices use, devices such as cellular phones and pagers will always have tiny displays. Most web applications will still need to maintain a simplified interface for these devices to minimize the amount of scrolling the user has to do. Therefore, XSLT will continue to be important.