yep, a lot of work. we needed something that we can point to and say
that is our "official" way of supporting spring and injection in
general, so there it is.
-Igor
On 11/15/05, Phil Kulak <[EMAIL PROTECTED]> wrote:
Thanks for the writeup, Igor. I had no idea about the progress thathad been made i
Thanks for the writeup, Igor. I had no idea about the progress that
had been made in the Spring project lately.
---
This SF.Net email is sponsored by the JBoss Inc. Get Certified Today
Register for a JBoss Training Course. Free Certification E
Hi Phil and Igor,
thank You for the quick answers, the great overview and the phonebook-patch.
It is exactly what I was looking for!
Again, many thanks.
Maik
Igor Vaynberg wrote:
While I agree with Phil, a lot of other people do not. the spring
integration package is still very much a work
While I agree with Phil, a lot of other people do not. the spring
integration package is still very much a work in progress and thats why
ive spent very little time on the documentation. That said, all the
major pieces of it have javadoc and unit tests. What it lacks is an
overview, so here it is:
It's best to keep your app context beans in the Wicket application.
See the wicket-phonebook example in wicket-stuff cvs.
On 11/14/05, Maik Dobryn <[EMAIL PROTECTED]> wrote:
> Hi Igor,
>
> I'm very new to Wicket. The last days I tried to figure out how the
> Spring integration in Wicket works.
>
>
Hi Igor,
I'm very new to Wicket. The last days I tried to figure out how the
Spring integration in Wicket works.
There is a lot of confusion about the most recent practice.
Unforturnatly, no documentation does exist which covers this important
technique.
So would You please provide a small
