 1 | when 'getEntities()' is invoked. The prototype is running in a Tomcat server with a RESOURCE_LOCAL |
1 | --127.0.0.1-8080-1) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930)
12:25 |
1 | I added a simple User entity during Tomcat startup: class User { @Id @GeneratedValue private long id; @Basic(optional = false) private String firstName; private String middleName; @Basic(optional = false) private String lastName; } Everything works fine until I restart the server, which does a em |
1 | Hi, So I'm currently having an issue where createEntityManagerFactory returns null. When I run the application on the my local machine through Tomcat it works fine, the odb file is created.
public class TaskDaoODBImpl implements TaskDao {
private EntityManagerFactory emf;
private |
1 | .AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589)
at org.apache.tomcat.util.net |
1 | ) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930)
10:29:15,063 ERROR |
1 | is using Tomcat 7.0 and getting the following exception
06-Sep 14:30:01 ERROR |
1 | available for itself. I experienced something similar when my app server (Tomcat/Tomee) was using |
1 | If I label a class @PersistenceCapable do I still need to explicitly enhance? Do I need a package.jdo file? This question relates to experiences with ODB 1, in which one has to: a) create a package.jdo, and b) run the Enhancer In my experience, using this with Tomcat, and running the enhancer in |
1 | .java:589)
at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:312 |
