Dmitry, it would probably be fairly easy to build your own support for
this. Just look at how wicket-spring-annot is done, and translate that
to support @Resource.
Eelco
On Mon, Jul 7, 2008 at 11:38 AM, Igor Vaynberg [EMAIL PROTECTED] wrote:
because when we created @SpringBean there was no
Why wicket framework used it's own annotation @SpringBean instead standard
annotation @Resource?
(I want configure other web framework to use anotation for bean injecting)
Dmitry.
because when we created @SpringBean there was no standard @Resource.
also, afaik, @Resource is part of jdk6 while Wicket requires 1.4/5.
perhaps when we require jdk6 we can use @Resource
-igor
On Mon, Jul 7, 2008 at 11:32 AM, Dima Rzhevskiy [EMAIL PROTECTED] wrote:
Why wicket framework used
Thank you for answer.
2008/7/7, Igor Vaynberg [EMAIL PROTECTED]:
because when we created @SpringBean there was no standard @Resource.
also, afaik, @Resource is part of jdk6 while Wicket requires 1.4/5.
perhaps when we require jdk6 we can use @Resource
-igor
On Mon, Jul 7, 2008 at 11:32
