#: Eelco Hillenius changed the world a bit at a time by saying on 11/6/2005
9:38 PM :#
I see absolutely nothing wrong with lookups at that level. It's less
code than you would need for any component configuration and it's more
efficient too. And there are just no disadvantages, are there?
And... for this whole discussion: if you like one approach... go
implement it now! Create your own component factory, annotations
processor, aop, and please contribute when you've got something nice
working. Or let us know when you need specific changes to Wicket to
support your needs. We'll most probably honor such requests if they
are reasonable as we've done in the past.
Eelco
My single contribution to this discussion was not to proove something is bad, but rather to
understand others points of view and also to feedback my understanding regarding ioc/di. Considering
this, I would probably still be able to point you that lookup is not bad per se, but it is not
ioc/di. Sure, there are a few disadvantages when compairing these 2, and iirc these are presented in
Spring discussions.
As regards implementing it: when reaching the point where I would need them, if nothing is available
I will definitely come out with something. As, maybe some of the people here are aware, I am
involved in oss projects for quite a while, so if this will be the case I will do my best to
contribute them back to the community.
cheers,
./alex
--
.w( the_mindstorm )p.
On 11/6/05, Alexandru Popescu <[EMAIL PROTECTED]> wrote:
#: Igor Vaynberg changed the world a bit at a time by saying on 11/6/2005 7:06
PM :#
> Or how about a simple solution:
>
> public MyApplication extends WebApplication {
> public Object lookup(String name) {
> Object=...do a lookup from somewhere like spring context or app object...;
> return object;
> }
> }
>
> public MyPage extends Page {
> public transient SomeService service;
>
> public SomeService getService() {
> if (service==null) {
> service=getApplication().lookup(SomeService.class.getName());
> }
> return service;
> }
>
> I know its not quiete as elegant as ioc but it has none of the performance
> hits an automatic injection would cause if it would be done on
> deserialization of every component. Also its a lazy lookup so you dont do it
> until its needed, and its only done once per page (until it gets
> deserialized).
>
> -Igor
>
But this was exactly what I was suggesting to avoid ;-). Lookups and factories
are not ioc/di.
./alex
--
.w( the_mindstorm )p.
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
