On Wed, Sep 19, 2007 at 09:05:48AM -0400, Rick Reumann wrote: > > Yea, I'd like to use the annotation but I believe that's only working when > running under Java5? (sadly, this app has to run on an old websever that is > using Java4.) (The annotation is in the wicket-contrib-spring-jdk5 so I just > figured it required Java5 - but I'm not positive of that requirement - can > someone confirm ? )
Yup, Java5 is required for annotations. > Also, where you mention "allows me to manually inject test instances of my > services/business > delegates to do unit tests." - I get the same benefit with the proxy > approach which is why I'm using Spring in the first place:) - it's just > slightly more verbose, although if I use the 'createSpringBeanProxy' from my > Base application class it's really only one line so it's not 'that' bad - > unless there is something else that annotation approach gives me that I'm > missing? Sounds like you still need a Spring context for your unit tests, to give createSpringBeanProxy something to work with. Not a huge deal but still a minor complication. With the annotation approach, I can just ignore the annotation and inject a stub using the setter. But if you can't use Java5 it's kinda moot. jk --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
