Bugs with ResourceStore exceptions messages about gwt-google-apis HOT 12 CLOSED

Two part patch:

1) Apply exception-properties-issue1845-r1610.patch from GWT 1845#2:
   http://code.google.com/p/google-web-toolkit/issues/detail?id=1845#c2

2) Apply attached issue7-meaningful-exceptions-r82.patch which updates:

M     
samples/gwtnote/src/com/google/gwt/gears/sample/gwtnote/client/local/GearsHelper
.java
M      google-apis/src/com/google/gwt/gears/localserver/client/LocalServer.java
M      
google-apis/src/com/google/gwt/gears/localserver/client/ResourceStore.java
M      google-apis/src/com/google/gwt/gears/workerpool/client/WorkerPool.java
M      
google-apis/src/com/google/gwt/gears/database/client/DatabaseException.java
M      google-apis/src/com/google/gwt/gears/database/client/Database.java
M      google-apis/src/com/google/gwt/gears/database/client/ResultSet.java
M      google-apis/src/com/google/gwt/gears/core/client/GearsException.java
M      google-apis/src/com/google/gwt/gears/core/client/impl/GearsImpl.java

The net result is that something like this:
  [Object Object]

Is turned into:
  SQLite prepare() failed. ERROR: SQL logic error or missing database DETAILS: near
"foo": syntax error EXPRESSION: create table foo

For now, I think that we should just use the e.message || e.toString() pattern
instead of relying on a GWT patch that may not make it into GWT 1.5.

I also think that once GWT's improved JavaScriptObject handling is available 
(GWT
1.5), we should be able to overlay a Java type onto the JS exception and provide
better failure capture information.

Based on additional discussions, I conceded.  We will catch JavaScriptException 
in
the Java code and pass that as the cause to the GearsException types.

Committed as r86.