Functional specifications
The user can see the FreeBusyTime of other persons. He only has to know their FreeBusyURL. The URLs that are added will be
stored in the database.
- FreeBusyTime must be retrieved over WebDav with help of the FreeBusyURL and read into the database
- The FreeBusyURL and the contactname are stored in the database
Technical interpretation
- Domain objects and Hibernate mapping
- Dao
- Extend the DaoFactory with FreeBusyDaoWebDavHibernateBufferedImpl
- FreeBusyDao
- FreeBusyDaoWebDavHibernateBufferedImpl
- Manager
- Wicket
- FreeBusyContactsPanel
- To be placed on the BasePage
- AddEditFreeBusyContactForm
- FreeBusyView
- Component placed on the EventViewPanels that shows the FreeBusyTime of the contact (Non Ajax)
Budget/Hours
| task |
hours |
todo |
| FreeBusy + Mapping |
3 |
3 |
| Extend the DaoFactory |
1 |
1 |
| FreeBusyDao |
1 |
1 |
| FreeBusyDaoWebDavHibernateBufferedImpl |
4 |
4 |
| FreeBusyManager |
2 |
2 |
| FreeBusyContactsPanel |
4 |
4 |
| AddEditFreeBusyContactForm |
4 |
4 |
| FreeBusyView |
5 |
5 |
| Total |
24 |
24 |
Discussion
FreeBusySpecification
Formal Definition: A "VFREEBUSY" calendar component is defined by the
following notation:
freebusyc = "BEGIN" ":" "VFREEBUSY" CRLF
fbprop
"END" ":" "VFREEBUSY" CRLF
fbprop = *(
; the following are optional,
; but MUST NOT occur more than once
contact / dtstart / dtend / duration / dtstamp /
organizer / uid / url /
; the following are optional,
; and MAY occur more than once
attendee / comment / freebusy / rstatus / x-prop
)
--
JochemKolthof - 20 Sep 2006