In what way is serialization the issue? Because the fields are marked as
transient anyway, so not serialized, and after deserialization, Spring
re-injects the bean. Or are you saying this does not happen? It seemed
to work...
James Carman wrote:
Serialization is the issue. @Configurable doesn't handle
serialization properly.
On Sat, Nov 15, 2008 at 2:59 PM, Robert <[EMAIL PROTECTED]> wrote:
Hi,
I have been using the @SpringBean annotation for dependency inject my DAO's
inside certain objects. However for objects that are not managed by wicket
the InjectorHolder is needed and this might be easy to forget. So I tried an
alternative way to inject my Spring beans.
Now I use the Spring @Configurable and @Resource annotation, together with
load-time aspect weaving. I also mark the objects as transient.
It all seems to work well. But I just wanted to ask if there are any special
cases I should be worried about. Are there any disadvantages (except being
forced to use weaving)?
Robert
---------------------------------------------------------------------
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]
