- described more detailed what you have to do and why
0) Make sure to have Payara 4.1.2.181 installed AND have javax.faces.jar
REPLACED with version 2.3.9 (2.4.0 seem to be a little to new) as the WAR
0) Make sure to have Payara 4.1.2.181 installed AND have javax.faces.jar
REPLACED with version 2.3.9 (2.4.0 seem to be a little to new) as the WAR
- project requires JSF 2.3 (not JSF 2.2). Paraya is currently required as a
- @NamedCache annotation alongside @Inject is being used to inject the cache
- into the backing bean.
+ project requires JSF 2.3 (not JSF 2.2 what is shipped with Payara).
+ Paraya is currently required as a @NamedCache annotation alongside @Inject
+ is being used to inject the cache into the backing bean.
The server.log should reveal a line with "Initializing Mojarra 2.3.9". If
The server.log should reveal a line with "Initializing Mojarra 2.3.9". If
- that is the case, it SHOULD work.
+ that is the case, half way is done and you can continue. Hint: "grep" on it!
A common mistake is to copy the required JARs not to ~/personal_domain/lib/
(or where ever your domain's lib path is) as the required JARs varies from
A common mistake is to copy the required JARs not to ~/personal_domain/lib/
(or where ever your domain's lib path is) as the required JARs varies from
database resource works surely differently (other URL, user/password can be
anything non-empty). I would recommend SQLite3 for development (up to 1 mio.
records with almost no performance drop) and MariaDB/PostreSQL (later not
database resource works surely differently (other URL, user/password can be
anything non-empty). I would recommend SQLite3 for development (up to 1 mio.
records with almost no performance drop) and MariaDB/PostreSQL (later not
- tested by myself) or any other DBMS (including MongoDB) as this project only
- uses the javax.persistence package and not EclipseLink/Hibernate/DataNucleus
- specific packages.
+ tested by myself) or any other DBMS (including MongoDB) for the "productive"
+ installation as this project only imports from the javax.persistence package
+ and not EclipseLink/Hibernate/DataNucleus specific packages.
Pool name: JJobsPool
Resource type: java.sql.Driver
Pool name: JJobsPool
Resource type: java.sql.Driver
JNDI name: jdbc/jjobs
Pool name: JJobsPool
JNDI name: jdbc/jjobs
Pool name: JJobsPool
-4) In juser-core project you will find a JAR named "commons-codec-1.10.jar" you
- need to copy this to your $GLASSFISH_DOMAIN/lib/ path to make password
- encryption working. Please setup sufficient access rights (CHMOD 0644 is
- enough).
+4) You DO have to copy A LOT JARs from my project's directories, including my
+ custom JARs as they contain the entity classes, custom exceptions, utility
+ classes, event classes/interfaces and many required more. Plus you also
+ need to copy all 3rd-party JARs or else it will end with the all-famous
+ NoClassDefError.
If you forgot this file to copy and you have copied it now, please restart
the Glassfish server so the JAR can be found and loaded.
If you forgot this file to copy and you have copied it now, please restart
the Glassfish server so the JAR can be found and loaded.
Optional, but more secure/sometimes required advanced properties:
Optional, but more secure/sometimes required advanced properties:
+mail.smtp.host : <hostname> (localhost is default)
mail.smtp.password : <email password>
mail.smtp.port : <email port>
mail.smtp.auth : true
mail.smtp.password : <email password>
mail.smtp.port : <email port>
mail.smtp.auth : true
Physical destination name: jjobsUserActivityLog
Resource type: javax.jms.Queue
Physical destination name: jjobsUserActivityLog
Resource type: javax.jms.Queue
-9) In WAR project, copy local_xx_XX.properties-dist to local_de_DE.properties
- and local_en_US.properties. If for example your application uses
- product_categories from jproduct-core, you may want to add your custom i18n
- strings to the local properties files as this doesn't cause any later merge
- conflicts as they are ignored by default.
+9) From the WAR project, copy local_xx_XX.properties-dist to
+ local_de_DE.properties and local_en_US.properties. If for example your
+ application uses product_categories from jproduct-core, you may want to add
+ your custom i18n strings to the local properties files as this doesn't cause
+ any later merge conflicts as they are added to .gitignore file.