Re: Wicket / Spring bean annotations
Although I do not know for sure, I would think not, because my understanding is that a proxy is created that is safe to be serialized. However, I would ask *why* do this? If you're passing it to another component, why not just have that component also use an annotation? I wouldn't think that passing services around is typically a great use-case. -- Jeremy Thomerson http://www.wickettraining.com On Tue, Jan 20, 2009 at 6:00 PM, Andrew Humphries (MEL) andrew.humphr...@foxtel.com.au wrote: Hi - Probably a simple question : We are using Spring with Wicket in our project. I have opted for the use of the Spring bean annotations as described in 'Wicket in Action'. In the chapter on integrating the two technologies the book explains that you should use proxies instead of direct references to Spring beans in your components, so that you don't end up serializing your whole application context. It then goes on to explain the technique of annotating Spring bean references in your components - which I gather is safe in this regard (else why would it be recommended). Is it also safe to pass references to the Spring beans initialized in one component via an annotation to other components and set them as members on those other components ? Or will this risk app context serialization ? Thanks Andrew Humphies Analyst/Programmer This e-mail, and any attachment, is confidential. If you are not the intended recipient, please delete it from your system, do not use or disclose the information in any way, and notify the sender immediately. Any views expressed in this message are those of the individual sender and may not be the views of FOXTEL, unless specifically stated. No warranty is made that the e-mail or attachment (s) are free from computer viruses or other defects.
RE: Wicket / Spring bean annotations
Thanks for your quick answer Jeremy. However, I would ask *why* do this? If you're passing it to another component, why not just have that component also use an annotation? I wouldn't think that passing services around is typically a great use-case. Yes, you're right, theres no point in annotating some components and not others, and then passing around the reference. I'll stick to doing that, but I was also intersted out of curiosity. Andrew -Original Message- From: Jeremy Thomerson [mailto:jer...@wickettraining.com] Sent: Wednesday, 21 January 2009 11:03 AM To: users@wicket.apache.org Subject: Re: Wicket / Spring bean annotations Although I do not know for sure, I would think not, because my understanding is that a proxy is created that is safe to be serialized. However, I would ask *why* do this? If you're passing it to another component, why not just have that component also use an annotation? I wouldn't think that passing services around is typically a great use-case. -- Jeremy Thomerson http://www.wickettraining.com On Tue, Jan 20, 2009 at 6:00 PM, Andrew Humphries (MEL) andrew.humphr...@foxtel.com.au wrote: Hi - Probably a simple question : We are using Spring with Wicket in our project. I have opted for the use of the Spring bean annotations as described in 'Wicket in Action'. In the chapter on integrating the two technologies the book explains that you should use proxies instead of direct references to Spring beans in your components, so that you don't end up serializing your whole application context. It then goes on to explain the technique of annotating Spring bean references in your components - which I gather is safe in this regard (else why would it be recommended). Is it also safe to pass references to the Spring beans initialized in one component via an annotation to other components and set them as members on those other components ? Or will this risk app context serialization ? Thanks Andrew Humphies Analyst/Programmer This e-mail, and any attachment, is confidential. If you are not the intended recipient, please delete it from your system, do not use or disclose the information in any way, and notify the sender immediately. Any views expressed in this message are those of the individual sender and may not be the views of FOXTEL, unless specifically stated. No warranty is made that the e-mail or attachment (s) are free from computer viruses or other defects. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicket / Spring bean annotations
However, if you're not writing those other components, you have no choice. So, this case does show up. On Tue, Jan 20, 2009 at 7:15 PM, Andrew Humphries (MEL) andrew.humphr...@foxtel.com.au wrote: Thanks for your quick answer Jeremy. However, I would ask *why* do this? If you're passing it to another component, why not just have that component also use an annotation? I wouldn't think that passing services around is typically a great use-case. Yes, you're right, theres no point in annotating some components and not others, and then passing around the reference. I'll stick to doing that, but I was also intersted out of curiosity. Andrew -Original Message- From: Jeremy Thomerson [mailto:jer...@wickettraining.com] Sent: Wednesday, 21 January 2009 11:03 AM To: users@wicket.apache.org Subject: Re: Wicket / Spring bean annotations Although I do not know for sure, I would think not, because my understanding is that a proxy is created that is safe to be serialized. However, I would ask *why* do this? If you're passing it to another component, why not just have that component also use an annotation? I wouldn't think that passing services around is typically a great use-case. -- Jeremy Thomerson http://www.wickettraining.com On Tue, Jan 20, 2009 at 6:00 PM, Andrew Humphries (MEL) andrew.humphr...@foxtel.com.au wrote: Hi - Probably a simple question : We are using Spring with Wicket in our project. I have opted for the use of the Spring bean annotations as described in 'Wicket in Action'. In the chapter on integrating the two technologies the book explains that you should use proxies instead of direct references to Spring beans in your components, so that you don't end up serializing your whole application context. It then goes on to explain the technique of annotating Spring bean references in your components - which I gather is safe in this regard (else why would it be recommended). Is it also safe to pass references to the Spring beans initialized in one component via an annotation to other components and set them as members on those other components ? Or will this risk app context serialization ? Thanks Andrew Humphies Analyst/Programmer This e-mail, and any attachment, is confidential. If you are not the intended recipient, please delete it from your system, do not use or disclose the information in any way, and notify the sender immediately. Any views expressed in this message are those of the individual sender and may not be the views of FOXTEL, unless specifically stated. No warranty is made that the e-mail or attachment (s) are free from computer viruses or other defects. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicket / Spring bean annotations
there is a point, however, to passing references to injected dependencies into models and dataproviders - something you cannot do with wicket's proxy. -igor On Tue, Jan 20, 2009 at 4:15 PM, Andrew Humphries (MEL) andrew.humphr...@foxtel.com.au wrote: Thanks for your quick answer Jeremy. However, I would ask *why* do this? If you're passing it to another component, why not just have that component also use an annotation? I wouldn't think that passing services around is typically a great use-case. Yes, you're right, theres no point in annotating some components and not others, and then passing around the reference. I'll stick to doing that, but I was also intersted out of curiosity. Andrew -Original Message- From: Jeremy Thomerson [mailto:jer...@wickettraining.com] Sent: Wednesday, 21 January 2009 11:03 AM To: users@wicket.apache.org Subject: Re: Wicket / Spring bean annotations Although I do not know for sure, I would think not, because my understanding is that a proxy is created that is safe to be serialized. However, I would ask *why* do this? If you're passing it to another component, why not just have that component also use an annotation? I wouldn't think that passing services around is typically a great use-case. -- Jeremy Thomerson http://www.wickettraining.com On Tue, Jan 20, 2009 at 6:00 PM, Andrew Humphries (MEL) andrew.humphr...@foxtel.com.au wrote: Hi - Probably a simple question : We are using Spring with Wicket in our project. I have opted for the use of the Spring bean annotations as described in 'Wicket in Action'. In the chapter on integrating the two technologies the book explains that you should use proxies instead of direct references to Spring beans in your components, so that you don't end up serializing your whole application context. It then goes on to explain the technique of annotating Spring bean references in your components - which I gather is safe in this regard (else why would it be recommended). Is it also safe to pass references to the Spring beans initialized in one component via an annotation to other components and set them as members on those other components ? Or will this risk app context serialization ? Thanks Andrew Humphies Analyst/Programmer This e-mail, and any attachment, is confidential. If you are not the intended recipient, please delete it from your system, do not use or disclose the information in any way, and notify the sender immediately. Any views expressed in this message are those of the individual sender and may not be the views of FOXTEL, unless specifically stated. No warranty is made that the e-mail or attachment (s) are free from computer viruses or other defects. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicket / Spring bean annotations
erm. s/with/without/ :) -igor On Tue, Jan 20, 2009 at 5:47 PM, Igor Vaynberg igor.vaynb...@gmail.com wrote: there is a point, however, to passing references to injected dependencies into models and dataproviders - something you cannot do with wicket's proxy. -igor On Tue, Jan 20, 2009 at 4:15 PM, Andrew Humphries (MEL) andrew.humphr...@foxtel.com.au wrote: Thanks for your quick answer Jeremy. However, I would ask *why* do this? If you're passing it to another component, why not just have that component also use an annotation? I wouldn't think that passing services around is typically a great use-case. Yes, you're right, theres no point in annotating some components and not others, and then passing around the reference. I'll stick to doing that, but I was also intersted out of curiosity. Andrew -Original Message- From: Jeremy Thomerson [mailto:jer...@wickettraining.com] Sent: Wednesday, 21 January 2009 11:03 AM To: users@wicket.apache.org Subject: Re: Wicket / Spring bean annotations Although I do not know for sure, I would think not, because my understanding is that a proxy is created that is safe to be serialized. However, I would ask *why* do this? If you're passing it to another component, why not just have that component also use an annotation? I wouldn't think that passing services around is typically a great use-case. -- Jeremy Thomerson http://www.wickettraining.com On Tue, Jan 20, 2009 at 6:00 PM, Andrew Humphries (MEL) andrew.humphr...@foxtel.com.au wrote: Hi - Probably a simple question : We are using Spring with Wicket in our project. I have opted for the use of the Spring bean annotations as described in 'Wicket in Action'. In the chapter on integrating the two technologies the book explains that you should use proxies instead of direct references to Spring beans in your components, so that you don't end up serializing your whole application context. It then goes on to explain the technique of annotating Spring bean references in your components - which I gather is safe in this regard (else why would it be recommended). Is it also safe to pass references to the Spring beans initialized in one component via an annotation to other components and set them as members on those other components ? Or will this risk app context serialization ? Thanks Andrew Humphies Analyst/Programmer This e-mail, and any attachment, is confidential. If you are not the intended recipient, please delete it from your system, do not use or disclose the information in any way, and notify the sender immediately. Any views expressed in this message are those of the individual sender and may not be the views of FOXTEL, unless specifically stated. No warranty is made that the e-mail or attachment (s) are free from computer viruses or other defects. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
