3 Replies Latest reply on Jan 22, 2013 6:17 PM by csa

How to add and EventHandler to an @Templated component?

mdhirsch30345 Jan 16, 2013 6:09 PM

I have an @Templated class which extends composite. In the Errai-UI documentation https://docs.jboss.org/author/display/ERRAI/Errai+UI#ErraiUI-Concepts is says:

Event handler methods annotated with a bare @EventHandler annotation (no annotation parameter) are wired to receive events on the @Templated component itself.

If I try to use a base @EventHandler My IDE shows this as an error and the build fails with

annotation org.jboss.errai.ui.shared.api.annotations.EventHandler is missing value

Strangely, devmode doesn't give me an error, but the page never loads--it just shows a blank page.

Is there a way to add and EventHandler to my templated class?

Thanks,

Michael

1. Re: How to add and EventHandler to an @Templated component?

csa Jan 17, 2013 12:38 AM (in response to mdhirsch30345)

Hi Michael,

Which version of Errai are you using? This feature (@EventHandlers without parameters defaulting to this) was introduced in Errai 2.2.0.CR1.

Here's an example using the feature:
https://github.com/errai/errai/blob/master/errai-jpa/demos/errai-jpa-demo-todo-list/src/main/java/org/jboss/errai/demo/todo/client/local/TodoItemWidget.java

Cheers,
Christian
Actions
2. Re: How to add and EventHandler to an @Templated component?

mdhirsch30345 Jan 22, 2013 6:04 PM (in response to csa)

That's it, Christian. I am still on 2.1.0. I didn't realize that the docs are available like that for the next release. I'll have to see if I can restrict myself to reading only published docs.

Would it be possible for the docs to indicate when a feature was introduced? I love that feature of the Java javadocs. If I end up reading the 1.7 docs I can tell if the feature is in 1.5.

Thanks,

Michael
Actions
3. Re: How to add and EventHandler to an @Templated component?

csa Jan 22, 2013 6:17 PM (in response to mdhirsch30345)

Yes, we started adding "since" annotations to chapters in confluence at some point, but removed them when we realized that we had to process them manually in the exported docs for releases (because e.g. all chapters in the released docs should refer to functionality that's actually available in that release). I still think having these annotations is a good idea but we need to automate our doc export more.
Actions

Go to original post