You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@myfaces.apache.org by Zied Hamdi <ja...@gmail.com> on 2007/10/05 00:28:01 UTC
Re: [tobago] separating the date and time components
Hello,
I've just wrote a util class that could help in this task.
Regards,
Zied
2007/9/21, Zied Hamdi <ja...@gmail.com>:
>
>
> Sorry forgot to mention [tobago]
> ---------- Forwarded message ----------
> From: Zied Hamdi <javahamdi@gmail.com >
> Date: 21 sept. 2007 15:36
> Subject: separating the date and time components
> To: MyFaces <us...@myfaces.apache.org>
>
> Hi,
>
> I have attempted to assemble a tx:date with a tc:time follow the same
> field (expecting each componenent will fill its data in the part it is
> concerned with)
>
> < tx:date
>
> id ="workStartDate"
>
> value ="#{intervention.workStart}"
>
> label ="#{i18n.workStartDate}" >
>
> < f:convertDateTime pattern = "dd.MM.yyyy" />
>
> </ tx:date>
>
>
>
> < tc:time
>
> id ="workStart"
>
> value = "#{intervention.workStart}" />
>
>
>
>
>
> The result is that tc:time seams to create a new instance with a date set
> to 0 (01.01.1970) instead of using GregorianCalendar.set() on the existing
> one.
>
> Do I have to cretae a minor issue on this behavior?
>
> --
> Zied Hamdi
> zatreex.sourceforge.net
>
>
>
> --
> Zied Hamdi
> zatreex.sourceforge.net
>
>
--
Zied Hamdi
zatreex.sourceforge.net
Re: [tobago] separating the date and time components
Posted by Zied Hamdi <ja...@gmail.com>.
Hello,
Sorry for spamming, I found a bug in the class I sent you this morning: so
just to see how tedious it is to point to the same Date with separate
tc:date and tc:time tags, if every tag was just updating the fields he
shows, we could point to the same field without ths linking cables:
*public* Date getWorkStartTime() {
*return* getCurrentWorkTask().getWorkStart();
}
*public* Date getWorkStartDate() {
Date start = getCurrentWorkTask().getWorkStart();
*if*( start == *null* || CalendarUtil.*equalsDate*( start,
1970, 0, 1 ) )
*return* *null*;
*return* start;
}
*public* *void* setWorkStartDate(Date workStart) {
getCurrentWorkTask().setWorkStart( CalendarUtil.*setDate*(
workStart, getWorkStart() ) );
}
*public* String toString() {
*return* getCurrentWorkTask().toString();
}
To remind what I would like to have here's what I expected from these
components:
<tx:date
id ="workStartDate"
value ="#{intervention.*workStart*}"
label ="#{i18n.workStartDate}" >
< f:convertDateTime pattern ="dd.MM.yyyy" />
</ tx:date>
< tc:time
id ="workStart"
value= "#{intervention.*workStart*}" />
in that case all the code above is simplified in a pojo manner.
Regards,
Zied
2007/10/5, Zied Hamdi <ja...@gmail.com>:
>
> Hello again,
>
> Sorry I forgot we're in multitasking.
>
> Here's a better version.
>
> Regards,
> Zied
>
>
> 2007/10/5, Zied Hamdi <ja...@gmail.com>:
> >
> > Hello,
> >
> > I've just wrote a util class that could help in this task.
> >
> > Regards,
> > Zied
> >
> >
> > 2007/9/21, Zied Hamdi <ja...@gmail.com>:
> > >
> > >
> > > Sorry forgot to mention [tobago]
> > > ---------- Forwarded message ----------
> > > From: Zied Hamdi < javahamdi@gmail.com >
> > > Date: 21 sept. 2007 15:36
> > > Subject: separating the date and time components
> > > To: MyFaces < users@myfaces.apache.org>
> > >
> > > Hi,
> > >
> > > I have attempted to assemble a tx:date with a tc:time follow the same
> > > field (expecting each componenent will fill its data in the part it is
> > > concerned with)
> > >
> > > < tx:date
> > >
> > > id ="workStartDate"
> > >
> > > value ="#{intervention.workStart}"
> > >
> > > label ="#{i18n.workStartDate}" >
> > >
> > > < f:convertDateTime pattern = "dd.MM.yyyy" />
> > >
> > > </ tx:date>
> > >
> > >
> > >
> > > < tc:time
> > >
> > > id ="workStart"
> > >
> > > value = "#{intervention.workStart}" />
> > >
> > >
> > >
> > >
> > >
> > > The result is that tc:time seams to create a new instance with a date
> > > set to 0 (01.01.1970) instead of using GregorianCalendar.set() on the
> > > existing one.
> > >
> > > Do I have to cretae a minor issue on this behavior?
> > >
> > > --
> > > Zied Hamdi
> > > zatreex.sourceforge.net
> > >
> > >
> > >
> > > --
> > > Zied Hamdi
> > > zatreex.sourceforge.net
> > >
> > >
> >
> >
> > --
> > Zied Hamdi
> > zatreex.sourceforge.net
> >
> >
>
>
> --
> Zied Hamdi
> zatreex.sourceforge.net
>
>
--
Zied Hamdi
zatreex.sourceforge.net
Re: [tobago] separating the date and time components
Posted by Zied Hamdi <ja...@gmail.com>.
Hello again,
Sorry I forgot we're in multitasking.
Here's a better version.
Regards,
Zied
2007/10/5, Zied Hamdi <ja...@gmail.com>:
>
> Hello,
>
> I've just wrote a util class that could help in this task.
>
> Regards,
> Zied
>
>
> 2007/9/21, Zied Hamdi <ja...@gmail.com>:
> >
> >
> > Sorry forgot to mention [tobago]
> > ---------- Forwarded message ----------
> > From: Zied Hamdi < javahamdi@gmail.com >
> > Date: 21 sept. 2007 15:36
> > Subject: separating the date and time components
> > To: MyFaces < users@myfaces.apache.org>
> >
> > Hi,
> >
> > I have attempted to assemble a tx:date with a tc:time follow the same
> > field (expecting each componenent will fill its data in the part it is
> > concerned with)
> >
> > < tx:date
> >
> > id ="workStartDate"
> >
> > value ="#{intervention.workStart}"
> >
> > label ="#{i18n.workStartDate}" >
> >
> > < f:convertDateTime pattern = "dd.MM.yyyy" />
> >
> > </ tx:date>
> >
> >
> >
> > < tc:time
> >
> > id ="workStart"
> >
> > value = "#{intervention.workStart}" />
> >
> >
> >
> >
> >
> > The result is that tc:time seams to create a new instance with a date
> > set to 0 (01.01.1970) instead of using GregorianCalendar.set() on the
> > existing one.
> >
> > Do I have to cretae a minor issue on this behavior?
> >
> > --
> > Zied Hamdi
> > zatreex.sourceforge.net
> >
> >
> >
> > --
> > Zied Hamdi
> > zatreex.sourceforge.net
> >
> >
>
>
> --
> Zied Hamdi
> zatreex.sourceforge.net
>
>
--
Zied Hamdi
zatreex.sourceforge.net