Gary I looked at Rolodex example. I think this method is useful for more
nested components rite? But for this simple case do you think it is a good
practise to use this method?
On 9/21/05, Gary VanMatre <[EMAIL PROTECTED]> wrote:
>
> > >I am trying to setup Acegi security for my project.
> > >
> > >I have these following files.
> > >
> > >1) good.html -- Protected Resource
> > >2) login.html -- Unprotected Resource
> > >
> > >login.html is a standard html that has
> > ><form action="j_acegi_security_check" method="POST">
> > >
> > >When I access good.html , acegi filter redirects it to login.html. Clay
> > >filter identifies that it needs to render login.html and renders it.
> > >Obiviously when login.html is rendered , clay changes the <form> tag to
> > ><form id="clayView:_id0:_id63" method="post"
> action="/docs/login_acegi.html"
> > >enctype="application/x-www-form-urlencoded">
> > >
> > >Is there a way I could bypass Clay for login.html alone. Or is there a
> way
> > >to instruct Clay not to change the action for login.html.
> >
> > You might try renaming your login.html to login.htm. I think that should
> work.
> > Full html clay views look at the suffix of the view id. It sounds like
> you have
> > overridden the default and are using "*.html".
> >
>
> Another way to handle it would be to use the "*.html" suffix and create a
> clay RUNTIME component to render a form and it's content. I don't think the
> XML would work because you would have to excape it.
>
> <span jsfid="clay" shapeValidator="#{managed-bean-name.shapeForm}" />
>
> The shapeValidator event is a Validator method binding signature. It
> allows you to build meta-component elements that is used to construct the
> subtree. The basic idea is that you create a graph of the same objects used
> by the digester when reading the XML config files. The rolodex usecase
> example creates the tabs using this method.
>
> Gary
>
> > >Rgds,
> > >--Siva Jagadeesan
> >
> > Gary
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > 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]
>
>
