Thomas Andraschko
Thomas Andraschko
Yeah +1 Can you make a issue for the managed=true?
i think in case of both implementaionts, we just switch the default way. both have a SPI for it.
+1 this would be a very very nice addition The current approach via a custom ApplicationWrapper is not the nicest one as it puts the value in the stateHelper which...
1) would be the easiest one as StateHelperUICompoent should be a 1:1 ref, where we already have the component class
If we can align on a config format, i can easily Prototype it in MyFaces
thats a good question i think actually it belongs more to taglib.xml but thats something "closed", not build for inheritance we already have inheritance and ordering for faces-config, so it...
it even has property and attribute, i will go with attribute for now
there is only one problem: what about data conversion? only support primitives for now?
dont think so
@arjantijms @BalusC how is the flow in general in MF: - it parses all faces-config - it merges the config while consider the order - it holds the parsed faces-config...