On 6/16/06, Igor Vaynberg [EMAIL PROTECTED] wrote:
no, there are no problems with wicket-spring poject other then some people
dont think its a true way to integrate with spring. sigh.
I have some more concrete issues with the current spring integration code.
First, it is intrusive. Instead of
The application issue is known
(http://sourceforge.net/tracker/index.php?func=detailaid=1458736group_id=119783atid=684975)
and won't be fixed in 1.2 as it will break backwards compatibility.
Could you file a RFE for the Session injector?
Martijn
On 6/20/06, Stefan Arentz [EMAIL PROTECTED]
so far we only targetted the components being injected because that is what users asked for. its trivial to inject any object you wantclass MySession extends WebSession() {@SpringBean Foo bar; MySession() {
InjectorHolder.getInjector().inject(this); ... }}-IgorOn 6/20/06, Martijn Dashorst
[EMAIL
or since we do use a factory for creating application/session objects you can write a factory that pulls the session out of spring context where it is declared as a prototype bean.-Igor
On 6/20/06, Igor Vaynberg [EMAIL PROTECTED] wrote:
so far we only targetted the components being injected
Re deserialization:
You can use getter-based dependency injection to solve this problem.
Every time, a dependency-injected field is accessed (or corresponding
getter method is executed -- your choice), an advise can re-inject the
dependencies. See
Hey,
I was there as well, and I agree with you.
This could be the solution to all wicket-spring integration problems. Now for
someone to actually try it
Tom
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Michiel Trimpe
Sent: Friday, June 16, 2006 3:00
PM
Heh. Let's define 'problem' too. Many people are using Spring and Wicket together without any problems (and I'm being one of them)?Anyway, if it solves new problems, we're always happy to hear about new ideas/ get contributions.EelcoOn Jun 16, 2006, at 6:49 AM, Tom van Zummeren wrote:Hey, I
no it wont be the solution. havent you guys been following any of the other spring threads? injecting a component is not enough because you never want those dependencies serialized - thus the whole thing about wicket proxying the dependencies it injects.
you inject a service into a page's member
This could be the solution to all wicket-spring integration problems. Now for
someone to actually try it…May be I haven't been actively reading the list and missed some relevant posts. Has someone found a problem with current wicket-spring integration?.
no, there are no problems with wicket-spring poject other then some people dont think its a true way to integrate with spring. sigh.what the quote below shouldve read was
This could be the solution to all wicket - spring integration problems. Now for
someone to actually try it…-IgorOn 6/16/06,
10 matches
Mail list logo
