Re: [Core] Annotation processing discussion (attn: Jan Kees)

2009-03-08 Thread Jan-Kees van Andel
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

Re: [Core] Annotation processing discussion (attn: Jan Kees)

2009-03-03 Thread Curtiss Howard
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

Re: [Core] Annotation processing discussion (attn: Jan Kees)

2009-03-03 Thread Jan-Kees van Andel
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

Re: [Core] Annotation processing discussion (attn: Jan Kees)

2009-03-03 Thread Curtiss Howard
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

Re: [Core] Annotation processing discussion (attn: Jan Kees)

2009-02-28 Thread Jan-Kees van Andel
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

Re: [Core] Annotation processing discussion (attn: Jan Kees)

2009-02-27 Thread Mike Kienenberger
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