I can make that change. If only there were a way to make sure further
changes down the road did not cause this to regress... Any ideas? ;)
On 03/22/2013 03:17 AM, Christian Bauer wrote:
> Testing the latest scanner changes. Still trying to configure an explicit
> persistence unit, where only t
Testing the latest scanner changes. Still trying to configure an explicit
persistence unit, where only the listed annotated classes (and listed
package-info) are included, everything else should be ignored.
The PackageInfoArchiveEntryHandler will always add package names to
DeploymentResources
https://hibernate.atlassian.net/browse/HHH-8086
But I will change that from Bug to New Feature if it was not previously
documented anywhere.
To be honest, little nervous doing this as it effects provider
portability.
On Mon 18 Mar 2013 11:09:22 AM CDT, Steve Ebersole wrote:
> Out of curiosity,
On 18.03.2013, at 17:09, Steve Ebersole wrote:
> Out of curiosity, where is this documented as being supported?
http://docs.jboss.org/hibernate/entitymanager/3.6/reference/en/html/configuration.html
The class element specifies a fully qualified class name that you will map. By
default all pro
Out of curiosity, where is this documented as being supported?
On Mon 18 Mar 2013 08:34:29 AM CDT, Steve Ebersole wrote:
> The spec does not say anything about explicitly specifying packages.
> I was not aware of handling for that in the old code which I have been
> trying to de-spaghetti for som
The spec does not say anything about explicitly specifying packages. I
was not aware of handling for that in the old code which I have been
trying to de-spaghetti for some time, I can add that capability back in.
On 03/18/2013 08:22 AM, Christian Bauer wrote:
> Trying to upgrade to 4.3-SNAPSHOT
Trying to upgrade to 4.3-SNAPSHOT, the
EntityManagerFactoryBuilderImpl.indexResource() is failing for my
persistence.xml configuration in Java SE with
Persistence.createEntityManagerFactory():
myDS
org.jpwh.model
org.jpwh.model.simple.Item
org.jpwh.model.simple.U
