I tried this a year ago (trying to replace it James Carmans commons-proxy) but gave up because the MethodHandler just doesn't match well. We would need a lot of glue code, thus heavily slowing down each and every proxy invocation (and that are millions per webapp request).
LieGrue, strub --- On Tue, 12/7/10, Eric Covener <[email protected]> wrote: > From: Eric Covener <[email protected]> > Subject: Re: Proxy problems > To: [email protected] > Date: Tuesday, December 7, 2010, 11:58 AM > > I'm not understanding what you > are saying. Surely it is less work to replace javassist > than put an spi layer between OWB and javasisst. Are you > saying that if I say tomorrow removed javassist in favor of > proxy creation that did not require exposing server classes > to applications that would not be acceptable for the next > OWB release? If so, why? > > I don't see any sense in ripping it out without taking the > time to > wrap it in an SPI, so people impacted negatively by the > alternative > have some recourse. > > -- > Eric Covener > [email protected] >
