Recent changes to feature-requests

model file polling

Meinte Boersma — Sat, 22 Aug 2009 08:36:47 -0000

Once we start to implement real modularization, we cannot rely on polling the model file for each request -which is not extremely performant anyway.
So, implement/hook up a poller which polls a model directory and implement a listener strategy so the model loader can be signalled in case of a re-load. This is also appropriate to implement, e.g., model updates from source control.

auto-reload feature

Meinte Boersma — Sat, 22 Aug 2009 08:33:48 -0000

Create a "developer mode" which is configured in WebApplicationServer, off by default.

Switching it on makes every response served execute an Ajax request with a specific servlet which is signalled when the model is updated (through saving of the file). The response to the Ajax request is only sent when the signal comes true and the model is updated (re-loaded) and consists of a redirect URL. This "reloads" the current page or some other appropriate one in case the page doesn't exist in the model anymore or if it is impossible to serve the same page for some other reason.

injection/inclusion of basic types

Meinte Boersma — Sun, 09 Aug 2009 10:17:09 -0000

To be able to capture input coming from submitted HTML forms and to drive a(ny) data model, injection/inclusion of basic types (such as int, string, date, &c., but also parametrized types such as string(37)) is required. This needs both an addition to the (Example-)DSL as well as infrastructure to bring in a custom type mapper (probably referenced through the DSL instance) which basically serves the same purpose as the custom PropertyEditor-s of Spring MVC.