Hello Alis,
the Wicket programming model is based on the typical web application
request scenario - one thread typically processes one HTTP request using
the org.apache.wicket.protocol.http.WicketFilter. This filter sets the
application context using a thread-local, many wicket internals and
Hello,
I would like to introduce a similar pattern as fifty-five's SimpleCDN (
http://blog.55minutes.com/2012/01/simplecdn-and-the-newly-released-fiftyfive-wicket-32/).
Thereby I stumbled across the same obstacle as mbrictson:
Wicket does not understand scheme-less URLs that start with //.
Hello Chris,
I'm not sure, if i've got the point - you want to extract your own JS/CSS to a
cdn?
I've already used a similar implementation to this:
http://techblog.molindo.at/2011/03/serving-wicket-resources-from-cdn.html
Regards,
Jan
Von: Chris
Hej Eugene,
In practice the wicket frontend development is interrupted by frequent
small changes to the HTML, Javascript or CSS. Changes to these markups
are very expensive because they effort a new software release followed
by a software rollout. This depends on the fact, that the markup is
managing this for the designers?
Edgar Merino
On 04/12/12 04:15, Jan Riehn wrote:
Hello Edgar,
Yes, this is how it works.
For the best separation of the responsibilities, you may store the
resources outside of the web application (Think about a complete
physical separation).
We've made a good
Hello,
currently we've got a problem with faked ajax requests.these ajax
requests misses some parameters, but the wicket-ajax header flag is set.
So ServletWebRequest throws an exception:
java.lang.IllegalStateException: Current ajax request is missing the base url
header or parameter
Hey,
there is an open issue: https://issues.apache.org/jira/browse/WICKET-4358
the hint
((HttpServletResponse)bufferedWebResponse.getContainerResponse()).addCookie(
cookie ); works.
Best regards,
Jan
Von: wicket user [samd...@live.com]
Gesendet:
Hello,
we use a tomcat behind a apache. we also use mod_rewrite proxy rules to
manage requests from the apache to the tomcat. Our wicket application
modifies the location header:
curl -I http://wicket-application/application-context/login
HTTP/1.1 302 Moved Temporarily
Date: Wed, 30 May
Hello,
we use a tomcat behind a apache. we also use mod_rewrite proxy rules to
manage requests from the apache to the tomcat. Our wicket application
modifies the location header:
curl -I http://wicket-application/application-context/login
HTTP/1.1 302 Moved Temporarily
Date: Wed, 30 May