This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
1. Register JBoss 6 Milestone 5 2. Create a Java EE 6 Web application with JBoss target 3. Create some entities from database. Hibernate (JPA 2.0) will be used as the default JPA provider. 4. Build the application The JPA canonical model was not generated - it should be, Hibernate (as a compliant JPA 2 implementation) supports it.
It's can't be generated without hibernate but all libraries are on server side. looks like enhancement and will be implemented at the same time we will have latest hibernate bundled with nb. Have you tried to create hibernate library manually?
Just realized another solution. For eclipselink if glassfish is registred eclipselink library from glassfish installation is registred withing nb also, may be the same can be done fo JBoss 6.0, yet it will not wotk for j2se projects if there is no JBOss 6 registred in IDE.
Yes, I think this would be a fine solution. Still, I agree this is not too important to fix for 7.0.
can't be fixed/implemented without update of bundled hibernate of implementation of 212883(of cause if JBoss include hibernate with modelgen module if it's separate module in hibernate side)
move to jboss plugin to evaluate if it's possible to create nb hibernate library from jboss installation. still think it may be changed into enhancement request instead of an issue. model generation itself is not an issue as it depends on library only and what parts of library on project's classpath/project ap properties.
it's expected to update bundled lib in next release, no much need to get something from jboss in this case, bundled version can be added to processor classpath.
may be fixed already, but need to verify, anyway it can be fixed as hibernate 4.x is bundled now
works with jboss as 6.1 with a few more fixes http://hg.netbeans.org/web-main/rev/3c97b2c0068e