On Thu, Oct 7, 2010 at 5:47 PM, Mauro Ciancio maurocian...@gmail.com wrote:
It's not so important, but I can't figure out why I have the same bean
instance, taking into account that the page is serialized at the end
of the request and the inyected bean is actually a proxy of the bean,
so no
On Fri, Oct 8, 2010 at 4:30 AM, Daniel Stoch daniel.st...@gmail.com wrote:
Yes: after deserialization :). And yes: after deserialization of
yout page version this bean is relocated from Spring again. You can
chcek this: go to the previous page version by clicking back button
and press refresh
Hi,
Yes: after deserialization :). And yes: after deserialization of
yout page version this bean is relocated from Spring again. You can
chcek this: go to the previous page version by clicking back button
and press refresh button (if page is cached in a browser). Then you
can see that a new
On Fri, Oct 8, 2010 at 10:42 AM, Mauro Ciancio maurocian...@gmail.com wrote:
Wel, that explains the whole issue. If only if had known it before. :)
Thanks to all for the replies.
Regards.
-
For this particular use case (the current date), I would suggest you
just calculate that on-the-fly,
For this particular use case (the current date), I would suggest you
just calculate that on-the-fly, not at bean creation time. It's not
that expensive to calculate.
Yes, I appreciate your suggestion. :)
Thanks James.
Regards.
--
Mauro Ciancio
On Wed, Oct 6, 2010 at 10:51 PM, Mauro Ciancio maurocian...@gmail.com wrote:
BTW, I've defined all the beans with prototype scope, so it's not a
spring issue.
Why are you using prototype scope anyway?
-
To unsubscribe,
On 2010-10-07 04:51, Mauro Ciancio wrote:
Hello everyone,
I'm using spring in one wicket project and I'm lost about how the
proxy stuff works. I've realized that the fields marked with
@springbean are injected when the component injection listener runs.
Also, I've looked in
Hi,
Why are you using prototype scope anyway?
In order to get a new fresh instance every time is requested.
AFAIR the once the bean is looked up from spring it is being cached by
AnnotProxyFieldValueFactory itself.
So using prototype scope will not work anyway: either way you always get a
?type=nodenode=2966817i=0
For additional commands, e-mail: [hidden
email]http://user/SendEmail.jtp?type=nodenode=2966817i=1
--
View message @
http://apache-wicket.1842946.n4.nabble.com/Bean-injection-tp2966113p2966817.html
To start a new topic under Apache
On Thu, Oct 7, 2010 at 9:13 AM, Leszek Gawron lgaw...@apache.org wrote:
AFAIR the once the bean is looked up from spring it is being cached by
AnnotProxyFieldValueFactory itself.
So using prototype scope will not work anyway: either way you always get a
fresh bean (so you cannot keep state)
On Thu, Oct 7, 2010 at 9:50 AM, Mauro Ciancio maurocian...@gmail.com wrote:
OK, I understand, that explains my issue. However, I have a bean that
is stateful and the state cannot be sent by wicket componets (more
precisely it's a bean that provides the local date and local time, and
it's
and not
refetched. I have wanted to look more at this in the Proxy factory but
have not had a chance.
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Bean-injection-tp2966113p2967048.html
Sent from the Users forum mailing list archive at Nabble.com
Hi, thanks for the quick replies.
I think as a WorkAround is to get the beans yourself from the Spring context
insteads of relying on the @SpringBean annotation
Yes, that would work.
The code specifically checks to see if the bean is a singleton before
it caches it. Non-singleton beans
Hello everyone,
I'm using spring in one wicket project and I'm lost about how the
proxy stuff works. I've realized that the fields marked with
@springbean are injected when the component injection listener runs.
Also, I've looked in AnnotProxyFieldValueFactory.class to find out
how the bean
14 matches
Mail list logo
