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:
bean id=wicketApplication
Hello Christian,
Have you add the following statement in your web.xml :
context-param
param-namecontextConfigLocation/param-name
param-valueclasspath:applicationContext.xml/param-value
/context-param
?
On Sat, 21 Feb 2009 09:09:18 +
Hello Nicolas,
Have you add the following statement in your web.xml
Yes, exactly as you wrote:
context-param
param-namecontextConfigLocation/param-name
param-valueclasspath:applicationContext.xml/param-value
/context-param
I've also tried to use a wrong name for the xml
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
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 RepositoryPage implements IPageRepository
{
...
}
public class WikiPage extends WebPage
