Dont really know, I think it is more a tapestry question ;) Le 27 oct. 2012 18:15, "membersound" <[email protected]> a écrit :
> I know what the problem is: in my prior app I had my entities in > tapestry-app-path/entities. According to > http://tapestry.apache.org/integrating-with-jpa.html they are then found > by > default. > > So adding a new path to scan for entities should be done by: > public class AppModule { > > @Contribute(JpaEntityPackageManager.class) > public static void providePackages(Configuration<String> configuration) > { > > configuration.add("org.example.myapp.domain"); > configuration.add("com.acme.model"); > } > } > > > > NEW Problem: JpaEntityPackageManager.class does not exist. Is this a kind > of > placeholder for another class? Or should it be named exactly like this and > exist within the T5 library by default? > > > > -- > View this message in context: > http://openejb.979440.n4.nabble.com/Unknown-Entity-tp4658278p4658285.html > Sent from the OpenEJB User mailing list archive at Nabble.com. >
