Thank for the clarification; I'll be sure to keep that in mind with future
development. My web application is now running as designed, thanks for your
On Thursday, November 7, 2013 11:46 PM, Martin Grigorov mgrigo...@apache.org
wicket:xyz tags are not
finally i found the last problem bei incident:
I had the beans.xml under WEB-INF and WEB-INF/META-INF as described in the
docs and user forums. But actually it turned out that i had to put it under
classes/META-INF or whatever the class folder is named.
But nevertheless your hints were
may I ask what is the use case for this 1x1 PNG? Is it something that
cannot be handled via CSS + static image on resources?
On Fri, Nov 8, 2013 at 8:49 AM, Dirk Forchel dirk.forc...@exedio.comwrote:
Okay. I know, but their is no need for an additional parameter. I want to
generate always the
The sessionid appears in the url when the application is requested for a
In this case the request doesn't bring JSESSIONID cookie and the server
doesn't know whether cookies are supported/enabled in the browser so it
uses both url rewriting and cookie in the response. When the
No, actually not. We've got a complete layout for our web applications from
an external design company and they use this CSS+static image resource thing
quite often. And, as I have mentioned before, we have two Wicket web
applications running in the same container. One of them on the root context
I also tried to make a desktop Wicket application to look good on Android
1. Depending on application there is a big possibility to not be able to
show all the information. For me, it was ok to use css media query to have a
different css for Android phone. I had to tweak with fonts size
Dumb question everyone,
I heard somewhere that it is bad to declare variables as final in Wicket
because they are treated as class members, and Wicket serializes the page
that would increase your session size.
Because of this I have not declared any components I add to my page as final
The only thing I googled related to final and wicket is this:
7. Java nuances — There are two Java nuances that catch many Wicket
1. The first is serialization. Wicket uses Java serialization to store the
state of your component hierarchy (the page and all its components
after jqXHR.success et before the Ajax response is process.
Is there a aim ?
View this message in context:
There's no callback before the Ajax response is processed - what do you
need it for?
On 11/08/2013 07:45 PM, Olivier Dutrieux wrote:
since Wicket serializes all the components anyways, what would it hurt
to make a
component final or a class member when declaring it?
your reasoning is sound, it does not hurt (besides 4 additional bytes
for the object reference).
if I need to access them from an anonymous class I use
To simple explain : on before XHRHttpRequest I change some div and want to
restore the div before Ajax response is processed because sometime the
respond processed update the div and sometime not. and if the ajax response
update the div I want to keep it (don't restore it) and if the div is not
the ajax response by wicket-ajax.js) in IAjaxCallListener's success handler
if I set wr ajaxAttribute to false ?
View this message in context:
I need to build a page (maybe with Wicket, but not sure yet) that proxies
another page on a different server that I do not own nor control in any way.
Some background: let's call proxy my (wicket?) page, let's call backend
the other page.
Backend has a HTML form with three input
Mail list logo