Your GWT code must know about MyInterfaceImpl and its serializer, otherwise
GWT does not know how to deserialize the data when you send MyInterfaceImpl
from the server to the client.
When you use an interface with GWT-RPC then GWT will search for all
implementations of that interface and only t
MyInterfaceImpl.class in server class path, but module B is
not included in module A gwt.xml file. I got the following error message
- Type 'MyInterfaceImpl was not included in the set of types which can be
serialized by this SerializationPolicy or its Class object could not be
loaded. How do I re
Bredel:
>>
>> Hey Folks,
>>
>> how can I configure GWT web applications containing an encoded dash ('-'
>> gets %2D in some browser calls) to not fail when getting the
>> SerializationPolicy.
>>
>> I get this for example:
>>
>>
g an encoded dash ('-'
> gets %2D in some browser calls) to not fail when getting the
> SerializationPolicy.
>
> I get this for example:
>
> INFO: MySuperService: ERROR: The module path requested, */
> super%2Dwebapp/client/*, is not in the same web application as this
Hey Folks,
how can I configure GWT web applications containing an encoded dash ('-'
gets %2D in some browser calls) to not fail when getting the
SerializationPolicy.
I get this for example:
INFO: MySuperService: ERROR: The module path requested, */
super%2Dwebapp/client/*, is not i
StacktraceElement is marked as transient to keep it out of serialization.
Because of that, RPC system is not aware of the type. If you really want to
transfer the stack trace with your exception, then put a dummy field in
your exception:
private StackTraceElement dummyFieldToIncludeType;
This w
Hi guys,
I am unable to serialize my own Exception class. I have created an
exception class as follows:
public class KeyNotFoundException extends java.lang.Exception {
private String key;
private String resourceBundleName;
/**
* The key was not found in the resource bundle
It happened to me recently. This means an object returned by your
server-side code is actually a dynamic proxy. Hopefully by reading the
whole stack trace you might figure out which object in your graph is
the proxy. Then, you need to replace it by a serializable
implementation.
I am pretty sure y
Hey guys,
have you ever get an error like this?
All my types are Serializables, default constructor, etc... like always.
I dont know that is this '$Proxy86' that is shown in the error
thanks for your help
--
You received this message because you are subscribed to the Google Groups
"Google W
collections, maps and dates (which are subclasses of the
> original classes) i have problems receiving data from the database
> because those classes are not on the whitelist of GWTs
> SerializationPolicy. So i get the following error:
>
> "com.google.g
Hello,
I'm using GWT 2.3.0 with objectdb 2.2.8. Since objectdb uses proxy
classes for collections, maps and dates (which are subclasses of the
original classes) i have problems receiving data from the database
because those classes are not on the whitelist of GWTs
SerializationPolicy. So
IIRC, the names of the .gwt.rpc files match the permutations' strong name
(i.e. the *.cache.html names). The server loads the policy file that the
client tells it to in the request; so maybe your client code is stale? (such
as loaded from your browser cache, ith an older version as the one deplo
Hello, everybody.
I have some issue about serialization policy
02.02.2011 11:42:56 org.apache.catalina.core.ApplicationContext log
INFO: OfferService: ERROR: The serialization policy file '/projectname/
49A207B5053D225FEE4723A0D63D0A7E.gwt.rpc' was not found; did you
forget to inc
lude it in this
ion policy file '/bcs/
> 99E2FAA12E412633D1C3951141C107AD.gwt.rpc' was not found; did you
> forget to include it in this deployment?
> Dec 27, 2010 8:52:47 AM org.apache.catalina.core.ApplicationContext
> log
> INFO: ChatServlet: WARNING: Failed to get the SerializationPolicy
&
ion policy file '/bcs/
> 99E2FAA12E412633D1C3951141C107AD.gwt.rpc' was not found; did you
> forget to include it in this deployment?
> Dec 27, 2010 8:52:47 AM org.apache.catalina.core.ApplicationContext
> log
> INFO: ChatServlet: WARNING: Failed to get the SerializationPolicy
&
deployment?
Dec 27, 2010 8:52:47 AM org.apache.catalina.core.ApplicationContext
log
INFO: ChatServlet: WARNING: Failed to get the SerializationPolicy
'99E2FAA12E412633D1C3951141C107AD' for module 'http://www.bavaria64.de/
bcs/bcs/'; a legacy, 1.3.3 compatible, serialization policy w
; through extend lengths to ensure this is not possible, and I can only
> come as close as:
> com.google.gwt.user.server.rpc.RPC:252:
> SerializationPolicy serializationPolicy =
> streamReader.getSerializationPolicy();
>
> So I end up with something like this:
>
> Method ta
d by RPC's
ServerSerializingStreamReader. But as it seems, the GWT team has gone
through extend lengths to ensure this is not possible, and I can only
come as close as:
com.google.gwt.user.server.rpc.RPC:252:
SerializationPolicy serializationPolicy =
streamReader.getSerializationPolicy();
So I end up
ed here, the problem changes to:
>
> com.google.gwt.user.client.rpc.SerializationException: Type '[I' 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.: instan
described here, the problem changes to:
com.google.gwt.user.client.rpc.SerializationException: Type '[I' 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
erializableWhiteList serializableWhiteList
(SerializableWhiteList s) {
throw new RuntimeException("This Method is only used to put
Beans to
the SerializationPolicy, please do not call it");
}
}
Greetings
On Nov 16, 4:51 am, Edgenius wrote:
> It is not new question
I am faced the same problem.
So what is the way to customize serialization whitelist ?
On 16 ноя, 06:51, Edgenius wrote:
> It is not new questions in this group. But I face a new problem in
> 2.0M2 as SerializationPolicy logic is changed. I know GWT will put
> serializition c
It is not new questions in this group. But I face a new problem in
2.0M2 as SerializationPolicy logic is changed. I know GWT will put
serializition class into SerializationPolicy whitelist. Before 2.0, I
create a dummy method which hold all classes I want to pass to client
side but they are not
class to SerializationPolicy directly?
> I don't want to reference it in Service class and I cannot refernce it
> as a non-transient member.
> I need this because this class is a member of another class having its
> own custom serializer and this class also has its own serializer. Both
Hello, everyone!
How can I add a class to SerializationPolicy directly?
I don't want to reference it in Service class and I cannot refernce it
as a non-transient member.
I need this because this class is a member of another class having its
own custom serializer and this class also has it
I agree with that, i'm using a generic DTO too with a Map because i don't want to bother to create an
IServiceInterfaceAsync for every RPC method i need. So telling in an
annotation to GWT which objects are likely to travel over http would
be nice.
However if we could provide something more flexi
+1, a way to specify Object to serialize would be fine !!!
On Apr 17, 10:20 pm, Daniel Kurka wrote:
> this is exactly what i was thinking.
> we need a way to specify the classes that are okay to serialiaze with the
> service
>
> 2009/4/17 Vitali Lovich
>
>
>
> > Hasn't been accepted - just open
this is exactly what i was thinking.
we need a way to specify the classes that are okay to serialiaze with the
service
2009/4/17 Vitali Lovich
> Hasn't been accepted - just opened. Anyone can open issues against GWT.
>
> That being said, I think there could be room for improvement. For
> insta
Hasn't been accepted - just opened. Anyone can open issues against GWT.
That being said, I think there could be room for improvement. For instance,
if you specify a serializable interface or serializable abstract class, you
should be allowed to enumerate all the various types that can possibly g
Frankly I don't see how that issue could be accepted, the fact that
you have to mark all your serializable objects as Serializable or
IsSerializable has been there from the beginning. It's related to the
way the compiler has to know at compile time what objects are allowed
to travel through RPCs a
I added my concerns to this issue in the gwt issue tracker:
http://code.google.com/p/google-web-toolkit/issues/detail?id=3521
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To post to th
Using IsSerializable instead of Serializable should also cut down on the
number of objects (although of course you have to modify your classes if you
marked them as Serializable only).
On Thu, Apr 16, 2009 at 6:10 AM, Salvador Diaz wrote:
>
> > any more suggestions?
>
> Create a marker interface
> any more suggestions?
Create a marker interface for the objects that you want to go through
RPCs and type your Map with it:
public interface DTO extends Serializable{
}
...
The you declare your Map as:
Map
Would that work ?
--~--~-~--~~~---~--~~
You received
avoid
this solution...
Is it not possible:
1. to implement the SerializationPolicy and add the class that are
Serializable.
2. define annotations in the RPC service with allowed Serializable
objects.
Fred
On Apr 15, 9:30 pm, Daniel Kurka wrote:
> The problem is that the compiler will create
; > compiler at compile time by analizing the members of a class.
> >
> > > But we can have classes (which ARE serializable) inside our transient
> map,
> > > but gwt will not serialize this classes because of the
> SerializationPolicy
> > > (these
ass.
>
> > But we can have classes (which ARE serializable) inside our transient map,
> > but gwt will not serialize this classes because of the SerializationPolicy
> > (these classes could not be found by the compiler at compile time).
>
> > Is there any way to extend the whi
xtend the SerializationPolicy
(whiteList...) ?? perhaps can we use annotations like
@gwt.typeArgs
On 14 avr, 16:36, Daniel Kurka wrote:
> For data transport we use a simple java class containing a Map Object> This map is transient and we serialize it with a custom field
> serializer. This
generated by the
compiler at compile time by analizing the members of a class.
But we can have classes (which ARE serializable) inside our transient map,
but gwt will not serialize this classes because of the SerializationPolicy
(these classes could not be found by the compiler at compile time
not using default) with the tag?
On Apr 10, 6:08 am, PeteF wrote:
> Hi all,
>
> I am getting the exception "TableVO 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
Hi all,
I am getting the exception "TableVO 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." and I do not understand why. Here is the struc
Hello all,
How can I force a class into the SerializationPolicy file? I have a
CustomSerializer for class A, which contains class B as an attribute,
B also serializes though a CustomSerializer. In A's CustomSerializer I
have a call to streamWriter.writeObject(instance.getB()), but this
fai
I described what I am doing with the serialization in greater detail
in this blog post:
http://www.techhui.com/profiles/blogs/simpler-and-speedier-gwt-with
thanks,
Pat
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Grou
I described what I'm doing with the serialization in great detail here
in a blog posting, just in case anyone is interested:
http://www.techhui.com/profiles/blog/show?id=1702911%3ABlogPost%3A31619&page=1#comment-1702911_Comment_31745
thanks,
Pat
--~--~-~--~~~---~--~-
The Google IO talk that introduced the topic is here:
http://sites.google.com/site/io/resource-bundles-and-linkers-in-google-web-toolkit
The public APIs are just not very convenient to use at this point.
thanks,
Pat
--~--~-~--~~~---~--~~
You received this messag
I see. Interesting.
In that case the easiest way I can think of would be to forget the
strong name, name the RPC file some arbitrary name that you copy the
generated file to after the GWT compile, and then use that name with
SerializationPolicyLoader to get your policy instance.
But yeah, like y
Just to clarify - I'm doing this as part of a regular page request
that bootstraps part of my application, not in response to a GWT RPC
call. So, for example, the client goes to the Foo page and my app
returns the Foo GWT gadget in the page along with all of the data it
needs to start up.
So th
On Feb 2, 8:27 pm, Dan Ox wrote:
> When the GWT RPC client sends a request, the 5th field is the strong
> name. If you are creating your own encoded message on the server, then
> you can put whatever string you want in there and, presuming you name
> the RPC file with the same string, it should
When the GWT RPC client sends a request, the 5th field is the strong
name. If you are creating your own encoded message on the server, then
you can put whatever string you want in there and, presuming you name
the RPC file with the same string, it should automatically get read in
by the code I men
On Feb 2, 7:45 pm, Dan Ox wrote:
> Are you decoding the request by hand?
No. I'm simply encoding an object on the server side and stuffing it
into the page using RPC.encodeResponseForSuccess(). Then on the
client side I am pulling it out and decoding it with a
SerializationStreamFactory. (S
e RPC will use your SerializationPolicyProvider to generate
the policy. it returns an RPCRequest which you can then call
getSerializationPolicy() on and pass the policy instance through to
encodeResponseForSuccess(Method, Object, SerializationPolicy)
Hope that helps.
On Feb 3, 11:11 am, &quo
We are using RPC.encodeResponseForSuccess() in our code to serialize
GWT objects and include them in the page (avoiding an extra round trip
and simplifying startup logic in some cases).
This is a bit awkward as this (the only public) API requires passing a
serialization policy, which changes ever
51 matches
Mail list logo
