| | | |
| Well... package it into a deployable .war file, de | | Well... package it into a deployable .war file, de |
| ploy it .. and if you are using tomcat you probabl | | ploy it .. and if you are using tomcat you probabl |
| y want to restart it (since iirc it has known memo | | y want to restart it (since iirc it has known memo |
| ry leaks) | | ry leaks) |
| | | |
| ** How extend able is the result ? (e.g. Imagine i | | ** How extend able is the result ? (e.g. Imagine i |
| would like to add a workflow where changes get on | | would like to add a workflow where changes get on |
| line once an administrator approves them) ** | | line once an administrator approves them) ** |
| | | |
| t | reasonable.. not perfect though.
| t | reasonable.. not perfect though. (it is sometimes |
| | | hard to add new features without breaking existing |
| | | code because of weak references and very context |
| | | sensitive actions.)
|
| | | |
| ** How much duplication was necessary ? (e.g. need | | ** How much duplication was necessary ? (e.g. need |
| to describe the models in the database as well as | | to describe the models in the database as well as |
| in code or xml ? / need to describe attributes of | | in code or xml ? / need to describe attributes of |
| models in models and views ?, etc.) ** | | models in models and views ?, etc.) ** |
| | | |
| Not too much - although the object types (models) | | Not too much - although the object types (models) |
| were configured with attributes and their type, wh | | were configured with attributes and their type, wh |
| ich has to be repeated for the edit form (and the | | ich has to be repeated for the edit form (and the |
| list). | | list). |
| | | |
