Thanks a lot again, Maurice, this time it was just the question of syntax.
In fact, is there a description of the .hive file syntax somewhere, or at
least a really complex .hive file to look at?
On Sun, Jun 29, 2008 at 4:38 PM, Maurice Marrink <[EMAIL PROTECTED]> wrote:
> In version 1.3.0 inheritance is somewhat limited. It can only follow
> absolute paths.
> So unless your ${SecuredTextFieldOne} alias resolves to something like
> this: PageClass:panel1ID:panel2ID:textfieldID it will not work.
>
> This has been fixed in 1.3-SNAPSHOT where you can now use container
> classes in the same way as pages. If you can switch to that version
> something like org.mypackage.SecurePanelTwo:textfieldID should do the
> trick or if you want to be more precise
> PageClass:Panel1Class:Panel2Class:textfieldID
>
> Hope this helps.
>
> Maurice
>
> On Thu, Jun 26, 2008 at 11:00 PM, Sergey Podatelev
> <[EMAIL PROTECTED]> wrote:
> > Hello,
> >
> > I'm using Wicket-Security-1.3, and can't enable SecureTextFields.
> > The SecureTextField sitting in a panel, which extends SecurePanel, which
> > sits in another secured panel, and all this is on SecureWebPage.
> >
> > The problem is, no matter what I write in my policies.hive file, that
> > textfield won't allow to write to it. It's displayed as disabled input.
> >
> > policies.hive:
> >
> > grant principal ${DefaultPrincipal} "testuser"
> > {
> > permission ${ComponentPermission} "${SecurePageOne}", "inherit, render";
> > permission ${ComponentPermission} "${SecurePageOne}", "enable";
> >
> > permission ${ComponentPermission} "${SecurePanelOne}", "inherit,
> render";
> > permission ${ComponentPermission} "${SecurePanelOne}", "enable";
> >
> > permission ${ComponentPermission} "${SecurePanelTwo}", "inherit,
> render";
> > permission ${ComponentPermission} "${SecurePanelTwo}", "enable";
> >
> > permission ${ComponentPermission} "${SecuredTextFieldOne}", "render,
> > enable";
> >
> > };
> >
> > SecurePanelTwo.java:
> >
> > public class SecurePanelTwo extends SecurePanel {
> > public SecurePanelTwo(String id) {
> > super(id);
> >
> > SecureTextFieldOne someField = new SecureTextFieldOne("someId");
> > add(someField);
> >
> > }
> >
> > class SecureTextFieldOne extends SecureTextField {
> > public SecureTextFieldOne(String id) {
> > super(id);
> > }
> > }
> > }
> >
> > In LianetApplications, all those aliases are set properly.
> >
> > --
> > sp
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
sp