for example: if you are using aop you can do page-level injection using that, and if you use aop and jdk5 you can use annotations. if you like the service locator you can do it using that. it all depends on what toolset you are working with and what your particular requirements are. what all these discussions were about is to find a universally good way to do this, but i do not think we will find something that works for everyone.
-igor
On 11/6/05, Dan Gould <[EMAIL PROTECTED]> wrote:
Eelco Hillenius wrote:
> Most of the Wicket developers don't think Wicket is lacking on the
> Spring field /at all/. Wicket is not a managed framework, which means
> that in some cases you have more responsibilities yourself.
> Furthermore, there are several strategies that arise from these
> discussions. You can implement them all, now.
First, thanks for all the discussion. I suppose that all I'm reacting to
is that my own code (Wicket + Spring for a bunch of DAOs) seems to be
messier than I'd like. It may be that there's nothing that needs to be
touched in Wicket. What I'd love is some more examples of "how to do it
correctly" so I feel more confident that I'm not making a mess of my
program.
[That said, on most fronts, the core developers are doing an amazing job
of keeping Wicket clean, simple, and elegant. I'm impressed even if I
don't yet deal with the internals enough to make any interest
contributions. Thanks!]
-------------------------------------------------------
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-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
