Wes Wannemacher wrote:
If you're using AOP, you'll need to tell spring to proxy classes using
CGLIB rather than dynamic JDK proxies... To do so, you'll have to add
the cglib jars to your project and add the following to your
applicationContext.xml ->
<aop:config proxy-target-class="true" />
http://static.springsource.org/spring/docs/2.0.x/reference/aop-api.html#aop-pfb-proxy-types
I understand if the OP has methods in the implementation that are not in
the interface that the interface based proxy won't have those methods.
I'm unclear, though, whether your advice is a general suggestion, or
just to solve this specific problem (without the (IMHO) more advisable
solution of adding input1() to the implemented interface). Without the
OP's problems, I don't understand what the benefit of having the
auto-generated proxies extend the class rather than implement the same
interfaces would be. It seems that there are many more pitfalls (with
private/protected, whether or not the proxy calls super() methods
(before then calling them on the wrapped bean), etc.) with this
solution, no?
Sorry to ask spring questions on a struts list, but I'm just trying to
understand the already proffered advice.
-Dale
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
For additional commands, e-mail: user-h...@struts.apache.org
