lexevs issue handling invalid URI

[darmbrust]

This should be re-verified on a lexevs server where all of the versions line up - I'm not positive if this is caused by the mismatch in versions between my current levevs client that the remote server or not. It might go away when the SearchExtension is available.

Trying to resolve an entity by URI with an invalid URI currently leads to a null pointer exceptions.

http://localhost:8080/entitybyuri?uri=INVALID&maxtoreturn=1&list=false

java.lang.NullPointerException
at java.lang.StringBuilder.(StringBuilder.java:109)
at edu.mayo.cts2.framework.model.exception.ExceptionFactory.createUnknownException(ExceptionFactory.java:259)
at edu.mayo.cts2.framework.webapp.rest.controller.AbstractController.handleException(AbstractController.java:202)
at edu.mayo.cts2.framework.webapp.rest.controller.AbstractController$$FastClassByCGLIB$$ca1950b5.invoke()
at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:191)
at org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:689)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:90)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
at org.springframework.aop.framework.Cglib2AopProxy$DynamicAdvisedInterceptor.intercept(Cglib2AopProxy.java:622)
at edu.mayo.cts2.framework.webapp.rest.controller.EntityDescriptionController$$EnhancerByCGLIB$$709914d9.handleException()