see also http://wicket.apache.org/quickstart.html
Maarten
On Fri, Nov 7, 2008 at 8:43 AM, Martin Funk [EMAIL PROTECTED] wrote:
2008/11/7 Sean Brookes [EMAIL PROTECTED]
Thank you for your quick response igor but I don't think I understand your
response. We are currently using version 1.3.4,
I know the recommeded approach is to use relative context URLs for CSS and
Javascript but our application places static assets on a separate server for
performance reasons so relative paths are not an option. From what I
understand if my path starts with http://; or https://; wicket should
can you make sure its still broken in 1.3.x branch and if it is create
a quickstart.
-igor
On Thu, Nov 6, 2008 at 3:25 PM, Sean Brookes [EMAIL PROTECTED] wrote:
I know the recommeded approach is to use relative context URLs for CSS and
Javascript but our application places static assets on a
Thank you for your quick response igor but I don't think I understand your
response. We are currently using version 1.3.4, although we are assessing
the impact of moving to 1.3.5 and I will certainly test it there when we do.
I'm afraid I don't know what you mean when you suggest I 'create a
2008/11/7 Sean Brookes [EMAIL PROTECTED]
Thank you for your quick response igor but I don't think I understand your
response. We are currently using version 1.3.4, although we are assessing
the impact of moving to 1.3.5 and I will certainly test it there when we
do.
I'm afraid I don't
