| Home >> All >> org >> apache >> cocoon >> components >> [ elementprocessor Javadoc ] |
• org.apache.cocoon.components.elementprocessor: Javadoc index of package org.apache.cocoon.components.elementprocessor.
Package Samples:
• org.apache.cocoon.components.elementprocessor.impl.poi.hssf.elements
• org.apache.cocoon.components.elementprocessor.impl.poi.hssf
• org.apache.cocoon.components.elementprocessor.impl.poi
• org.apache.cocoon.components.elementprocessor.impl
• org.apache.cocoon.components.elementprocessor.types
Classes:
• ElementProcessor: The ElementProcessor interface defines behavior for classes that can handle a particular XML element's content. The life cycle of an ElementProcessor instance is: Creation Initialization via a call to initialize Acquisition of element data via calls to acceptCharacters and acceptWhitespaceCharacters Completion of processing via a call to endProcessing In response to a startElement event, the POIFSSerializer creates an ElementProcessor, delegating the act of creation to an ElementProcessorFactory, and then initializes the ElementProcessor. In response to subsequent characters and ignorableWhitespace ...
• Anchors: Anchors. This particular object is represented in gnumeric's XML as four integers, space separated. Presumably, each represents an anchor for a particular direction -- top, bottom, left, right -- but what the reference is for each anchor is not known, nor is it known which one is top, bottom, left, or right, or even whether that's the correct interpretation of the numbers. This is an area of the gnumeric XML that is not terribly well documented even in their code, and I don't think the features that use anchors are terribly mature yet.
• Offsets: Offsets. This particular object is represented in gnumeric's XML as four doubles, space separated. Presumably, each represents an offset in a particular direction -- top, bottom, left, right -- but what the reference is for each offset is not known, nor is it known which one is top, bottom, left, or right, or even whether that's the correct interpretation of the numbers. This is an area of the gnumeric XML that is not terribly well documented even in their code, and I don't think the features that use offsets are terribly mature yet.
• BaseElementProcessor: The BaseElementProcessor class provides default behavior for classes that can handle a particular XML element's content. It is intended that all ElementProcessors should extend this class. This class is declared Abstract although it has no abstract methods. It can be used 'as is' for a no-op ElementProcessor, and an ElementProcessor that chooses to simply extend this class with no overrides will be a no-op ElementProcessor.
• EPSheet: No-op implementation of ElementProcessor to handle the "Sheet" tag This element contains other elements and has the following boolean attributes: DisplayFormulas HideZero HideGrid HideColHeader HideRowHeader DisplayOutlines OutlineSymbolsBelow OutlineSymbolsRight
• EPSheetNameIndex: No-op implementation of ElementProcessor to handle the "SheetNameIndex" tag This element has no attributes and contains other elements This element is not used in HSSFSerializer 1.0 and probably never will be, as the gnumeric code indicates that it is a kludge
• EPSelections: No-op implementation of ElementProcessor to handle the "Selections" tag This element is a container element with two attributes: CursorCol and CursorRow, which presumable show where the cursor should be. This element is not used in HSSFSerializer 1.0
• EPSheetName: No-op implementation of ElementProcessor to handle the "SheetName" tag This element has no attributes and contains a string This element is not used in HSSFSerializer 1.0 and probably never will be, as the gnumeric code indicates that it is a kludge
• EPSolver: No-op implementation of ElementProcessor to handle the "Solver" tag This element is a container with four atributes (TargetRow, TargetCol, and ProblemType are integers, and Inputs is a String) This element is not used in HSSFSerializer 1.0
• EP_Order: No-op implementation of ElementProcessor to handle the "order" tag This element has no attributes and contains a string describing the print ordering (right then down, or down then right) This element is not used in HSSFSerializer 1.0
• EP_Paper: No-op implementation of ElementProcessor to handle the "paper" tag This element contains no other elements and has no attributes. Its content describes the paper to be used (e.g., A4) This element is not used in HSSFSerializer 1.0
• EP_Orientation: No-op implementation of ElementProcessor to handle the "orientation" tag This element has no attributes and contains a string describing the print orientation (landscape or portrait) This element is not used in HSSFSerializer 1.0
• EPSelection: No-op implementation of ElementProcessor to handle the "Selection" tag This element is a container of other elements and has four attributes that define the boundaries of the region. This element is not used in HSSFSerializer 1.0
• EPUIData: No-op implementation of ElementProcessor to handle the "UIData" tag This element contains no data and has an attribute, SelectedTab, that indicates which sheet is currently selected This element is not used in HSSFSerializer 1.0
• EPWorkbook: ElementProcessor that handles the "Workbook" tag The Workbook element includes one attribute ("gmr"), which basically gives us the Gnumeric major version. At some point we might care about that, but not today.
• EPFont: No-op implementation of ElementProcessor to handle the "Font" tag This element has five attributes and also holds the name of the font as element content. This element is not used in HSSFSerializer 1.0
• EPFooter: No-op implementation of ElementProcessor to handle the "Footer" tag This element has three attributes: Left, Middle, and Top, and no contents. This element is not used in HSSFSerializer 1.0
• EPConstr: No-op implementation of ElementProcessor to handle the "Constr" tag This element contains several attributes and no content or other elements. This element is not used in HSSFSerializer 1.0
• EP_EvenIfOnlyStyles: No-op implementation of ElementProcessor to handle the "even_if_only_styles" tag This element has a single attribute, value, which is boolean. This element is not used in HSSFSerializer 1.0
• EPHeader: No-op implementation of ElementProcessor to handle the "Header" tag This element has three attributes: Left, Middle, and Top, and no contents. This element is not used in HSSFSerializer 1.0
• EPSheetObjectFilled: No-op implementation of ElementProcessor to handle the "SheetObjectFilled" tag This element has a small number of Attributes and no content. This element is not used in HSSFSerializer 1.0
• EPSheetObjectBonobo: No-op implementation of ElementProcessor to handle the "SheetObjectBonobo" tag This element has a small number of Attributes and no content. This element is not used in HSSFSerializer 1.0
• EP_Type: No-op implementation of ElementProcessor to handle the "type" tag This element is not used in HSSFSerializer 1.0 This element has no attributes, but has string content, which is numeric.
• EPStyle: No-op implementation of ElementProcessor to handle the "Style" tag This element is a container of other elements and has several attributes This element is not used in HSSFSerializer 1.0
• HorizontalAlignment: Horizontal alignment is written as an integer, and each bit in the integer specifies a particular boolean attribute. This class deals with all that information in an easily digested form.
| Home | Contact Us | Privacy Policy | Terms of Service |