Details
Description
This is the overall task for reducing differences between our Facelets derived
implementation versus the stock Facelets implementation.
We've had two main older approaches:
1. Override TextUnit[Factory], and add support in CompilationManager, for
hierarchial creation of separate TextUnit objects, which could either create
text nodes or UIXhtmlComponents.
2. Make the overridden TextUnit only create text nodes, and use
TagCompilationUnit[Factory] to create the UIXhtmlComponents.
The current targetted approach (stock-er) is to:
- Make TextUnit and CompilationManager only do stock behaviour
- Use the stock TagDecorator and TagLibrary interfaces, along with a helper
UIXhtmlComponentHandler helper class, to replace our proprietary
TagCompilationUnit[Factory] approach
- Make any specific functionality that we need in Facelets itself to work off of
boolean options, which we will submit as patches, so that if they are accepted,
we will work with stock Facelets.
implementation versus the stock Facelets implementation.
We've had two main older approaches:
1. Override TextUnit[Factory], and add support in CompilationManager, for
hierarchial creation of separate TextUnit objects, which could either create
text nodes or UIXhtmlComponents.
2. Make the overridden TextUnit only create text nodes, and use
TagCompilationUnit[Factory] to create the UIXhtmlComponents.
The current targetted approach (stock-er) is to:
- Make TextUnit and CompilationManager only do stock behaviour
- Use the stock TagDecorator and TagLibrary interfaces, along with a helper
UIXhtmlComponentHandler helper class, to replace our proprietary
TagCompilationUnit[Factory] approach
- Make any specific functionality that we need in Facelets itself to work off of
boolean options, which we will submit as patches, so that if they are accepted,
we will work with stock Facelets.
The following efforts have been made so far:
1. Use TagDecorator instead of TagCompilationUnit
2. Don't override TextUnit anymore
3. LiteralTextInstruction whitespace issue
https://facelets.dev.java.net/issues/show_bug.cgi?id=187
This was found when using the ICE Facelets 1.1.11 code,
and has to be looked at again with 1.1.12, since Jacob
could not reproduce it under 1.1.12.
4. Evaluating Facelets 1.2 versus 1.1.12, opting to go with 1.1.12.
5. Separately IRAPtor'ed issues: 1113, 1116