Hi Bryan, I was working on 6802, 6803 when I realized this. You had pointed out earlier that we would be needing DRDAConnThread.buildSqlerrmc() in MessageUtils.
> Regarding the other classes, it seems that nearly all of them > are present in order to provide support for the method > > MessageUtils.getSQLException(...) > > Can we simply remove getSQLException() from MessageUtils? > > It doesn't seem to me that we should need it, and if we remove > getSQLException() from MessageUtils, and also remove the > helper method wrapArgsForTransportAcrossDRDA, > then I believe we can remove all the classes: > But earlier this week when I was removing MessageUtils.getSQLException(...), I ended up removing the buildSqlerrmc() that I had refactored in MessageUtils, the reason being, we were weeding out StandardException that I had moved to shared area for getSQLException. Now when I included buildSqlerrmc(), it occurred to me that this function too needs StandardException and all it's supporting classes. It needs StandardException.getArgumentFerry() to be precise. How should we solve this ? Should we move StandardException too, to the shared area again ? I can't seem to get through without it. Meanwhile I'm attaching MessageUtils, that does not compile at the moment, because of this.
