OK, here's a problem we all know:
The JEE spec' dictates that no resources should be accessed from a JEE application other than via a JCA comatible datasources, for example, JDBC or JNDI stores... As in other cases, the spec' writer live in an ideal world: In practice, many applications have a filesystem dependency on some product.home directory whee they read configuration from.
Meet EAC4J: