[
https://issues.apache.org/jira/browse/DERBY-1958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12888646#action_12888646
]
Bryan Pendleton commented on DERBY-1958:
----------------------------------------
> But still I don't understand how to get the parameters here {1} and {2}.
StandardException.newException() has a whole bunch of overloads,
each one is a different way to pass arguments to an error message.
To create an exception with a message with 3 parameters, try using
the overload which takes (messageID, Object[]), and in the Object array
put your three arguments.
Something like:
throw StandardException.newException(
SQLState.FILE_CONTAINER_EXCEPTION,
new Object[] {
this.toString(),
"read",
file });
> improve XSDG3 error to print container, actual i/o operation, and file name.
> ----------------------------------------------------------------------------
>
> Key: DERBY-1958
> URL: https://issues.apache.org/jira/browse/DERBY-1958
> Project: Derby
> Issue Type: Improvement
> Components: Store
> Affects Versions: 10.1.3.1, 10.2.1.6, 10.3.1.4
> Reporter: Mike Matrigali
> Priority: Trivial
>
> The current error does not give enough information to know what container is
> the problem:
> ERROR XSDG3: Meta-data for Container
> org.apache.derby.impl.store.raw.data.rafcontai...@10632cd could not be
> accessed
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
