 1 | your application WEB-INF/lib directory. If this doesn't help you may want to try this Maven Java EE |
1 | you may submit a sample web project that demonstrates it. Stephen |
1 | implementation in your web application or class path. Hi, On my classpath I have the entry |
1 | As we all know, embedded databases out perform server databases on every occasion. The problem with embedded databases is that theyre difficult to scale. If I were to create an entire enterprise web application within a single jar file using embedded tomcat and embedded objectdb I would run into |
1 | As we all know, embedded databases out-perform server databases on every occasion. The problem with embedded databases is that theyre difficult to scale. If I were to create an entire enterprise web application within a single jar file using embedded tomcat and embedded objectdb I would run into |
1 | Is it safe to use this wonderful and undocumented feature in production, and rely on its problem-free functioning? For my case it would be really beneficial: 1 physical server with SSD 1 JVM running on it 2 web applications on Tomcat 1 ObjectDB Server deployed, in embedded server mode 2 ObjectDB |
1 | . It is more efficient to create one EntityManagerFactory per database during the application lifecycle, as demonstrated in the Guest Book web application tutorial. |
1 | the eclipse project layout: (Note eclipse is deploying the application and I can access the web |
1 | also fixes a similar duplicate-on-merge problem I was encountering in my full web application. Thanks. webel |
1 | (instead of putting objectdb.jar in the web application lib directory). Add to the persistence.xml file |
