subject:"RPC problem"

Re: GWT RPC Problem

2012-02-06 Thread JoseM

You can use RequestFactory append to do a batch request  
http://code.google.com/p/google-web-toolkit/wiki/RequestFactory_2_4#Improved_request_batching

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-web-toolkit/-/_F52YUhG7UUJ.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: GWT RPC Problem

2012-02-06 Thread Jens

Well I think Google search is your friend. A quick search gave 
me http://support.microsoft.com/kb/282402 which shows you how to increase 
the limit in IE. Don't know if its possible in other browsers.

In general I would say you should write your app in a way that it does not 
depend on a lot of parallel ajax connections. If you have a lot of very 
long running tasks on the server you should think about executing these 
tasks in threads and let the browser asks for their status periodically 
(maybe every 10 to 20 seconds). That way the RPC request will return 
immediately and the browser does not run out of parallel connections. 
You can also batch requests, which means instead of calling 10 methods 
directly just call one method which tells the server to do 10 things at 
once.

-- J.

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-web-toolkit/-/x30Hc-uM49cJ.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: GWT RPC Problem

2012-02-06 Thread Alan Chaney


On 2/6/2012 8:45 AM, paramesh reddy wrote:

Hi,

  please can any one slove my problem.how I can make more than 6 RPC 
call at a time.some peoples told me it is depending on browser,but I 
tried in IE ,Chorme and firefox every where same result.


Well, they were right - the browser controls the number of connections. 
In firefox, for example:


about:config
network.http.max-persistent-connections-per-server;6

The *user* can change this. You, the programmer, can't. Unless you are 
working on something used purely internally within an organization and 
your IT dept. has complete control

over the browser installations (very unlikely) then you must:

A. Change your app so it doesn't need to make so many requests

or

B. Ask your users to change their configuration.

The only sensible answer is A.

Regards

Alan





On Sat, Jan 28, 2012 at 12:59 PM, paramesh reddy 
mailto:permi.re...@gmail.com>> wrote:


Hi,
  I tried in IE and Chrome Browser ,both have same.can you tell me
how to avoid this problem?


On Thu, Jan 26, 2012 at 8:28 PM, Alfredo Quiroga-Villamil
mailto:laww...@gmail.com>> wrote:

This is a limitation superimposed by browsers and it varies
depending on which browser you are dealing with. My suggestion
if you have a number of requests, each taking an X amount of
time is to look into a Server Push approach.

Regards,

Alfredo

On Wed, Jan 25, 2012 at 1:54 PM, permi mailto:permi.re...@gmail.com>> wrote:

Hi,

 I am able to call max 6 RPC calls at a time .how I can
increase the
calls.

Ex: I have a 10 methods ,each method is take 5 min time to
complete
the task.so when I start to call all methods at a time I
can able to
call max 6 methods, reaming 4 calls in queue i think,after
completion
of earlier call reaming 4 calls going to call.

help me ,how I can call 10 methods at a time and get the
response.

--
You received this message because you are subscribed to
the Google Groups "Google Web Toolkit" group.
To post to this group, send email to
google-web-toolkit@googlegroups.com
.
To unsubscribe from this group, send email to
google-web-toolkit+unsubscr...@googlegroups.com
.
For more options, visit this group at
http://groups.google.com/group/google-web-toolkit?hl=en.




-- 
Alfredo Quiroga-Villamil


AOL/Yahoo/Gmail/MSN IM:  lawwton


-- 
You received this message because you are subscribed to the

Google Groups "Google Web Toolkit" group.
To post to this group, send email to
google-web-toolkit@googlegroups.com
.
To unsubscribe from this group, send email to
google-web-toolkit+unsubscr...@googlegroups.com
.
For more options, visit this group at
http://groups.google.com/group/google-web-toolkit?hl=en.



--
You received this message because you are subscribed to the Google 
Groups "Google Web Toolkit" group.

To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.


--
You received this message because you are subscribed to the Google Groups "Google 
Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: GWT RPC Problem

2012-02-06 Thread paramesh reddy

Hi,

  please can any one slove my problem.how I can make more than 6 RPC call
at a time.some peoples told me it is depending on browser,but I tried in IE
,Chorme and firefox every where same result.

On Sat, Jan 28, 2012 at 12:59 PM, paramesh reddy wrote:

> Hi,
>
>   I tried in IE and Chrome Browser ,both have same.can you tell me how to
> avoid this problem?
>
>
> On Thu, Jan 26, 2012 at 8:28 PM, Alfredo Quiroga-Villamil <
> laww...@gmail.com> wrote:
>
>> This is a limitation superimposed by browsers and it varies depending on
>> which browser you are dealing with. My suggestion if you have a number of
>> requests, each taking an X amount of time is to look into a Server Push
>> approach.
>>
>> Regards,
>>
>> Alfredo
>>
>> On Wed, Jan 25, 2012 at 1:54 PM, permi  wrote:
>>
>>> Hi,
>>>
>>>  I am able to call max 6 RPC calls at a time .how I can increase the
>>> calls.
>>>
>>> Ex: I have a 10 methods ,each method is take 5 min time to complete
>>> the task.so when I start to call all methods at a time I can able to
>>> call max 6 methods, reaming 4 calls in queue i think,after completion
>>> of earlier call reaming 4 calls going to call.
>>>
>>> help me ,how I can call 10 methods at a time and get the response.
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Google Web Toolkit" group.
>>> To post to this group, send email to google-web-toolkit@googlegroups.com
>>> .
>>> To unsubscribe from this group, send email to
>>> google-web-toolkit+unsubscr...@googlegroups.com.
>>> For more options, visit this group at
>>> http://groups.google.com/group/google-web-toolkit?hl=en.
>>>
>>>
>>
>>
>> --
>> Alfredo Quiroga-Villamil
>>
>> AOL/Yahoo/Gmail/MSN IM:  lawwton
>>
>>
>>  --
>> You received this message because you are subscribed to the Google Groups
>> "Google Web Toolkit" group.
>> To post to this group, send email to google-web-toolkit@googlegroups.com.
>> To unsubscribe from this group, send email to
>> google-web-toolkit+unsubscr...@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/google-web-toolkit?hl=en.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: GWT RPC Problem

2012-01-27 Thread paramesh reddy

Hi,

  I tried in IE and Chrome Browser ,both have same.can you tell me how to
avoid this problem?


On Thu, Jan 26, 2012 at 8:28 PM, Alfredo Quiroga-Villamil  wrote:

> This is a limitation superimposed by browsers and it varies depending on
> which browser you are dealing with. My suggestion if you have a number of
> requests, each taking an X amount of time is to look into a Server Push
> approach.
>
> Regards,
>
> Alfredo
>
> On Wed, Jan 25, 2012 at 1:54 PM, permi  wrote:
>
>> Hi,
>>
>>  I am able to call max 6 RPC calls at a time .how I can increase the
>> calls.
>>
>> Ex: I have a 10 methods ,each method is take 5 min time to complete
>> the task.so when I start to call all methods at a time I can able to
>> call max 6 methods, reaming 4 calls in queue i think,after completion
>> of earlier call reaming 4 calls going to call.
>>
>> help me ,how I can call 10 methods at a time and get the response.
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Google Web Toolkit" group.
>> To post to this group, send email to google-web-toolkit@googlegroups.com.
>> To unsubscribe from this group, send email to
>> google-web-toolkit+unsubscr...@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/google-web-toolkit?hl=en.
>>
>>
>
>
> --
> Alfredo Quiroga-Villamil
>
> AOL/Yahoo/Gmail/MSN IM:  lawwton
>
>
>  --
> You received this message because you are subscribed to the Google Groups
> "Google Web Toolkit" group.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> To unsubscribe from this group, send email to
> google-web-toolkit+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-web-toolkit?hl=en.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: GWT RPC Problem

2012-01-26 Thread Alfredo Quiroga-Villamil

This is a limitation superimposed by browsers and it varies depending on
which browser you are dealing with. My suggestion if you have a number of
requests, each taking an X amount of time is to look into a Server Push
approach.

Regards,

Alfredo

On Wed, Jan 25, 2012 at 1:54 PM, permi  wrote:

> Hi,
>
>  I am able to call max 6 RPC calls at a time .how I can increase the
> calls.
>
> Ex: I have a 10 methods ,each method is take 5 min time to complete
> the task.so when I start to call all methods at a time I can able to
> call max 6 methods, reaming 4 calls in queue i think,after completion
> of earlier call reaming 4 calls going to call.
>
> help me ,how I can call 10 methods at a time and get the response.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google Web Toolkit" group.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> To unsubscribe from this group, send email to
> google-web-toolkit+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-web-toolkit?hl=en.
>
>


-- 
Alfredo Quiroga-Villamil

AOL/Yahoo/Gmail/MSN IM:  lawwton

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

GWT RPC Problem

2012-01-25 Thread permi

Hi,

 I am able to call max 6 RPC calls at a time .how I can increase the
calls.

Ex: I have a 10 methods ,each method is take 5 min time to complete
the task.so when I start to call all methods at a time I can able to
call max 6 methods, reaming 4 calls in queue i think,after completion
of earlier call reaming 4 calls going to call.

help me ,how I can call 10 methods at a time and get the response.

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: Rpc Problem

2011-12-13 Thread Kanagaraj M

The problem could be in the servlet mapping part of your web.xml.
Check it out.

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-web-toolkit/-/coQpDmqZChgJ.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Rpc Problem

2011-12-13 Thread sasi sasindran

Hi all,
I have a problem when sending a message to server and it return a
replay to client that it shows an error plus this below warining.



[WARN] 404 - POST /send (127.0.0.1) 1390 bytes
   Request headers
  Accept: */*
  Accept-Language: en-us
  x-gwt-module-base: http://127.0.0.1:/sample/
  Content-Type: text/x-gwt-rpc; charset=utf-8
  x-gwt-permutation: HostedMode
  Referer: http://127.0.0.1:/Sample.html?gwt.codesvr=127.0.0.1:9997
  Accept-Encoding: gzip, deflate
  User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1;
Trident/5.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR
3.0.30729; Media Center PC 6.0)
  Host: 127.0.0.1:
  Content-Length: 157
  Connection: Keep-Alive
  Cache-Control: no-cache
   Response headers
  Content-Type: text/html; charset=iso-8859-1
  Content-Length: 1390

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: RPC problem?

2011-10-24 Thread Thad

I uses a serialized exception. The class looks something like:

public class GwtAppException extends Exception implements Serializable
{
public GwtAppException() {
super();
// my code follows
}
public GwtAppException(String message) {
super(message);
// my code follows
}
... etc.
}

Put this somewhere that it complies for both client and server (the
way your RemoteServices do). Declare your RemoteServices methods to
throw this error.

In you client code,

AsyncCallback callback = new AsyncCallback() {
public void onFailure(Throwable caught) {
Window.alert((new GwtAppException(caught)).getMessage());
}
...

On Oct 21, 8:09 am, András Csányi  wrote:
> On 21 October 2011 13:56, Sean  wrote:
>
> > I also recommend creating a Serialized Exception, and have ALL your RPCs do
> > adequate error handling and throw these Serialized Exceptions for display on
> > your page. This has made RPC debugging 3000x better.
>
> Sean, it sounds really good, but I'm very new at GWT and java as well.
> So, would you so kind to provide a simple example which is usable?
>
> Many thanks in advance!
>
> --
> - -
> --  Csanyi Andras (Sayusi Ando)  
> --http://sayusi.hu--http://facebook.com/andras.csanyi
> --  ""Trust in God and keep your gunpowder dry!" - Cromwell

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: RPC problem?

2011-10-21 Thread Sudhakar Abraham

Your tomcat mapping may be incorrect as it cannot find the url mapping
for the RemoteServiceServlet you are calling. See the error on
"Apache Software Foundation\Apache Tomcat 6.0.18\logs\catalina.
2011-01-21.log" directory. Check your StatusCode  of Http response.

S. Abraham
www.DataStoreGwt.com
Persist objects directly in Google App Engine

On Oct 21, 3:50 pm, Brito  wrote:
>  RPC that is working fine in host mode but fails in web mode
> and I don't know what to do to troubleshoot it. On the client, I get a
> message box that says "Failure:
> com.google.gwt.user.client.rpc.StatusCodeException: The call failed on
> the server; see server log for details".

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: RPC problem?

2011-10-21 Thread András Csányi

On 21 October 2011 13:56, Sean  wrote:
> I also recommend creating a Serialized Exception, and have ALL your RPCs do
> adequate error handling and throw these Serialized Exceptions for display on
> your page. This has made RPC debugging 3000x better.

Sean, it sounds really good, but I'm very new at GWT and java as well.
So, would you so kind to provide a simple example which is usable?

Many thanks in advance!

-- 
- -
--  Csanyi Andras (Sayusi Ando)  -- http://sayusi.hu --
http://facebook.com/andras.csanyi
--  ""Trust in God and keep your gunpowder dry!" - Cromwell

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: RPC problem?

2011-10-21 Thread Sean

I also recommend creating a Serialized Exception, and have ALL your RPCs do 
adequate error handling and throw these Serialized Exceptions for display on 
your page. This has made RPC debugging 3000x better. 

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-web-toolkit/-/d86-w5SyjTgJ.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: RPC problem?

2011-10-21 Thread Thomas Broyer

Have you looked at your server logs? What's the status code? (use Firebug or 
whatever to see what the server responds: 404 → the 
RemoteServiceRelativePath is wrong and/or you have an issue in how you 
deployed your app; 500 → there was another error on the server, maybe you 
reached a non-RPC servlet; 405 → you reached something that doesn't accept 
POSTs, so it's not your RPC servlet)

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-web-toolkit/-/v8_z6HRluuYJ.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

RPC problem?

2011-10-21 Thread Brito

 RPC that is working fine in host mode but fails in web mode
and I don't know what to do to troubleshoot it. On the client, I get a
message box that says "Failure:
com.google.gwt.user.client.rpc.StatusCodeException: The call failed on
the server; see server log for details".

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

[RPC problem] Caused by: java.lang.OutOfMemoryError: Java heap space

2011-08-03 Thread Rafael

Hello everyone!

I have a very disturbing problem (disturbing to me at least), the
exception mentioned in the title of this post occurs on the server
side but after the RPC executes.

I'll explain briefly, i have a DAO interface and a DAO implementation,
and besides, i have the two interfaces and class necessary to
implement a GWT RPC, i use the latter to define a way to call the
methods of the DAO from the client via a asynchronous call.

When i try to invoke the GWT RPC, the method in the DAO executes
without incident but before the result can be returned to the client
the exception takes place.

I am starting tomcat with the -Xms1024M flag in order to increase the
heap space but i guess there is some very unefficient memory handling
somewhere in there (in my app, not in tomcat nor in GWT) but i need to
know where before i can fix it... has this happened to anyone? my
guess is that the memmory suffices for handling the RPC but not for
serializing...

anyway, i decided to seek your advice... thanks in advance!

Rafael

Here is the root cause if i am not mistaken:

Caused by: java.lang.OutOfMemoryError: Java heap space
at java.util.IdentityHashMap.resize(IdentityHashMap.java:452)
at java.util.IdentityHashMap.put(IdentityHashMap.java:428)
at
com.google.gwt.user.client.rpc.impl.AbstractSerializationStreamWriter.saveIndexForObject(AbstractSerializationStreamWriter.java:
202)
at
com.google.gwt.user.client.rpc.impl.AbstractSerializationStreamWriter.writeObject(AbstractSerializationStreamWriter.java:
123)
at
com.google.gwt.user.client.rpc.core.java.util.Map_CustomFieldSerializerBase.serialize(Map_CustomFieldSerializerBase.java:
49)
at
com.google.gwt.user.client.rpc.core.java.util.HashMap_CustomFieldSerializer.serialize(HashMap_CustomFieldSerializer.java:
36)
at sun.reflect.GeneratedMethodAccessor541.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:
25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
com.google.gwt.user.server.rpc.impl.ServerSerializationStreamWriter.serializeWithCustomSerializer(ServerSerializationStreamWriter.java:
742)
at
com.google.gwt.user.server.rpc.impl.ServerSerializationStreamWriter.serializeImpl(ServerSerializationStreamWriter.java:
723)
at
com.google.gwt.user.server.rpc.impl.ServerSerializationStreamWriter.serialize(ServerSerializationStreamWriter.java:
612)
at
com.google.gwt.user.client.rpc.impl.AbstractSerializationStreamWriter.writeObject(AbstractSerializationStreamWriter.java:
129)
at com.google.gwt.user.server.rpc.impl.ServerSerializationStreamWriter
$ValueWriter$8.write(ServerSerializationStreamWriter.java:152)
at
com.google.gwt.user.server.rpc.impl.ServerSerializationStreamWriter.serializeValue(ServerSerializationStreamWriter.java:
534)
at
com.google.gwt.user.server.rpc.impl.ServerSerializationStreamWriter.serializeClass(ServerSerializationStreamWriter.java:
700)
at
com.google.gwt.user.server.rpc.impl.ServerSerializationStreamWriter.serializeImpl(ServerSerializationStreamWriter.java:
730)
at
com.google.gwt.user.server.rpc.impl.ServerSerializationStreamWriter.serializeClass(ServerSerializationStreamWriter.java:
712)
at
com.google.gwt.user.server.rpc.impl.ServerSerializationStreamWriter.serializeImpl(ServerSerializationStreamWriter.java:
730)
at
com.google.gwt.user.server.rpc.impl.ServerSerializationStreamWriter.serializeClass(ServerSerializationStreamWriter.java:
712)
at
com.google.gwt.user.server.rpc.impl.ServerSerializationStreamWriter.serializeImpl(ServerSerializationStreamWriter.java:
730)
at
com.google.gwt.user.server.rpc.impl.ServerSerializationStreamWriter.serialize(ServerSerializationStreamWriter.java:
612)
at
com.google.gwt.user.client.rpc.impl.AbstractSerializationStreamWriter.writeObject(AbstractSerializationStreamWriter.java:
129)
at
com.google.gwt.user.client.rpc.core.java.util.Collection_CustomFieldSerializerBase.serialize(Collection_CustomFieldSerializerBase.java:
43)
at
com.google.gwt.user.client.rpc.core.java.util.HashSet_CustomFieldSerializer.serialize(HashSet_CustomFieldSerializer.java:
36)
at sun.reflect.GeneratedMethodAccessor544.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:
25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
com.google.gwt.user.server.rpc.impl.ServerSerializationStreamWriter.serializeWithCustomSerializer(ServerSerializationStreamWriter.java:
742)
at
com.google.gwt.user.server.rpc.impl.ServerSerializationStreamWriter.serializeImpl(ServerSerializationStreamWriter.java:
723)
at
com.google.gwt.user.server.rpc.impl.ServerSerializationStreamWriter.serialize(ServerSerializationStreamWriter.java:
612)
at
com.google.gwt.user.client.rpc.impl.AbstractSerializationStre

Re: RPC Problem with HashMap containing ArrayList Value

2011-03-30 Thread SergeZ

There are always some ways to solve a problem. But, from the OOP point
of view, I think, that your solution is better. I definetely have to
make a note)))

On 29 мар, 23:12, ciosbel  wrote:
> I mean that instead using List as base type (that will create
> a serialization policy for all types that extend Serializable), you just use
> List where MyDTO is
>
> public interface MyDTO extends Serializable {
>
> }
>
> then gwt will create a serialization policy only for all types that
> implement MyDTO.
>
> But if you are fine with Serializable, just use it. I think that manually
> declare all possible types is avoidable. But i'm not an expert.

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: RPC Problem with HashMap containing ArrayList Value

2011-03-29 Thread ciosbel

I mean that instead using List as base type (that will create 
a serialization policy for all types that extend Serializable), you just use 
List where MyDTO is

public interface MyDTO extends Serializable {
}

then gwt will create a serialization policy only for all types that 
implement MyDTO.

But if you are fine with Serializable, just use it. I think that manually 
declare all possible types is avoidable. But i'm not an expert.

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: RPC Problem with HashMap containing ArrayList Value

2011-03-29 Thread SergeZ

If I got you right, than, the first part of my first post comes up!
Instead of declaring all your generics using Serializable object, you
can just declare ( in the shared package ) all your possible
combinaitons ( the whole veriety of all your non-trivial types ) and
than, in your client-side code, you can safetly define objects of your
types, and do not worry about serialization issues.

On 29 мар, 02:02, Ben Imp  wrote:
> The more generic your remote interface, the more code the GWT compiler
> generates to try and handle all the possible values you may pass
> through it.
>
> Having a method that can take something of type Serializable would, I
> believe, make the GWT compiler generate code for all possible types,
> since you can't get any more generic than that.
>
> -Ben
>
> On Mar 28, 3:58 pm, SergeZ  wrote:
>
>
>
> > What it means ? Is it bad or not ? I see nothing bad or just nothing
> > that takes my attention to that ! Can you explain your point about
> > serialization policy in more details ? What did you mean ?
>
> > On 28 мар, 22:56, ciosbel  wrote:
>
> > > Remember that gwt will create a serialization policy for all serializable
> > > types at compile time.

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: RPC Problem with HashMap containing ArrayList Value

2011-03-28 Thread ciosbel

Not necessarily a problem, but the serialization file is bigger and 
compilation can take a while longer.
When i faced that problem i also see plenty of warnings, but maybe recent 
releases are less verbose.

I got to use an interface that extends Serializable, and then mark my DTOs 
used with generics with that.

Hope that helps.

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: RPC Problem with HashMap containing ArrayList Value

2011-03-28 Thread Ben Imp

The more generic your remote interface, the more code the GWT compiler
generates to try and handle all the possible values you may pass
through it.

Having a method that can take something of type Serializable would, I
believe, make the GWT compiler generate code for all possible types,
since you can't get any more generic than that.

-Ben

On Mar 28, 3:58 pm, SergeZ  wrote:
> What it means ? Is it bad or not ? I see nothing bad or just nothing
> that takes my attention to that ! Can you explain your point about
> serialization policy in more details ? What did you mean ?
>
> On 28 мар, 22:56, ciosbel  wrote:
>
>
>
>
>
>
>
> > Remember that gwt will create a serialization policy for all serializable
> > types at compile time.

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: RPC Problem with HashMap containing ArrayList Value

2011-03-28 Thread SergeZ

What it means ? Is it bad or not ? I see nothing bad or just nothing
that takes my attention to that ! Can you explain your point about
serialization policy in more details ? What did you mean ?

On 28 мар, 22:56, ciosbel  wrote:
> Remember that gwt will create a serialization policy for all serializable
> types at compile time.

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: RPC Problem with HashMap containing ArrayList Value

2011-03-28 Thread ciosbel

Remember that gwt will create a serialization policy for all serializable 
types at compile time.

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: RPC Problem with HashMap containing ArrayList Value

2011-03-28 Thread richip

Changing the value type to java.io.Serializable did the trick for me.
Thanks!
--

Richi


On Mar 26, 8:20 am, SergeZ  wrote:
> Based on my own experience of working with collections in GWTs RPC
> mechanism, I can suggest you to create a POJO (Plain Old Java Object)
> file in the *.shared package of your application, where you have to
> declare all possible combinations of types (arrays of them) that you
> are going to send to the server ( actually which you are going to
> serialize ). For Example:
> import java.io.Serializable;
> import java.util.HashMap;
> import java.util.ArrayList;
> import java.utils.LinkedList;
>
> Class DummyRPCData implements Serializable{
>
> HashMap[] foo1;
> HashMap>[] foo2;
> HashMap>[] foo3;
> HashMap>[] foo4;
> ..
> ..
> ..
> HashMap[] fooN;
>  public Serializable[] fix025;
>
> public DummyPRCData() {
>     foo1 = null;
>     foo2 = null;
>     
>     
>     
>     fooN = null;
>
> }
> }
>
> You also will be able to use just Serializable identifier in your
> client side-code instead of defining the particular type at any
> particular place, for example:
> instead of:
>     HashMap map = new HashMap();
>     map.put("KEY", "VALUE");
> you can write the following:
>     HashMap map = new HashMap Serializable>();
>     map.put("KEY", "VALUE");
> But flexibility comes up not in the case of String type, but, when you
> want to declare a hashmap of types String, and some triky
> LinkedList
>     HashMap map = new HashMap Serializable>();
>     LinkedList> list = new
> LinkedList>();
>     map.put("KEY", list);
>     //and then send map to the server.
>
> I home my post is quite clear.
>
> P.S.: The main idea is to declare all the types you are going to send
> to the server.
>
> On Mar 25, 6:59 pm, richip  wrote:
>
>
>
>
>
>
>
> > I've an object which contains a HashMap instance. I'm
> > finding that when I put a value of type ArrayList, RPC calls fail with
> > a SerializationException that starts with:
>
> > com.google.gwt.user.client.rpc.SerializationException
> >         at
> > com.google.gwt.user.client.rpc.impl.SerializerBase.getTypeHandler(SerializerBase.java:
> > 148)
> > ...
>
> > Any ideas why and suggestions on what to do to get to my intended
> > process?

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: RPC Problem with HashMap containing ArrayList Value

2011-03-26 Thread SergeZ

Based on my own experience of working with collections in GWTs RPC
mechanism, I can suggest you to create a POJO (Plain Old Java Object)
file in the *.shared package of your application, where you have to
declare all possible combinations of types (arrays of them) that you
are going to send to the server ( actually which you are going to
serialize ). For Example:
import java.io.Serializable;
import java.util.HashMap;
import java.util.ArrayList;
import java.utils.LinkedList;

Class DummyRPCData implements Serializable{

HashMap[] foo1;
HashMap>[] foo2;
HashMap>[] foo3;
HashMap>[] foo4;
..
..
..
HashMap[] fooN;
 public Serializable[] fix025;

public DummyPRCData() {
foo1 = null;
foo2 = null;

fooN = null;
}

}

You also will be able to use just Serializable identifier in your
client side-code instead of defining the particular type at any
particular place, for example:
instead of:
HashMap map = new HashMap();
map.put("KEY", "VALUE");
you can write the following:
HashMap map = new HashMap();
map.put("KEY", "VALUE");
But flexibility comes up not in the case of String type, but, when you
want to declare a hashmap of types String, and some triky
LinkedList map = new HashMap();
LinkedList> list = new
LinkedList>();
map.put("KEY", list);
//and then send map to the server.

I home my post is quite clear.

P.S.: The main idea is to declare all the types you are going to send
to the server.

On Mar 25, 6:59 pm, richip  wrote:
> I've an object which contains a HashMap instance. I'm
> finding that when I put a value of type ArrayList, RPC calls fail with
> a SerializationException that starts with:
>
> com.google.gwt.user.client.rpc.SerializationException
>         at
> com.google.gwt.user.client.rpc.impl.SerializerBase.getTypeHandler(SerializerBase.java:
> 148)
> ...
>
> Any ideas why and suggestions on what to do to get to my intended
> process?

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

RPC Problem with HashMap containing ArrayList Value

2011-03-25 Thread richip

I've an object which contains a HashMap instance. I'm
finding that when I put a value of type ArrayList, RPC calls fail with
a SerializationException that starts with:

com.google.gwt.user.client.rpc.SerializationException
at
com.google.gwt.user.client.rpc.impl.SerializerBase.getTypeHandler(SerializerBase.java:
148)
...

Any ideas why and suggestions on what to do to get to my intended
process?

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Spring MVC with GWT RPC problem

2010-05-07 Thread kirti

Hi,
I integrated my GWT application with spring mvc following :
http://code.google.com/p/google-web-toolkit-incubator/wiki/IntegratingWithSpring

But after integration this.getThreadLocalRequest() method invocation
in my serviceImpl class returns null. Please help !!

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to google-web-tool...@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

GWT IFrame RPC problem in Firefox 3.6

2010-05-04 Thread Kelbi

Hello everybody!

I made a GWT module as usual in its own HTML page. I tried to use this
HTML in my application in an iframe. The module builds up its UI in
the onModuleLoad method, then makes an RPC request to fill the widgets
with data. This works well in IE, Chrome and Opera. However, in
Firefox there is a major problem. The RPC request never makes it to
the server. The UI builds up perfectly, so the module is loaded. I've
put a breakpoint on the server side, at the start of the RPC call. It
never runs on Firefox. There is absolutely nothing unique about my
application, and this is not the first time I've made an application
like this. This happens on my PC and on my server machine too.

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to google-web-tool...@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Google Webtoolkit RPC Problem: AsyncCallback parameterization not compatible with return type

2010-01-20 Thread Simon

Hi,

I am working on an opensource application, openxdata. It uses GWT
1.5 . Am using ubuntu 9.04, eclipse 3.4, spring and hibernate
frameworks.

I get the error below

Description ResourcePathLocationType
AsyncCallback parameterization is not compatible with the return type
of ReportService.deleteMappedReport ReportServiceAsync.java
OpenXDataServerAdmin/src/org/openxdata/server/admin/client/service
line 29 Google Web Toolkit RPC Problem

Looking forward for your help.

Simon.
-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to google-web-tool...@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.

Re: GWT 2.0 RPC Problem

2009-10-12 Thread Zé Vicente


In fact, I did many tests... If I compile the application I get the
same error.

For the Jars I quite sure the is ok. If I go back to GWT 1.7 it works
fine.

My scenario again:

ServeviceAAsync serviceA = GWT.create(ServiceA.class);
ServeviceBAsync serviceB = GWT.create(ServiceB.class);
ServeviceCAsync serviceC = GWT.create(ServiceC.class);

So, if  I use serviceA, it works fine. When I use serviceB or C in the
sequence, I get the exception. I can use any sequence, the second
service always crash.

Regards,
José Vicente



On 12 out, 01:18, Sripathi Krishnan 
wrote:
> Documentation for IncompatibleRemoteServiceException says -
> *".. Exception that will be passed to the method when an incompatibility is
> detected between a RemoteService client and its corresponding  RemoteService
> server."*
>
> Are you able to get run it in web mode (ie. after compiling using gwtc)?
> Also, try to see if you have the right jars in the classpath when starting
> up hosted mode/oophm. Perhaps you have both versions of gwt in your
> classpath?
>
> --Sri
>
> 2009/10/11 Zé Vicente 
>
>
>
>
>
> > Hello all,
>
> > I very happy to be able to test GWT 2.0. The new features are
> > amazing The code splitting and Declarative UI are going to place
> > GWT on the top of choice for UI development. I am quite sure the the
> > market will require more professionals with GWT experience.
>
> > Well, but we still have some problems to solve. In my case, I did the
> > migration of my project from 1.7 to 2.0. Now I have a very strange
> > behavior. My first rpc call works fine. But it does not matter which
> > service I call the second time. It always crash. So, in my second rpc
> > call I get an error message like that:
>
> > com.google.gwt.user.client.rpc.IncompatibleRemoteServiceException: The
> > response could not be deserialized
> >        at
>
> > com.google.gwt.user.client.rpc.impl.RequestCallbackAdapter.onResponseReceiv 
> > ed
> > (RequestCallbackAdapter.java:204)
> >        at com.google.gwt.http.client.Request.fireOnResponseReceivedImpl
> > (Request.java:316)
> >        at com.google.gwt.http.client.Request.fireOnResponseReceivedAndCatch
> > (Request.java:288)
> >        at com.google.gwt.http.client.Request.fireOnResponseReceived
> > (Request.java:270)
> >        at com.google.gwt.http.client.RequestBuilder$1.onReadyStateChange
> > (RequestBuilder.java:396)
> >        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >        at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> >        at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> >        at java.lang.reflect.Method.invoke(Unknown Source)
> >        at com.google.gwt.dev.shell.MethodAdaptor.invoke(MethodAdaptor.java:
> > 103)
> >        at
> > com.google.gwt.dev.shell.MethodDispatch.invoke(MethodDispatch.java:
> > 71)
> >        at com.google.gwt.dev.shell.OophmSessionHandler.invoke
> > (OophmSessionHandler.java:146)
> >        at com.google.gwt.dev.shell.BrowserChannel.reactToMessages
> > (BrowserChannel.java:1542)
> >        at com.google.gwt.dev.shell.BrowserChannelServer.processConnection
> > (BrowserChannelServer.java:396)
> >        at com.google.gwt.dev.shell.BrowserChannelServer.run
> > (BrowserChannelServer.java:178)
> >        at java.lang.Thread.run(Unknown Source)
> > Caused by: com.google.gwt.user.client.rpc.SerializationException:
> > Brazil
> >        at com.google.gwt.user.client.rpc.impl.SerializerBase.check
> > (SerializerBase.java:161)
> >        at com.google.gwt.user.client.rpc.impl.SerializerBase.instantiate
> > (SerializerBase.java:138)
> >        at
>
> > com.google.gwt.user.client.rpc.impl.ClientSerializationStreamReader.deseria 
> > lize
> > (ClientSerializationStreamReader.java:114)
> >        at
>
> > com.google.gwt.user.client.rpc.impl.AbstractSerializationStreamReader.readO 
> > bject
> > (AbstractSerializationStreamReader.java:61)
> >        at com.myproject.model.AppStartUPData_FieldSerializer.deserialize
> > (transient source for
> > com.myproject.model.AppStartUPData_FieldSerializer:21)
> >        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >        at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> >        at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> >        at java.lang.reflect.Method.invoke(Unknown Source)
> >        at com.google.gwt.dev.shell.MethodAdaptor.invoke(MethodAdaptor.java:
> > 103)
> >        at
> > com.google.gwt.dev.shell.MethodDispatch.invoke(MethodDispatch.java:
> > 71)
> >        at com.google.gwt.dev.shell.OophmSessionHandler.invoke
> > (OophmSessionHandler.java:146)
> >        at
>
> > com.google.gwt.dev.shell.BrowserChannel.reactToMessagesWhileWaitingForRetur 
> > n
> > (BrowserChannel.java:1573)
> >        at com.google.gwt.dev.shell.BrowserChannelServer.invokeJavascript
> > (BrowserChannelServer.java:124)
> >        at com.google.gwt.dev.shell.ModuleSpaceOOPHM.doInvoke
> > (ModuleSpaceOOPHM.java:120)
> >

Re: GWT 2.0 RPC Problem

2009-10-11 Thread Sripathi Krishnan

Documentation for IncompatibleRemoteServiceException says -
*".. Exception that will be passed to the method when an incompatibility is
detected between a RemoteService client and its corresponding  RemoteService
server."*

Are you able to get run it in web mode (ie. after compiling using gwtc)?
Also, try to see if you have the right jars in the classpath when starting
up hosted mode/oophm. Perhaps you have both versions of gwt in your
classpath?

--Sri


2009/10/11 Zé Vicente 

>
> Hello all,
>
> I very happy to be able to test GWT 2.0. The new features are
> amazing The code splitting and Declarative UI are going to place
> GWT on the top of choice for UI development. I am quite sure the the
> market will require more professionals with GWT experience.
>
> Well, but we still have some problems to solve. In my case, I did the
> migration of my project from 1.7 to 2.0. Now I have a very strange
> behavior. My first rpc call works fine. But it does not matter which
> service I call the second time. It always crash. So, in my second rpc
> call I get an error message like that:
>
> com.google.gwt.user.client.rpc.IncompatibleRemoteServiceException: The
> response could not be deserialized
>at
>
> com.google.gwt.user.client.rpc.impl.RequestCallbackAdapter.onResponseReceived
> (RequestCallbackAdapter.java:204)
>at com.google.gwt.http.client.Request.fireOnResponseReceivedImpl
> (Request.java:316)
>at com.google.gwt.http.client.Request.fireOnResponseReceivedAndCatch
> (Request.java:288)
>at com.google.gwt.http.client.Request.fireOnResponseReceived
> (Request.java:270)
>at com.google.gwt.http.client.RequestBuilder$1.onReadyStateChange
> (RequestBuilder.java:396)
>at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
>at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
>at java.lang.reflect.Method.invoke(Unknown Source)
>at com.google.gwt.dev.shell.MethodAdaptor.invoke(MethodAdaptor.java:
> 103)
>at
> com.google.gwt.dev.shell.MethodDispatch.invoke(MethodDispatch.java:
> 71)
>at com.google.gwt.dev.shell.OophmSessionHandler.invoke
> (OophmSessionHandler.java:146)
>at com.google.gwt.dev.shell.BrowserChannel.reactToMessages
> (BrowserChannel.java:1542)
>at com.google.gwt.dev.shell.BrowserChannelServer.processConnection
> (BrowserChannelServer.java:396)
>at com.google.gwt.dev.shell.BrowserChannelServer.run
> (BrowserChannelServer.java:178)
>at java.lang.Thread.run(Unknown Source)
> Caused by: com.google.gwt.user.client.rpc.SerializationException:
> Brazil
>at com.google.gwt.user.client.rpc.impl.SerializerBase.check
> (SerializerBase.java:161)
>at com.google.gwt.user.client.rpc.impl.SerializerBase.instantiate
> (SerializerBase.java:138)
>at
>
> com.google.gwt.user.client.rpc.impl.ClientSerializationStreamReader.deserialize
> (ClientSerializationStreamReader.java:114)
>at
>
> com.google.gwt.user.client.rpc.impl.AbstractSerializationStreamReader.readObject
> (AbstractSerializationStreamReader.java:61)
>at com.myproject.model.AppStartUPData_FieldSerializer.deserialize
> (transient source for
> com.myproject.model.AppStartUPData_FieldSerializer:21)
>at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
>at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
>at java.lang.reflect.Method.invoke(Unknown Source)
>at com.google.gwt.dev.shell.MethodAdaptor.invoke(MethodAdaptor.java:
> 103)
>at
> com.google.gwt.dev.shell.MethodDispatch.invoke(MethodDispatch.java:
> 71)
>at com.google.gwt.dev.shell.OophmSessionHandler.invoke
> (OophmSessionHandler.java:146)
>at
>
> com.google.gwt.dev.shell.BrowserChannel.reactToMessagesWhileWaitingForReturn
> (BrowserChannel.java:1573)
>at com.google.gwt.dev.shell.BrowserChannelServer.invokeJavascript
> (BrowserChannelServer.java:124)
>at com.google.gwt.dev.shell.ModuleSpaceOOPHM.doInvoke
> (ModuleSpaceOOPHM.java:120)
>at
> com.google.gwt.dev.shell.ModuleSpace.invokeNative(ModuleSpace.java:
> 502)
>at com.google.gwt.dev.shell.ModuleSpace.invokeNativeVoid
> (ModuleSpace.java:295)
>at com.google.gwt.dev.shell.JavaScriptHost.invokeNativeVoid
> (JavaScriptHost.java:107)
>at com.google.gwt.user.client.rpc.impl.SerializerBase$MethodMap
> $.deserialize$(SerializerBase.java)
>at com.google.gwt.user.client.rpc.impl.SerializerBase.deserialize
> (SerializerBase.java:124)
>at
>
> com.google.gwt.user.client.rpc.impl.ClientSerializationStreamReader.deserialize
> (ClientSerializationStreamReader.java:116)
>at
>
> com.google.gwt.user.client.rpc.impl.AbstractSerializationStreamReader.readObject
> (AbstractSerializationStreamReader.java:61)
>

GWT 2.0 RPC Problem

2009-10-11 Thread Zé Vicente


Hello all,

I very happy to be able to test GWT 2.0. The new features are
amazing The code splitting and Declarative UI are going to place
GWT on the top of choice for UI development. I am quite sure the the
market will require more professionals with GWT experience.

Well, but we still have some problems to solve. In my case, I did the
migration of my project from 1.7 to 2.0. Now I have a very strange
behavior. My first rpc call works fine. But it does not matter which
service I call the second time. It always crash. So, in my second rpc
call I get an error message like that:

com.google.gwt.user.client.rpc.IncompatibleRemoteServiceException: The
response could not be deserialized
at
com.google.gwt.user.client.rpc.impl.RequestCallbackAdapter.onResponseReceived
(RequestCallbackAdapter.java:204)
at com.google.gwt.http.client.Request.fireOnResponseReceivedImpl
(Request.java:316)
at com.google.gwt.http.client.Request.fireOnResponseReceivedAndCatch
(Request.java:288)
at com.google.gwt.http.client.Request.fireOnResponseReceived
(Request.java:270)
at com.google.gwt.http.client.RequestBuilder$1.onReadyStateChange
(RequestBuilder.java:396)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.google.gwt.dev.shell.MethodAdaptor.invoke(MethodAdaptor.java:
103)
at com.google.gwt.dev.shell.MethodDispatch.invoke(MethodDispatch.java:
71)
at com.google.gwt.dev.shell.OophmSessionHandler.invoke
(OophmSessionHandler.java:146)
at com.google.gwt.dev.shell.BrowserChannel.reactToMessages
(BrowserChannel.java:1542)
at com.google.gwt.dev.shell.BrowserChannelServer.processConnection
(BrowserChannelServer.java:396)
at com.google.gwt.dev.shell.BrowserChannelServer.run
(BrowserChannelServer.java:178)
at java.lang.Thread.run(Unknown Source)
Caused by: com.google.gwt.user.client.rpc.SerializationException:
Brazil
at com.google.gwt.user.client.rpc.impl.SerializerBase.check
(SerializerBase.java:161)
at com.google.gwt.user.client.rpc.impl.SerializerBase.instantiate
(SerializerBase.java:138)
at
com.google.gwt.user.client.rpc.impl.ClientSerializationStreamReader.deserialize
(ClientSerializationStreamReader.java:114)
at
com.google.gwt.user.client.rpc.impl.AbstractSerializationStreamReader.readObject
(AbstractSerializationStreamReader.java:61)
at com.myproject.model.AppStartUPData_FieldSerializer.deserialize
(transient source for
com.myproject.model.AppStartUPData_FieldSerializer:21)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.google.gwt.dev.shell.MethodAdaptor.invoke(MethodAdaptor.java:
103)
at com.google.gwt.dev.shell.MethodDispatch.invoke(MethodDispatch.java:
71)
at com.google.gwt.dev.shell.OophmSessionHandler.invoke
(OophmSessionHandler.java:146)
at
com.google.gwt.dev.shell.BrowserChannel.reactToMessagesWhileWaitingForReturn
(BrowserChannel.java:1573)
at com.google.gwt.dev.shell.BrowserChannelServer.invokeJavascript
(BrowserChannelServer.java:124)
at com.google.gwt.dev.shell.ModuleSpaceOOPHM.doInvoke
(ModuleSpaceOOPHM.java:120)
at com.google.gwt.dev.shell.ModuleSpace.invokeNative(ModuleSpace.java:
502)
at com.google.gwt.dev.shell.ModuleSpace.invokeNativeVoid
(ModuleSpace.java:295)
at com.google.gwt.dev.shell.JavaScriptHost.invokeNativeVoid
(JavaScriptHost.java:107)
at com.google.gwt.user.client.rpc.impl.SerializerBase$MethodMap
$.deserialize$(SerializerBase.java)
at com.google.gwt.user.client.rpc.impl.SerializerBase.deserialize
(SerializerBase.java:124)
at
com.google.gwt.user.client.rpc.impl.ClientSerializationStreamReader.deserialize
(ClientSerializationStreamReader.java:116)
at
com.google.gwt.user.client.rpc.impl.AbstractSerializationStreamReader.readObject
(AbstractSerializationStreamReader.java:61)
at com.myproject.model.Country_FieldSerializer.deserialize(transient
source for com.myproject.model.Country_FieldSerializer:22)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.google.gwt.dev.shell.MethodAdaptor.invoke(MethodAdaptor.java:
103)
at com.google.gwt.dev.shell.MethodDispatch.invoke(MethodDispatch.java:
71)
at com.google.gwt.dev.shell.OophmSessionHandler.invoke
(OophmSes

Re: GWT RPC Problem with JDP

2009-09-08 Thread Sri


You cannot return StreamingQueryResult from your RPC Method.
The RPC Method must return an object that implements Serializable and
has a default no-args constructor. Also, this class should not depend
on any server specific class.

Remember - the object you return from your RPC method will ultimately
be converted to javascript, so you really cannot return any arbitrary
class.


On Sep 8, 1:19 am, vasem want  wrote:
> This is no RPC issue but it is the thread invokation
> it seems all yours threads are busy and on top of
> that it is not able to find the object you are riding
> the data on , check your object response and check
> your pooling first
>
> On Mon, Sep 7, 2009 at 6:08 PM, webnazar  wrote:
>
> > Mudassar Nazar : Software Engineer
>
> > This is not only a problem, but also a bug issue, i was trying from
> > app the possiblities of trial and error method for ruuning the program
> > but it is failed.
>
> > Sep 7, 2009 3:32:55 PM
> > com.google.appengine.tools.development.ApiProxyLocalImpl log
> > SEVERE: [1252317775578000] javax.servlet.ServletContext log: Exception
> > while dispatching incoming RPC call
> > com.google.gwt.user.client.rpc.SerializationException: Type
> > 'org.datanucleus.store.appengine.query.StreamingQueryResult' was not
> > included in the set of types which can be serialized by this
> > SerializationPolicy or its Class object could not be loaded. For
> > security purposes, this type will not be serialized.
> >        at
>
> > com.google.gwt.user.server.rpc.impl.StandardSerializationPolicy.validateSerialize
> > (StandardSerializationPolicy.java:83)
> >        at
>
> > com.google.gwt.user.server.rpc.impl.ServerSerializationStreamWriter.serialize
> > (ServerSerializationStreamWriter.java:591)
> >        at
>
> > com.google.gwt.user.client.rpc.impl.AbstractSerializationStreamWriter.writeObject
> > (AbstractSerializationStreamWriter.java:129)
> >        at
> > com.google.gwt.user.server.rpc.impl.ServerSerializationStreamWriter
> > $ValueWriter$8.write(ServerSerializationStreamWriter.java:146)
> >        at
>
> > com.google.gwt.user.server.rpc.impl.ServerSerializationStreamWriter.serializeValue
> > (ServerSerializationStreamWriter.java:530)
> >        at com.google.gwt.user.server.rpc.RPC.encodeResponse(RPC.java:573)
> >        at com.google.gwt.user.server.rpc.RPC.encodeResponseForSuccess
> > (RPC.java:441)
> >        at com.google.gwt.user.server.rpc.RPC.invokeAndEncodeResponse
> > (RPC.java:529)
> >        at com.google.gwt.user.server.rpc.RemoteServiceServlet.processCall
> > (RemoteServiceServlet.java:166)
> >        at com.google.gwt.user.server.rpc.RemoteServiceServlet.doPost
> > (RemoteServiceServlet.java:86)
> >        at javax.servlet.http.HttpServlet.service(HttpServlet.java:713)
> >        at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
> >        at
> > org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:
> > 487)
> >        at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter
> > (ServletHandler.java:1093)
> >        at
> > com.google.apphosting.utils.servlet.TransactionCleanupFilter.doFilter
> > (TransactionCleanupFilter.java:43)
> >        at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter
> > (ServletHandler.java:1084)
> >        at com.google.appengine.tools.development.StaticFileFilter.doFilter
> > (StaticFileFilter.java:121)
> >        at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter
> > (ServletHandler.java:1084)
> >        at org.mortbay.jetty.servlet.ServletHandler.handle
> > (ServletHandler.java:360)
> >        at org.mortbay.jetty.security.SecurityHandler.handle
> > (SecurityHandler.java:216)
> >        at org.mortbay.jetty.servlet.SessionHandler.handle
> > (SessionHandler.java:181)
> >        at org.mortbay.jetty.handler.ContextHandler.handle
> > (ContextHandler.java:712)
> >        at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:
> > 405)
> >        at
> > com.google.apphosting.utils.jetty.DevAppEngineWebAppContext.handle
> > (DevAppEngineWebAppContext.java:54)
> >        at org.mortbay.jetty.handler.HandlerWrapper.handle
> > (HandlerWrapper.java:139)
> >        at com.google.appengine.tools.development.JettyContainerService
> > $ApiProxyHandler.handle(JettyContainerService.java:313)
> >        at org.mortbay.jetty.handler.HandlerWrapper.handle
> > (HandlerWrapper.java:139)
> >        at org.mortbay.jetty.Server.handle(Server.java:313)
> >        at
> > org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:
> > 506)
> >        at org.mortbay.jetty.HttpConnection$RequestHandler.content
> > (HttpConnection.java:844)
> >        at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:644)
> >        at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:205)
> >        at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:381)
> >        at org.mortbay.io.nio.SelectChannelEndPoint.run
> > (SelectChannelEndPoint.java:396)
> >        at org.m

Re: GWT RPC Problem with JDP

2009-09-07 Thread vasem want

This is no RPC issue but it is the thread invokation
it seems all yours threads are busy and on top of
that it is not able to find the object you are riding
the data on , check your object response and check
your pooling first




On Mon, Sep 7, 2009 at 6:08 PM, webnazar  wrote:

>
> Mudassar Nazar : Software Engineer
>
> This is not only a problem, but also a bug issue, i was trying from
> app the possiblities of trial and error method for ruuning the program
> but it is failed.
>
> Sep 7, 2009 3:32:55 PM
> com.google.appengine.tools.development.ApiProxyLocalImpl log
> SEVERE: [1252317775578000] javax.servlet.ServletContext log: Exception
> while dispatching incoming RPC call
> com.google.gwt.user.client.rpc.SerializationException: Type
> 'org.datanucleus.store.appengine.query.StreamingQueryResult' was not
> included in the set of types which can be serialized by this
> SerializationPolicy or its Class object could not be loaded. For
> security purposes, this type will not be serialized.
>at
>
> com.google.gwt.user.server.rpc.impl.StandardSerializationPolicy.validateSerialize
> (StandardSerializationPolicy.java:83)
>at
>
> com.google.gwt.user.server.rpc.impl.ServerSerializationStreamWriter.serialize
> (ServerSerializationStreamWriter.java:591)
>at
>
> com.google.gwt.user.client.rpc.impl.AbstractSerializationStreamWriter.writeObject
> (AbstractSerializationStreamWriter.java:129)
>at
> com.google.gwt.user.server.rpc.impl.ServerSerializationStreamWriter
> $ValueWriter$8.write(ServerSerializationStreamWriter.java:146)
>at
>
> com.google.gwt.user.server.rpc.impl.ServerSerializationStreamWriter.serializeValue
> (ServerSerializationStreamWriter.java:530)
>at com.google.gwt.user.server.rpc.RPC.encodeResponse(RPC.java:573)
>at com.google.gwt.user.server.rpc.RPC.encodeResponseForSuccess
> (RPC.java:441)
>at com.google.gwt.user.server.rpc.RPC.invokeAndEncodeResponse
> (RPC.java:529)
>at com.google.gwt.user.server.rpc.RemoteServiceServlet.processCall
> (RemoteServiceServlet.java:166)
>at com.google.gwt.user.server.rpc.RemoteServiceServlet.doPost
> (RemoteServiceServlet.java:86)
>at javax.servlet.http.HttpServlet.service(HttpServlet.java:713)
>at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
>at
> org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:
> 487)
>at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter
> (ServletHandler.java:1093)
>at
> com.google.apphosting.utils.servlet.TransactionCleanupFilter.doFilter
> (TransactionCleanupFilter.java:43)
>at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter
> (ServletHandler.java:1084)
>at com.google.appengine.tools.development.StaticFileFilter.doFilter
> (StaticFileFilter.java:121)
>at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter
> (ServletHandler.java:1084)
>at org.mortbay.jetty.servlet.ServletHandler.handle
> (ServletHandler.java:360)
>at org.mortbay.jetty.security.SecurityHandler.handle
> (SecurityHandler.java:216)
>at org.mortbay.jetty.servlet.SessionHandler.handle
> (SessionHandler.java:181)
>at org.mortbay.jetty.handler.ContextHandler.handle
> (ContextHandler.java:712)
>at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:
> 405)
>at
> com.google.apphosting.utils.jetty.DevAppEngineWebAppContext.handle
> (DevAppEngineWebAppContext.java:54)
>at org.mortbay.jetty.handler.HandlerWrapper.handle
> (HandlerWrapper.java:139)
>at com.google.appengine.tools.development.JettyContainerService
> $ApiProxyHandler.handle(JettyContainerService.java:313)
>at org.mortbay.jetty.handler.HandlerWrapper.handle
> (HandlerWrapper.java:139)
>at org.mortbay.jetty.Server.handle(Server.java:313)
>at
> org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:
> 506)
>at org.mortbay.jetty.HttpConnection$RequestHandler.content
> (HttpConnection.java:844)
>at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:644)
>at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:205)
>at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:381)
>at org.mortbay.io.nio.SelectChannelEndPoint.run
> (SelectChannelEndPoint.java:396)
>at org.mortbay.thread.BoundedThreadPool$PoolThread.run
> (BoundedThreadPool.java:442)
>
> >
>

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en
-~--~~~~--~~--~--~---

GWT RPC Problem with JDP

2009-09-07 Thread webnazar


Mudassar Nazar : Software Engineer

This is not only a problem, but also a bug issue, i was trying from
app the possiblities of trial and error method for ruuning the program
but it is failed.

Sep 7, 2009 3:32:55 PM
com.google.appengine.tools.development.ApiProxyLocalImpl log
SEVERE: [1252317775578000] javax.servlet.ServletContext log: Exception
while dispatching incoming RPC call
com.google.gwt.user.client.rpc.SerializationException: Type
'org.datanucleus.store.appengine.query.StreamingQueryResult' was not
included in the set of types which can be serialized by this
SerializationPolicy or its Class object could not be loaded. For
security purposes, this type will not be serialized.
at
com.google.gwt.user.server.rpc.impl.StandardSerializationPolicy.validateSerialize
(StandardSerializationPolicy.java:83)
at
com.google.gwt.user.server.rpc.impl.ServerSerializationStreamWriter.serialize
(ServerSerializationStreamWriter.java:591)
at
com.google.gwt.user.client.rpc.impl.AbstractSerializationStreamWriter.writeObject
(AbstractSerializationStreamWriter.java:129)
at com.google.gwt.user.server.rpc.impl.ServerSerializationStreamWriter
$ValueWriter$8.write(ServerSerializationStreamWriter.java:146)
at
com.google.gwt.user.server.rpc.impl.ServerSerializationStreamWriter.serializeValue
(ServerSerializationStreamWriter.java:530)
at com.google.gwt.user.server.rpc.RPC.encodeResponse(RPC.java:573)
at com.google.gwt.user.server.rpc.RPC.encodeResponseForSuccess
(RPC.java:441)
at com.google.gwt.user.server.rpc.RPC.invokeAndEncodeResponse
(RPC.java:529)
at com.google.gwt.user.server.rpc.RemoteServiceServlet.processCall
(RemoteServiceServlet.java:166)
at com.google.gwt.user.server.rpc.RemoteServiceServlet.doPost
(RemoteServiceServlet.java:86)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:713)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:
487)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter
(ServletHandler.java:1093)
at
com.google.apphosting.utils.servlet.TransactionCleanupFilter.doFilter
(TransactionCleanupFilter.java:43)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter
(ServletHandler.java:1084)
at com.google.appengine.tools.development.StaticFileFilter.doFilter
(StaticFileFilter.java:121)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter
(ServletHandler.java:1084)
at org.mortbay.jetty.servlet.ServletHandler.handle
(ServletHandler.java:360)
at org.mortbay.jetty.security.SecurityHandler.handle
(SecurityHandler.java:216)
at org.mortbay.jetty.servlet.SessionHandler.handle
(SessionHandler.java:181)
at org.mortbay.jetty.handler.ContextHandler.handle
(ContextHandler.java:712)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:
405)
at com.google.apphosting.utils.jetty.DevAppEngineWebAppContext.handle
(DevAppEngineWebAppContext.java:54)
at org.mortbay.jetty.handler.HandlerWrapper.handle
(HandlerWrapper.java:139)
at com.google.appengine.tools.development.JettyContainerService
$ApiProxyHandler.handle(JettyContainerService.java:313)
at org.mortbay.jetty.handler.HandlerWrapper.handle
(HandlerWrapper.java:139)
at org.mortbay.jetty.Server.handle(Server.java:313)
at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:
506)
at org.mortbay.jetty.HttpConnection$RequestHandler.content
(HttpConnection.java:844)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:644)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:205)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:381)
at org.mortbay.io.nio.SelectChannelEndPoint.run
(SelectChannelEndPoint.java:396)
at org.mortbay.thread.BoundedThreadPool$PoolThread.run
(BoundedThreadPool.java:442)

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en
-~--~~~~--~~--~--~---

Re: RPC problem after deploying on server

2009-05-12 Thread Jason Essington


Looks like your servlet mapping is incorrect.

Either change your @RemoteServiceRelativePath to "test/gwt" OR your  
servlet mapping to "/gwt"

-jason

On May 12, 2009, at 3:56 PM, Rod wrote:

>
> I have two classes on client , one named POST, and second POSTAsync.
> In POST I have "@RemoteServiceRelativePath("gwt")" command to set
> path.
> On server side I have POSTImpl class with methods(bodies) to deal with
> database.
> And I have the following settings in web.xml file:
>
> 
>gwtServlet
>pl.mydomain.server.POSTImpl
>  
>
>  
>gwtServlet
>/test/gwt
>  
>
> And all of it works on localhost.
>
> Thx Salvador, I have checked  the permissions on server to this
> folder: 0777, so I don't know if that's the reason. But it might be
> something more advanced in settings I have no idea.
> I pasted the source and description, maybe there are some more advices
> I can get here.
>
> Thx for all help.
>
> On 12 Maj, 22:57, Salvador Diaz  wrote:
>> Hi,
>>
>> It definitively looks like a server configuration error:
>>
>> "
>> You don't have permission to access
>> /Test/war/test/gwt/
>> "
>>
>> Make sure the permissions are correctly setup in the filesystem of
>> your server.
>>
>> Hope that helps,
>>
>> Salvador
>>
>> On May 12, 10:32 pm, Jim  wrote:
>>
>>> Can you post some of your code? Without any code, we can not  
>>> figure it
>>> out.
>>
>>> Jimhttp://www.gwtorm.comhttp://code.google.com/p/dreamsource-orm/ 
>>> downloa...
>>
>>> On May 12, 3:57 pm, Rod  wrote:
>>
 Thank You for answer, but can You be more precise?
 I have hidden the database-communication part of the code but the
 problem still occured, so I think it's the problem between server  
 and
 client.
>>
 I'm wondering about this server. What if it doesn't have any  
 mechanism
 to run servlet's on it?
>>
 On 12 Maj, 20:30, Jim  wrote:
>>
> For GWT-database application, you can find an example 
> inhttp://www.gwtorm.com/mail/Mail.html 
> . The source code is also
> available there.Usually this kind of issue is due to  
> serializable or
> exception that is not handled in service.
>>
> Jimhttp://www.gwtorm.comhttp://code.google.com/p/dreamsource-orm/ 
> downloa...
>>
> On May 12, 12:56 pm, Rod  wrote:
>>
>> Hello,
>>
>>  I'm completly new to GWT. I created an application and  
>> started it
>> on local host in hosted mode with no problems. It was  
>> communicating
>> with external database successfuly. But after I put it on a  
>> server I
>> got an RPC exception:
>>
>> com.google.gwt.user.client.rpc.StatusCodeException: 
>> 
>> 
>> 
>> (none)
>> 
>> 
>> 
>>
>> [...]
>>
>> 
>> 
>> 
>> You don't have permission to access
>> 
>> /Test/war/test/gwt/
>> 
>> on this server.
>> 
>>
>> [...]
>>
>> I have completly no idea what's the reason of this problem. I've
>> searched the web for solution but I couldn't find any. The server
>> isn't mine so I think it may be problem in its configuration.   
>> I'll be
>> very grateful for any help.- Hide quoted text -
>>
 - Show quoted text -
> >


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to Google-Web-Toolkit@googlegroups.com
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~--~~~~--~~--~--~---

Re: RPC problem after deploying on server

2009-05-12 Thread Rod


I have two classes on client , one named POST, and second POSTAsync.
In POST I have "@RemoteServiceRelativePath("gwt")" command to set
path.
On server side I have POSTImpl class with methods(bodies) to deal with
database.
And I have the following settings in web.xml file:


gwtServlet
pl.mydomain.server.POSTImpl
  

  
gwtServlet
/test/gwt
  

And all of it works on localhost.

Thx Salvador, I have checked  the permissions on server to this
folder: 0777, so I don't know if that's the reason. But it might be
something more advanced in settings I have no idea.
I pasted the source and description, maybe there are some more advices
I can get here.

Thx for all help.

On 12 Maj, 22:57, Salvador Diaz  wrote:
> Hi,
>
> It definitively looks like a server configuration error:
>
> "
> You don't have permission to access
> /Test/war/test/gwt/
> "
>
> Make sure the permissions are correctly setup in the filesystem of
> your server.
>
> Hope that helps,
>
> Salvador
>
> On May 12, 10:32 pm, Jim  wrote:
>
> > Can you post some of your code? Without any code, we can not figure it
> > out.
>
> > Jimhttp://www.gwtorm.comhttp://code.google.com/p/dreamsource-orm/downloa...
>
> > On May 12, 3:57 pm, Rod  wrote:
>
> > > Thank You for answer, but can You be more precise?
> > > I have hidden the database-communication part of the code but the
> > > problem still occured, so I think it's the problem between server and
> > > client.
>
> > > I'm wondering about this server. What if it doesn't have any mechanism
> > > to run servlet's on it?
>
> > > On 12 Maj, 20:30, Jim  wrote:
>
> > > > For GWT-database application, you can find an example 
> > > > inhttp://www.gwtorm.com/mail/Mail.html. The source code is also
> > > > available there.Usually this kind of issue is due to serializable or
> > > > exception that is not handled in service.
>
> > > > Jimhttp://www.gwtorm.comhttp://code.google.com/p/dreamsource-orm/downloa...
>
> > > > On May 12, 12:56 pm, Rod  wrote:
>
> > > > > Hello,
>
> > > > >      I'm completly new to GWT. I created an application and started it
> > > > > on local host in hosted mode with no problems. It was communicating
> > > > > with external database successfuly. But after I put it on a server I
> > > > > got an RPC exception:
>
> > > > > com.google.gwt.user.client.rpc.StatusCodeException: 
> > > > > 
> > > > > 
> > > > > 
> > > > > (none)
> > > > > 
> > > > > 
> > > > > 
>
> > > > > [...]
>
> > > > > 
> > > > > 
> > > > > 
> > > > > You don't have permission to access
> > > > > 
> > > > > /Test/war/test/gwt/
> > > > > 
> > > > > on this server.
> > > > > 
>
> > > > > [...]
>
> > > > > I have completly no idea what's the reason of this problem. I've
> > > > > searched the web for solution but I couldn't find any. The server
> > > > > isn't mine so I think it may be problem in its configuration.  I'll be
> > > > > very grateful for any help.- Hide quoted text -
>
> > > - Show quoted text -
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to Google-Web-Toolkit@googlegroups.com
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~--~~~~--~~--~--~---

Re: RPC problem after deploying on server

2009-05-12 Thread Salvador Diaz


Hi,

It definitively looks like a server configuration error:

"
You don't have permission to access
/Test/war/test/gwt/
"

Make sure the permissions are correctly setup in the filesystem of
your server.

Hope that helps,

Salvador

On May 12, 10:32 pm, Jim  wrote:
> Can you post some of your code? Without any code, we can not figure it
> out.
>
> Jimhttp://www.gwtorm.comhttp://code.google.com/p/dreamsource-orm/downloads/list
>
> On May 12, 3:57 pm, Rod  wrote:
>
> > Thank You for answer, but can You be more precise?
> > I have hidden the database-communication part of the code but the
> > problem still occured, so I think it's the problem between server and
> > client.
>
> > I'm wondering about this server. What if it doesn't have any mechanism
> > to run servlet's on it?
>
> > On 12 Maj, 20:30, Jim  wrote:
>
> > > For GWT-database application, you can find an example 
> > > inhttp://www.gwtorm.com/mail/Mail.html. The source code is also
> > > available there.Usually this kind of issue is due to serializable or
> > > exception that is not handled in service.
>
> > > Jimhttp://www.gwtorm.comhttp://code.google.com/p/dreamsource-orm/downloa...
>
> > > On May 12, 12:56 pm, Rod  wrote:
>
> > > > Hello,
>
> > > >      I'm completly new to GWT. I created an application and started it
> > > > on local host in hosted mode with no problems. It was communicating
> > > > with external database successfuly. But after I put it on a server I
> > > > got an RPC exception:
>
> > > > com.google.gwt.user.client.rpc.StatusCodeException: 
> > > > 
> > > > 
> > > > 
> > > > (none)
> > > > 
> > > > 
> > > > 
>
> > > > [...]
>
> > > > 
> > > > 
> > > > 
> > > > You don't have permission to access
> > > > 
> > > > /Test/war/test/gwt/
> > > > 
> > > > on this server.
> > > > 
>
> > > > [...]
>
> > > > I have completly no idea what's the reason of this problem. I've
> > > > searched the web for solution but I couldn't find any. The server
> > > > isn't mine so I think it may be problem in its configuration.  I'll be
> > > > very grateful for any help.- Hide quoted text -
>
> > - Show quoted text -
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to Google-Web-Toolkit@googlegroups.com
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~--~~~~--~~--~--~---

Re: RPC problem after deploying on server

2009-05-12 Thread Jim


Can you post some of your code? Without any code, we can not figure it
out.


Jim
http://www.gwtorm.com
http://code.google.com/p/dreamsource-orm/downloads/list




On May 12, 3:57 pm, Rod  wrote:
> Thank You for answer, but can You be more precise?
> I have hidden the database-communication part of the code but the
> problem still occured, so I think it's the problem between server and
> client.
>
> I'm wondering about this server. What if it doesn't have any mechanism
> to run servlet's on it?
>
> On 12 Maj, 20:30, Jim  wrote:
>
>
>
> > For GWT-database application, you can find an example 
> > inhttp://www.gwtorm.com/mail/Mail.html. The source code is also
> > available there.Usually this kind of issue is due to serializable or
> > exception that is not handled in service.
>
> > Jimhttp://www.gwtorm.comhttp://code.google.com/p/dreamsource-orm/downloa...
>
> > On May 12, 12:56 pm, Rod  wrote:
>
> > > Hello,
>
> > >      I'm completly new to GWT. I created an application and started it
> > > on local host in hosted mode with no problems. It was communicating
> > > with external database successfuly. But after I put it on a server I
> > > got an RPC exception:
>
> > > com.google.gwt.user.client.rpc.StatusCodeException: 
> > > 
> > > 
> > > 
> > > (none)
> > > 
> > > 
> > > 
>
> > > [...]
>
> > > 
> > > 
> > > 
> > > You don't have permission to access
> > > 
> > > /Test/war/test/gwt/
> > > 
> > > on this server.
> > > 
>
> > > [...]
>
> > > I have completly no idea what's the reason of this problem. I've
> > > searched the web for solution but I couldn't find any. The server
> > > isn't mine so I think it may be problem in its configuration.  I'll be
> > > very grateful for any help.- Hide quoted text -
>
> - Show quoted text -
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to Google-Web-Toolkit@googlegroups.com
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~--~~~~--~~--~--~---

Re: RPC problem after deploying on server

2009-05-12 Thread Rod


Thank You for answer, but can You be more precise?
I have hidden the database-communication part of the code but the
problem still occured, so I think it's the problem between server and
client.

I'm wondering about this server. What if it doesn't have any mechanism
to run servlet's on it?

On 12 Maj, 20:30, Jim  wrote:
> For GWT-database application, you can find an example 
> inhttp://www.gwtorm.com/mail/Mail.html. The source code is also
> available there.Usually this kind of issue is due to serializable or
> exception that is not handled in service.
>
> Jimhttp://www.gwtorm.comhttp://code.google.com/p/dreamsource-orm/downloads/list
>
> On May 12, 12:56 pm, Rod  wrote:
>
> > Hello,
>
> >      I'm completly new to GWT. I created an application and started it
> > on local host in hosted mode with no problems. It was communicating
> > with external database successfuly. But after I put it on a server I
> > got an RPC exception:
>
> > com.google.gwt.user.client.rpc.StatusCodeException: 
> > 
> > 
> > 
> > (none)
> > 
> > 
> > 
>
> > [...]
>
> > 
> > 
> > 
> > You don't have permission to access
> > 
> > /Test/war/test/gwt/
> > 
> > on this server.
> > 
>
> > [...]
>
> > I have completly no idea what's the reason of this problem. I've
> > searched the web for solution but I couldn't find any. The server
> > isn't mine so I think it may be problem in its configuration.  I'll be
> > very grateful for any help.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to Google-Web-Toolkit@googlegroups.com
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~--~~~~--~~--~--~---

Re: RPC problem after deploying on server

2009-05-12 Thread Jim


For GWT-database application, you can find an example in
http://www.gwtorm.com/mail/Mail.html. The source code is also
available there.Usually this kind of issue is due to serializable or
exception that is not handled in service.


Jim
http://www.gwtorm.com
http://code.google.com/p/dreamsource-orm/downloads/list

On May 12, 12:56 pm, Rod  wrote:
> Hello,
>
>      I'm completly new to GWT. I created an application and started it
> on local host in hosted mode with no problems. It was communicating
> with external database successfuly. But after I put it on a server I
> got an RPC exception:
>
> com.google.gwt.user.client.rpc.StatusCodeException: 
> 
> 
> 
> (none)
> 
> 
> 
>
> [...]
>
> 
> 
> 
> You don't have permission to access
> 
> /Test/war/test/gwt/
> 
> on this server.
> 
>
> [...]
>
> I have completly no idea what's the reason of this problem. I've
> searched the web for solution but I couldn't find any. The server
> isn't mine so I think it may be problem in its configuration.  I'll be
> very grateful for any help.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to Google-Web-Toolkit@googlegroups.com
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~--~~~~--~~--~--~---

RPC problem after deploying on server

2009-05-12 Thread Rod


Hello,


 I'm completly new to GWT. I created an application and started it
on local host in hosted mode with no problems. It was communicating
with external database successfuly. But after I put it on a server I
got an RPC exception:

com.google.gwt.user.client.rpc.StatusCodeException: 



(none)




[...]




You don't have permission to access

/Test/war/test/gwt/

on this server.


[...]

I have completly no idea what's the reason of this problem. I've
searched the web for solution but I couldn't find any. The server
isn't mine so I think it may be problem in its configuration.  I'll be
very grateful for any help.


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to Google-Web-Toolkit@googlegroups.com
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~--~~~~--~~--~--~---

Re: Android RPC Problem

2009-04-05 Thread Evan Ruff


Works perfectly.

Sorry guys, my fault.

E

On Apr 5, 2:17 pm, Evan Ruff  wrote:
> ANNND, I'm a moron.
>
> I've got 1.5.3 sitting there, but it's compiling against 1.5.2.
>
> Sorry guys!!!
>
> I'll upgrade and I'm sure that'll fix the issues.
>
> PHEW
>
> Evan
>
> On Apr 5, 2:13 pm, Evan Ruff  wrote:
>
> > Hey guys,
>
> > I'm trying to test out a simple little RPC guy using my G1. The
> > service works as expected on any of the desktop browsers, but when I
> > got to dispatch my RPC call from the G1, I get a service failed alert
> > on the client (aka, I hit the onFailure portion of the AsyncCallback)
> > and I get a "StandardContext[]Exception while dispatching incoming RPC
> > call" in the hosted mode console.
>
> > Here's the full stack:
>
> > [WARN] StandardContext[]Exception while dispatching incoming RPC call
> > java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
> >         at java.util.ArrayList.RangeCheck(ArrayList.java:546)
> >         at java.util.ArrayList.get(ArrayList.java:321)
> >         at
> > com.google.gwt.user.server.rpc.impl.ServerSerializationStreamReader.extract
> > (ServerSerializationStreamReader.java:617)
> >         at
> > com.google.gwt.user.server.rpc.impl.ServerSerializationStreamReader.readInt
> > (ServerSerializationStreamReader.java:432)
> >         at
> > com.google.gwt.user.client.rpc.impl.AbstractSerializationStreamReader.prepareToRead
> > (AbstractSerializationStreamReader.java:38)
> >         at
> > com.google.gwt.user.server.rpc.impl.ServerSerializationStreamReader.prepareToRead
> > (ServerSerializationStreamReader.java:383)
> >         at com.google.gwt.user.server.rpc.RPCCopy_GWT15.decodeRequest
> > (RPCCopy_GWT15.java:222)
> >         at 
> > com.google.gwt.user.server.rpc.RPCCopy.decodeRequest(RPCCopy.java:
> > 112)
> >         at net.sf.gilead.gwt.PersistentRemoteService.processCall
> > (PersistentRemoteService.java:143)
> >         at com.google.gwt.user.server.rpc.RemoteServiceServlet.doPost
> > (RemoteServiceServlet.java:86)
> >         at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
> >         at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
> >         at com.google.gwt.dev.shell.GWTShellServlet.service
> > (GWTShellServlet.java:289)
> >         at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
> >         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter
> > (ApplicationFilterChain.java:237)
> >         at org.apache.catalina.core.ApplicationFilterChain.doFilter
> > (ApplicationFilterChain.java:157)
> >         at org.apache.catalina.core.StandardWrapperValve.invoke
> > (StandardWrapperValve.java:214)
> >         at org.apache.catalina.core.StandardValveContext.invokeNext
> > (StandardValveContext.java:104)
> >         at org.apache.catalina.core.StandardPipeline.invoke
> > (StandardPipeline.java:520)
> >         at org.apache.catalina.core.StandardContextValve.invokeInternal
> > (StandardContextValve.java:198)
> >         at org.apache.catalina.core.StandardContextValve.invoke
> > (StandardContextValve.java:152)
> >         at org.apache.catalina.core.StandardValveContext.invokeNext
> > (StandardValveContext.java:104)
> >         at org.apache.catalina.core.StandardPipeline.invoke
> > (StandardPipeline.java:520)
> >         at org.apache.catalina.core.StandardHostValve.invoke
> > (StandardHostValve.java:137)
> >         at org.apache.catalina.core.StandardValveContext.invokeNext
> > (StandardValveContext.java:104)
> >         at org.apache.catalina.valves.ErrorReportValve.invoke
> > (ErrorReportValve.java:118)
> >         at org.apache.catalina.core.StandardValveContext.invokeNext
> > (StandardValveContext.java:102)
> >         at org.apache.catalina.core.StandardPipeline.invoke
> > (StandardPipeline.java:520)
> >         at org.apache.catalina.core.StandardEngineValve.invoke
> > (StandardEngineValve.java:109)
> >         at org.apache.catalina.core.StandardValveContext.invokeNext
> > (StandardValveContext.java:104)
> >         at org.apache.catalina.core.StandardPipeline.invoke
> > (StandardPipeline.java:520)
> >         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:
> > 929)
> >         at 
> > org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:
> > 160)
> >         at org.apache.coyote.http11.Http11Processor.process
> > (Http11Processor.java:799)
> >         at org.apache.coyote.http11.Http11Protocol
> > $Http11ConnectionHandler.processConnection(Http11Protocol.java:705)
> >         at org.apache.tomcat.util.net.TcpWorkerThread.runIt
> > (PoolTcpEndpoint.java:577)
> >         at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run
> > (ThreadPool.java:683)
> >         at java.lang.Thread.run(Thread.java:595)
>
> > I'm running GWT 1.5.3 on a Windows PC.
>
> > Has anyone else encountered this? The client side is a very simple
> > form that just submits a user name and password. I'm attempting to
> > just push the user back to the phone.

Re: Android RPC Problem

2009-04-05 Thread Evan Ruff


ANNND, I'm a moron.

I've got 1.5.3 sitting there, but it's compiling against 1.5.2.

Sorry guys!!!

I'll upgrade and I'm sure that'll fix the issues.

PHEW

Evan

On Apr 5, 2:13 pm, Evan Ruff  wrote:
> Hey guys,
>
> I'm trying to test out a simple little RPC guy using my G1. The
> service works as expected on any of the desktop browsers, but when I
> got to dispatch my RPC call from the G1, I get a service failed alert
> on the client (aka, I hit the onFailure portion of the AsyncCallback)
> and I get a "StandardContext[]Exception while dispatching incoming RPC
> call" in the hosted mode console.
>
> Here's the full stack:
>
> [WARN] StandardContext[]Exception while dispatching incoming RPC call
> java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
>         at java.util.ArrayList.RangeCheck(ArrayList.java:546)
>         at java.util.ArrayList.get(ArrayList.java:321)
>         at
> com.google.gwt.user.server.rpc.impl.ServerSerializationStreamReader.extract
> (ServerSerializationStreamReader.java:617)
>         at
> com.google.gwt.user.server.rpc.impl.ServerSerializationStreamReader.readInt
> (ServerSerializationStreamReader.java:432)
>         at
> com.google.gwt.user.client.rpc.impl.AbstractSerializationStreamReader.prepareToRead
> (AbstractSerializationStreamReader.java:38)
>         at
> com.google.gwt.user.server.rpc.impl.ServerSerializationStreamReader.prepareToRead
> (ServerSerializationStreamReader.java:383)
>         at com.google.gwt.user.server.rpc.RPCCopy_GWT15.decodeRequest
> (RPCCopy_GWT15.java:222)
>         at com.google.gwt.user.server.rpc.RPCCopy.decodeRequest(RPCCopy.java:
> 112)
>         at net.sf.gilead.gwt.PersistentRemoteService.processCall
> (PersistentRemoteService.java:143)
>         at com.google.gwt.user.server.rpc.RemoteServiceServlet.doPost
> (RemoteServiceServlet.java:86)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
>         at com.google.gwt.dev.shell.GWTShellServlet.service
> (GWTShellServlet.java:289)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
>         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter
> (ApplicationFilterChain.java:237)
>         at org.apache.catalina.core.ApplicationFilterChain.doFilter
> (ApplicationFilterChain.java:157)
>         at org.apache.catalina.core.StandardWrapperValve.invoke
> (StandardWrapperValve.java:214)
>         at org.apache.catalina.core.StandardValveContext.invokeNext
> (StandardValveContext.java:104)
>         at org.apache.catalina.core.StandardPipeline.invoke
> (StandardPipeline.java:520)
>         at org.apache.catalina.core.StandardContextValve.invokeInternal
> (StandardContextValve.java:198)
>         at org.apache.catalina.core.StandardContextValve.invoke
> (StandardContextValve.java:152)
>         at org.apache.catalina.core.StandardValveContext.invokeNext
> (StandardValveContext.java:104)
>         at org.apache.catalina.core.StandardPipeline.invoke
> (StandardPipeline.java:520)
>         at org.apache.catalina.core.StandardHostValve.invoke
> (StandardHostValve.java:137)
>         at org.apache.catalina.core.StandardValveContext.invokeNext
> (StandardValveContext.java:104)
>         at org.apache.catalina.valves.ErrorReportValve.invoke
> (ErrorReportValve.java:118)
>         at org.apache.catalina.core.StandardValveContext.invokeNext
> (StandardValveContext.java:102)
>         at org.apache.catalina.core.StandardPipeline.invoke
> (StandardPipeline.java:520)
>         at org.apache.catalina.core.StandardEngineValve.invoke
> (StandardEngineValve.java:109)
>         at org.apache.catalina.core.StandardValveContext.invokeNext
> (StandardValveContext.java:104)
>         at org.apache.catalina.core.StandardPipeline.invoke
> (StandardPipeline.java:520)
>         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:
> 929)
>         at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:
> 160)
>         at org.apache.coyote.http11.Http11Processor.process
> (Http11Processor.java:799)
>         at org.apache.coyote.http11.Http11Protocol
> $Http11ConnectionHandler.processConnection(Http11Protocol.java:705)
>         at org.apache.tomcat.util.net.TcpWorkerThread.runIt
> (PoolTcpEndpoint.java:577)
>         at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run
> (ThreadPool.java:683)
>         at java.lang.Thread.run(Thread.java:595)
>
> I'm running GWT 1.5.3 on a Windows PC.
>
> Has anyone else encountered this? The client side is a very simple
> form that just submits a user name and password. I'm attempting to
> just push the user back to the phone.
>
> Thanks for any help or advice!
>
> Evan
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to Google-Web-Toolkit@googlegroups.com
To unsubscribe

Android RPC Problem

2009-04-05 Thread Evan Ruff


Hey guys,

I'm trying to test out a simple little RPC guy using my G1. The
service works as expected on any of the desktop browsers, but when I
got to dispatch my RPC call from the G1, I get a service failed alert
on the client (aka, I hit the onFailure portion of the AsyncCallback)
and I get a "StandardContext[]Exception while dispatching incoming RPC
call" in the hosted mode console.

Here's the full stack:

[WARN] StandardContext[]Exception while dispatching incoming RPC call
java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
at java.util.ArrayList.RangeCheck(ArrayList.java:546)
at java.util.ArrayList.get(ArrayList.java:321)
at
com.google.gwt.user.server.rpc.impl.ServerSerializationStreamReader.extract
(ServerSerializationStreamReader.java:617)
at
com.google.gwt.user.server.rpc.impl.ServerSerializationStreamReader.readInt
(ServerSerializationStreamReader.java:432)
at
com.google.gwt.user.client.rpc.impl.AbstractSerializationStreamReader.prepareToRead
(AbstractSerializationStreamReader.java:38)
at
com.google.gwt.user.server.rpc.impl.ServerSerializationStreamReader.prepareToRead
(ServerSerializationStreamReader.java:383)
at com.google.gwt.user.server.rpc.RPCCopy_GWT15.decodeRequest
(RPCCopy_GWT15.java:222)
at com.google.gwt.user.server.rpc.RPCCopy.decodeRequest(RPCCopy.java:
112)
at net.sf.gilead.gwt.PersistentRemoteService.processCall
(PersistentRemoteService.java:143)
at com.google.gwt.user.server.rpc.RemoteServiceServlet.doPost
(RemoteServiceServlet.java:86)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at com.google.gwt.dev.shell.GWTShellServlet.service
(GWTShellServlet.java:289)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter
(ApplicationFilterChain.java:237)
at org.apache.catalina.core.ApplicationFilterChain.doFilter
(ApplicationFilterChain.java:157)
at org.apache.catalina.core.StandardWrapperValve.invoke
(StandardWrapperValve.java:214)
at org.apache.catalina.core.StandardValveContext.invokeNext
(StandardValveContext.java:104)
at org.apache.catalina.core.StandardPipeline.invoke
(StandardPipeline.java:520)
at org.apache.catalina.core.StandardContextValve.invokeInternal
(StandardContextValve.java:198)
at org.apache.catalina.core.StandardContextValve.invoke
(StandardContextValve.java:152)
at org.apache.catalina.core.StandardValveContext.invokeNext
(StandardValveContext.java:104)
at org.apache.catalina.core.StandardPipeline.invoke
(StandardPipeline.java:520)
at org.apache.catalina.core.StandardHostValve.invoke
(StandardHostValve.java:137)
at org.apache.catalina.core.StandardValveContext.invokeNext
(StandardValveContext.java:104)
at org.apache.catalina.valves.ErrorReportValve.invoke
(ErrorReportValve.java:118)
at org.apache.catalina.core.StandardValveContext.invokeNext
(StandardValveContext.java:102)
at org.apache.catalina.core.StandardPipeline.invoke
(StandardPipeline.java:520)
at org.apache.catalina.core.StandardEngineValve.invoke
(StandardEngineValve.java:109)
at org.apache.catalina.core.StandardValveContext.invokeNext
(StandardValveContext.java:104)
at org.apache.catalina.core.StandardPipeline.invoke
(StandardPipeline.java:520)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:
929)
at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:
160)
at org.apache.coyote.http11.Http11Processor.process
(Http11Processor.java:799)
at org.apache.coyote.http11.Http11Protocol
$Http11ConnectionHandler.processConnection(Http11Protocol.java:705)
at org.apache.tomcat.util.net.TcpWorkerThread.runIt
(PoolTcpEndpoint.java:577)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run
(ThreadPool.java:683)
at java.lang.Thread.run(Thread.java:595)

I'm running GWT 1.5.3 on a Windows PC.

Has anyone else encountered this? The client side is a very simple
form that just submits a user name and password. I'm attempting to
just push the user back to the phone.

Thanks for any help or advice!

Evan

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to Google-Web-Toolkit@googlegroups.com
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~--~~~~--~~--~--~---

GWT RPC problem..

2009-03-27 Thread chandrashekhar patil

Hi All,
I am new to GWT. I am getting problem in calling the RPC methods. before I
had problem with entity not mapped,  it solved now but getting new problem
that not returning any valued from *getOneByLoginAndPassword* method.. I get
value from database but not *LoginImpl*..

gettting following error and source code given as well

[WARN] StandardContext[]Exception while dispatching incoming RPC call
com.google.gwt.user.server.rpc.UnexpectedException: Service method 'public
abstract java.lang.String
com.mycompany.client.gwtinterfaces.Login.login(java.lang.String,java.lang.String)'
threw an unexpected exception: java.lang.NullPointerException
at
com.google.gwt.user.server.rpc.RPC.encodeResponseForFailure(RPC.java:360)
at
com.google.gwt.user.server.rpc.RPC.invokeAndEncodeResponse(RPC.java:546)
at
com.google.gwt.user.server.rpc.RemoteServiceServlet.processCall(RemoteServiceServlet.java:164)
at
com.google.gwt.user.server.rpc.RemoteServiceServlet.doPost(RemoteServiceServlet.java:86)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at
com.google.gwt.dev.shell.GWTShellServlet.service(GWTShellServlet.java:289)

<..skip ..>
..
Caused by: java.lang.NullPointerException: null
at com.mycompany.server.LoginImpl.login(LoginImpl.java:37)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
com.google.gwt.user.server.rpc.RPC.invokeAndEncodeResponse(RPC.java:527)
at
com.google.gwt.user.server.rpc.RemoteServiceServlet.processCall(RemoteServiceServlet.java:164)
at
com.google.gwt.user.server.rpc.RemoteServiceServlet.doPost(RemoteServiceServlet.java:86)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at
com.google.gwt.dev.shell.GWTShellServlet.service(GWTShellServlet.java:289)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237)

source Code  is as follows..

*1.*
*public class LoginImpl extends RemoteServiceServlet implements Login {*
*public String login(String user, String password) {*
System.out.println(" user"+user+"  pass;"+password);
   * UserLogin userLogin = new
UserLoginsDb().getOneByLoginAndPassword(user, password)*;
System.out.println("User is:" +userLogin.login);* // Not getting
any thing gives error*
*}*
*}*

*2.*
*public class UserLoginsDb extends GenericDbOperations {*

public UserLogin *getOneByLoginAndPassword(String login, String
password)* {
 try {
   * return new
NativeSqlQueryExecutor().executeSqlOneRow(
 "select * from userlogin where login=:login and
cryptedpassword=:password and isactive=1",
new String[]{"login","password"},
new Object[]{login,password});*
}
catch (TooManyRowsException e) {
// TODO Auto-generated catch block
LogMain.error(e.getMessage());
return null;
}
}

*}*

*
3.
   public T executeSqlOneRow( String sql, String[] paramNames,
Object[] paramValues) throws TooManyRowsException {*

  *  List l=executeSql(sql,paramNames,paramValues);*
if (l.size()==0) return null;
   // if (l.size()>1) throw new TooManyRowsException();
System.out.println("excuteSQL one row" +l.get(0)); *   // I am
getting object output here*
System.out.println("excuteSQL one row" +l.size());   * // I am
getting object output here*
return l.get(0);
*}*


*4.*
   @SuppressWarnings("unchecked") *public List executeSql(String sql,
String[] paramNames,
Object[] paramValues) {*
Session sess = null;
try {
sess = HibernateUtil.getSessionWithTransaction();

Query query = sess.createSQLQuery(sql);
if (paramNames != null) {
for (int i = 0; i < paramNames.length; i++) {
   query.setParameter(paramNames[i], paramValues[i]);
}
}
List list = (List) query.list(); // here hibernate
executes the query

sess.close();
return list;
}
finally {
if (sess != null) {
if (sess.isOpen())
if (sess.getTransaction() != null)
sess.getTransaction().rollback();
}
}
 *   }*


Can anybody please tell where is the problem. Really don't understand why..
if anything more needed please let me know..
thx in advance.

--~--~-~--~~~---~--~~
You received this message because you are subscrib

Re: GWT RPC problem while deploying on glassfish

2009-02-19 Thread Felipe Cypriano

What's is the code for this class: client.modeller.Student  ?

Regards,

---
Felipe Marin Cypriano
Vitória - ES
http://www.linkedin.com/in/felipecypriano


On Wed, Feb 18, 2009 at 12:15 PM, yek...@gmail.com  wrote:

>
> Hi everybody
>
> I builded a war and using gwt-rpc mechanism. It works well on tomcat.
> But there comes a problem when I want to deploy on glassfish. I
> couldn't find anything on web. I will be happy if somebody helps. The
> error is written below.(detected on glassfish logs)
>
> Exception while dispatching incoming RPC call
> com.google.gwt.user.client.rpc.SerializationException: Type
> '[Lheadman.client.modeller.Student;' was not included in the set of
> types which can be serialized by this SerializationPolicy or its Class
> object could not be loaded. For security purposes, this type will not
> be serialized.
>at
>
> com.google.gwt.user.server.rpc.impl.StandardSerializationPolicy.validateSerialize
> (StandardSerializationPolicy.java:83)
>at
>
> com.google.gwt.user.server.rpc.impl.ServerSerializationStreamWriter.serialize
> (ServerSerializationStreamWriter.java:591)
>at
>
> com.google.gwt.user.client.rpc.impl.AbstractSerializationStreamWriter.writeObject
> (AbstractSerializationStreamWriter.java:129)
>at
> com.google.gwt.user.server.rpc.impl.ServerSerializationStreamWriter
> $ValueWriter$8.write(ServerSerializationStreamWriter.java:146)
>at
>
> com.google.gwt.user.server.rpc.impl.ServerSerializationStreamWriter.serializeValue
> (ServerSerializationStreamWriter.java:530)
>at com.google.gwt.user.server.rpc.RPC.encodeResponse(RPC.java:
> 573)
>at com.google.gwt.user.server.rpc.RPC.encodeResponseForSuccess
> (RPC.java:441)
>at com.google.gwt.user.server.rpc.RPC.invokeAndEncodeResponse
> (RPC.java:529)
>at
> com.google.gwt.user.server.rpc.RemoteServiceServlet.processCall
> (RemoteServiceServlet.java:164)
>at com.google.gwt.user.server.rpc.RemoteServiceServlet.doPost
> (RemoteServiceServlet.java:86)
>at javax.servlet.http.HttpServlet.service(HttpServlet.java:
> 754)
>at javax.servlet.http.HttpServlet.service(HttpServlet.java:
> 847)
>at
> org.apache.catalina.core.ApplicationFilterChain.servletService
> (ApplicationFilterChain.java:427)
>at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter
> (ApplicationFilterChain.java:333)
>at org.apache.catalina.core.ApplicationFilterChain.doFilter
> (ApplicationFilterChain.java:214)
>at com.uwyn.rife.servlet.RifeFilter.doFilter(RifeFilter.java:
> 192)
>at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter
> (ApplicationFilterChain.java:246)
>at org.apache.catalina.core.ApplicationFilterChain.doFilter
> (ApplicationFilterChain.java:214)
>at org.apache.catalina.core.StandardWrapperValve.invoke
> (StandardWrapperValve.java:313)
>at org.apache.catalina.core.StandardContextValve.invokeInternal
> (StandardContextValve.java:287)
>at org.apache.catalina.core.StandardContextValve.invoke
> (StandardContextValve.java:218)
>at org.apache.catalina.core.StandardPipeline.doInvoke
> (StandardPipeline.java:648)
>at org.apache.catalina.core.StandardPipeline.doInvoke
> (StandardPipeline.java:593)
>at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:
> 94)
>at
> com.sun.enterprise.web.PESessionLockingStandardPipeline.invoke
> (PESessionLockingStandardPipeline.java:98)
>at org.apache.catalina.core.StandardHostValve.invoke
> (StandardHostValve.java:222)
>at org.apache.catalina.core.StandardPipeline.doInvoke
> (StandardPipeline.java:648)
>at org.apache.catalina.core.StandardPipeline.doInvoke
> (StandardPipeline.java:593)
>at org.apache.catalina.core.StandardPipeline.invoke
> (StandardPipeline.java:587)
>at org.apache.catalina.core.ContainerBase.invoke
> (ContainerBase.java:1096)
>at org.apache.catalina.core.StandardEngineValve.invoke
> (StandardEngineValve.java:166)
>at org.apache.catalina.core.StandardPipeline.doInvoke
> (StandardPipeline.java:648)
>at org.apache.catalina.core.StandardPipeline.doInvoke
> (StandardPipeline.java:593)
>at org.apache.catalina.core.StandardPipeline.invoke
> (StandardPipeline.java:587)
>at org.apache.catalina.core.ContainerBase.invoke
> (ContainerBase.java:1096)
>at org.apache.coyote.tomcat5.CoyoteAdapter.service
> (CoyoteAdapter.java:288)
>at
> com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.invokeAdapter
> (DefaultProcessorTask.java:647)
>at
> com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.doProcess
> (DefaultProcessorTask.java:579)
>at
> com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.process
> (DefaultProcessorTask.java:831)
>at
>
> com.sun.enterprise.web.connector.grizzly.DefaultReadTask.executeProcessorTask
> (DefaultReadTask.java:341)
>

GWT RPC problem while deploying on glassfish

2009-02-18 Thread yek...@gmail.com


Hi everybody

I builded a war and using gwt-rpc mechanism. It works well on tomcat.
But there comes a problem when I want to deploy on glassfish. I
couldn't find anything on web. I will be happy if somebody helps. The
error is written below.(detected on glassfish logs)

Exception while dispatching incoming RPC call
com.google.gwt.user.client.rpc.SerializationException: Type
'[Lheadman.client.modeller.Student;' was not included in the set of
types which can be serialized by this SerializationPolicy or its Class
object could not be loaded. For security purposes, this type will not
be serialized.
at
com.google.gwt.user.server.rpc.impl.StandardSerializationPolicy.validateSerialize
(StandardSerializationPolicy.java:83)
at
com.google.gwt.user.server.rpc.impl.ServerSerializationStreamWriter.serialize
(ServerSerializationStreamWriter.java:591)
at
com.google.gwt.user.client.rpc.impl.AbstractSerializationStreamWriter.writeObject
(AbstractSerializationStreamWriter.java:129)
at
com.google.gwt.user.server.rpc.impl.ServerSerializationStreamWriter
$ValueWriter$8.write(ServerSerializationStreamWriter.java:146)
at
com.google.gwt.user.server.rpc.impl.ServerSerializationStreamWriter.serializeValue
(ServerSerializationStreamWriter.java:530)
at com.google.gwt.user.server.rpc.RPC.encodeResponse(RPC.java:
573)
at com.google.gwt.user.server.rpc.RPC.encodeResponseForSuccess
(RPC.java:441)
at com.google.gwt.user.server.rpc.RPC.invokeAndEncodeResponse
(RPC.java:529)
at
com.google.gwt.user.server.rpc.RemoteServiceServlet.processCall
(RemoteServiceServlet.java:164)
at com.google.gwt.user.server.rpc.RemoteServiceServlet.doPost
(RemoteServiceServlet.java:86)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:
754)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:
847)
at
org.apache.catalina.core.ApplicationFilterChain.servletService
(ApplicationFilterChain.java:427)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter
(ApplicationFilterChain.java:333)
at org.apache.catalina.core.ApplicationFilterChain.doFilter
(ApplicationFilterChain.java:214)
at com.uwyn.rife.servlet.RifeFilter.doFilter(RifeFilter.java:
192)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter
(ApplicationFilterChain.java:246)
at org.apache.catalina.core.ApplicationFilterChain.doFilter
(ApplicationFilterChain.java:214)
at org.apache.catalina.core.StandardWrapperValve.invoke
(StandardWrapperValve.java:313)
at org.apache.catalina.core.StandardContextValve.invokeInternal
(StandardContextValve.java:287)
at org.apache.catalina.core.StandardContextValve.invoke
(StandardContextValve.java:218)
at org.apache.catalina.core.StandardPipeline.doInvoke
(StandardPipeline.java:648)
at org.apache.catalina.core.StandardPipeline.doInvoke
(StandardPipeline.java:593)
at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:
94)
at
com.sun.enterprise.web.PESessionLockingStandardPipeline.invoke
(PESessionLockingStandardPipeline.java:98)
at org.apache.catalina.core.StandardHostValve.invoke
(StandardHostValve.java:222)
at org.apache.catalina.core.StandardPipeline.doInvoke
(StandardPipeline.java:648)
at org.apache.catalina.core.StandardPipeline.doInvoke
(StandardPipeline.java:593)
at org.apache.catalina.core.StandardPipeline.invoke
(StandardPipeline.java:587)
at org.apache.catalina.core.ContainerBase.invoke
(ContainerBase.java:1096)
at org.apache.catalina.core.StandardEngineValve.invoke
(StandardEngineValve.java:166)
at org.apache.catalina.core.StandardPipeline.doInvoke
(StandardPipeline.java:648)
at org.apache.catalina.core.StandardPipeline.doInvoke
(StandardPipeline.java:593)
at org.apache.catalina.core.StandardPipeline.invoke
(StandardPipeline.java:587)
at org.apache.catalina.core.ContainerBase.invoke
(ContainerBase.java:1096)
at org.apache.coyote.tomcat5.CoyoteAdapter.service
(CoyoteAdapter.java:288)
at
com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.invokeAdapter
(DefaultProcessorTask.java:647)
at
com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.doProcess
(DefaultProcessorTask.java:579)
at
com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.process
(DefaultProcessorTask.java:831)
at
com.sun.enterprise.web.connector.grizzly.DefaultReadTask.executeProcessorTask
(DefaultReadTask.java:341)
at
com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask
(DefaultReadTask.java:263)
at
com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask
(DefaultReadTask.java:214)
at com.sun.enterprise.web.portunif.PortUnificationPipeline
$PUTask.doTask(PortUnificationPipeline.java:380)
at com.sun.enterprise.web.connector.grizzly.TaskBase.run
(TaskBase.java:265)

Re: A simple RPC problem. Did anyone encounter a problem like this?

2009-01-09 Thread Sumit Chandel

Hi Patrick,

If the problem is indeed deployment configuration, I would recommend
checking out the doc linked below and comparing your configuration to the
ones prescribed.

Example Deployment with Tomcat:
http://code.google.com/docreader/#p=google-web-toolkit-doc-1-5&s=google-web-toolkit-doc-1-5&t=DevGuideRPCDeployment

Some extra information that would help would be if you could use an HTTP
traffic analyzer to check the request and response headers (if you are
receiving a response at all).

Hope that helps,
-Sumit Chandel

On Tue, Jan 6, 2009 at 4:30 PM, steve.myatt.2...@googlemail.com <
steve.my...@tesco.net> wrote:

>
> Hi Patrick
>
> I think I have same underlying problem - I don't think my servlet is
> being deployed properly. I suspect a config problem (web.xml and/or
> app.gwt.xml) OR deployment directories - /com/mycompany/app vs. /
> com.mycompany.app/ - for .class files.
>
> This thread is the nearest I've got to a solution, if it's config:
>
> http://www.manning-sandbox.com/thread.jspa?threadID=22204&tstart=0
>
> but it's a bit old.
>
> I bumped into this with very early experimentation with RPC.
>
> There are various howto's around on this topic, none of which have
> resolved this for me. google "gwt +rpc +deploy +tomcat"
>
> I put getModuleBaseURL to a text field and find (as per kebernet's
> explanation):
>
>  // external, tomcat:
>  //
> http://localhost:8080/music/MusicService
>  // hosted, eclipse:
>  //
> http://localhost:/net.dnsdojo.slm.music.Music/MusicService
>
> I double checked the XML files, no joy. Experimented changing a few
> url/paths to see what breaks (hosted, external). No solution so far.
>
> It's late here, got early start 2moz, gotta go - more later.
>
> Oh - BTW:
> Google Web Toolkit 1.5.3
> Apache Tomcat/6.0.18
> ???
> Cheers
>
>
> On Jan 2, 5:56 am, Patrick  wrote:
> > Hi all,
> > I have a GWT application which
> > - works fine in hosted mode,
> > - works fine in Firefox after being deployed in Tomcat6. but,
> > - does not work in IE6! no (right or wrong) response from remote
> > service.
> >
> > Environment: GWT1.53/GWT Designer 5.1/ Eclipse 3.4/Tomcat6.0
> >
> > The application is to reverse a string, and even when use IE6, the
> > service does do the work, eg. receives "123" from html page and covert
> > it into "321" (the ***Impl really does this work, there is a
> > System.out.println statement in ***Impl.java) and then return. It is
> > supposed that onSuccess or onFailure would be invoked, but there is no
> > output from the Window.alert(msg) statements in onSuccess and
> > onFailure method.
> >
> > Thanks!
> >
> > Patrick
>
> >
>

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to Google-Web-Toolkit@googlegroups.com
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~--~~~~--~~--~--~---

Re: A simple RPC problem. Did anyone encounter a problem like this?

2009-01-06 Thread steve.myatt.2...@googlemail.com

Hi Patrick

I think I have same underlying problem - I don't think my servlet is
being deployed properly. I suspect a config problem (web.xml and/or
app.gwt.xml) OR deployment directories - /com/mycompany/app vs. /
com.mycompany.app/ - for .class files.

This thread is the nearest I've got to a solution, if it's config:

http://www.manning-sandbox.com/thread.jspa?threadID=22204&tstart=0

but it's a bit old.

I bumped into this with very early experimentation with RPC.

There are various howto's around on this topic, none of which have
resolved this for me. google "gwt +rpc +deploy +tomcat"

I put getModuleBaseURL to a text field and find (as per kebernet's
explanation):

  // external, tomcat:
  //  http://localhost:8080/music/MusicService
  // hosted, eclipse:
  // 
http://localhost:/net.dnsdojo.slm.music.Music/MusicService

I double checked the XML files, no joy. Experimented changing a few
url/paths to see what breaks (hosted, external). No solution so far.

It's late here, got early start 2moz, gotta go - more later.

Oh - BTW:
Google Web Toolkit 1.5.3
Apache Tomcat/6.0.18
???
Cheers

On Jan 2, 5:56 am, Patrick  wrote:
> Hi all,
> I have a GWT application which
> - works fine in hosted mode,
> - works fine in Firefox after being deployed in Tomcat6. but,
> - does not work in IE6! no (right or wrong) response from remote
> service.
>
> Environment: GWT1.53/GWT Designer 5.1/ Eclipse 3.4/Tomcat6.0
>
> The application is to reverse a string, and even when use IE6, the
> service does do the work, eg. receives "123" from html page and covert
> it into "321" (the ***Impl really does this work, there is a
> System.out.println statement in ***Impl.java) and then return. It is
> supposed that onSuccess or onFailure would be invoked, but there is no
> output from the Window.alert(msg) statements in onSuccess and
> onFailure method.
>
> Thanks!
>
> Patrick

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to Google-Web-Toolkit@googlegroups.com
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~--~~~~--~~--~--~---

A simple RPC problem. Did anyone encounter a problem like this?

2009-01-02 Thread Patrick


Hi all,
I have a GWT application which
- works fine in hosted mode,
- works fine in Firefox after being deployed in Tomcat6. but,
- does not work in IE6! no (right or wrong) response from remote
service.

Environment: GWT1.53/GWT Designer 5.1/ Eclipse 3.4/Tomcat6.0

The application is to reverse a string, and even when use IE6, the
service does do the work, eg. receives "123" from html page and covert
it into "321" (the ***Impl really does this work, there is a
System.out.println statement in ***Impl.java) and then return. It is
supposed that onSuccess or onFailure would be invoked, but there is no
output from the Window.alert(msg) statements in onSuccess and
onFailure method.

Thanks!

Patrick

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to Google-Web-Toolkit@googlegroups.com
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~--~~~~--~~--~--~---

Re: RPC problem

2008-10-15 Thread Jamie


> Please teach me your solution.

My solution is to open up www.google.com and type in
IncompatibleRemoteServiceException.

The first hit lists a pretty good list of possible causes.
This could be caused by the client and server not running the same
codebase, as in, one or the other has not been compiled after a change
to the code.


On Oct 14, 6:43 am, Ryan <[EMAIL PROTECTED]> wrote:
> Hi group,
>
> I'm writing a gwt-rpc application, it does simple String message
> passing from server to client.
> But I got a runtime error
> "com.google.gwt.user.client.rpc.IncompatibleRemoteServiceException"
> and nothing can be received from the server.
> I have no idea what is the reason of this error.
> Does anyone has same experience?
> Please teach me your solution.
> Many Thanks!
>
> Ryan
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to Google-Web-Toolkit@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~--~~~~--~~--~--~---

RPC problem

2008-10-14 Thread Ryan


Hi group,

I'm writing a gwt-rpc application, it does simple String message
passing from server to client.
But I got a runtime error
"com.google.gwt.user.client.rpc.IncompatibleRemoteServiceException"
and nothing can be received from the server.
I have no idea what is the reason of this error.
Does anyone has same experience?
Please teach me your solution.
Many Thanks!

Ryan

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to Google-Web-Toolkit@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~--~~~~--~~--~--~---

53 matches

Mail list logo