Skip to end of metadata
Go to start of metadata
You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 2
Next »
Technologies
- StAX (XML Streaming APIs)
Pipeline Ordering Overview
- User Layout Store
- Attribute Incorporation Filter (Structure)
- XSLT (Structure)
- uses XSLT Parameter Provider to help setup the Transformer
- outputs XMLEventReader
- Portlet Rendering Initiator
- Uses Portlet Renderer API to initiate async portlet rendering
- outputs XMLEventReader
- Attribute Incorporation Filter (Theme)
- XSLT (Theme)
- uses XSLT Parameter Provider to help setup the Transformer
- outputs XMLEventReader
- Serializer
- Uses XMLOutputFactory to convert from XMLEventReader to Character data
- outputs CharacterEventReader
- Portlet Incorporation Filter
- Portlet Renderer API to retrieve portlet rendering results
- outputs CharacterEventReader
- Output Writer
- Writes to response Writer
Pipeline Component API
interface PipelineComponent {
CompositeCacheKey getCacheKey(HttpServletRequest, HttpServletResponse);
}
interface StAXPipelineComponent {
XMLEventReader getEventReader(HttpServletRequest, HttpServletResponse);
}
interface CharacterPipelineComponent {
CharacterEventReader getEventReader(HttpServletRequest, HttpServletResponse);
}
Pipeline Caching Flow
- Caching will be applied via additional filters in the chain, either a StAXCachingFilter or a CharacterCachingFilter.
- The filter will use the following steps when getEventReader is called
key = parentComponent.getCacheKey(req, res)
eventRender = cache.get(key)
- If
eventReader
is not null return it
- If
eventReader
is null call parentComponent.getEventReader(req, res)
- The caches that will be used will be chaining caches meaning they will be wired together in parallel to the rendering pipeline allowing parent expiration state checking.