2009/3/3 Curtiss Howard curtiss.how...@gmail.com:
Well, my intention with the interface I proposed is to have the
implementation set up xbean-finder (or whatever the case may be) when
the impl class is created via the factory. That would in fact take
care of all the problems my group and I
Sounds like a good plan. We can elaborate on this. But first, I'd like to
clean up the current FacesConfigurator class (split up into some
ConfiguratorStrategy classes). This will make it easier to work on the
codebase together without having annoying merge conflicts. I can do this
quite
I'm almost done.I think I can work on it this Thursday and then commit it.
But I've broken my test webapp, so I'll have to fix that before I can test
the stuff... ;-)
When it's in SVN, we have the necessary boilerplate to stay out of each
others' way. ;-)
Untill then, if you are bored, you can
Well, my intention with the interface I proposed is to have the
implementation set up xbean-finder (or whatever the case may be) when
the impl class is created via the factory. That would in fact take
care of all the problems my group and I would reasonably encounter.
I.e., the default MyFaces
2009/2/27 Mike Kienenberger mkien...@gmail.com
A simple pluggable API sounds like a reasonable approach to me. For
some situations, a pure reflection scanner might work better. For
others, it won't scale. You might need to temporarily switch to a
different scanner to determine if it's
A simple pluggable API sounds like a reasonable approach to me. For
some situations, a pure reflection scanner might work better. For
others, it won't scale. You might need to temporarily switch to a
different scanner to determine if it's the cause of some particular
bug. Or perhaps the