A Portfolio for Enterprise Web Applications
Thinking about “developing” a technology portfolio for Enterprise enabled Web Applications actually means:
- Researching, selecting, glueing and maintaining a set of Software Technology Components
- Adding some interesting code for the typical requirements of Mission Critical Applications
- Integration testing and proving everything in order to be able to concentrate on “the Application itself” later on.
The main aspects I’d like to focus on here and already came to my mind are roughly summed up in a series of small Articles written lately, as they are
- Control over lifecycle of persisted Entities
- Plug and Play Business Process Execution
- Best-Of-Breed UI Technologies
- Deploy and upgrade like a breeze
- JPA Database Import/Export Mechanism
- Document Storage – not everything needs to be (or is best suited to be) stored relational.
- Full Text Search
Some smaller and more technical aspects that are in my minds pipeline:
- Spring Bean Instantiation for JPA/Hibernate
- User Interface centric Object Model
- I18n aware, A/N sortable persistent labels


[...] to my thoughts about A portfolio for Enterprise Web Applications I am thinking about developing (= providing a well tested, bundled and documented software feature [...]