Thanks for reporting.

The persistence is generated by other (Persistence) area, so I'm reassigning the issue.

in general there is no support for libraries or for multiple libraries for the same jpa version, persistence support looks for first suitable library nb may know about. if some library is added manually and it's differnt version it may be hard for nb to understand if it's suitable enough.

Sergey,

my opinion on that case is if there is a JPA provider already on classpath of the project, netbeans should not add another dependency to pom (not to mention it's adding JPA 2.1 dependency to project associated with JEE 6 server).

(and there is still the issue that the generated code is not correct for given persistence.xml)

for ant project this check may work as a solution, but I'm not sure regarding maven, what will happens in case if dependency isn't downloaded yet.

maybe some configuration option than? I find NetBeans editing my pom incorrectly very annoying (and I would prefer it wouldn't touch it at all, if it's the only other option; it's not just this case - it seems as pretty typical use case to me that the JEE artifacts are in scope provided; they're part of the server - and I noticed multiple cases where netbeans adds something to pom that results in startup failure due to various classloading conflicts)

in general eclipselink shouldn't be added if server is registered, and it works this way for ant projects, eclipselink is added to processors classpath only. for maven separate processor classpath dependency isn't supported as I see the issue, or nb can't handle this case.

Agree, but it should respect the pom on top of that - Imagine that I don't use the server integration of the IDE - just do the maven build and deploy it to my server manually - the pom is perfectly correct, yet netbeans would (incorrectly) change it only because I'm not using the integration feature? 

I haven't used ant in years - but I'd say the processors classpath is there because dependency management in ant is non existent. Using the dependency scopes properly should be equivalent in the maven world.

This discussion should rather be under https://netbeans.org/bugzilla/show_bug.cgi?id=247506

the issue in this ticket was mainly about the fact that the generated Stateless *Facade beans does not respect the persistence.xml

(example below is generated from the sample MySQL employees db)

@Stateless
public class DepartmentsFacade extends AbstractFacade<Departments> {
    @PersistenceContext(unitName = "com.example_tutorial-jsf_war_1.0-SNAPSHOTPU")
    private EntityManager em;

    @Override
    protected EntityManager getEntityManager() {
        return em;
    }

    public DepartmentsFacade() {
        super(Departments.class);
    }

}

with persistence.xml:
...
 <persistence-unit name="com.example_tutorial-jsf_war_1.0-SNAPSHOTPU" transaction-type="RESOURCE_LOCAL">
...

the generated code should look like this to work:

@Stateless
public class DepartmentsFacade extends AbstractFacade<Departments> {
    @PersistenceUnit(unitName = "com.example_tutorial-jsf_war_1.0-SNAPSHOTPU")
    private EntityManagerFactory factory;

    @Override
    protected EntityManager getEntityManager() {
        return factory.createEntityManager();
    }

    public DepartmentsFacade() {
        super(Departments.class);
    }

}

the code I added is not complete modification, it should either hold one instance of the EntityManager. The code I posted works, but will create multiple EntityManagers (if the current AbstractFacade is kept) which wouldn't be a good idea.