On Jul 19, 2005, at 9:21 PM, Alan D. Cabrera wrote:
David Jencks wrote, On 7/20/2005 7:04 AM:
I'm against making coarser grained gbeans for this. In fact, I
would prefer to see gbeans for servlets, servlet mappings, and
filters as well.
I like the idea of a coarser grained GBean for simpler
configurations. Are the reasons for your preference for these
"detail" GBeans purely for management?
If this is really a problem (i.e. it is something users will
actually want to configure rather than always using our setup) IMO
the way to fix it is with a specialized builder. An example is
the login config builder.
I don't like the idea of GBeans being factories for other GBeans.
I think that the GBean configuration should be frozen at deployment
time. With that said, I like your preference for a specialized
builder.
Side note; our builders are GBeans. They just take the long way when
creating other GBeans :)
On topic, you guys realize this is a "problem" we are seeing over and
over again; the best runtime design is not necessarily the best
config/management perspective.
-David
