GWT gives you the opportunity to log exceptions the way you want them.
For server side exceptions, just override the
RemoteServiceServlet.doUnexpectedFailure()
in your RPC Servlet and put appropriate loggers over there.
For client side exceptions, call GWT.setUncaughtExceptionHandler() and
regist
I think it depends on just what is useful, which itself largely depends on
what problem you are trying to track down. In many cases where data isn't
being returned across the wire, the data returned in the GWT stack traces
can be helpful. In fact, in some cases it will even suggest resolution;
inco
On Oct 8, 6:56 pm, Sripathi Krishnan
wrote:
> Deliberate decision ..
>
> Few reasons that I know of --
I buy the not transmitting the errors to the client part; what I don't
understand is why the server log doesn't seem to show anything useful
in this case, at least, where it's come up for me.
-
Deliberate decision ..
Few reasons that I know of --
a) Server code is capable of generating exceptions which can't be translated
to javascript. Things like HibernateException can't be translated to JS.
b) From a security perspective, you don't want your server side stack traces
to be available t
On Sep 12, 7:39 am, Sripathi Krishnan
wrote:
> No - GWT doesn't propagate that exception/message to the client.
Is this a bug, tracked somewhere, or a deliberate decision that
doesn't currently make sense to me? :)
--~--~-~--~~~---~--~~
You received this message
No - GWT doesn't propagate that exception/message to the client.
--Sri
2009/9/12 Mohsen Saboorian
> There is no way to obtain the exception thrown somewhere in the client
> without overriding this class?
>
>
> On Sat, Sep 12, 2009 at 2:58 PM, Sripathi Krishnan <
> sripathi.krish...@gmail.com>
There is no way to obtain the exception thrown somewhere in the client
without overriding this class?
On Sat, Sep 12, 2009 at 2:58 PM, Sripathi Krishnan <
sripathi.krish...@gmail.com> wrote:
> Just override the RemoteServiceServlet.doUnexpectedFailure() in your RPC
> Servlet and put appropriate l
Just override the RemoteServiceServlet.doUnexpectedFailure() in your RPC
Servlet and put appropriate loggers over there.
--Sri
2009/9/12 Mohsen Saboorian
> I know this. My problem is how to log the exception thrown.
>
> Mohsen
>
>
> On Sat, Sep 12, 2009 at 2:39 PM, Sripathi Krishnan <
> sripa
I know this. My problem is how to log the exception thrown.
Mohsen
On Sat, Sep 12, 2009 at 2:39 PM, Sripathi Krishnan <
sripathi.krish...@gmail.com> wrote:
> You cannot return hibernate classes in your RPC servlet - because GWT has
> no way of compiling that into javascript objects.
>
> In your
You cannot return hibernate classes in your RPC servlet - because GWT has no
way of compiling that into javascript objects.
In your case, org.hibernate.collection.PersistentBag cannot be a part of any
object that is returned as part of RPC service call.
--Sri
2009/9/12 Mohsen Saboorian
> Hi,
10 matches
Mail list logo
