Thank for the feedback:
The name field does not get populated. I dont see how it could. If you look at the javadoc states for the return from the Level.parse() method, it states:
Passing an integer that corresponds to a known name (eg 700) will return the associated name (eg CONFIG). Passing an integer that does not (eg 1) will return a new level name initialized to that value.
Also, look at the Level.parse() code. When you pass an unknown level, you do not get the name back, you get the Level created with the integer value as its name.
To your second point; if logging code that is not River based uses River classes (com.sun.jini.logging.Levels), that code needs to either include com.sun.jini.logging classes in it's classpath, or the JVM that is sending that code must have as it's codebase a jar that has the com.sun.jini.logging.Levels class available so the remote JVM can load that custom Level.
If the former, then I would think that such a system is not River-independant, but rather uses River jars selectively (making them River dependent by definition). If the latter, then they never see jsk-dl.jar directly, it all appears magical with dynamic classloading capabilities