It's thrown as an ELException
because it happened during executing some EL expression.
You should be looking at the root cause of the exception to learn about the root cause of the exception. Look further down in the stack trace to find the root cause. The first is already present in the incomplete stacktrace you posted:
java.lang.NoClassDefFoundError: Could not initialize class com.myapps.util.UIStringUtil
This basically means that loading of the class as done by Java under the covers as follows
Class.forName("com.myapps.util.UIStringUtil");
has failed with an exception. If you're absolutely positive that the class is present in the runtime classpath, then that can only mean that any of the static variables or initializer blocks of the class has thrown an exception. Loading a class namely initializes all static variables and executes all static initilaizer blocks (haven't you ever wondered how those JDBC drivers work?).
That exception should in turn be visible as the bottommost root cause in the stack trace, after the java.lang.NoClassDefFoundError
cause. Perhaps a rather self-explaining java.lang.NullPointerException
?