avoid setters / getters by using ?
Hello, I have Wicket+Spring application. It has a service object which has a few DAO members. I can use Spring's autowiring to avoid mentioning the DAO dependencies for the service bean. However, in the Java program for the service bean, I still have to add setters and getters for each DAO member, which I don't like. How can I avoid these setters and getters? Using AOP? Any examples? I understand that this question is not strictly a Wicket, but I definitely want to ask my Wicket friends here. Thank you! - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: avoid setters / getters by using ?
At least in wicket you can access the fields themselves using propertymodels. ** Martin 2009/9/27 David Chang david_q_zh...@yahoo.com: Hello, I have Wicket+Spring application. It has a service object which has a few DAO members. I can use Spring's autowiring to avoid mentioning the DAO dependencies for the service bean. However, in the Java program for the service bean, I still have to add setters and getters for each DAO member, which I don't like. How can I avoid these setters and getters? Using AOP? Any examples? I understand that this question is not strictly a Wicket, but I definitely want to ask my Wicket friends here. Thank you! - 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: avoid setters / getters by using ?
Martin, Thanks for your input. My intention is how to get rid of these boring setters/getters from service beans that are usually generated only for the purpose of spring-injection. Cheers! --- On Sun, 9/27/09, Martin Makundi martin.maku...@koodaripalvelut.com wrote: From: Martin Makundi martin.maku...@koodaripalvelut.com Subject: Re: avoid setters / getters by using ? To: users@wicket.apache.org Date: Sunday, September 27, 2009, 3:55 PM At least in wicket you can access the fields themselves using propertymodels. ** Martin 2009/9/27 David Chang david_q_zh...@yahoo.com: Hello, I have Wicket+Spring application. It has a service object which has a few DAO members. I can use Spring's autowiring to avoid mentioning the DAO dependencies for the service bean. However, in the Java program for the service bean, I still have to add setters and getters for each DAO member, which I don't like. How can I avoid these setters and getters? Using AOP? Any examples? I understand that this question is not strictly a Wicket, but I definitely want to ask my Wicket friends here. Thank you! - 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 - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: avoid setters / getters by using ?
Use Lombok (http://projectlombok.org/), it allows you to generate setters and getters through annotations: @Getter @Setter private String name; /Casper David Chang wrote: Martin, Thanks for your input. My intention is how to get rid of these boring setters/getters from service beans that are usually generated only for the purpose of spring-injection. Cheers! --- On Sun, 9/27/09, Martin Makundi martin.maku...@koodaripalvelut.com wrote: From: Martin Makundi martin.maku...@koodaripalvelut.com Subject: Re: avoid setters / getters by using ? To: users@wicket.apache.org Date: Sunday, September 27, 2009, 3:55 PM At least in wicket you can access the fields themselves using propertymodels. ** Martin 2009/9/27 David Chang david_q_zh...@yahoo.com: Hello, I have Wicket+Spring application. It has a service object which has a few DAO members. I can use Spring's autowiring to avoid mentioning the DAO dependencies for the service bean. However, in the Java program for the service bean, I still have to add setters and getters for each DAO member, which I don't like. How can I avoid these setters and getters? Using AOP? Any examples? I understand that this question is not strictly a Wicket, but I definitely want to ask my Wicket friends here. Thank you! - 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 - 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: avoid setters / getters by using ?
Hi David, if you use Eclipse, you can get rid of the getters/setters by using http://projectlombok.org/. Cheers, Christian David Chang schrieb: Martin, Thanks for your input. My intention is how to get rid of these boring setters/getters from service beans that are usually generated only for the purpose of spring-injection. Cheers! --- On Sun, 9/27/09, Martin Makundi martin.maku...@koodaripalvelut.com wrote: From: Martin Makundi martin.maku...@koodaripalvelut.com Subject: Re: avoid setters / getters by using ? To: users@wicket.apache.org Date: Sunday, September 27, 2009, 3:55 PM At least in wicket you can access the fields themselves using propertymodels. ** Martin 2009/9/27 David Chang david_q_zh...@yahoo.com: Hello, I have Wicket+Spring application. It has a service object which has a few DAO members. I can use Spring's autowiring to avoid mentioning the DAO dependencies for the service bean. However, in the Java program for the service bean, I still have to add setters and getters for each DAO member, which I don't like. How can I avoid these setters and getters? Using AOP? Any examples? I understand that this question is not strictly a Wicket, but I definitely want to ask my Wicket friends here. Thank you! - 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 - 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: avoid setters / getters by using ?
My intention is how to get rid of these boring setters/getters from service beans that are usually generated only for the purpose of spring-injection. Well, my solution is: 1. Use abstract static service classes that cannot be instantiated. 2. Won't need spring. ** Martin --- On Sun, 9/27/09, Martin Makundi martin.maku...@koodaripalvelut.com wrote: From: Martin Makundi martin.maku...@koodaripalvelut.com Subject: Re: avoid setters / getters by using ? To: users@wicket.apache.org Date: Sunday, September 27, 2009, 3:55 PM At least in wicket you can access the fields themselves using propertymodels. ** Martin 2009/9/27 David Chang david_q_zh...@yahoo.com: Hello, I have Wicket+Spring application. It has a service object which has a few DAO members. I can use Spring's autowiring to avoid mentioning the DAO dependencies for the service bean. However, in the Java program for the service bean, I still have to add setters and getters for each DAO member, which I don't like. How can I avoid these setters and getters? Using AOP? Any examples? I understand that this question is not strictly a Wicket, but I definitely want to ask my Wicket friends here. Thank you! - 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 - 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
