Discussion:
[errai-users] Ways around @ExposeEntity
Asgeir Frimannsson
2010-04-14 00:37:56 UTC
Permalink
Hi all,
From the documentation, one of the requirements for serialization is
the use of an @ExposeEntity annotation. Is there any ways around this,
so that I can send POJOs generated by frameworks which doesn't know
about Errai (but still follow GWT RPC serialization rules)?

If not, would it be possible to get rid of it? ;-)

For instance, by e.g.:
a) Following a similar 'white-list' approach that GWT uses, or
b) Define an annotation where I could add my exposed entities, such as
@ExposedEntities({
MyPOJO.class
MyOtherPojo.class
})

Any hints or approaches appreciated!

cheers,
asgeir
Mike Brock
2010-04-14 16:15:08 UTC
Permalink
We are working on a way of doing just that. It's definitely on our priority list. Hopefully we will provide such an annotation and/or a configuration file to allow you define external entities. We will move this up on our priority list -- as you're not the first to ask about this.

Mike.
Post by Asgeir Frimannsson
Hi all,
From the documentation, one of the requirements for serialization is
so that I can send POJOs generated by frameworks which doesn't know
about Errai (but still follow GWT RPC serialization rules)?
If not, would it be possible to get rid of it? ;-)
a) Following a similar 'white-list' approach that GWT uses, or
b) Define an annotation where I could add my exposed entities, such as
@ExposedEntities({
MyPOJO.class
MyOtherPojo.class
})
Any hints or approaches appreciated!
cheers,
asgeir
_______________________________________________
errai-users mailing list
errai-users at lists.jboss.org
https://lists.jboss.org/mailman/listinfo/errai-users
Loading...