I'm going to have to think about that a bit. I only glanced at the new stuff for about a half hour this morning so far. I plan to do a deeper dive, though. Here's an interesting question though. How about allowing service points to have more than one service interface?
On 11/7/06, Achim Hügen <[EMAIL PROTECTED]> wrote:
James Carman schrieb: > I started looking through the new API today and so far it looks pretty > cool. One thing I don't like, though, is having the ClassResolver > stuff inside the definition classes. Is that absolutely necessary? I > was kind of hoping that we could use something like commons proxy to > do all of the proxying logic and get ourselves out of the Javassist > business if we can. The ModuleImpl needs a class provider for the resolveType method. It is provided by the ModuleDefinition. I think this has the same justification as the ClassResolver mechanism itself. Do you see another way? Achim
