Re: wicket security future - contribute!

2010-01-14 Thread Emond Papegaaij
On Thursday 14 January 2010 00:12:41 Alexander Elsholz wrote:
 in my last wicket projects i used wicket-auth roles and swarm/wasp. i think
 swarm/wasp is a really good base for larger web-applications. but we all
  know about the problem with swarm/wasp. i developed a few extensions for
  swarm, but its a lot of code and so nobody starts to maintain and whats
  more important to develop. so wasp swarm stops on wicket 1.3.

Wicket-security certainly does not stop at wicket 1.3. A snapshot for wicket 
1.4 is available and working. I am thinking about moving wicket-security under 
the WicketStuff Core project, but it is also possible that wicket-security 
will get it's own release cycle.

 there was plans to integrate wicket-security in 1.5. @wicket developers: is
  this still relevant?

I don't know about these plans, but it is possible that this has been 
discussed.

 i think we will not find one person who develops wicket-security allone -
  so who's interested?
 its not the part brings the most fun in wicket development area but a very
  very important part of every enterprise application - so contribute! lets
  define a security-subteam.

Well, actually, I recently volunteered to maintain wicket-security. I must 
admit that my time is somewhat limited, but I think wicket-security is too 
important to leave it unmaintained. At Topicus, we still heavily depend on it 
for old, current and new projects. Suggestions (and patches) are always 
welcome!

My short-term plans are to release a stable wicket-1.4 version, so you no 
longer need to depend on a SNAPSHOT. This week, a new version for wicket-1.3 
(wicket-security-1.3.1) was released, incorporation many fixes made by Maurice 
just before his accident and some minor new features. Work on a wicket-1.5 
version has not yet started.

Best regards,
Emond Papegaaij

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: wicket security future - contribute!

2010-01-14 Thread Les Hazlewood
Just a quick note to those interested - the Shiro dev team is trying
very hard to get a 1.0 final release out hopefully before the end of
this month.

Best,

Les
(Apache Shiro team)

On Thu, Jan 14, 2010 at 2:14 AM, Adrian Wiesmann awiesm...@somap.org wrote:
 Hi Alex

 i think we will not find one person who develops wicket-security allone -
 so
 who's interested?
 its not the part brings the most fun in wicket development area but a very
 very
 important part of every enterprise application - so contribute! lets
 define a
 security-subteam.

 I started with the built in security functionality and then moved to Apache
 Shiro. Shiro makes it very simple to authenticate users and to check
 permission from within your application code. And what I really like is that
 users of our tool still can personalise parts of those mechanisms when
 configuring their installation. Another plus is the permission based
 authorisation mechanism which makes defining and configuring permissions
 very flexible.

 So what I could contribute are classes to integrate Shiro into Wicket. If
 that is of interest.

 Cheers,
 Adrian

 -
 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



Re: wicket security future - contribute!

2010-01-14 Thread Vojtěch Krása
Hi,

have someone tried to integrate wicket + shiro + guice?
some example would be great.

Thanks,
V.

2010/1/14 Les Hazlewood lhazlew...@apache.org

 Just a quick note to those interested - the Shiro dev team is trying
 very hard to get a 1.0 final release out hopefully before the end of
 this month.

 Best,

 Les
 (Apache Shiro team)

 On Thu, Jan 14, 2010 at 2:14 AM, Adrian Wiesmann awiesm...@somap.org
 wrote:
  Hi Alex
 
  i think we will not find one person who develops wicket-security allone
 -
  so
  who's interested?
  its not the part brings the most fun in wicket development area but a
 very
  very
  important part of every enterprise application - so contribute! lets
  define a
  security-subteam.
 
  I started with the built in security functionality and then moved to
 Apache
  Shiro. Shiro makes it very simple to authenticate users and to check
  permission from within your application code. And what I really like is
 that
  users of our tool still can personalise parts of those mechanisms when
  configuring their installation. Another plus is the permission based
  authorisation mechanism which makes defining and configuring permissions
  very flexible.
 
  So what I could contribute are classes to integrate Shiro into Wicket. If
  that is of interest.
 
  Cheers,
  Adrian
 
  -
  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




wicket security future - contribute!

2010-01-13 Thread Alexander Elsholz
hi wicket folks,

in my last wicket projects i used wicket-auth roles and swarm/wasp. i think
swarm/wasp is a really good base for larger web-applications. but we all know
about the problem with swarm/wasp. i developed a few extensions for swarm, but
its a lot of code and so nobody starts to maintain and whats more important to 
develop. so wasp swarm stops on wicket 1.3.

there was plans to integrate wicket-security in 1.5. @wicket developers: is this
still relevant?

i think we will not find one person who develops wicket-security allone - so
who's interested?
its not the part brings the most fun in wicket development area but a very very
important part of every enterprise application - so contribute! lets define a
security-subteam.

regards alex


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: wicket security future - contribute!

2010-01-13 Thread Adrian Wiesmann

Hi Alex


i think we will not find one person who develops wicket-security allone - so
who's interested?
its not the part brings the most fun in wicket development area but a very very
important part of every enterprise application - so contribute! lets define a
security-subteam.


I started with the built in security functionality and then moved to 
Apache Shiro. Shiro makes it very simple to authenticate users and to 
check permission from within your application code. And what I really 
like is that users of our tool still can personalise parts of those 
mechanisms when configuring their installation. Another plus is the 
permission based authorisation mechanism which makes defining and 
configuring permissions very flexible.


So what I could contribute are classes to integrate Shiro into Wicket. 
If that is of interest.


Cheers,
Adrian

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org