Considering the fact that my employer does not have enough money to pay me,
I am going to have some free time that is *mine* comming up soon. While I
am looking for a new job, I have some plans for Fortress before we make a
1.0 release. They are fundamental enough that I don't want to mess up installs
that are using an officially released Fortress.
Below is a list of planned activities. If anyone wants to volunteer for
anything, let me know (that way we don't duplicate efforts). If anyone
has problems with any of these planned changes let me know, because it
is better to have a good design rather than a good implementation.
Planned Changes
---------------
* Change ContainerManager to Kernel, and make it the root of all core services
(like the Event based services), and make containers act like components.
* Move the core services from the ContextManager/Builder to the Kernel.
That includes ThreadMaanger, CommandManager, PoolManager, and the core
SourceLocator setup (supporting the "context://" and "resource://"
protocols.
* Make a standard Kernel config file
- Root container set (yes there can be more than one)
+ class name
+ Configuration (at least a pointer to the config file)
+ RoleManager configs
+ Assembly configs
- Context entries
- Logger configuration (or a pointer to the config file)
- ThreadManager configs
- CommandManager configs
* Make some root frameworks
- Servlet Kernel
+ Root servlet (binding container[s] to JNDI)
+ skeleton servlet that controls kernel with servlet events
- CLI Kernel skeleton
- Block Kernel skeleton
All that a user will have to do is embed the config in the right place,
and the Kernel will do the rest.
--
"They that give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety."
- Benjamin Franklin
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
