Hi,
I know there has been some discussion on this. But I've had a hard
time deciding how this project should use security anyway.
The application in question is layered into three layers for
presentation, services and persistence using Wicket, Spring and
Hibernate.
What we need:
-
I think community would be interested in this feature. Could you post the
code?
Marat Radchenko-2 wrote:
Wicket pages/components can be either stateful or stateless. Wicket
manages hem transparently and it is very easy to write any complex
page you want. Stateful pages are much more
Hi Kent,
Go with something that enables authorization in the service layer (e.g.
Spring Security, jSecurity, ...).
Next base your custom wicket authorization on the authentication store
of the chosen base technology. Spring Security uses a thread local as
authentication store and has a
maven.test.skip=true was the first I needed to remember, so it is hard
to get out of my head and replace it with -DskipTests
You could also consider running the maven build with a Java 5 JDK
instead of your Java 6 JDK. The tests shouldn't fail then (Java 6 has
altered the internals of
Cant you enforce that in POM file (what version to use) so it doesn't
proceed at all ... (use jdk 5 or fail).
Regards
Vyas, Anirudh
On Sun, Mar 8, 2009 at 4:23 PM, Martijn Dashorst martijn.dasho...@gmail.com
wrote:
maven.test.skip=true was the first I needed to remember, so it is hard
to get
If community was interested, it would say something in 3 months, uh?
:) I'll post it on tuesday.
2009/3/8, Alex Objelean alexandru.objel...@isdc.ro:
I think community would be interested in this feature. Could you post the
code?
Marat Radchenko-2 wrote:
Wicket pages/components can
And if you want to contribute something, it is often better to also
attach it to a JIRA issue, since then it doesn't get lost in the
archives. A jira issue can be assigned, tracked etc, whereas a message
in the archives tend to get lost in the huge amount of traffic. It
takes just one generics
Hi,
we're just thinking about a session store using memcached. I just want
to ask if somebody already implemented this (and wants to share) before
we implement this.
Btw, is there some documentation about ISessionStore semantics, in
addition to javadocs? I would be interested in the order in
You can check the TIM integration work from the Terracotta guys. That
should make things easier, and you could even try it out, perhaps
saving a memcached implementation completely :)
Martijn
On Sun, Mar 8, 2009 at 11:01 PM, Martin Grotzke
martin.grot...@javakaffee.de wrote:
Hi,
we're just
I wrote a memcached session manager store for jetty, that our wicket
app utilizes. Works well, except I can't open source it,
since it was created on the company's dime ;-(
Here is my opinion on memcached as a session store.
Memcached will not work well as a wicket session store, due to 1mb
file a jira, preferrably with a quickstart
-igor
On Sat, Mar 7, 2009 at 6:29 AM, Antoine van Wel
antoine.van@gmail.com wrote:
Hey hey,
trying to construct a URL like this:
RequestUtils.toAbsolutePath(urlFor(MyPage.class, null).toString());
this works fine in general, but when
Problem solved.
I had both wicket:head and head sections in my html and the
FormModificationDetectorBehavior was being attached twice. This was
causing a too many recursions error in the javascript and the code was
dying. Pulling out the head tag and placing everything within
wicket:head
Hello,
I'm new to Wicket (using 1.4-rc2, using IDEA IntelliJ 8.1 and maven2 with
jetty:run plugin)
In development mode, I expected to be able to edit html pages in the IDE,
and see changes reflected immediately in the browser upon browser refresh,
without having to restart wicket. Also,
13 matches
Mail list logo
