Le 28/06/2013 13:40, Thiago H de Paula Figueiredo a écrit :
On Fri, 28 Jun 2013 08:14:21 -0300, Raphaël Ouazana-Sustowski
<raphael.ouaz...@linagora.com> wrote:
Do you need the field in onProvideCompletions()?
Yes I do. My purpose is to do a generic autocomplete editor. So I
need some configuration that is in the context.
Which configuration? Just curious. :)
In this case LDAP configuration. We use beanEditors to make CRUD on
LDAP entries. Some LDAP attributes can be links to other LDAP entries.
So, depending on the attribute type, I will provide different
autocompletions. Ex: a peopleLink attribute will look in the ou=people
LDAP branch for the uid attribute, while a structureLink attribute will
look in the ou=structures LDAP branch for the ou attribute.
If you are really curious, you can look at the project:
https://redmine.linid.org/projects/directory-manager
I already tried to make different editors for each configuration
type, and it works.
Nice. :)
Yes, but I'd like something more generic :)
Isn't this an issue that the context is not available in Ajax
requests?
Exactly (for "context" = "PropertyEditConstant", not activation
context, so people don't misunderstand what we're talking about here,
which is advanced Tapestry). The context is pushed by BeanEditor
(which is the basis of BeanEditForm) while it (BeanEditor) is
rendered, and it is not rendered in AJAX requests (except when the
AJAX requests renders the BeanEditor, such as in Zone updates which
have a BeanEditor inside).
I see. Do you think I can open a feature request about this and that it
has a chance to be fixed?
Regards,
Raphaël Ouazana.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
