Hi Kito.
There is a relative simple way to ensure all EditableValueHoolders have a
Converter and also wrap explicitly added converters.
Wrap Application and override createComponent() and createConverter()
methods.
In createComponent() methods you can check the component type to find out
if you should add your special converter already.
In createConverter() method you can get the wanted converter and wrap it
with your special converter.
One point to consider is where Converter-for-type is used - I'm not sure
but guess also that should result in callin Application.creatConverter() -
where you can wrap the requested Converter.
Regards
Hanspeter Duennenberger
2014-12-11 16:56 GMT+01:00 Kito Mann <kito.mann_at_virtua.com>:
> Hello everyone,
>
> On my current project, I have a situation where I'd like to process input
> from _every_ JSF input component on the page. There are a few different
> ways I can do this, but what I really want is to be able to apply a global
> converter, much like global validators. However, in order to do this, we
> would have to have some sort of "converter chaining" mechanism so that
> existing converters won't get clobbered. I could implement this by walking
> through all of the EditableValueHolders in the view and adding a special
> converter that can wrap an existing converter if necessary. However, this
> is something that would work well at the spec level. Thoughts?
> ___
>
> Kito D. Mann | @kito99 | Author, JSF in Action
> Virtua, Inc. | http://www.virtua.com | JSF/Java EE training and consulting
> http://www.JSFCentral.com | @jsfcentral
> +1 203-998-0403
>
> * Listen to the Enterprise Java Newscast: *http://
> <http://blogs.jsfcentral.com/JSFNewscast/>enterprisejavanews.com
> <http://ww.enterprisejavanews.com>*
> * JSFCentral Interviews Podcast:
> http://www.jsfcentral.com/resources/jsfcentralpodcasts/
> * Sign up for the JSFCentral Newsletter:
> http://oi.vresp.com/?fid=ac048d0e17
>