What you are saying doesn't make sense. The SpringBean proxy doesn't cache anything, so would still proxy all method calls to the original bean. If you are not seeing updated values in that bean, there is something else going on. Unless with "update" you mean that you replace the original bean with another instance in the context, which you really should not....
On Mon, 29 Aug 2011 08:39 -0700, "Arjun Dhar" <[email protected]> wrote: > Hi, > I believe @SpringBean creates a proxy over the original bean. > > I have a situation where in the Application.init() --<callls> --> Service > layer that has direct access to SpringContext. I modify the original Bean > (getting it via Spring Context). However, this update to the object wont > reflect in the associated proxy. > > Anyone know how I can get a ref to the original bean or have the proxy > updated; so without the Annotation how can I get access to the Proxy > object > via API? > > Currently looking @ for clues... > https://cwiki.apache.org/WICKET/spring.html > > Pointers appreciated! > thanks > > > > > ----- > Software documentation is like sex: when it is good, it is very, very > good; and when it is bad, it is still better than nothing! > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/How-to-update-SpringBean-proxy-tp3776522p3776522.html > Sent from the Users forum mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
