{"id":338,"date":"2009-12-17T16:15:26","date_gmt":"2009-12-17T16:15:26","guid":{"rendered":"http:\/\/salientsoft.co.uk\/?p=338"},"modified":"2010-02-26T21:05:28","modified_gmt":"2010-02-26T21:05:28","slug":"using-eclipseeclipselinkjsfjpa-with-tomcat-6","status":"publish","type":"post","link":"https:\/\/salientsoft.co.uk\/?p=338","title":{"rendered":"Using Eclipse\/JSF\/JPA with Tomcat 6"},"content":{"rendered":"

I’ve found that this is useful for prototyping\/mockups of apps that are targetted for GlassFish. It is possible to run JPA with Eclipselink outside an EJB\u00a0container, so a JSF\/JPA app can be run under Tomcat, resulting in less overhead and faster turnaround of changes. For a while I’ve\u00a0had to use a PC which is RAM limited, and so developing\/prototyping with Eclipse and Glassfish has been slow. Turning around deployments\/changes around takes time, and I’ve found the synchronisation between Eclipse and Glassfish to be a bit fussy – sometimes Eclipse misunderstands the state of Glassfish, needing a Glassfish restart which again takes valuable time.<\/p>\n

Note the following points on doing this:-<\/p>\n

1\/<\/strong> My application stack looks similar to the ‘real’ one, but my Service layer\/domain objects are just POJOs which are explicitly created or\u00a0injected via\u00a0faces_config.xml. This Oracle Example<\/a><\/strong> <\/a>details the various IOC features of the JSF. managed bean facility.<\/p>\n

2\/<\/strong> Persistence.xml needs setting up differently to run JPA outside the container. I have found it\u00a0easiest to specify the database connection explicitly, rather than using a data source. In Eclipse, you can use the persistence.xml<\/strong> editor to populate the connection properties directly from the one Eclipse uses for its entity validation. Whilst you can do JNDI lookups of a data source stored in Tomcat, the naming context used is different, as it makes use of the Enterprise Naming Context (ENC), i.e. “java:comp\/env”. This<\/strong> <\/a>example details how to do it if you want to go that way. A sample persistence.xml<\/strong> follows (with entries commented out where they have been replaced for use with Tomcat)\u00a0:-\u00a0<\/p>\n

<?xml version=\"1.0\" encoding=\"UTF-8\"?>\r\n<persistence version=\"1.0\" xmlns=\"http:\/\/java.sun.com\/xml\/ns\/persistence<\/a>\"\r\n\u00a0xmlns:xsi=\"http:\/\/www.w3.org\/2001\/XMLSchema-instance<\/a>\"\r\n\u00a0xsi:schemaLocation=\"http:\/\/java.sun.com\/xml\/ns\/persistence<\/a>\r\n\u00a0http:\/\/java.sun.com\/xml\/ns\/persistence\/persistence_1_0.xsd<\/a>\">\r\n\r\n\u00a0<!--<persistence-unit name=\"SentryPrototype\" transaction-type=\"JTA\">-->\r\n\u00a0<persistence-unit name=\"SentryPrototype\" transaction-type=\"RESOURCE_LOCAL\">\r\n\r\n\u00a0\u00a0 <provider>org.eclipse.persistence.jpa.PersistenceProvider<\/provider>\r\n\r\n\u00a0\u00a0 <!--<jta-data-source>jdbc\/JPATestPool<\/jta-data-source>-->\r\n\r\n\u00a0\u00a0 <class>uk.co.salientsoft.jpatest.domain.UserInfo<\/class>\r\n\u00a0\u00a0 <properties>\r\n\u00a0\u00a0\u00a0 <property name=\"eclipselink.logging.level\" value=\"INFO\" \/>\r\n\r\n\u00a0\u00a0\u00a0 <!-- <property name=\"eclipselink.target-server\" value=\"SunAS9\" \/>-->\r\n\u00a0\u00a0\u00a0 <property name=\"eclipselink.target-server\" value=\"None\" \/>\r\n\r\n\u00a0\u00a0\u00a0 <property name=\"eclipselink.session-name\" value=\"SentryPrototypeSession\" \/>\r\n\u00a0\u00a0\u00a0 <property name=\"eclipselink.target-database\" value=\"Oracle\" \/>\u00a0\u00a0\u00a0\r\n\u00a0\u00a0\u00a0 <property name=\"eclipselink.ddl-generation.output-mode\" value=\"database\" \/>\r\n\r\n\u00a0\u00a0\u00a0 <property name=\"eclipselink.jdbc.url\" value=\"jdbc:oracle:thin:@localhost:1521:xe\"\/>\r\n\u00a0\u00a0\u00a0 <property name=\"eclipselink.jdbc.user\" value=\"sentry\"\/>\r\n\u00a0\u00a0\u00a0 <property name=\"eclipselink.jdbc.password\" value=\"sentry\"\/>\r\n\u00a0\u00a0\u00a0 <property name=\"eclipselink.jdbc.driver\" value=\"oracle.jdbc.OracleDriver\"\/>\r\n\r\n\u00a0\u00a0 <\/properties>\r\n\u00a0 <\/persistence-unit>\r\n<\/persistence><\/pre>\n
\u00a0<\/strong><\/p>\n
3\/\u00a0<\/strong>Ref this eclipse tutorial<\/a>\u00a0:-
\n<\/strong>Tomcat does not have an EJB container so you must add EJB 3.0\/JPA 1.0 capability for EclipseLink JPA by placing the specification persistence.jar into the container lib directory $TOMCAT_HOME\/lib.
\n<\/em>It is recommended to put persistence_1_0.xsd there as well.\u00a0 It is not recommended that the WAR include its own version of persistence.jar. Your eclipse project should reference but not include this jar and xsd.<\/p>\n
The eclipselink.jar should be placed off of the container lib directory $TOMCAT_HOME\/lib.
\n<\/em>Since Tomcat does not include an EJB container, you may put eclipselink.jar in the web applications’s lib directory or higher up in the classloader by putting it off of Tomcats’ lib directory, where all web applications can access it.
\nDo not split the eclipselink.jar from the javax.persistence jar – keep them together – preferably in $TOMCAT_HOME\/lib<\/em><\/p>\n
\u00a04\/<\/strong> Tomcat has its own dependencies on the Expression Language (EL) web libraries. These should be removed from WEB_INF\/lib when deploying to Tomcat as pointed out here<\/a><\/strong>. (If you do not do this, the application will crash with duplicate class loading exceptions.) This may be done in eclipse on the Java Server Faces facet page<\/strong>\u00a0– open the project properties for the project, and select Java Server Faces<\/strong> under Project Facets.<\/strong> Untick the entry for Standardized EL Library v1.0.<\/strong><\/p>\n