Hi Frank,
Yes, that is what I do already. But I would like to redirect to a page
where the user can see the exception and put it in a tracking system.
That exception is invaluable because access to the logs of a production
system is problematic.
Erik.
Frank Bille schreef:
For failing
I'd say that a file descriptor leak is not an option in any case.
The code I supplied tests to see if something is a JarURLConnection and
get's the URL to the jar file itself if this is the case. You can then
test if THAT url is modified. This is what the JarURLConnection does
anyway, so you
its already in for 2.0 en 1.3
On 12/3/06, Sebastiaan van Erk [EMAIL PROTECTED] wrote:
I'd say that a file descriptor leak is not an option in any case.
The code I supplied tests to see if something is a JarURLConnection and
get's the URL to the jar file itself if this is the case. You can
I have a question about what Wicket should traverse properties files
and what it does.
Take a look in http://cwiki.apache.org/WICKET/i18n-and-resource-boundles.html
here it says Wicket will look in properties files according to this:
1. MyPanel_locale.properties
2. then MyPanel.properties
3.
