Hi Aidan.
I did what you said about catch the null pointer exception, It looked
like the servlet for the request factory was bad mapped (but it was
never warned on compilation/excecution time). I re-mapped the servlet
as the bellow page says and it worked (for now, because I proved with
the more s
Give this a try:
Start in debug mode,
1 - Get the app ready to fire() your request,
*then*
2 - In eclipse, add Java Exception Breakpoint on
java.lang.NullPointerException - make sure 'caught exceptions' is ticked.
3 - Make your app fire() the request.
You should drop into debug mode when the NPE
Hi all again! I've just tried to use a CustomRequestFactoryServlet in
order to catch and resolve the NPE in the server side. I could do it,
but the catched error was "NullPointerException" with no other info
(at all), no strackTrace, no specific cause (just "null") and no
location specified! Help,
Aidan, thanks by your answer.
When I said my server side is not reached, I reffer to some
breakpoints in the back-end wich are never reached on debug mode (in
the Service class in server side). just after calling the fire method,
the debug stake catches another breakpoint in the onFailure method o
Hi, Thomas, I've read the RequestFactorySource and Annotation
Processing. I have already the requestfactory-apt.jar referenced as it
is shown in the link bellow, but it doesn't seem to be the problem.
Right now I'm trying to implement something in order to catch the
server side exception as Aidan h
On Wed, Dec 21, 2011 at 6:07 PM, MagusDrk wrote:
> never reaches the server side. All error detail is a "Server Error:
> null" (absolutelly nothing else)
>
>
RequestFactoryServlet by default catches all exceptions and returns them to
the client, without stack-traces or much details, I usually get
When you say "never reaches the server side", you mean it never reaches
your own code, right? Have you looked at the server logs?
You might be interested by
http://code.google.com/p/google-web-toolkit/wiki/RequestFactory_2_4#RequestFactorySource_and_Annotation_Processing
too,
which is unfortun
Hi everybody!
I have two weeks trying to implement RequestFactory, I've done my data
classes model, locators, proxies, etc, but I simply can't get it to
work. I've tried all configurations suggested on Starting With Requst
Factory Page, but I still get the same problem.
When the line request.fire
Hi everybody!
I have two weeks trying to implement RequestFactory, I've done my data
classes model, locators, proxies, etc, but I simply can't get it to
work. I've tried all configurations suggested on Starting With Requst
Factory Page, but I still get the same problem.
When the line request.fire