Re: @Configurable instead of @SpringBean
I made a test case and it works. BTW - My thread seems to be put inside another thread. I did not expect this to happen if I would hit reply in Thunderbird using Gmail IMAP. Sorry! James Carman wrote: Are you sure they're being deserialized? I'd try a test case On 11/15/08, Robert [EMAIL PROTECTED] wrote: 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]
Re: @Configurable instead of @SpringBean
as jweekend told you, you should read this thread [1] [1] http://www.nabble.com/%40SpringBean-vs-%40Configurable-to18572291.html -igor On Sun, Nov 16, 2008 at 1:14 PM, Robert [EMAIL PROTECTED] wrote: I made a test case and it works. BTW - My thread seems to be put inside another thread. I did not expect this to happen if I would hit reply in Thunderbird using Gmail IMAP. Sorry! James Carman wrote: Are you sure they're being deserialized? I'd try a test case On 11/15/08, Robert [EMAIL PROTECTED] wrote: 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: @Configurable instead of @SpringBean
Yes, I read it. I was just responding to James. I understand now the problem that would occur when passing a bean to another object that will be serialized. So both methods seems to have its positive and negative sides. Igor Vaynberg wrote: as jweekend told you, you should read this thread [1] [1] http://www.nabble.com/%40SpringBean-vs-%40Configurable-to18572291.html -igor On Sun, Nov 16, 2008 at 1:14 PM, Robert [EMAIL PROTECTED] wrote: I made a test case and it works. BTW - My thread seems to be put inside another thread. I did not expect this to happen if I would hit reply in Thunderbird using Gmail IMAP. Sorry! James Carman wrote: Are you sure they're being deserialized? I'd try a test case On 11/15/08, Robert [EMAIL PROTECTED] wrote: 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
@Configurable instead of @SpringBean
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]
Re: @Configurable instead of @SpringBean
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]
Re: @Configurable instead of @SpringBean
Robert, See http://www.nabble.com/%40SpringBean-vs-%40Configurable-to18572291.html this thread and http://jira.springframework.org/browse/SPR-4302 . Regards - Cemal http://www.jWeekend.co.uk http://jWeekend.co.uk Robert ... 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] -- View this message in context: http://www.nabble.com/TextField-inside-a-ModalWindow-problems-tp20363183p20519701.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: @Configurable instead of @SpringBean
You may also want to take a look at: http://jira.springframework.org/browse/SPR-4777 On Sat, Nov 15, 2008 at 4:39 PM, jWeekend [EMAIL PROTECTED] wrote: Robert, See http://www.nabble.com/%40SpringBean-vs-%40Configurable-to18572291.html this thread and http://jira.springframework.org/browse/SPR-4302 . Regards - Cemal http://www.jWeekend.co.uk http://jWeekend.co.uk Robert ... 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] -- View this message in context: http://www.nabble.com/TextField-inside-a-ModalWindow-problems-tp20363183p20519701.html Sent from the Wicket - User 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]
Re: @Configurable instead of @SpringBean
Are you sure they're being deserialized? I'd try a test case On 11/15/08, Robert [EMAIL PROTECTED] wrote: 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] -- Sent from my mobile device - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
