Otherwise it cause trouble with multiple datasource using ebean as when entity class is not supplied by act (via @Db annotation specified) it will be loaded by Ebean using a different class loader than Act's app class loader, and cause type casting issue.
Otherwise it cause trouble with multiple datasource using ebean as when entity class is not supplied by act (via @Db annotation specified) it will be loaded by Ebean using a different class loader than Act's app class loader, and cause type casting issue.