On Sun, May 25, 2008 at 8:40 PM, Tim Russell <[EMAIL PROTECTED]> wrote:
> I'm trying to get a feel of how suitable swarm is for an application -
> particularly how much support for what we need is handled by swarm/wasp and
> how much we need to write ourselves.
> swarm looks good, eg
> http://wicketstuff.org/confluence/display/STUFFWIKI/Getting+started+with+Swarm
>
> At the minute II have a couple of questions:
> - do I have to assign Principals programmatically - or does swarm enable
> declarative of users/subjects mapping to Principals?
You need to assign principals to subjects yourself in the
LoginContext, Swarm does not make any automatic assumptions for you.
> - can I set up two different ComponentPermissions for two instances of the
> same type of component (eg SecureTextField)?: it looks like the declarative
> permissions are on a class basis rather than instance basis.
Sure, i'm guessing you have mostly seen permissions dealing with the
entire page but you can just as easy append a componentpath:
permission ${ComponentPermission}
"org.SomePage:container:myForm:textfield1" "render"; //full path
specified
If you use 1.3-SNAPSHOT you can even do
permission ${ComponentPermission}
"org.apache.wicket.markup.html.form.Form:textfield1" "render";
//partial path
which will grant render permissions to every "textfield1" nested
inside a form (regardless of the page)
Maurice
>
> Thanks,
> Tim
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
