You could also print stacktrace of all invocations of the constructor by
adding this line:
new Exception().printStackTrace();
br, Edvard
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/why-is-getHomePage-called-multiple-times-tp1881852p4660161.html
Sent from the
https://issues.apache.org/jira/browse/WICKET-5232
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Can-i-display-a-WepPage-in-a-PDF-How-to-get-the-rendered-markup-tp4659290p4659438.html
Sent from the Users forum mailing list archive at Nabble.com.
---
I created a quickstart but didn't create a ticket yet, because I found out
that ComponentRenderer expects to get a component whose markupId equals to
ComponentRenderer.COMP_ID.
Is this a bug or a feature? Is there some way to render the markup of an
existing component that has an arbitrary markupI
Good point. Anyway, that still leaves me the issue with ListView...
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Can-i-display-a-WepPage-in-a-PDF-How-to-get-the-rendered-markup-tp4659290p4659354.html
Sent from the Users forum mailing list archive at Nabble.com.
-
FYI:
I had a problem using ComponentRenderer with ListView (it was complaining
the there was no markup for wicket-id "my-wicket-id").
Additionally, ITextRenderer (or xerces actually) was not able to parse XML
from the markup with Wicket tags ("The prefix "wicket" for element
"wicket:container" is
If you have src="app2/image?item-123" in a resource located in
http://localhost:8080/app1/, it will be resolved as
http://localhost:8080/app1/app2/image?item-123 as you noticed.
Adding "/" to the beginning should help: src="/app2/image?item-123" should
be resolved as http://localhost:8080/app2/ima
If you are already using XmlWebApplicationContext (extends
AbstractRefreshableWebApplicationContext like
AnnotationConfigWebApplicationContext) that is probably not the issue, but
you can set the context class in your web.xml like this:
...
contextClass
org.sprin