Anyone?
It seems like getApplicationSettings does not have setContextPath method
anymore.
Relative paths also don't work properly as there are cross references
between packages, so there is a scenario where relative paths fail.
Based on the answer I got from this DL, I am now generating absolute
paths - but they do lack the context information of apache2.
Regards,
Niranjan
On 12/22/2011 05:42 PM, Niranjan Rao wrote:
Hi folks,
Trying to set up apache2/wicket combo. Wondering if instructions at
https://cwiki.apache.org/WICKET/wicket-behind-a-front-end-proxy.html#Wicketbehindafront-endproxy-HowtofixWicketgeneratedlinks
are still valid for wicket 1.5. If not does anyone has pointer to new
setup of documents?
What I want to achieve is something as follows:
QA server running apache2 has two tomcat AJP connectors coming from
two different server - say test and staging. Want to setup apache2 so
that if you go to http://qa/test, results are served using test ajp
connector. This works - almost. When wicket sees I need to sign-in or
other wicket generated urls, they don't have my apache2 context.
I thought fixed above mentioned was solution but that does not seem to
be working. May be I am doing something bad.
Any help is appreciated.
Regards,
Niranjan
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
