See the comment in tobago ViewHandlerImpl line 71
// ensure tobago UIViewRoot RI don't create the component via application
[EMAIL PROTECTED] schrieb:
What bug specifically?
Hello
Werner Punz schrieb:
Well I think it is quite ok, just to concentrate on the
code sharing and later try to integrate this stuff, this seems like a
viable way to me.
:-)
The main problem I see with all this is more JSF related and less
myfaces related. We have this critical conflict point view handlers
which cannot be combined in a decent way due to limitations
of the pattern and the handling of only being able to define one
per web application.
Now we have this situation that many libraries and component sets
use those to bypass some limitations of the JSF APIs
(Shale uses it for a simpler lifecycle handling and events
related to the requests to my knowledge, Tiles and Facelets use
them to kickstart their own rendering part for layouting, Tobago (I
really have to look at the code) probably for similar reasons)
None of them combinable out of the box.
The main reason for the own ViewHandler in Tobago is a bug in RI.
The rest of the stuff can moved to other places :-)
Have a nice and happy new Year
Bernd
--
Dipl.-Ing. Bernd Bohmann - Atanion GmbH - Software Development
Bismarckstr. 13, 26122 Oldenburg, http://www.atanion.com
phone: +49 441 4082312, mobile: +49 173 8839471, fax: +49 441 4082333
--
Dipl.-Ing. Bernd Bohmann - Atanion GmbH - Software Development
Bismarckstr. 13, 26122 Oldenburg, http://www.atanion.com
phone: +49 441 4082312, mobile: +49 173 8839471, fax: +49 441 4082333
