You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wicket.apache.org by Korbinian Bachl - privat <ko...@whiskyworld.de> on 2008/07/06 20:19:05 UTC
Swarm & Wicket 1.4 m2
Hello,
I just spend some time to change my app (on wicket 1.4) to use the SWARM
implementation of WASP.
However, it seems that WASP 1.3.0 as well as the current 1.3-Snapshot
(1.3.1) wont work with 1.4; The error is nearly allways the same:
1.3.1:
"
java.lang.NoSuchMethodError:
org.apache.wicket.MetaDataKey.<init>(Ljava/lang/Class;)V
org.apache.wicket.security.log.AuthorizationErrorKey.<init>(AuthorizationErrorKey.java:41)
org.apache.wicket.security.strategies.WaspAuthorizationStrategy.<clinit>(WaspAuthorizationStrategy.java:57)
org.apache.wicket.security.swarm.strategies.SwarmStrategyFactory.newStrategy(SwarmStrategyFactory.java:80)
org.apache.wicket.security.WaspSession.<init>(WaspSession.java:48)
org.apache.wicket.security.WaspWebApplication.newSession(WaspWebApplication.java:71)
org.apache.wicket.Session.findOrCreate(Session.java:231)
org.apache.wicket.Session.findOrCreate(Session.java:214)
org.apache.wicket.Session.get(Session.java:253)
org.apache.wicket.RequestCycle.getSession(RequestCycle.java:436)
org.apache.wicket.request.AbstractRequestCycleProcessor.resolveHomePageTarget(AbstractRequestCycleProcessor.java:315)
org.apache.wicket.protocol.http.WebRequestCycleProcessor.resolve(WebRequestCycleProcessor.java:159)
org.apache.wicket.RequestCycle.step(RequestCycle.java:1246)
org.apache.wicket.RequestCycle.steps(RequestCycle.java:1366)
org.apache.wicket.RequestCycle.request(RequestCycle.java:499)
org.apache.wicket.protocol.http.WicketFilter.doGet(WicketFilter.java:387)
org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:199)
"
and 1.3.0:
"
java.lang.NoSuchMethodError:
org.apache.wicket.MetaDataKey.<init>(Ljava/lang/Class;)V
org.apache.wicket.security.checks.WaspKey.<init>(WaspKey.java:41)
org.apache.wicket.security.components.SecureComponentHelper.getSecurityCheck(SecureComponentHelper.java:55)
org.apache.wicket.security.strategies.WaspAuthorizationStrategy.getSecurityCheck(WaspAuthorizationStrategy.java:185)
org.apache.wicket.security.strategies.WaspAuthorizationStrategy.isActionAuthorized(WaspAuthorizationStrategy.java:159)
org.apache.wicket.Component.isActionAuthorized(Component.java:1983)
org.apache.wicket.Page.renderPage(Page.java:855)
org.apache.wicket.request.target.component.BookmarkablePageRequestTarget.respond(BookmarkablePageRequestTarget.java:241)
org.apache.wicket.request.AbstractRequestCycleProcessor.respond(AbstractRequestCycleProcessor.java:104)
org.apache.wicket.RequestCycle.processEventsAndRespond(RequestCycle.java:1194)
org.apache.wicket.RequestCycle.step(RequestCycle.java:1265)
org.apache.wicket.RequestCycle.steps(RequestCycle.java:1366)
org.apache.wicket.RequestCycle.request(RequestCycle.java:499)
org.apache.wicket.protocol.http.WicketFilter.doGet(WicketFilter.java:387)
org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:199)
"
Is there any workaround Maurice?
Best,
Korbinian
Re: Swarm & Wicket 1.4 m2
Posted by Korbinian Bachl - privat <ko...@whiskyworld.de>.
Hi James,
thats no flaming - thats just human :) - I mean, when I first saw it I
thought "WTF!?! - this is a big mess..." but after spending some time on
it, it turned out that its really a cool thing.
IMHO the biggest mess Maurice made was the naming of its parts... I mean
WASP, SWARM, HIVE, Principal & co: Man! This sounds like some sort of a
B-class-horror-movie... but soon after you understand the meanings in
the context you see how neat and cool this is.
I mean, security is usually never beloved nor easy - I know of some SAP
system having more than 1000 defined roles (!) in over 10 Levels of
usage each - but its just necessary. If you look at the current one we
have with wicket, its just best described as : easy - and somehow
useless in bigger contexts. Just imagine if every user may do everything
if he's logged in - we authenticate but not really authorize, nor can we
easily secure information or parts of it.
I mean, with swarm you got some really cool things like SecureModels or
the possibility to overtake security from other places/ apps. This of
course is not so easy anymore but is powerful and necessary in many
applications.
If you want to get a good grip on it and what it can do just look this
presentation:
http://www.slideshare.net/mrmean/wicket-security-presentation/
and grab the examples:
http://wicketstuff.org/confluence/display/STUFFWIKI/Wicket-Security+Examples
(to see them in action: http://wicketstuff.org/wicketsecurity/ )
Best,
Korbinian
James Carman schrieb:
> On Mon, Jul 7, 2008 at 11:38 AM, Maurice Marrink <ma...@gmail.com> wrote:
>
>> No particular reason other then that we are trying to make the
>> migration from wicket 1.3 to wicket 1.4 as small as possible.
>> There has not been an official vote on this yet but the plan is to
>> integrate it in wicket 1.5 which we will begin working on shortly
>> after 1.4 has been released.
>
> I'm not trying to flame here or anything, but from what I've read of
> Swarm/Wasp, it's quite complicated and that would go against the
> spirit of Wicket, IMHO. Also, it uses external files for
> configuration. Again, this goes against the spirit of Wicket.
> Perhaps if there were a programmatic way of configuring everything?
> Again, I've never used it, but I've seen responses on the lists about
> how to do things and it just scared me away from it. That's just my
> $0.02. To be fair, maybe I should play with it a bit to see it for
> myself, but I haven't had the cycles. Sorry.
Re: Swarm & Wicket 1.4 m2
Posted by Nino Saturnino Martinez Vazquez Wael <ni...@jayway.dk>.
There are a lot of us just waiting for the annotation part of swarm I
think.. Then I'll switch to swarm.. And when it gets adopted by wicket,
well theres gonna be a lot more users...
RUMikeP wrote:
> My ZAR0.02 worth (a lot less than $0.02 ;-)
>
> I have to be honest, that initially I was also a bit confused, but once you
> take half an hour to work though it, it is REALLY powerful and customisable.
>
> It you are building an application end-to-end from scratch, and are using
> Wicket for the UI, it may be tempting to build in the security concepts in
> the UI. However, larger corporates generally have a mix legacy and newer
> security mechanisms that one needs to integrate with, and (maybe it is just
> the projects that I need to implement, but) generally the Wicket UI is
> designed to sit on top of an existing backend. Therefore, you can almost
> guarantee that you will need to authenticate against some external system,
> obtain a list of groups and or roles granted to that user and then map those
> groups/roles to permissions to perform certain actions on the UI layer.
> Swarm fulfils this role perfectly in our situation, and the fact that it is
> decoupled from the core Wicket UI code, provides a high level of comfort
> that we could replace the Swarm implementation with a different custom
> implementation if necessary without a major rework of the UI code.
>
> I have made use of Swarm out-of-the-box except for creating a
> PolicyDatabaseHiveFactory to read in the role-to-permission mappings from a
> database table. It would be just as simple to create a Policy Hive Factory
> that builds up the mapping in Java code rather than reading it from a
> properties file or database table, i.e. by creating your own implementation
> of one class, it gives you a security implementation based on your
> preference for where the mapping is stored/implemented.
>
> I am not saying it is a perfect fit for everyone, but I do believe that the
> Wicket Community needs to more actively promote the use of Swarm (where
> appropriate) and I really would like to see more people using it so that
> there is a larger pool of knowledgeable resources to assist and guide newer
> users (especially since there is a plan to make it part of core in 1.5)
>
> Mike
>
>
>
> Mr Mean wrote:
>
>> On Mon, Jul 7, 2008 at 6:01 PM, Guðmundur Bjarni Ólafsson
>> <gu...@gmail.com> wrote:
>>
>>> On Mon, Jul 7, 2008 at 5:50 PM, James Carman <ja...@carmanconsulting.com>
>>> wrote:
>>>
>>>
>>>> I'm not trying to flame here or anything, but from what I've read of
>>>> Swarm/Wasp, it's quite complicated and that would go against the
>>>> spirit of Wicket, IMHO. Also, it uses external files for
>>>> configuration. Again, this goes against the spirit of Wicket.
>>>> Perhaps if there were a programmatic way of configuring everything?
>>>> Again, I've never used it, but I've seen responses on the lists about
>>>> how to do things and it just scared me away from it. That's just my
>>>> $0.02. To be fair, maybe I should play with it a bit to see it for
>>>> myself, but I haven't had the cycles. Sorry.
>>>>
>>>>
>>> I cooked up a small API that does just this. Simply put, it's just an
>>> implementation of a HiveFactory which acts as a Builder. I plan to
>>> publish
>>> some time in the near future but there are several small issues that I'd
>>> like to solve first.
>>>
>>> Right now the usage of the API looks like this:
>>>
>>> BuilderHiveFactory hiveFactory = new BuilderHiveFactory();
>>> Principal principal = new SimplePrincipal("whatever");
>>> Set<Class<? extends WaspAction>> actions = ...;
>>> actions.add(Inherit.class);
>>> actions.add(Render.class);
>>> actions.add(Enable.class);
>>>
>>> hiveFactory.addComponentPermission(principal, MySecurePage.class,
>>> actions);
>>>
>>> I would love to get your thoughts and input on this kind of HiveFactory.
>>>
>> Sounds like a usable contribution :)
>> The whole idea of the Wasp and Swarm for that matter is that if you
>> don't like a part of it you easily implement it yourself.
>> Configuration of all the permissions is only a first step.
>> Even i don't use the default policy file reader, we do use policy
>> files but i added some extra scripting support (haven't decided yet if
>> it something that is really re-usable by others).
>> So if anyone has anything that he/she thinks is reusable, just let me
>> know.
>>
>> Maurice
>>
>>
>>> regards,
>>> Guðmundur Bjarni
>>>
>>>
>>
>
>
--
-Wicket for love
Nino Martinez Wael
Java Specialist @ Jayway DK
http://www.jayway.dk
+45 2936 7684
Re: Swarm & Wicket 1.4 m2
Posted by RUMikeP <mi...@rucus.net>.
My ZAR0.02 worth (a lot less than $0.02 ;-)
I have to be honest, that initially I was also a bit confused, but once you
take half an hour to work though it, it is REALLY powerful and customisable.
It you are building an application end-to-end from scratch, and are using
Wicket for the UI, it may be tempting to build in the security concepts in
the UI. However, larger corporates generally have a mix legacy and newer
security mechanisms that one needs to integrate with, and (maybe it is just
the projects that I need to implement, but) generally the Wicket UI is
designed to sit on top of an existing backend. Therefore, you can almost
guarantee that you will need to authenticate against some external system,
obtain a list of groups and or roles granted to that user and then map those
groups/roles to permissions to perform certain actions on the UI layer.
Swarm fulfils this role perfectly in our situation, and the fact that it is
decoupled from the core Wicket UI code, provides a high level of comfort
that we could replace the Swarm implementation with a different custom
implementation if necessary without a major rework of the UI code.
I have made use of Swarm out-of-the-box except for creating a
PolicyDatabaseHiveFactory to read in the role-to-permission mappings from a
database table. It would be just as simple to create a Policy Hive Factory
that builds up the mapping in Java code rather than reading it from a
properties file or database table, i.e. by creating your own implementation
of one class, it gives you a security implementation based on your
preference for where the mapping is stored/implemented.
I am not saying it is a perfect fit for everyone, but I do believe that the
Wicket Community needs to more actively promote the use of Swarm (where
appropriate) and I really would like to see more people using it so that
there is a larger pool of knowledgeable resources to assist and guide newer
users (especially since there is a plan to make it part of core in 1.5)
Mike
Mr Mean wrote:
>
> On Mon, Jul 7, 2008 at 6:01 PM, Guðmundur Bjarni Ólafsson
> <gu...@gmail.com> wrote:
>> On Mon, Jul 7, 2008 at 5:50 PM, James Carman <ja...@carmanconsulting.com>
>> wrote:
>>
>>> I'm not trying to flame here or anything, but from what I've read of
>>> Swarm/Wasp, it's quite complicated and that would go against the
>>> spirit of Wicket, IMHO. Also, it uses external files for
>>> configuration. Again, this goes against the spirit of Wicket.
>>> Perhaps if there were a programmatic way of configuring everything?
>>> Again, I've never used it, but I've seen responses on the lists about
>>> how to do things and it just scared me away from it. That's just my
>>> $0.02. To be fair, maybe I should play with it a bit to see it for
>>> myself, but I haven't had the cycles. Sorry.
>>>
>>
>>
>> I cooked up a small API that does just this. Simply put, it's just an
>> implementation of a HiveFactory which acts as a Builder. I plan to
>> publish
>> some time in the near future but there are several small issues that I'd
>> like to solve first.
>>
>> Right now the usage of the API looks like this:
>>
>> BuilderHiveFactory hiveFactory = new BuilderHiveFactory();
>> Principal principal = new SimplePrincipal("whatever");
>> Set<Class<? extends WaspAction>> actions = ...;
>> actions.add(Inherit.class);
>> actions.add(Render.class);
>> actions.add(Enable.class);
>>
>> hiveFactory.addComponentPermission(principal, MySecurePage.class,
>> actions);
>>
>> I would love to get your thoughts and input on this kind of HiveFactory.
>
> Sounds like a usable contribution :)
> The whole idea of the Wasp and Swarm for that matter is that if you
> don't like a part of it you easily implement it yourself.
> Configuration of all the permissions is only a first step.
> Even i don't use the default policy file reader, we do use policy
> files but i added some extra scripting support (haven't decided yet if
> it something that is really re-usable by others).
> So if anyone has anything that he/she thinks is reusable, just let me
> know.
>
> Maurice
>
>>
>> regards,
>> Guðmundur Bjarni
>>
>
>
--
View this message in context: http://www.nabble.com/Swarm---Wicket-1.4-m2-tp18304937p18355348.html
Sent from the Wicket - Dev mailing list archive at Nabble.com.
Re: Swarm & Wicket 1.4 m2
Posted by Maurice Marrink <ma...@gmail.com>.
On Mon, Jul 7, 2008 at 6:01 PM, Guðmundur Bjarni Ólafsson
<gu...@gmail.com> wrote:
> On Mon, Jul 7, 2008 at 5:50 PM, James Carman <ja...@carmanconsulting.com>
> wrote:
>
>> I'm not trying to flame here or anything, but from what I've read of
>> Swarm/Wasp, it's quite complicated and that would go against the
>> spirit of Wicket, IMHO. Also, it uses external files for
>> configuration. Again, this goes against the spirit of Wicket.
>> Perhaps if there were a programmatic way of configuring everything?
>> Again, I've never used it, but I've seen responses on the lists about
>> how to do things and it just scared me away from it. That's just my
>> $0.02. To be fair, maybe I should play with it a bit to see it for
>> myself, but I haven't had the cycles. Sorry.
>>
>
>
> I cooked up a small API that does just this. Simply put, it's just an
> implementation of a HiveFactory which acts as a Builder. I plan to publish
> some time in the near future but there are several small issues that I'd
> like to solve first.
>
> Right now the usage of the API looks like this:
>
> BuilderHiveFactory hiveFactory = new BuilderHiveFactory();
> Principal principal = new SimplePrincipal("whatever");
> Set<Class<? extends WaspAction>> actions = ...;
> actions.add(Inherit.class);
> actions.add(Render.class);
> actions.add(Enable.class);
>
> hiveFactory.addComponentPermission(principal, MySecurePage.class, actions);
>
> I would love to get your thoughts and input on this kind of HiveFactory.
Sounds like a usable contribution :)
The whole idea of the Wasp and Swarm for that matter is that if you
don't like a part of it you easily implement it yourself.
Configuration of all the permissions is only a first step.
Even i don't use the default policy file reader, we do use policy
files but i added some extra scripting support (haven't decided yet if
it something that is really re-usable by others).
So if anyone has anything that he/she thinks is reusable, just let me know.
Maurice
>
> regards,
> Guðmundur Bjarni
>
Re: Swarm & Wicket 1.4 m2
Posted by James Carman <ja...@carmanconsulting.com>.
On Mon, Jul 7, 2008 at 12:01 PM, Guðmundur Bjarni Ólafsson
<gu...@gmail.com> wrote:
> I cooked up a small API that does just this. Simply put, it's just an
> implementation of a HiveFactory which acts as a Builder. I plan to publish
> some time in the near future but there are several small issues that I'd
> like to solve first.
>
> Right now the usage of the API looks like this:
>
> BuilderHiveFactory hiveFactory = new BuilderHiveFactory();
> Principal principal = new SimplePrincipal("whatever");
> Set<Class<? extends WaspAction>> actions = ...;
> actions.add(Inherit.class);
> actions.add(Render.class);
> actions.add(Enable.class);
>
> hiveFactory.addComponentPermission(principal, MySecurePage.class, actions);
>
> I would love to get your thoughts and input on this kind of HiveFactory.
Well, that's exactly what I'm talking about! I really hated putting
stuff into external files when one of the biggest selling points about
Wicket was the fact that there are no configuration files necessary
(aside from the simple hook in the web.xml file of course). I'm not
familiar enough with the configuration stuff yet, but the idea is just
what I'm looking for.
Re: Swarm & Wicket 1.4 m2
Posted by Guðmundur Bjarni Ólafsson <gu...@gmail.com>.
On Mon, Jul 7, 2008 at 5:50 PM, James Carman <ja...@carmanconsulting.com>
wrote:
> I'm not trying to flame here or anything, but from what I've read of
> Swarm/Wasp, it's quite complicated and that would go against the
> spirit of Wicket, IMHO. Also, it uses external files for
> configuration. Again, this goes against the spirit of Wicket.
> Perhaps if there were a programmatic way of configuring everything?
> Again, I've never used it, but I've seen responses on the lists about
> how to do things and it just scared me away from it. That's just my
> $0.02. To be fair, maybe I should play with it a bit to see it for
> myself, but I haven't had the cycles. Sorry.
>
I cooked up a small API that does just this. Simply put, it's just an
implementation of a HiveFactory which acts as a Builder. I plan to publish
some time in the near future but there are several small issues that I'd
like to solve first.
Right now the usage of the API looks like this:
BuilderHiveFactory hiveFactory = new BuilderHiveFactory();
Principal principal = new SimplePrincipal("whatever");
Set<Class<? extends WaspAction>> actions = ...;
actions.add(Inherit.class);
actions.add(Render.class);
actions.add(Enable.class);
hiveFactory.addComponentPermission(principal, MySecurePage.class, actions);
I would love to get your thoughts and input on this kind of HiveFactory.
regards,
Guðmundur Bjarni
Re: Swarm & Wicket 1.4 m2
Posted by James Carman <ja...@carmanconsulting.com>.
On Mon, Jul 7, 2008 at 11:38 AM, Maurice Marrink <ma...@gmail.com> wrote:
> No particular reason other then that we are trying to make the
> migration from wicket 1.3 to wicket 1.4 as small as possible.
> There has not been an official vote on this yet but the plan is to
> integrate it in wicket 1.5 which we will begin working on shortly
> after 1.4 has been released.
I'm not trying to flame here or anything, but from what I've read of
Swarm/Wasp, it's quite complicated and that would go against the
spirit of Wicket, IMHO. Also, it uses external files for
configuration. Again, this goes against the spirit of Wicket.
Perhaps if there were a programmatic way of configuring everything?
Again, I've never used it, but I've seen responses on the lists about
how to do things and it just scared me away from it. That's just my
$0.02. To be fair, maybe I should play with it a bit to see it for
myself, but I haven't had the cycles. Sorry.
Re: Swarm & Wicket 1.4 m2
Posted by Maurice Marrink <ma...@gmail.com>.
On Mon, Jul 7, 2008 at 3:39 PM, Korbinian Bachl - privat
<ko...@whiskyworld.de> wrote:
> Hi Maurice,
>
> thx for the info. Im using the "use old wicket authentication thingy"
> workaround then :)
>
> Would be cool if wicket 1.4m3 up or so would be compatible to swarm...
> however, do you think it would be possible for you to do a wicket 1.4 branch
> of swarm/ wasp then? Im quite busy but maybe someone can grab a bit of time
> to dig a bit in, as I somehow like the idea - after I read the doc and your
> presentation several times - of SWARM for wicket apps (especially as its
> something wicket really needs).
I know, I'm actually a bit pissed at myself for not having it done
yet. Really need to make some time for this.
>
> Is there a reason why swarm/ wasp is not going to core for 1.4 ?
No particular reason other then that we are trying to make the
migration from wicket 1.3 to wicket 1.4 as small as possible.
There has not been an official vote on this yet but the plan is to
integrate it in wicket 1.5 which we will begin working on shortly
after 1.4 has been released.
Maurice
>
> Best,
>
> Korbinian
>
>
> Maurice Marrink schrieb:
>>
>> Sorry, atm wasp/swarm is not yet compatible with wicket 1.4.
>> I am waiting for at least a beta of wasp/swarm 1.3.1 before i start
>> working on version 1.4.
>> I realize 1.3.1 is long overdue and try to get it out as soon as possible.
>> In the meantime sorry for the inconvenience.
>> I am afraid your only option at this time is to check out the entire
>> wicket security project from svn and patch it to compile against
>> wicket 1.4
>> Again sorry for the inconvenience.
>>
>> Maurice
>>
>> On Sun, Jul 6, 2008 at 8:19 PM, Korbinian Bachl - privat
>> <ko...@whiskyworld.de> wrote:
>>>
>>> Hello,
>>>
>>> I just spend some time to change my app (on wicket 1.4) to use the SWARM
>>> implementation of WASP.
>>>
>>> However, it seems that WASP 1.3.0 as well as the current 1.3-Snapshot
>>> (1.3.1) wont work with 1.4; The error is nearly allways the same:
>>>
>>>
>>> 1.3.1:
>>> "
>>> java.lang.NoSuchMethodError:
>>> org.apache.wicket.MetaDataKey.<init>(Ljava/lang/Class;)V
>>>
>>>
>>> org.apache.wicket.security.log.AuthorizationErrorKey.<init>(AuthorizationErrorKey.java:41)
>>>
>>>
>>> org.apache.wicket.security.strategies.WaspAuthorizationStrategy.<clinit>(WaspAuthorizationStrategy.java:57)
>>>
>>>
>>> org.apache.wicket.security.swarm.strategies.SwarmStrategyFactory.newStrategy(SwarmStrategyFactory.java:80)
>>> org.apache.wicket.security.WaspSession.<init>(WaspSession.java:48)
>>>
>>>
>>> org.apache.wicket.security.WaspWebApplication.newSession(WaspWebApplication.java:71)
>>> org.apache.wicket.Session.findOrCreate(Session.java:231)
>>> org.apache.wicket.Session.findOrCreate(Session.java:214)
>>> org.apache.wicket.Session.get(Session.java:253)
>>> org.apache.wicket.RequestCycle.getSession(RequestCycle.java:436)
>>>
>>>
>>> org.apache.wicket.request.AbstractRequestCycleProcessor.resolveHomePageTarget(AbstractRequestCycleProcessor.java:315)
>>>
>>>
>>> org.apache.wicket.protocol.http.WebRequestCycleProcessor.resolve(WebRequestCycleProcessor.java:159)
>>> org.apache.wicket.RequestCycle.step(RequestCycle.java:1246)
>>> org.apache.wicket.RequestCycle.steps(RequestCycle.java:1366)
>>> org.apache.wicket.RequestCycle.request(RequestCycle.java:499)
>>>
>>>
>>> org.apache.wicket.protocol.http.WicketFilter.doGet(WicketFilter.java:387)
>>>
>>>
>>> org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:199)
>>>
>>> "
>>>
>>> and 1.3.0:
>>>
>>> "
>>> java.lang.NoSuchMethodError:
>>> org.apache.wicket.MetaDataKey.<init>(Ljava/lang/Class;)V
>>> org.apache.wicket.security.checks.WaspKey.<init>(WaspKey.java:41)
>>>
>>>
>>> org.apache.wicket.security.components.SecureComponentHelper.getSecurityCheck(SecureComponentHelper.java:55)
>>>
>>>
>>> org.apache.wicket.security.strategies.WaspAuthorizationStrategy.getSecurityCheck(WaspAuthorizationStrategy.java:185)
>>>
>>>
>>> org.apache.wicket.security.strategies.WaspAuthorizationStrategy.isActionAuthorized(WaspAuthorizationStrategy.java:159)
>>> org.apache.wicket.Component.isActionAuthorized(Component.java:1983)
>>> org.apache.wicket.Page.renderPage(Page.java:855)
>>>
>>>
>>> org.apache.wicket.request.target.component.BookmarkablePageRequestTarget.respond(BookmarkablePageRequestTarget.java:241)
>>>
>>>
>>> org.apache.wicket.request.AbstractRequestCycleProcessor.respond(AbstractRequestCycleProcessor.java:104)
>>>
>>>
>>> org.apache.wicket.RequestCycle.processEventsAndRespond(RequestCycle.java:1194)
>>> org.apache.wicket.RequestCycle.step(RequestCycle.java:1265)
>>> org.apache.wicket.RequestCycle.steps(RequestCycle.java:1366)
>>> org.apache.wicket.RequestCycle.request(RequestCycle.java:499)
>>>
>>>
>>> org.apache.wicket.protocol.http.WicketFilter.doGet(WicketFilter.java:387)
>>>
>>>
>>> org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:199)
>>>
>>> "
>>>
>>> Is there any workaround Maurice?
>>>
>>> Best,
>>>
>>> Korbinian
>>>
>
Re: Swarm & Wicket 1.4 m2
Posted by Korbinian Bachl - privat <ko...@whiskyworld.de>.
Hi Maurice,
thx for the info. Im using the "use old wicket authentication thingy"
workaround then :)
Would be cool if wicket 1.4m3 up or so would be compatible to swarm...
however, do you think it would be possible for you to do a wicket 1.4
branch of swarm/ wasp then? Im quite busy but maybe someone can grab a
bit of time to dig a bit in, as I somehow like the idea - after I read
the doc and your presentation several times - of SWARM for wicket apps
(especially as its something wicket really needs).
Is there a reason why swarm/ wasp is not going to core for 1.4 ?
Best,
Korbinian
Maurice Marrink schrieb:
> Sorry, atm wasp/swarm is not yet compatible with wicket 1.4.
> I am waiting for at least a beta of wasp/swarm 1.3.1 before i start
> working on version 1.4.
> I realize 1.3.1 is long overdue and try to get it out as soon as possible.
> In the meantime sorry for the inconvenience.
> I am afraid your only option at this time is to check out the entire
> wicket security project from svn and patch it to compile against
> wicket 1.4
> Again sorry for the inconvenience.
>
> Maurice
>
> On Sun, Jul 6, 2008 at 8:19 PM, Korbinian Bachl - privat
> <ko...@whiskyworld.de> wrote:
>> Hello,
>>
>> I just spend some time to change my app (on wicket 1.4) to use the SWARM
>> implementation of WASP.
>>
>> However, it seems that WASP 1.3.0 as well as the current 1.3-Snapshot
>> (1.3.1) wont work with 1.4; The error is nearly allways the same:
>>
>>
>> 1.3.1:
>> "
>> java.lang.NoSuchMethodError:
>> org.apache.wicket.MetaDataKey.<init>(Ljava/lang/Class;)V
>>
>> org.apache.wicket.security.log.AuthorizationErrorKey.<init>(AuthorizationErrorKey.java:41)
>>
>> org.apache.wicket.security.strategies.WaspAuthorizationStrategy.<clinit>(WaspAuthorizationStrategy.java:57)
>>
>> org.apache.wicket.security.swarm.strategies.SwarmStrategyFactory.newStrategy(SwarmStrategyFactory.java:80)
>> org.apache.wicket.security.WaspSession.<init>(WaspSession.java:48)
>>
>> org.apache.wicket.security.WaspWebApplication.newSession(WaspWebApplication.java:71)
>> org.apache.wicket.Session.findOrCreate(Session.java:231)
>> org.apache.wicket.Session.findOrCreate(Session.java:214)
>> org.apache.wicket.Session.get(Session.java:253)
>> org.apache.wicket.RequestCycle.getSession(RequestCycle.java:436)
>>
>> org.apache.wicket.request.AbstractRequestCycleProcessor.resolveHomePageTarget(AbstractRequestCycleProcessor.java:315)
>>
>> org.apache.wicket.protocol.http.WebRequestCycleProcessor.resolve(WebRequestCycleProcessor.java:159)
>> org.apache.wicket.RequestCycle.step(RequestCycle.java:1246)
>> org.apache.wicket.RequestCycle.steps(RequestCycle.java:1366)
>> org.apache.wicket.RequestCycle.request(RequestCycle.java:499)
>>
>> org.apache.wicket.protocol.http.WicketFilter.doGet(WicketFilter.java:387)
>>
>> org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:199)
>>
>> "
>>
>> and 1.3.0:
>>
>> "
>> java.lang.NoSuchMethodError:
>> org.apache.wicket.MetaDataKey.<init>(Ljava/lang/Class;)V
>> org.apache.wicket.security.checks.WaspKey.<init>(WaspKey.java:41)
>>
>> org.apache.wicket.security.components.SecureComponentHelper.getSecurityCheck(SecureComponentHelper.java:55)
>>
>> org.apache.wicket.security.strategies.WaspAuthorizationStrategy.getSecurityCheck(WaspAuthorizationStrategy.java:185)
>>
>> org.apache.wicket.security.strategies.WaspAuthorizationStrategy.isActionAuthorized(WaspAuthorizationStrategy.java:159)
>> org.apache.wicket.Component.isActionAuthorized(Component.java:1983)
>> org.apache.wicket.Page.renderPage(Page.java:855)
>>
>> org.apache.wicket.request.target.component.BookmarkablePageRequestTarget.respond(BookmarkablePageRequestTarget.java:241)
>>
>> org.apache.wicket.request.AbstractRequestCycleProcessor.respond(AbstractRequestCycleProcessor.java:104)
>>
>> org.apache.wicket.RequestCycle.processEventsAndRespond(RequestCycle.java:1194)
>> org.apache.wicket.RequestCycle.step(RequestCycle.java:1265)
>> org.apache.wicket.RequestCycle.steps(RequestCycle.java:1366)
>> org.apache.wicket.RequestCycle.request(RequestCycle.java:499)
>>
>> org.apache.wicket.protocol.http.WicketFilter.doGet(WicketFilter.java:387)
>>
>> org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:199)
>>
>> "
>>
>> Is there any workaround Maurice?
>>
>> Best,
>>
>> Korbinian
>>
Re: Swarm & Wicket 1.4 m2
Posted by Maurice Marrink <ma...@gmail.com>.
Sorry, atm wasp/swarm is not yet compatible with wicket 1.4.
I am waiting for at least a beta of wasp/swarm 1.3.1 before i start
working on version 1.4.
I realize 1.3.1 is long overdue and try to get it out as soon as possible.
In the meantime sorry for the inconvenience.
I am afraid your only option at this time is to check out the entire
wicket security project from svn and patch it to compile against
wicket 1.4
Again sorry for the inconvenience.
Maurice
On Sun, Jul 6, 2008 at 8:19 PM, Korbinian Bachl - privat
<ko...@whiskyworld.de> wrote:
> Hello,
>
> I just spend some time to change my app (on wicket 1.4) to use the SWARM
> implementation of WASP.
>
> However, it seems that WASP 1.3.0 as well as the current 1.3-Snapshot
> (1.3.1) wont work with 1.4; The error is nearly allways the same:
>
>
> 1.3.1:
> "
> java.lang.NoSuchMethodError:
> org.apache.wicket.MetaDataKey.<init>(Ljava/lang/Class;)V
>
> org.apache.wicket.security.log.AuthorizationErrorKey.<init>(AuthorizationErrorKey.java:41)
>
> org.apache.wicket.security.strategies.WaspAuthorizationStrategy.<clinit>(WaspAuthorizationStrategy.java:57)
>
> org.apache.wicket.security.swarm.strategies.SwarmStrategyFactory.newStrategy(SwarmStrategyFactory.java:80)
> org.apache.wicket.security.WaspSession.<init>(WaspSession.java:48)
>
> org.apache.wicket.security.WaspWebApplication.newSession(WaspWebApplication.java:71)
> org.apache.wicket.Session.findOrCreate(Session.java:231)
> org.apache.wicket.Session.findOrCreate(Session.java:214)
> org.apache.wicket.Session.get(Session.java:253)
> org.apache.wicket.RequestCycle.getSession(RequestCycle.java:436)
>
> org.apache.wicket.request.AbstractRequestCycleProcessor.resolveHomePageTarget(AbstractRequestCycleProcessor.java:315)
>
> org.apache.wicket.protocol.http.WebRequestCycleProcessor.resolve(WebRequestCycleProcessor.java:159)
> org.apache.wicket.RequestCycle.step(RequestCycle.java:1246)
> org.apache.wicket.RequestCycle.steps(RequestCycle.java:1366)
> org.apache.wicket.RequestCycle.request(RequestCycle.java:499)
>
> org.apache.wicket.protocol.http.WicketFilter.doGet(WicketFilter.java:387)
>
> org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:199)
>
> "
>
> and 1.3.0:
>
> "
> java.lang.NoSuchMethodError:
> org.apache.wicket.MetaDataKey.<init>(Ljava/lang/Class;)V
> org.apache.wicket.security.checks.WaspKey.<init>(WaspKey.java:41)
>
> org.apache.wicket.security.components.SecureComponentHelper.getSecurityCheck(SecureComponentHelper.java:55)
>
> org.apache.wicket.security.strategies.WaspAuthorizationStrategy.getSecurityCheck(WaspAuthorizationStrategy.java:185)
>
> org.apache.wicket.security.strategies.WaspAuthorizationStrategy.isActionAuthorized(WaspAuthorizationStrategy.java:159)
> org.apache.wicket.Component.isActionAuthorized(Component.java:1983)
> org.apache.wicket.Page.renderPage(Page.java:855)
>
> org.apache.wicket.request.target.component.BookmarkablePageRequestTarget.respond(BookmarkablePageRequestTarget.java:241)
>
> org.apache.wicket.request.AbstractRequestCycleProcessor.respond(AbstractRequestCycleProcessor.java:104)
>
> org.apache.wicket.RequestCycle.processEventsAndRespond(RequestCycle.java:1194)
> org.apache.wicket.RequestCycle.step(RequestCycle.java:1265)
> org.apache.wicket.RequestCycle.steps(RequestCycle.java:1366)
> org.apache.wicket.RequestCycle.request(RequestCycle.java:499)
>
> org.apache.wicket.protocol.http.WicketFilter.doGet(WicketFilter.java:387)
>
> org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:199)
>
> "
>
> Is there any workaround Maurice?
>
> Best,
>
> Korbinian
>