2016-06-21 7:46 GMT+02:00 sundar <[email protected]>: > Hi Romain, > There is no other place where persistence.xml is present. We are > using JBPM in our project and I believe JBPM needs drools as well. > I would like to know how to exclude EclipseLink as JPA and use Hibernate > as default? I tried to add eclipselink to my WEB-INF/exclusions.list file, > but I still get the below error. Kindly suggest how to resolve this error. > > Well I did ;). Just change the provider in conf/system.properties. Exclusion is for scanning, JPA doesnt use it but <provider> value. This means your setup has something wrong since you configured hibernate.
> Internal Exception: Exception [EclipseLink-7161] (Eclipse Persistence > Services - 2.6.3.v20160428-59c81c5): > org.eclipse.persistence.exceptions.ValidationException > Exception Description: Entity class [class > org.jbpm.services.task.impl.model.UserImpl] has no primary key specified. > It should define either an @Id, @EmbeddedId or an @IdClass. If you have > defined PK using any of these annotations then make sure that you do not > have mixed access-type (both fields and properties annotated) in your > entity class hierarchy.: javax.persistence.PersistenceException: Exception > [EclipseLink-28018] (Eclipse Persistence Services - > 2.6.3.v20160428-59c81c5): > org.eclipse.persistence.exceptions.EntityManagerSetupException > > > Regards, > Sundar. > > -----"Romain Manni-Bucau [via TomEE & OpenEJB]" < > [email protected]> wrote: ----- > To: sundar <[email protected]> > From: "Romain Manni-Bucau [via TomEE & OpenEJB]" < > [email protected]> > Date: 06/20/2016 12:40PM > Subject: Re: Unable to deploy web application in TomEEPlume1.7.3. It works > with Tomcat7.0.47 > > Hmm, > > if this is the persistence.xml then tomee shouldn't use eclipselink since > it explicitly request hibernate. Isnt it another persistence.xml somewhere? > > Side note: you can set globally the provider in conf/system.properties > javax.persistence.provider=....MyJpaProvider > > About the exclusion: idea was to exclude drools as mentionned in a previous > answer (check the one about exclusions.list which contains the procedure) > > > Romain Manni-Bucau > @rmannibucau <https://twitter.com/rmannibucau> | Blog > <https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog > <http://rmannibucau.wordpress.com> | Github < > https://github.com/rmannibucau> | > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber > <http://www.tomitribe.com> | JavaEE Factory > <https://javaeefactory-rmannibucau.rhcloud.com> > > 2016-06-20 8:20 GMT+02:00 sundar <[hidden email]>: > > > Hi Romain, > > Pl find my persistence.xml. Kindly guide me how to exclude the > > EclipseLink jar. > > > > <persistence version="2.0" > > xsi:schemaLocation="http://java.sun.com/xml/ns/persistence > > http://java.sun.com/xml/ns/persistence/persistence_2_0.xsd > > > > http://java.sun.com/xml/ns/persistence/orm > > http://java.sun.com/xml/ns/persistence/orm_2_0.xsd" > > xmlns:orm=" > http://java.sun.com/xml/ns/persistence/orm" > > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > > xmlns="http://java.sun.com/xml/ns/persistence"> > > > > <provider>org.hibernate.ejb.HibernatePersistence</provider> > > <persistence-unit name="org.jbpm.domain" > > transaction-type="RESOURCE_LOCAL"> > > > > <mapping-file>META-INF/JBPMorm.xml</mapping-file> > > <mapping-file>META-INF/Taskorm.xml</mapping-file> > > <mapping-file>META-INF/TaskAuditorm.xml</mapping-file> > > > > > > <class>org.jbpm.persistence.processinstance.ProcessInstanceInfo</class> > > <class>org.drools.persistence.info.SessionInfo</class> > > ... > > </persistence-unit> > > </persistence> > > > > > > Regards, > > Sundar. > > > > -----"Romain Manni-Bucau [via TomEE & OpenEJB]" < > > [hidden email]> wrote: ----- > > To: sundar <[hidden email]> > > From: "Romain Manni-Bucau [via TomEE & OpenEJB]" < > > [hidden email]> > > Date: 06/20/2016 12:02PM > > Subject: Re: Unable to deploy web application in TomEEPlume1.7.3. It > works > > with Tomcat7.0.47 > > > > likely cause the persistence.xml is scanned and the provider not set in > > persistence.xml. If it is resource_local and doesnt need container > handling > > (no @PersistenceUnit for instance) then just exclude the jar > > > > > > Romain Manni-Bucau > > @rmannibucau <https://twitter.com/rmannibucau> | Blog > > <https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog > > <http://rmannibucau.wordpress.com> | Github < > > https://github.com/rmannibucau> | > > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber > > <http://www.tomitribe.com> | JavaEE Factory > > <https://javaeefactory-rmannibucau.rhcloud.com> > > > > 2016-06-20 7:48 GMT+02:00 sundar <[hidden email]>: > > > > > Hi Romain, > > > We are using Hibernate. We dont have the EclipseLink related > jars > > > in my project structure as well. How to avoid EclipseLink getting > kicking > > > in? > > > > > > Regards, > > > Sundar. > > > > > > -----"Romain Manni-Bucau [via TomEE & OpenEJB]" < > > > [hidden email]> wrote: ----- > > > To: sundar <[hidden email]> > > > From: "Romain Manni-Bucau [via TomEE & OpenEJB]" < > > > [hidden email]> > > > Date: 06/20/2016 11:42AM > > > Subject: Re: Unable to deploy web application in TomEEPlume1.7.3. It > > works > > > with Tomcat7.0.47 > > > > > > Well, tomee will do more than tomact at startup and then it depends > your > > > app. If you don't need this part then just exclude the jars containing > > > these classes with exclusions.list. > > > > > > About the error: it seems hibernate and openjpa tolerates a mapping of > > date > > > more largely than eclipselink which implements strictly one sentence of > > the > > > spec (we got the same issue on batchee). Said otherwise it would need > to > > be > > > fixed on drools or you need to not use eclipselink for these entities > to > > > get rid of it. > > > > > > > > > > > > Romain Manni-Bucau > > > @rmannibucau <https://twitter.com/rmannibucau> | ÿBlog > > > <https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog > > > <http://rmannibucau.wordpress.com> | Github < > > > https://github.com/rmannibucau> | > > > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber > > > <http://www.tomitribe.com> | JavaEE Factory > > > <https://javaeefactory-rmannibucau.rhcloud.com> > > > > > > 2016-06-20 6:46 GMT+02:00 sundar <[hidden email]>: > > > > > > > Hi Romain, > > > > ÿ ÿ ÿ ÿ I tried to add all the necessary jars (which tomee was > > > > complaining) to my web application. As I mentioned I never had to add > > > these > > > > jars to work in Tomcat. Now when I start my application, I get the > > > attached > > > > error and I don't have any control over changing these entities. > Please > > > > suggest what could be done. > > > > > > > > Regards, > > > > Sundar. > > > > > > > > -----"Romain Manni-Bucau [via TomEE & OpenEJB]" < > > > > [hidden email]> wrote: ----- > > > > To: sundar <[hidden email]> > > > > From: "Romain Manni-Bucau [via TomEE & OpenEJB]" < > > > > [hidden email]> > > > > Date: 06/17/2016 02:35PM > > > > Subject: Re: Unable to deploy web application in TomEEPlume1.7.3. It > > > works > > > > with Tomcat7.0.47 > > > > > > > > Just configure the scanning to exclude jars referring to this missing > > > > class. > > > > Le 17 juin 2016 10:28, "sundar" <[hidden email]> a ‚crit : > > > > > > > > > Hi Romain, > > > > > ÿ ÿ ÿ ÿ Sorry. Could you please explain in detail what you would > like > > > me > > > > > to do. It will really help me as I'm struggling to sort this issue > > out. > > > > > > > > > > Regards, > > > > > Sundar. > > > > > > > > > > -----"Romain Manni-Bucau [via TomEE & OpenEJB]" < > > > > > [hidden email]> wrote: ----- > > > > > To: sundar <[hidden email]> > > > > > From: "Romain Manni-Bucau [via TomEE & OpenEJB]" < > > > > > [hidden email]> > > > > > Date: 06/17/2016 12:17PM > > > > > Subject: Re: Unable to deploy web application in TomEEPlume1.7.3. > It > > > > works > > > > > with Tomcat7.0.47 > > > > > > > > > > Ok so likely a jar scanned with a dependency on that > > CommandWebService > > > > > which is missing. Add a WEB-INF/exclusions.list with > > > > > > > > > > default-list > > > > > [all jar prefix you dont need to scan] > > > > > > > > > > for instance > > > > > > > > > > default-list > > > > > spring > > > > > drools > > > > > ... > > > > > > > > > > > > > > > Romain Manni-Bucau > > > > > @rmannibucau <https://twitter.com/rmannibucau> | ÿBlog > > > > > <https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog > > > > > <http://rmannibucau.wordpress.com> | Github < > > > > > https://github.com/rmannibucau> | > > > > > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber > > > > > <http://www.tomitribe.com> | JavaEE Factory > > > > > <https://javaeefactory-rmannibucau.rhcloud.com> > > > > > > > > > > 2016-06-17 7:53 GMT+02:00 sundar <[hidden email]>: > > > > > > > > > > > Hi Romain, > > > > > > ˜ ˜Pl find attached list of jars used in the > application. ˜jar.txt > > > > > > <http://tomee-openejb.979440.n4.nabble.com/file/n4678942/jar.txt > > > > > ˜. I > > > > > > have > > > > > > also added kie-remote-ws-wsdl-cmd-6.1.0.Beta4 to my > > > > > > apache-tomee-plume-1.7.3\lib folder. However while starting the > > > > > application > > > > > > getting the below error. Please help. > > > > > > > > > > > > org.apache.catalina.LifecycleException: Failed to start component > > > > > > > [StandardEngine[Catalina].StandardHost[localhost].StandardContext[ > > > > > > ˜ ˜ ˜ ˜ at > > > > > > > > org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154) > > > > > > ˜ ˜ ˜ ˜ at > > > > > > > > > > > > > > > > > > > > > > > > > > > org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901) > > > > > > ˜ ˜ ˜ ˜ at > > > > > > > > > org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877) > > > > > > ˜ ˜ ˜ ˜ at > > > > > > > > org.apache.catalina.core.StandardHost.addChild(StandardHost.java:652) > > > > > > ˜ ˜ ˜ ˜ at > > > > > > > > > org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:1095) > > > > > > ˜ ˜ ˜ ˜ at > > > > > > > > > > > > > > > > > > > > > org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1930) > > > > > > ˜ ˜ ˜ ˜ at > > > > > > > > > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > > > > > > ˜ ˜ ˜ ˜ at > java.util.concurrent.FutureTask.run(FutureTask.java:262) > > > > > > ˜ ˜ ˜ ˜ at > > > > > > > > > > > > > > > > > > > > > > > > > > > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > > > > > > ˜ ˜ ˜ ˜ at > > > > > > > > > > > > > > > > > > > > > > > > > > > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > > > > > > ˜ ˜ ˜ ˜ at > java.lang.Thread.run(Thread.java:744) > > > > > > Caused by: java.lang.NoClassDefFoundError: > > > > > > org/kie/remote/services/ws/wsdl/generated/CommandWebService > > > > > > ˜ ˜ ˜ ˜ at > java.lang.ClassLoader.defineClass1(Native Method) > > > > > > ˜ ˜ ˜ ˜ at > java.lang.ClassLoader.defineClass(ClassLoader.java:800) > > > > > > ˜ ˜ ˜ ˜ at > > > > > > > > > java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) > > > > > > ˜ ˜ ˜ ˜ at > > > java.net.URLClassLoader.defineClass(URLClassLoader.java:449) > > > > > > ˜ ˜ ˜ ˜ at > > java.net.URLClassLoader.access$100(URLClassLoader.java:71) > > > > > > ˜ ˜ ˜ ˜ at > > java.net.URLClassLoader$1.run(URLClassLoader.java:361) > > > > > > ˜ ˜ ˜ ˜ at > > java.net.URLClassLoader$1.run(URLClassLoader.java:355) > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > View this message in context: > > > > > > > > > > > > > > > > > > > > > http://tomee-openejb.979440.n4.nabble.com/Unable-to-deploy-web-application-in-TomEEPlume1-7-3-It-works-with-Tomcat7-0-47-tp4678842p4678942.html > > > > > > Sent from the TomEE Users mailing list archive at Nabble.com. > > > > > > > > > > > > > > > > > > > > > If you reply to this email, your message will be added to the > > > discussion > > > > > below: > > > > > > > > > > > > > > > > > > > > http://tomee-openejb.979440.n4.nabble.com/Unable-to-deploy-web-application-in-TomEEPlume1-7-3-It-works-with-Tomcat7-0-47-tp4678842p4678943.html > > > > > To unsubscribe from Unable to deploy web application in > > > TomEEPlume1.7.3. > > > > > It works with Tomcat7.0.47, click here. > > > > > NAML > > > > > =====-----=====-----===== > > > > > Notice: The information contained in this e-mail > > > > > message and/or attachments to it may contain > > > > > confidential or privileged information. If you are > > > > > not the intended recipient, any dissemination, use, > > > > > review, distribution, printing or copying of the > > > > > information contained in this e-mail message > > > > > and/or attachments to it are strictly prohibited. If > > > > > you have received this communication in error, > > > > > please notify us by reply e-mail or telephone and > > > > > immediately and permanently delete the message > > > > > and any attachments. Thank you > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > View this message in context: > > > > > > > > > > > > > > > http://tomee-openejb.979440.n4.nabble.com/Unable-to-deploy-web-application-in-TomEEPlume1-7-3-It-works-with-Tomcat7-0-47-tp4678842p4678944.html > > > > > Sent from the TomEE Users mailing list archive at Nabble.com. > > > > > > > > > > > > If you reply to this email, your message will be added to the > > discussion > > > > below: > > > > > > > > > > > > > > http://tomee-openejb.979440.n4.nabble.com/Unable-to-deploy-web-application-in-TomEEPlume1-7-3-It-works-with-Tomcat7-0-47-tp4678842p4678945.html > > > > To unsubscribe from Unable to deploy web application in > > TomEEPlume1.7.3. > > > > It works with Tomcat7.0.47, click here. > > > > NAML > > > > > > > > Exception.txt (3K) < > > > > > > > > > > http://tomee-openejb.979440.n4.nabble.com/attachment/4678963/0/Exception.txt > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > View this message in context: > > > > > > > > > > http://tomee-openejb.979440.n4.nabble.com/Unable-to-deploy-web-application-in-TomEEPlume1-7-3-It-works-with-Tomcat7-0-47-tp4678842p4678963.html > > > > Sent from the TomEE Users mailing list archive at Nabble.com. > > > > > > > > > > > > > If you reply to this email, your message will be added to the > discussion > > > below: > > > > > > > > > http://tomee-openejb.979440.n4.nabble.com/Unable-to-deploy-web-application-in-TomEEPlume1-7-3-It-works-with-Tomcat7-0-47-tp4678842p4678964.html > > > To unsubscribe from Unable to deploy web application in > TomEEPlume1.7.3. > > > It works with Tomcat7.0.47, click here. > > > NAML > > > > > > > > > > > > -- > > > View this message in context: > > > > > > http://tomee-openejb.979440.n4.nabble.com/Unable-to-deploy-web-application-in-TomEEPlume1-7-3-It-works-with-Tomcat7-0-47-tp4678842p4678966.html > > > Sent from the TomEE Users mailing list archive at Nabble.com. > > > > > > > > > If you reply to this email, your message will be added to the discussion > > below: > > > > > http://tomee-openejb.979440.n4.nabble.com/Unable-to-deploy-web-application-in-TomEEPlume1-7-3-It-works-with-Tomcat7-0-47-tp4678842p4678967.html > > To unsubscribe from Unable to deploy web application in TomEEPlume1.7.3. > > It works with Tomcat7.0.47, click here. > > NAML > > > > > > > > -- > > View this message in context: > > > http://tomee-openejb.979440.n4.nabble.com/Unable-to-deploy-web-application-in-TomEEPlume1-7-3-It-works-with-Tomcat7-0-47-tp4678842p4678968.html > > Sent from the TomEE Users mailing list archive at Nabble.com. > > > > > If you reply to this email, your message will be added to the discussion > below: > > http://tomee-openejb.979440.n4.nabble.com/Unable-to-deploy-web-application-in-TomEEPlume1-7-3-It-works-with-Tomcat7-0-47-tp4678842p4678969.html > To unsubscribe from Unable to deploy web application in TomEEPlume1.7.3. > It works with Tomcat7.0.47, click here. > NAML > > > > -- > View this message in context: > http://tomee-openejb.979440.n4.nabble.com/Unable-to-deploy-web-application-in-TomEEPlume1-7-3-It-works-with-Tomcat7-0-47-tp4678842p4678983.html > Sent from the TomEE Users mailing list archive at Nabble.com. >
