DUE TO SPAM, SIGN-UP IS DISABLED. Goto Selfserve wiki signup and request an account.
Page History
...
| Code Block |
|---|
while (st.hasMoreTokens()) {
final String token = st.nextToken();
final CommandType listType = annotation.collectionType();...
switch (listType) {
case INTEGER:
listParam.add(Integer.valueOf(token));
break;
case UUID:
if (token.isEmpty())
break;
final Long internalId = translateUuidToInternalId(token, annotation);
listParam.add(internalId);
break;
...
case LONG: {
}
listParam.add(Long.valueOf(token));
}
break;
case SHORT:
listParam.add(Short.valueOf(token));
case STRING:
listParam.add(token);
break;
}
}
field.set(cmdObj, listParam);
break;
... |
Detailed error messages in events
In case of events logged due to an error occurred while processing a job or change of state of a resource , a detailed error message describing the reason of failure would be logged into the error_message field of the event. Based on who the user is an admin or a normal user relevant error message would be shown to the end user.
How would error_message data be filled?
Currently, the error messages are ignored in case of any exceptions while a job is performed. The event interceptors in case of error log error events with the hard coded description provided in the event files.
| Code Block |
|---|
public class ActionEventInterceptor implements ComponentMethodInterceptor, MethodInterceptor { ... @Override public Object invoke(MethodInvocation invocation) throws Throwable { ... try { interceptorData = case UUID:interceptStart(m, target); Object result if (paramObj.toString().isEmpty())= invocation.proceed(); success = true; return result; } finally break;{ if (success) { final Long internalId = translateUuidToInternalId(paramObj.toString(), annotationinterceptComplete(m, target, interceptorData); } else { field.set(cmdObjinterceptException(m, target, internalIdinterceptorData); } break; |
Detailed error messages in events
}
... |
A catch block would help to have descriptive error messages, instead of displaying short un-descriptive event descriptions in case of error eventsIn case of events logged due to an error occurred while processing a job or change of state of a resource , a detailed error message describing the reason of failure would be logged into the error_message field of the event. Based on who the user is an admin or a normal user relevant error message would be shown to the end user.
Externalize the event descriptions strings
...
Overview
Content Tools