I use JNDI contexts for datasources too, and still use hosted mode - works fine for me. See the simpledatasample, for example. GWT-Maven automatically can configure the hosted mode tomcat, including filters and realms and datasources and anything a regular tomcat can handle. http://gwt-maven.googlecode.com/svn/docs/maven-googlewebtoolkit2-plugin/tomcatlite.html
But, getting back on track to what you actually asked about ;) . . . the rcp serialization policy has been there since 1.4 I believe, as soon as they added support for "Serializable" as well as "IsSerializable" that file became necessary, if I recall correctly. That file is generated by the compiler typically, so it's not available unless you compile. That's why deploying and using web mode works fine. For the shell purposes, GWT has some special magic that creates the rpc policy data and pipes into GWTShellServlet, I think, again. If you use noserver and need rpc files, I think you need to compile first, and then copy the rpc files to your external container - that should fix it. GWT-Maven doesn't handle the container config part, just launches the shell with noserver. On Sep 25, 8:50 am, Darren Hartford <[EMAIL PROTECTED]> wrote: > yes, only runtime issues. > > I did some more digging, and my understanding is starting with RC2 (which I > never deployed) they started using the *.gwt.rcp file for > SerializationPolicy. Looking at the logs, this looks like the culprit -- but > for specific scenarios. > > Deploying to tomcat and running straight from tomcat seems to work fine, but > when I run hosted mode (mvn gwt:gwt) and try to connect to that tomcat > instead of the embedded tomcat it complains about a *different* hashcoded > *.gwt.rpc file not being there...which is very strange. > > I haven't been able to get a successful hosted mode to work while working > with noserver (I use JNDI contexts for datasources) since swapping to GWT > 1.5.2/GWT-maven b23. > > --- On Wed, 9/24/08, Mirko Nasato <[EMAIL PROTECTED]> wrote: > > > From: Mirko Nasato <[EMAIL PROTECTED]> > > Subject: Re: gwt 1.5.2, RPC issue (enum not assignable IsSerializable) > > To: [email protected] > > Date: Wednesday, September 24, 2008, 6:16 PM > > So everything compiles fine, it's only at runtime that > > you get those issues? > > Have you tried simply forcing a page refresh in the > > browser? Sometimes it's > > just the browser using old stuff from its cache. > > > 2008/9/24 dhartford <[EMAIL PROTECTED]> > > > > Hey all, > > > Working from GWT 1.5.0-rc1/gwt-maven-plugin b20, have > > a perfectly > > > fine, running application. No problems, works great > > hosted mode, works > > > great deployed. > > > > Upgrade to GWT 1.5.2/gwt-maven-plugin b23 (exact same > > application > > > code), getting RPC issues on the Server as follows > > (from a linux build > > > deployed to a linux tomcat 5.5.20): > > > > =========== > > > Caused by: > > com.google.gwt.user.client.rpc.SerializationException: Type > > > '[Ljava.lang.Enum;' was not assignable to > > > 'com.google.gwt.user.client.rpc.IsSerializable' and > > did not have a > > > custom field serializer. For security purposes, this > > type will not be > > > deserialized. > > > at > > > com.google.gwt.user.server.rpc.impl.LegacySerializationPolicy.validateDeserialize(LegacySerializationPolicy.java: > > > 123) > > > at > > > com.google.gwt.user.server.rpc.impl.ServerSerializationStreamReader.deserialize(ServerSerializationStreamReader.java: > > > 461) > > > at > > > com.google.gwt.user.client.rpc.impl.AbstractSerializationStreamReader.readObject(AbstractSerializationStreamReader.java: > > > 61) > > > at > > > com.google.gwt.user.server.rpc.impl.ServerSerializationStreamReader > > > $ValueReader$8.readValue(ServerSerializationStreamReader.java:124) > > > at > > > com.google.gwt.user.server.rpc.impl.ServerSerializationStreamReader.deserializeValue(ServerSerializationStreamReader.java: > > > 362) > > > at > > com.google.gwt.user.server.rpc.RPC.decodeRequest(RPC.java:287) > > > =========== > > > > Checking here first incase it is some type of > > switch/argument I might > > > have missed in the maven GWT plugin before posting to > > GWT group. > > > > thanky! > > > -D --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "gwt-maven" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/gwt-maven?hl=en -~----------~----~----~----~------~----~------~--~---
