How to exclude entities from the scope of Errai JPA when compiling

[vwjugow]

Hi everyone.

I'm using Errai 3.0.0-Final (currently upgrating to 3.0.2-Final)

I want to add the org.jboss.errai.jpa.JPA module to my application. I will use it with only one simple entity for the moment. However I have several other entities in another gwt module which I am including in my .gwt.xml file. So, after adding jpa dependency and module, my app stopped compiling due to some JPA errors in some of the other entities which I don't want to use with Errai JPA (e.g it complaints about not supporting autogenerated Id String fields) (I do use them in hibernate and in both client and server side, so I can't remove the @Entity annotation nor just exclude them from my project). Is there any way of excluding these entities from the scope of Errai JPA ?

Thanks in advance.

Victor.-

[csa]

Hi Victor,

There are currently only two options for hiding @Entity types from our JPA scanner.

1. Move the types to a non-translatable package

2. Put it in a jar/module without an ErraiApp.properties (note that will exclude the whole jar from scanning so Errai won't find any types in there)

Based on your description it does sound like we need a new feature for white/blacklisting JPA types though as it seems you're actually using the other JPA types on the client but you don't want them to be used by Errai JPA. If that's correct, can you create a JIRA for us?

Cheers,

Christian

[vwjugow]

Hi Christian,

thanks for getting back to me so quickly. Yes that is correct. Here's the jira ticket: [ERRAI-832] Add posibility to exclude Entities from Errai JPA scan - JBoss Issue Tracker

Thanks!

Victor.-