Sorry for top posting, the handy client makes it hard to make it right. What you have done so far is great I think. But there is a third way of configuring a converter. This is configuring a converter with its own tag, like dateTimeConverter. This allows you to configure this very instance of the converter.
I don't know how it works exactly from top of my head. Probably it is very easy. As a first step our converter wrapper should save the state of the spring converter (if it is a StateHolder) too. Mario -----Original Message----- From: simon <[EMAIL PROTECTED]> Date: Sunday, Feb 17, 2008 9:08 am Subject: Re: [orchestra] conversation-scoped converters To: Reply- "MyFaces Development" <dev@myfaces.apache.org>To: MyFaces Development <dev@myfaces.apache.org> >On Sun, 2008-02-17 at 08:16 +0100, Mario Ivankovits wrote: > > >> If we find a way how these could work I wouldn't mind if we get rid of the > >> current solution. > > > >Your wish is my command. > > When thinking about it, this one wasn't possible with my solution either. So, > probably lets not put this as high priority on the todo list. > >Sorry Mario, I don't understand what you mean here. > >I thought your earlier email said that you still wanted to be able to >configure a Converter on a component by using a nested tag (instead of just >using the converter attribute). So yesterday I added a new tag to do this: > <orchestra:converter beanName="..."/> >It is already tested and added to svn. > >Is that sufficient, or do you still really want to be able to use the standard >f:converter tag to pull in converters from the spring >configuration? > >Regards, >Simon > >
