On Thu, 13 Jan 2005 00:03:07 +0100, Martijn Dashorst
<[EMAIL PROTECTED]> wrote:
> Juergen,
>
> Of course the wiki gives the necessary information to change your
> password yourself (or to remove your current account):
>
> * If you're a Wicket developer and want to change the auto-generated
>
Juergen,
Of course the wiki gives the necessary information to change your
password yourself (or to remove your current account):
* If you’re a Wicket developer and want to change the auto-generated
password you were sent, you should obtain the MD5 hash of your new
password then upda
That is what I think I did. I used my sourceforge login name. Is that
any different to the ID you mean. Trying to register again, the wiki
complains that my username is already in use.
Juergen
On Wed, 12 Jan 2005 22:40:38 +0100, Martijn Dashorst
<[EMAIL PROTECTED]> wrote:
> I think you have to u
I think you have to use your sourceforge ID to register. That's at least
what I remember. I've used that ID to register myself, and didn't have
problems accessing the wiki.
Martijn
Juergen Donnerstag wrote:
Eelco,
does it make sense to copy such info into the wiki?
I tried to access the wiki a c
Yep, that is a good idea.
Eelco
Juergen Donnerstag wrote:
Eelco,
does it make sense to copy such info into the wiki?
I tried to access the wiki a couple of days before and failed. I
registered, but did never receive the email with my password as is
mentioned on the register page and thus are not ab
Eelco,
does it make sense to copy such info into the wiki?
I tried to access the wiki a couple of days before and failed. I
registered, but did never receive the email with my password as is
mentioned on the register page and thus are not able to add any
information I intended to copy the maven i
Another anti-pattern: replacing components while not invalidating the
page. This gives problems with the back button. If you do not want *any*
backbutton problems, you should work paged based (like Hangman does).
The disadvantage of this is that the re-use of highlevel components like
panels wi
Try JConsole under JDK 1.5. It handles this sort of thing quite well!
Gili
--Original Message Text---
From: Jonathan Carlson
Date: Wed, 05 Jan 2005 09:30:33 -0600
Has anyone tried running a Wicket app over a long period of time to make sure that old objects are garbage collected
Try JConsole under JDK 1.5. It handles this sort of thing quite well!
Gili
--Original Message Text---
From: Jonathan Carlson
Date: Wed, 05 Jan 2005 09:30:33 -0600
Has anyone tried running a Wicket app over a long period of time to make sure that old objects are garbage collected
I tried it some time ago, and did not find leaks. I would be a good idea
for more people to do some serious profiling.
Anti-patterns would be using too many internal classes (I just found
out); you'll end up with spaghetti code. And - though not an
anti-pattern - be carefull about your componen
we are running it now and then with the yourkit profiler..
I will do it again when we are planning to release 1.0 to see if there
are no leaks in wicket.
Jonathan Carlson wrote:
Has anyone tried running a Wicket app over a long
period of time to make sure that old objects are garbage
Has anyone tried running a Wicket app over a long period of
time to make sure that old objects are garbage collected
properly? (Preferably with something like JMeter hitting pages the
whole time)
Are there any anti-patterns to avoid?
- Jonathan
*
12 matches
Mail list logo
