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.
When creating a Maven EJB separate or in Maven enterprise project and adding a entity bean with toplink. The persistent.xml file is created with the persistent unit transaction type is set RESOURCE_LOCAL. There is no option to change it JTA and its the opposite of what the ANT based netbeans project does. Is it possible to make it optional and allow JTA type available ?
Created attachment 77879 [details] sample maven ejb project
AFAIK the persistence wizard decides based on some criteria what to use. (Thus not choosable by user). One of them is the presence of a deployment server. If the app server is defined for the project, the db connections from the server instance will be offered and also the JPA type of transaction is created. I'm not 100% sure if that logic is correct or is a legacy of ant based projects that always have app server defined and always put the app server's jars on classpath. In maven projects, selecting a deployment server is optional only to cater to all the people who created and use the projects without netbeans as well.
reassigning to persistence support for evaluation if the JPA/local resource can be selectable by user..
post 6.7 feature freeze
it's also valid to set resource_local as user may select tomcat or any non-jee server later. but it's good to allow to change to jta if j22 server will be selected later.
What is interesting about this issue is that when creating a persistence unit in a normal NetBeans 6.8 EJB project sets the persistence attribute to JTA If you create a Maven EJB project it sets the persistence attribute to Resource Local. The user then needs to read the server.log to find out what is wrong.
This old bug may not be relevant anymore. If you can still reproduce it in 8.2 development builds please reopen this issue. Thanks for your cooperation, NetBeans IDE 8.2 Release Boss