Hi, With JBoss 7 (Wildfly uses a similar approach) you could create an OrientDB module containing only the jars needed by your application. Then you need to declare the module dependency as a manifest entry. The pros of this approach is that your application war (or ear) will not contain the third party jars (because are installed in the jboss module folder) and you won't get any library conflict.
Here https://groups.google.com/forum/#!topic/orient-database/bw8HFdXOcC8 you can find an old post with some details on how to handle orient as a module in jboss 7. Hope it helps, Fabrizio On Thursday, May 29, 2014 4:26:19 PM UTC+1, Odysseas wrote: > > > There is a dependency in the maven pom files between the graphdb project > and the tools project. Because of this dependency, when I deploy an > application that uses the graphdb project onto the Wildfly app server, I > get an error with the OrientDB JPA provider which I am not using. By > removing the dependency I am able to build everything and run it without > issues so, my question is, do you really need to have that dependency there? > > Thanks, > Odysseas > > From pom.xml in orient-graphdb: > > <dependency> > <groupId>com.orientechnologies</groupId> > <artifactId>orientdb-tools</artifactId> > <version>${project.version}</version> > </dependency> > -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
