See if we need to add anything to environment setup guide, and if it is straightforward.

Eg. Data Source

Currently, when adding or delete new row will write to the db permanently without calling save-all explicitly, consider fixing.

The project field is numerical; the WP field is a string. The combination of project and WP must be unique within a timesheet.

So we don't have to manually create database tables.

@jhou2

http://javaknowledge.info/?p=204

<h:commandButton value="reset" action="reset" immediate="true" />

When using conversation scoped in conjunction with h:link tags, the outcome drops the cid. This result in lost conversation.

Proposed solution: use "<f:viewParam /> with <h:link />"

Add new row, delete row, editable functionality... all in one page!

Currently have this, but it doesn't work yet:

<f:metadata>
    <f:viewParam name="week" value="#{TimeTable.currentWeek}"
        required="true" />
</f:metadata>

<h:link outcome="#{TimeTable.resetTotalHours()}" value="Next Week">
    <f:param name="week" value="#{TimeTable.currentWeek} + 1}" />
</h:link>

<h:link outcome="#{TimeTable.resetTotalHours()}" value="Previous Week">
    <f:param name="week" value="#{TimeTable.currentWeek} - 1}" />
</h:link>

It will save a lot of time if IDs are auto generated. Currently in testing.

Hibernate? JPA? JDBC?

Version change: 0.2-SNAPSHOT

The Total column and row are calculated based on the data in the week-day columns.

Extend functionality of manager classes, move some functionality away from front-end TimeTable/UserSession.

Eg. Login/authentication, selecting correct time sheets.

Valid values are in the range [0.0 .. 24.0]

Print error message in appropriate area near the top.

To keep track what to persist back to the database.