messagesArea.append("Updating settings to base station " + hostAddress + "......\n");
....
}
(before the message, and before the skipped updating code).
Actually, it would be more helpful (for the maintainers) not to catch just any exception (as now, in this block of code), but let exceptions fall through and print the backtrace.
Then it would be easier to see how to adapt this code to the new Java...
As I could understand, NullPointerExce ption is thrown somewhere in the beginning of this piece of code:
try writeData( ); tData() ; ta();
{
infoPane.
setDependen
setStaticDa
performCons istencyChecks( );
String password = communityField. getText( );
InetAddress hostAddress = InetAddress. getByName( hostIDField. getText( ));
messagesAre a.append( "Updating settings to base station " + hostAddress + "......\n");
....
}
(before the message, and before the skipped updating code).
Actually, it would be more helpful (for the maintainers) not to catch just any exception (as now, in this block of code), but let exceptions fall through and print the backtrace.
Then it would be easier to see how to adapt this code to the new Java...