If the cause is allowing the application to deploy with the persistence unit
root being the entire EAR, I am interested in feedback on what to do. e.g.
throw a deployment exception or log a warning. Logging a warning is probably
best, if this is indeed the cause. It might be harsh to fail the
Hi Marc,
sorry for the late reply. I forgot to answer :-(
On 5 Jan 2014, at 19:11, Marc Schipperheyn wrote:
> Current situation
> * Loading Wallposts directly from Lucene index.
> * Posts references properties that change relatively often or have cascading
> indexing impact if they would be sa
exclude-unlisted-classes has no impact on hbm.xml discovery
On Tue, Sep 16, 2014 at 5:50 AM, Scott Marlow wrote:
> If the cause is allowing the application to deploy with the persistence
> unit root being the entire EAR, I am interested in feedback on what to do.
> e.g. throw a deployment except