]
David Lloyd commented on LOGTOOL-31:
------------------------------------
The string name parameter should be optional. If not specified it should use the name of
the parameter itself.
Allow exception methods to set fields on the exception object
-------------------------------------------------------------
Key: LOGTOOL-31
URL:
https://issues.jboss.org/browse/LOGTOOL-31
Project: Log Tool
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Reporter: David Lloyd
Assignee: David Lloyd
Fix For: 1.0.0.Beta9
Create a new annotation called @Field which accepts a single string parameter. For
methods which return an exception, the values of these parameters will be assigned to
fields on the exception object with the corresponding name.
For example:
{code}
@Message(id = 1000, "The transaction failed because blah blah %s")
XAException transactionFailedBlah(String blah, @Field("errorCode") int
errorCode);
// should also continue to work with @Cause in conjunction with exceptions which
don't have a cause param:
@Message(id = 1001, "The operation was interrupted unexpectedly by %s")
InterruptedIOException surprise(String reason, @Cause Throwable someCause,
@Field("bytesTransferred") int bytesTransferred);
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: