Hi Christian,
Glad it helped you, I once had something similar. :) Have fun with the
real problems now! ;)
Martijn
On Sat, Feb 21, 2009 at 12:05 PM, Christian Helmbold
wrote:
> Hello Martijn,
>
> thank you very much! The Spring config was not in the correct directory.
> Another problem were mi
Hello Martijn,
thank you very much! The Spring config was not in the correct directory.
Another problem were missing JARs (yes, I should use maven ...). Now I'm happy
that it works and that I can concentrate myself on the next problems - with JPA
this time and not Wicket and Spring ;-)
Regar
Hi Christian,
I am using the same config as you (as far as I can tell), with the
exception I always use: @SpringBean (name="nameHere") so I always use
the name of a bean. So far I never had trouble with that. Perhaps its
the wicket version you are using different from ours? I use 1.4rc2 and
accomp
Hello Nicolas,
> Have you add the following statement in your web.xml
Yes, exactly as you wrote:
contextConfigLocation
classpath:applicationContext.xml
I've also tried to use a wrong name for the xml file, only to see if I get an
error - and I get one. So the spring confi
Hello Christian,
Have you add the following statement in your web.xml :
contextConfigLocation
classpath:applicationContext.xml
?
On Sat, 21 Feb 2009 09:09:18 + (GMT), Christian Helmbold
wrote:
> It seems like my Spring config doesn't t
It seems like my Spring config doesn't take effect. If I use a not existent
application class name in my applicationContext.xml the Wicket application
starts without an error message (the error with missing bean appears on first
request).
Wicket starts even with:
Spring itself seems to work:
Hello Cemal
thanks for your advice. Know I have extracted an interface which is used in my
WikiPage class and implemented by my Repository, but the the error is the same.
public class PageRepository extends Repository implements IPageRepository
{
...
}
public class WikiPage extends WebPage
{
Christian,
The declared type of your "repository" field should be an interface (that
PageRepository implements, in this case). In the Spiring config, your
PageRepository is used as a class, so I guess it is not an interface.
The proxy Wicket will inject is of the type of that interface, not
(nec
This is because of changes while writing my last email. Now all package names
are changed, but the error still occurs.
Christian
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail:
[wicki.domain.PageRepository] not found
missing com.helmbold ?!
El vie, 20-02-2009 a las 17:25 +, Christian Helmbold escribió:
> I try to use Wicket's Spring integration, but I get the following error:
>
> WicketMessage: Can't instantiate page using constructor public
> wicki.WikiPage()
>
I try to use Wicket's Spring integration, but I get the following error:
WicketMessage: Can't instantiate page using constructor public wicki.WikiPage()
Root cause:
java.lang.IllegalStateException: bean of type [wicki.domain.PageRepository] not
found
at
org.apache.wicket.spring.SpringBeanLocat
11 matches
Mail list logo