Exception constructing methods are not populating the message string -------------------------------------------------------------------- Key: LOGTOOL-13 URL: https://issues.jboss.org/browse/LOGTOOL-13 Project: Log Tool Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 1.0.0.Beta5 Reporter: David Lloyd Assignee: James Perkins Priority: Critical Fix For: 1.0.0.Beta6 ...which sometimes leads to compile errors. This input: {code:title=InvocationMessages.java} // ... @Message(id = 3, value = "Null value passed in for parameter %s") IllegalArgumentException nullParameter(String param); @Message(id = 4, value = "Null value specified for serialized field %s") InvalidObjectException nullField(String param); @Message(id = 5, value = "The given interceptor instance is of the wrong type") IllegalArgumentException wrongInterceptorType(); // ... {code} Yields this output: {code:title=InvocationMessages_$bundle.java} // ... @Override public final IllegalArgumentException nullParameter(final String param) { IllegalArgumentException result = new IllegalArgumentException(); return result; } protected String nullParameter$str() { return nullParameter; } @Override public final InvalidObjectException nullField(final String param) { InvalidObjectException result = new InvalidObjectException(); return result; } protected String nullField$str() { return nullField; } @Override public final IllegalArgumentException wrongInterceptorType() { IllegalArgumentException result = new IllegalArgumentException(); return result; } protected String wrongInterceptorType$str() { return wrongInterceptorType; } // ... {code} In particular this is an issue because InvalidObjectException does not have a no-arg constructor. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira