[morellik]

Arun Gupta wrote:

Does your app specifically rely on EclipseLink ? If not, then you can remove the persistence-provider from persistence.xml and that should make further progress.

Have you tried copying your JAR in standalone/lib/ext ?

My application is based on EclipsLink, so I cannot remove it.

No I didn't tried to copying JAR, I deploy the WAR using the glassfish web interface.

[arungupta]

Can you bundle EclipseLink jar in WEB-INF/lib ?

[morellik]

Arun Gupta wrote:

Can you bundle EclipseLink jar in WEB-INF/lib ?

Ok, I copy the jar file in the WEB-INF/lib. So when I'll go to home I'll try to check the performance.

[bleathem]

Re: the the ajax mode of the menuItems: be sure to set the render attribute so you are rendering the desired portion of the page on ajax submission.

[morellik]

morellik wrote:

Arun Gupta wrote:

Can you bundle EclipseLink jar in WEB-INF/lib ?

Ok, I copy the jar file in the WEB-INF/lib. So when I'll go to home I'll try to check the performance.

Nothing changed. The performance are the same.

[morellik]

Brian Leathem wrote:

Re: the the ajax mode of the menuItems: be sure to set the render attribute so you are rendering the desired portion of the page on ajax submission.

Changing the mode/render combination now seems to be working. But now, sometimes, I've to click two times on menu items or on commandLink to fire an event.

[arungupta]

Are you trying to get it working or get a better performance ?

[morellik]

Arun Gupta wrote:

Are you trying to get it working or get a better performance ?

I don't understand if it's working because nothing it's changed. After the copy there are other operations to do?

[arungupta]

Did you redeploy the WAR after copying eclipselink JAR in WEB-INF/lib ?

Also read Migrating a Java EE App from GlassFish to WildFly · WildFly, might be useful for you.

[morellik]

Arun Gupta wrote:

Did you redeploy the WAR after copying eclipselink JAR in WEB-INF/lib ?

Also read Migrating a Java EE App from GlassFish to WildFly · WildFly, might be useful for you.

Yes. A  stupid question, but how can work the application without eclipselink?

[arungupta]

What kind of dependency do you have on EclipseLink ? Are you using org.persistence.eclipselink.* imports in your code ?

[morellik]

Arun Gupta wrote:

What kind of dependency do you have on EclipseLink ? Are you using org.persistence.eclipselink.* imports in your code ?

No, I'm not using the import. I selected eplipselink 2.0 like Persistence Provider under NetBeans that generates the following persistence.xml

<?xml version="1.0" encoding="UTF-8"?>

<persistence version="2.0" xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_2_0.xsd">

  <persistence-unit name="IDPbyNMRMeetingPU" transaction-type="JTA">

    <provider>org.eclipse.persistence.jpa.PersistenceProvider</provider>

    <jta-data-source>jdbc/idpbynmr</jta-data-source>

    <exclude-unlisted-classes>false</exclude-unlisted-classes>

    <properties>

      <property name="eclipselink.ddl-generation" value="create-tables"/>

      <property name="eclipselink.logging.level" value="FINEST"/>

    </properties>

  </persistence-unit>

</persistence>

[arungupta]

OK, try removing the following line:

<provider>org.eclipse.persistence.jpa.PersistenceProvider</provider>

create your JDBC resource in WildFly, and then deploy the application.

What version of NetBeans are you using ? It should not be generating an implementation-specific persistence.xml for a standard Java EE application.

[arungupta]

I checked NetBeans 7.4 and 8.0 Beta and they do not generate <provider> element in persistence.xml.

[morellik]

Arun Gupta wrote:

I checked NetBeans 7.4 and 8.0 Beta and they do not generate <provider> element in persistence.xml.

By clicking with the right mouse button on a project New/Persistence Unit. At the end NetBeans creates a new persistence.xml with the provider.

I'm using NetBeans 7.4 but the same thing is possible also in the older version I used.

I create a new Persistence Unit  and NetBeans generates the following persistence.xml

<?xml version="1.0" encoding="UTF-8"?>
<persistence version="2.0" xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_2_0.xsd">
  <persistence-unit name="IDPbyNMRPU" transaction-type="JTA">
    <provider>org.eclipse.persistence.jpa.PersistenceProvider</provider>
    <jta-data-source>jdbc/idpbynmr</jta-data-source>
    <exclude-unlisted-classes>false</exclude-unlisted-classes>
    <properties>
      <property name="eclipselink.ddl-generation" value="create-tables"/>
      <property name="javax.persistence.schema-generation.database.action" value="create"/>
    </properties>
  </persistence-unit>
  <persistence-unit name="IDPbyNMRPU2" transaction-type="JTA">
    <provider>org.eclipse.persistence.jpa.PersistenceProvider</provider>
    <jta-data-source>jdbc/idpbynmr</jta-data-source>
    <exclude-unlisted-classes>false</exclude-unlisted-classes>
    <properties>
      <property name="javax.persistence.schema-generation.database.action" value="create"/>
    </properties>
  </persistence-unit>
</persistence>