Also keep in mind that calling "getBytes()" without encoding is
dangerous. You should explicitly specify the encoding (default UTF-8 for
XML/SVG)
Am 03.09.2016 20:33, schrieb Tim Dudgeon:
Thank you. That did the trick.
-
You kan provide static content with the default mechanism of your
servlet-container (jetty? Tomcat? ...?) under a specific url. If for
whatever reason this does not work for you you can also mount resources
in Wicket to a static url.
Am 22.07.2016 09:10, schrieb ivan.cicevac:
Hi,
That is a
In fact there is no reliable way, since a client can close whenever it
needs to without notify the server.
You can try to guess it by observing sessions, and the you should use a
session-listener for maximum felxibility. In this listener you can of
course obtain the WicketSession it is stored
You could check if you can configure F5 to accept 302 code as a valid
life sign (maybe something like "don't follow redirects or such")
If you just want to check that the webserver is there an wicket is
running I would create a special CheckPage that is stateless and mounted
unter a static
By default, the bundle-plugin computes all import/export directives
automatically.
In Wicket 6 (at least 6.14) already contained OSGi headers so was this
removed in later versions?
Am 16.10.2015 06:06, schrieb Rakesh A:
Hi,
Yes, we might've to add some (import, export package) configuration;
Just a hint: If you like to use Wicket inside OSGi, maybe
https://ops4j1.jira.com/wiki/display/paxwicket/Pax+Wicket might be an
alternative instead of doing all things manually. You might also find a
hint about the initilizer there...
I think you have to provide more information, because in general
evicting the page from in -memory store just mean it must be reloaded
from the PageStor/DataStore! If this fails, then your application most
likeley has serialization issues.
So what is the crash you encounter? Why is it not
Why should wicket not be able to handle this kind of urls?
YOu can simply create a WikiPage mount it like
mountPage(WikiPage.class, /wiki/${pagename}); and you will receive
that name as a page Parameter.
You then can
a) load a Page if found (e.g in DB) under this name
b) present the user
Can you explain what is the reason for using a background-thread?
Depending on your container you might want to use e.g. Continuations or
Servlet-Async to compute lengthy values in the background and then let
render the page as normal in the RequestCycle depending on that result.
Am
Since I have reported the issue and investigated a lot in that place at
Wicket as well as Jetty side: Changing the session on each request can
have very negative impact on performance depending on the underlying
technology.
Even though you should never run into this issue when using the
If you are really eager to do so (in fact this is some kind of user
tracking that might be problematic as well as you users might try to
block it ...) you can fire an AJAX call in the domReady and one in the
close callback or when clicking a link. In fact you can only GUESS the
time a user
Why not simply use /profile/${username} or something like
/user-${username}?
Am 07.04.2015 12:43, schrieb wiseguy2:
I have that in the actual code.
I have two pages mounted.
1. Home page at / pointing to Index.class
2. Person profile page /${username}
Each time wicket tries to load a
Have you checked that the correct content-type is specified?
We use Jetty8 in a project with Wicket6 and serving package resource
files gzipped works without a problem.
What kind of Packe-Resource-Files do you see not beeing gziped? Can you
share Request/Response headers?
Am 03.04.2015 23:56,
IMO all kinds of how to prevent user-action-xyz aproaches are flawed
and bad design.
The middle-mouse-button is just one of several methods to open links
in a new tab/window. E.g. in most browsers you can archive this via
right-click, holding STRG or Command-Key or Plugin or...
So your best
Depending on your enviourment you can either use:
- Signed Java Applet
- ActiveX Control
- Browser Plugin
- Any other active technology
As mentioned earlier that is nothing specific to Wicket. And you should
consider why you want to switch to a WebApp if you have requirements to
start local
Since it sounds like the process is async you can use any of the async
modules of Wicket e.g. athmosphere or websockets.
Am 01.03.2015 21:22, schrieb long:
Hi, I made a website with Wicket and I am able to send information to a
payment site. But when I reveive an answer from this site, how do
16 matches
Mail list logo
