Martijn,
Good spot, thanks. The "exclusions" (copied from the phonebook pom.xml)
probably didn't help, in this case, to keep things clearer.
If the eclipse targets are deleted (properly cleaned) _and_ the library
versions are consistent in the pom before the build/run it all works fine.
FYI, I re
Did you try moving *all* wicket dependencies to SNAPSHOT?
You are now mixing snapshot with 1.3.0-beta3
Martijn
On 9/9/07, jweekend <[EMAIL PROTECTED]> wrote:
>
> Here's the pom.xml.
> Rergards - Cemal
> http://jWeekend.co.uk jWeekend.co.uk
>
> http://maven.apache.org/POM/4.0.0";
> xmlns:
Here's the pom.xml.
Rergards - Cemal
http://jWeekend.co.uk jWeekend.co.uk
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd";>
4.0.0
1.3betae3
With no @SpringBean annotation, I can get to the HomePage.
When I put it back in (to inject the DAO, see below), and the
ComponentInjector gets called to do it job, I get:
--- Error ---
WicketMessage: Can't instantiate page using constructor public
com.sjw.HomePage(org.apache.wicket.P
