It would seem that Autocomplete needs a context. Please vote here:
https://issues.apache.org/jira/browse/TAP5-2329
Cheers,
Geoff
On 1 May 2014, at 6:59 am, Erich Gormann wrote:
> Hi all,
>
> currently I work with a number of autocomplete fields rendered in a loop.
> And thats exactl
Hi all,
currently I work with a number of autocomplete fields rendered in a loop.
And thats exactly the problem: after the loop and all fields have been
rendered, I'am not able to handle over a piece of specific information to
the onCompletion event, if this event handler is called on entering so
From my experience, you really don't want to put CommitAfter on a generic
method like that.
It really doesn't do what you expect in code like this:
void saveSomeData(List widgets) {
for (Widget w: widgets) {
widgetDao.saveWidget(widget);
}
}
In that case, assuming saveWidget is annotate
Hi,
I try to use the CommitAfter on a GenericDao, but the method does not
commit the transaction. Does it exists a worcaround to do that?
This is the code:
public interface GenericDao {
@CommitAfter
public void save(T entity);
}
public abstract class GenericDaoImpl {
@Override
pu
