The problem is I was using Eclipse's maven plug (m2eclipse?!) to manage the
POM (I think it comes with WTP already). Its got the nice GUI, with the
checkbox options of include javadocs and include Sources. I didn't add
it manually in the POM.
Well, very good to know that it doesn't work
I finally found out what exactly the problem is.
I used the quickstart to generate a new project from scratch.
In my maven, I have wicket javadoc to be dependency. whenever that
dependency is there. All the ajax calls failed in both jetty and tomcat (I
setup both servers to test them), and
Why do you add the *classifierjavadoc/classifier *
in your pom to have the JavaDocs, why not adding the the
-DdownloadSources=true -DdownloadJavadocs=true in your maven command, full
example:
mvn eclipse:eclipse -DdownloadSources=true -DdownloadJavadocs=true
On Tue, Oct 12, 2010 at 4:13 PM,
the problem is most likely the fact that wicket tries to load markup
out of the javadoc jar instead of the wicket jar. the javadoc has html
files named the same as wicket jar.
it doesnt make sense to have the javadoc jar on your classpath. but,
if you must, just make sure it is on the classpath
and yet it works just fine here: http://wicketstuff.org/wicket14/ajax/pageables
create a quickstart and attach it somewhere. that way we dont have to
grasp at straws.
-igor
On Mon, Aug 16, 2010 at 12:42 PM, btbluesky btblue...@gmail.com wrote:
I tried to use AjaxPagingNavigator in a simple
