These are my thoughts on design considerations.
The project is supposed to be a framework for other developers or end-users to use. It will provide a developer API and will also be functional from a JAR/WAR. It deviates from the only approach I have seen (the traditional approach).
I am deviating from that approach by providing the core framework (mud4j-core) and implementing it as if the end application were a multi-tiered enterprise application.
Multiple pluggable front-ends will be provided to the core framework. This will include web, and for telnet (mud4j-web, and mud4j-telnet). They will access the core framework just the same, but I will be implementing this as part of view pattern and using a two-step view most likely to accomplish this.
It should not be designed for any particular container. The design will include normal POJOs with a domain model pattern approach.
Spring for IoC and dependency injection with transactional support and hibernate because I like hibernate better than other ORM mapping frameworks.
I will also plan to use Acegi for security concerns. I haven't designed on what type of view strategy I want to use. View transformation or something else.
Any thoughts or concerns, please do not hesitate to email the project.
