Isabelle,
I think JAAS is very interesting, and JMX is an important
strategic direction, for post 1.0.
So I think the priority right now is tutorial and docs. I've
been thinking about how best to do this, as it's urgent. The
following areas suggest themselves, with current owners.
Those marked with an asterisc are widely understood/used.
- JDBC (Thomas,*)
- Web (Juergen)
- Bean factory, application context *
- AOP (Rod)
- Transactions (Juergen/Rod)
There's also the matter of pulling everything together doc-
wise.
I suggest that the people responsible for each area put
together at least a list of contents and, ideally, code
examples. We will need a new CVS area (module?) for examples.
I don't have time to write a comprehensive tutorial on my
stuff (I guess the AOP stuff is still mainly in my head and
in code form in CVS), but I can certainly provide a brain
dump, some text, and some code. Isabelle, if you could pull
some of that together it would be fantastic! Also, as a fresh
developer you would be ideally placed to check that the
material will be helpful to someone who didn't implement the
code.
Then maybe everyone should review draft docs and kick in to
help.
Does this sound like a plan? For example, the actions on me
would be:
- provide notes on how AOP works and some code examples
(possibly needing refinement). This would also cover how it
integrates with the bean factory.
- provide notes on new functionality I've added to the bean
factory in the last couple of months--the basics are
described in the book and familiar to everyone.
A *simple* end-to-end web app using basic web functionality,
one or two AOP-enabled beans and JDBC would be a good
example, as well as more focused examples. If we agreed on
business interfaces and what it should do, maybe Juergen
could knock up the web interface and I could do the back end.
Isabelle, thanks for making contact with MagicDraw. I'll drop
your contact an email shortly.
Regards,
Rod
|
