no design time

After a restless night I've decided not to do the design time thing. Two reasons:
1. Every application class would need to support an additional constructor.
2. There is a one-to-many relationship between element types and element instances.

So instead we're going with configuration classes which will embrace [most of] the parameters of an element type definition. This can be implemented incrementally as well, which is important at this point.

design time

Today I was working on configuration. Configuration is never easy, but in the Element Model it seemed extra difficult because it is spread across too many classes. Finally decided to make use of the JavaBean design time idea. Application logic should support its configuration.

So obvious. Not even original. But I think it will help a lot.

element model release 10.0.0, goals for 11

New validate utility checks the integrity of a database.
Additional convenience methods added to AbstractApplication.
Javadoc rewritten for the elementmodel package.

This completes basic persistence. For release 11 there are 3 objectives:
- Employ weak references (in handles) and a cache to reduce the memory footprint.
- Use variable-length blocks in place of fixed-length blocks.
- Extend browse to the point where it operates as a simple wiki.

A light-weight EJB replacement

The Element model has come a long way and release 9-11 is out.

• Peer Proxies are complete.
• Basic persistence is done.
• Dump/Load commands can be used to migrate data from one release to the next.
• Naji has started work on integration with Jetty.

Download