take serveral steps to convert to use Response Writer from IDE or other implementation...
step by step converting ... (Using the same code base for 1.5 HEAD, remove dependencies and gradually refactoring existing code base)
#1. Separate Library dependencies:
icefaces-comps.jar file with tld (default component library).
not dependent on icefaces.jar to init.
survive with Faces Servlet, other ViewHandler (or delegate ViewHandler)
complete separate between API and Impl
#2. Naming Packaging completely separated (renderer/compponent)
renderer stays in one package
changes renderer class name in faces-config.xml (override or delegate if possible)
#3. core ICEfaces eats DOMException now ...( no tracking of problem)
DOM manipulate
#4. Log difference (IDE JDK logging only)
#5. avoid class casting (Reflection)
#6. no changes in Renderer over time
less code with designt time once refactoring complete... (step by step)
design time, time consuming to debugging. needs more stable code base. (visual element output only)
#7. No way to automated testing, so alternatively to use Faces Servlet and standard API only.
hopefully design time support container could be inited and used to test Renderer
#8. strict environment rules are not necessary for Run time (work around in most occasions)
many work around in run time.
#9. Once existing Renderer refactor to use Response Writer only.
delegate rendering possible at that stage.
take serveral steps to convert to use Response Writer from IDE or other implementation...
step by step converting ... (Using the same code base for 1.5 HEAD, remove dependencies and gradually refactoring existing code base)
#1. Separate Library dependencies:
icefaces-comps.jar file with tld (default component library).
not dependent on icefaces.jar to init.
survive with Faces Servlet, other ViewHandler (or delegate ViewHandler)
complete separate between API and Impl
#2. Naming Packaging completely separated (renderer/compponent)
renderer stays in one package
changes renderer class name in faces-config.xml (override or delegate if possible)
#3. core ICEfaces eats DOMException now ...( no tracking of problem)
DOM manipulate
#4. Log difference (IDE JDK logging only)
#5. avoid class casting (Reflection)
#6. no changes in Renderer over time
less code with designt time once refactoring complete... (step by step)
design time, time consuming to debugging. needs more stable code base. (visual element output only)
#7. No way to automated testing, so alternatively to use Faces Servlet and standard API only.
hopefully design time support container could be inited and used to test Renderer
#8. strict environment rules are not necessary for Run time (work around in most occasions)
many work around in run time.
#9. Once existing Renderer refactor to use Response Writer only.
delegate rendering possible at that stage.