I haven't been following this that closely (I've only been acquainted with Wicket for a few days) but on installing Wasp and Swarm and then (on learning it wouldn't be a final solution) giving up on it to go back to wicket-auth-roles as a simpler solution, might there be another possibility? Why not work on finalising a wicket-security package that is comprised on a security API (with no implementation), then have Wasp, Swarm, some kind of Spring bridge, etc. as competing implementations? That would permit a stable security solution to be provided via API whilst not "polluting" the core with an unproven solution, or with a solution that will always have application-specific alternatives.
Just an idea anyway. As to name, please choose one that isn't too cute. It doesn't have to be a brand, just a recognisable name or just an acronym with a reasonable explication. Ichiro On 9/17/10, Martijn Dashorst <martijn.dasho...@gmail.com> wrote: > The Wicket Security project WASP/SWARM has released a new version: 1.4.1 > > News worthy changes: > > * Moved code from SwarmStrategy to AbstractSwarmStrategy to allow > reuse with different implementations > * Logout now uses Session.invalidate() instead of invalidateNow(), to > prevent problems with the request logger > * Spring example is now based on Spring 3 > * Wicket dependency upgraded to 1.4.12 > > You can download the release from the Wicket stuff repository: > > http://wicketstuff.org/maven/repository/org/apache/wicket/wicket-security/ > > Or upgrade using the following in your pom: > > <dependency> > <groupId>org.apache.wicket.wicket-security</groupId> > <artifactId>swarm</artifactId> > <version>1.4.1</version> > </dependency> > > > ROADMAP > ======== > > Milestone 1.5-M1 > > As Wicket Security will not be adopted into core, we'll be changing > the package name and project name going forward. We're still not sure > about the final name, but these two are the runners up: > > - Chitin > - Wicket Keeper > > Both are nice names, and both have their pros and cons. Let us know > which one you prefer. > > Furthermore we'll be adding new annotations such that you'll be able > to authorize your pages using a Java class (for the principal) and an > annotation on your page to specify which principals are required. This > will eliminate the need for the policy files. > > Future milestones > > * Support for Wicket 1.5 > * A new home > * Deployment to maven central instead of wicketstuff repo > > We expect to release the first milestone in a week or so. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
