You don't appear to need the *.gwt.rpc serialization policy file in hosted mode. That file is generated by the compiler, and you don't need to even invoke the compiler for the shell/hosted mode.
I tried several applications that have beans that implement Serializable and it seems to work fine. Closing the issue unless someone has more info or a reproducible example. On Sep 9, 12:50 pm, Charlie Collins <[EMAIL PROTECTED]> wrote: > This does make sense, yes. > > Whether or not files need special treatment though depends on how they > are accessed. If they have to be in a particular file system location > they are different than if they just need to be on the classpath. > > For Spring and JPA stuff, and other things that need to be present at > a particular path location for the hosted mode tomcat, I have just > used the antrun plugin in the past to copy them to where they need to > be. I think others also just use noserver once things get complicated > (but that has it's own other issues, can't run tests, etc). > > We actually used to have an issue in the tracker for > this:http://code.google.com/p/gwt-maven/issues/detail?id=82(which I am re- > opening to revisit). It details how to use ant run and such. > > I am adding an issue for the *rpc file. That should automatically get > copied over for sure. > > On Sep 9, 12:19 pm, Holger <[EMAIL PROTECTED]> wrote: > > > I'm trying to use gwt 1.5.2, spring 2.5.4, gwt-sl 0.1.5a and gwt-maven > > 2.0-beta22. > > > Has someone got this setup to work in web mode and hosted mode? > > > Currently, I have one maven project to test this integration > > based on the StockWatcher example from the gwt tutorial. > > The GWT-RPC should call a spring configured service, exported via > > GWTRPCServiceExporter from gwt-sl. > > > So, my src/main/webapp/ directory contains > > - web.xml (defining Spring DispatcherServlet) > > - remoting-servlet.xml (defining UrlMapping and > > GWTRPCServiceExporter ) > > - applicationContext.xml (defining Spring business objects) > > - log4j.properties (defining loggers and appenders) > > > What I want to achieve is to start and run the app in hosted mode with > > "mvn gwt:gwt". > > I have enabled the "mergewebxml" goal to be able to use my web.xml > > file and it > > gets copied to directory "target/tomcat/webapps/ROOT/WEB-INF" - Ok. > > But the other files (remoting-servlet.xml, applicationContext.xml, > > log4j.properties) > > are missing there, so when executing "mvn gwt:gwt" these files are not > > found. > > When I copy them manually to the above location, the shell starts up > > correctly. > > > Would it make sense to add this funtionality to gwt-maven, e.g. coping > > the files from > > src/main/webapp/WEB-INF to target/tomcat/webapps/ROOT/WEB-INF to > > support this > > use case or is there something I'm doing wrong ? > > > In addition, theserializationpolicy(*.gwt.rpc) file cannot be found > > in hosted mode. I had to > > copy it manually to target/tomcat/webapps/ROOT/<module-name>/*.gwt.rpc > > to make it available. > > It is needed when the classes used in RPC implement Serializable > > instead of IsSerializable. > > > Does this all make sense to you? > > > Thanks, > > Holger --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
