Glassfish deployment issue: "Could not load any resource bundle by...."

While attempting to redeploy a web project to Glassfish the following error occurred:

"Could not load any resource bundle by com.sun.org.apache.xerces.internal.impl.msg.XMLSchemaMessages"

When trying to restart the Glassfish domain it ran into errors and would not start.  After some troubleshooting the problem turned out to be with the Glassfish server not Glassfish or the project.  It turns out that a teammate ran into some problems while running updates on the Ubuntu server that was hosting Glassfish and that caused java to be temporarily uninstalled (which would obviously cause problems for the java application server).  After re-running the updates, rebooting, then re-running updates again (not sure if all of these steps were necessary) the  Glassfish domain was able to start and deployment of the project worked with no errors.

Runtime ClassNotFoundExceptions may result

Problem:

When using Eclipse Kepler to create Java EE projects, I was getting the following warnings:

Classpath entry <jar library here> will not be exported or published.  Runtime ClassNotFoundExceptions may result.

Solution:

The warning is telling me that the jar file (in my case it was a log4j library) will not be included in the archive that is deployed to application server.  This warning is just a reminder that unless you put the jar file in the classpath of the application server you will receive ClassNotFoundExceptions when trying to run the projects.  A very handy reminder but somewhat irritating since I don't like the little yellow triangle with exclamation point that appears on the project because of the warning.  The can be fixed by adding the jar file for the required library to the Deployment Assembley (Project Properties -> Deployment Assembly -> Add... -> Java Build Path Entries -> <jar library>).  The downside to this is that the jar will be included in the EAR or WAR that is generated thus making is much larger.

Null or zero primary key encountered in unit of work clone

Null or zero primary key encountered in unit of work clone [Object@3622086c], primary key [0]. Set descriptors IdValidation or the "eclipselink.id-validation" property.

Ran into this at runtime when running a EJB on Glassfish using JPA Entities.  The problem turned out to be a missing annotation on one of the properties in one of the JPA Entities (@GeneratedValue).

The value in question was the primary key for the table and was auto-generated.

Full corrected code:

@Id
@GeneratedValue(strategy = GenerationType.IDENTITY)
private int id;