If RAFContainer is in use I can't see any problem of doing so. I'll start the working on it. Thanks for the ideas.
On Tue, Jul 6, 2010 at 6:38 AM, Bryan Pendleton (JIRA) <[email protected]>wrote: > > [ > https://issues.apache.org/jira/browse/DERBY-1958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12885380#action_12885380] > > Bryan Pendleton commented on DERBY-1958: > ---------------------------------------- > > Thanks Knut, that makes sense. > > It seems to me that the best approach for this particular issue, then, is: > 1) Using a custom version of BaseDataFileFactoryJ4, as described > above, force the code through RAFContainer.readPage/writePage > 2) Using a custom version of RAFContainer, force readPage/writePage > to generate the XSDG3 error > 3) Verify that the new message is formatted as expected, and > contains the expected information > 4) Commit the changes with the improved error message, and > declare this issue complete. > > Eranda, does this strategy seem reasonable? > > > > 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. > >
