[X] Yes, let's go ApacheDirk2006/8/21, Eelco Hillenius <[EMAIL PROTECTED]>:
Hi all,Some time ago we announced that we started negotiations with Apache tostart an incubation process. That basically means we would be enteringa 'test period' where we proof ourselves to fit in as an Apache
process, adh
us, so need for us to do it.-Igor
On 4/25/06,
Dirk Markert <[EMAIL PROTECTED]> wrote:
I think the problem is the clz variable. It is modified inside the synchronized block and read in a not synchronized part.2006/4/26, Igor Vaynberg <
[EMAIL PROTECTED]>:
we are using a map with con
I think the problem is the clz variable. It is modified inside the synchronized block and read in a not synchronized part.2006/4/26, Igor Vaynberg <
[EMAIL PROTECTED]>:we are using a map with concurrency semantics already built into it.
-IgorOn 4/25/06,
Dirk Markert <
[EMAIL
After reading this article http://www.javaworld.com/jw-02-2001/jw-0209-double.html about the double-checked locking idiom I looked at resolveClass() in DefaultClassResolver. Comparing the example in the article and the resolveClass() method I got the impression that resolveClass() might not work as
I think it is. The problem is so widespread and reoccuring (just have a look at the tapestry and struts user list) that it should be supported by the framework. Why not look at it as special kind of validation? The incoming double submitted form as a whole is valid or not. The application develope
Hello,
addResources(scope, pattern, resources, new StringBuffer(relativePath).append(file.getName()) .append('/'), file, recurse);
This line does not compile in revision 5191.
Dirk
As there is now IAuthorizationStrategy it should be used for checking page access. There should be only one way wicket offers authorization. Page.checkAccess() AND IAuthorizationStrategy would be two. To give people a chance to move to the new implementation mark
Page.checkAccess() as deprecated a
