Software Development Cross Solution - Index of - Free

Mercury Meals class continued...
{
public boolean submitOrder(Order cO)
try {
MM mm = MM.establish();
mm.su(this.cO);
catch (Exception e)
{ // write out an error message } return false; }
public Order[] getOrdersThatMatchKeyword(String qk)
}}
Order o = new Order[];
try {
o = MM.establish().find(qk, qk);
} catch (Exception e) {
}
return null;
return o;
Believe it or not, this bracket here
closes the class, but from the poor use of
indentation, you’d be hard-pressed to be
sure of that from looking.
No documentation on any of this class’s methods.
Something that described what the methods are
supposed to do would make life a LOT easier.
No wonder the software gave no indication whether
it was working or not (except by just hanging...) This
method swallows all exceptions that are raised. This is
a classic exception anti-pattern. If an exception gets
raised, and you can’t deal with it locally, then pass
the exception up to the caller so they can at least
know what went wrong.
the next iteration
The code indentation is still all
over the place. This makes things
very hard to read.
throws MercuryMealsConnectionException {
Hiding exceptions again! The caller of
this method will never have to handle a
MercuryMealsConnectionException or any other
exception because this method is hiding anything
that goes wrong and just returning null.
Download at WoweBook.Com
Which qk is being used here? This
doesn’t make sense, and might be a bug.
you are here 4 377