Hi Martin
Yes, to solve the problem with t:inputCalendar and t:inputDate it was clear
an interface like that was necessary but it is tied to java.util.Date in
this case:
/**
* Provide a bridge between the java.util.Date instance used by a component
* that receive date/time values and the "business" value used to represent
* the value.
*/
public interface DateBusinessConverter
{
/**
* Convert the java.util.Date instance calculated from submittedValue,
* so the resulting object will be used later as the converted value
* and validation.
*/
public Object getBusinessValue(FacesContext context,
UIComponent component,
java.util.Date value);
/**
* Used to retrieve the value stored in the business bean and convert
* it in a representation that the component (t:inputCalendar and
* t:inputDate for example)using this class can manipulate.
*/
public java.util.Date getDateValue(FacesContext context,
UIComponent component,
Object value);
}
This two components requires a date/time interface, and in this case the
choice was java.util.Date, to keep things simple, and to indicate that
internally, t:inputCalendar and t:inputDate only "understands"
java.util.Date for rendering.
best regards,
Leonardo
2010/9/8 Martin Marinschek <mmarinsc...@apache.org>
> > I discussed this with the EG (and also Ed privately),
> > and there wasn't much interest for adding this.
>
> P.S.: it might however be useful to have this in the MyFaces
> implementation somehow.
>
> @Leonardo: did you actually provide a business-converter interface -
> we discussed about this?
>
> best regards,
>
> Martin
>
> > --
> >
> > http://www.irian.at
> >
> > Your JSF powerhouse -
> > JSF Consulting, Development and
> > Courses in English and German
> >
> > Professional Support for Apache MyFaces
> >
>
>
> --
>
> http://www.irian.at
>
> Your JSF powerhouse -
> JSF Consulting, Development and
> Courses in English and German
>
> Professional Support for Apache MyFaces
>
