Hi Manolo, I wanted to confirm something just to make the jvm rpc serialization arg is taken into account when working with the legacy jar, which is going to be embedded in Eclipse. And if not, I could bake it in to the Eclipse the jvm args if needed when SDM is turned on. I'm going to do some testing tonight to verify if this path could be a end user issue. I'm wrapping up the GPE PR requests, but could add this if we thought it was a benefit to the end user development workflow.
The rpc tests I did didn't show a problem so far, but I suspect thats because thats because its ok. It's probably only an issue when people use -noserver. I'll verify. Thanks for the Help Jens, Brandon On Friday, September 5, 2014 9:55:55 AM UTC-7, Jens wrote: > > It is only required for GWT-RPC with SDM because SDM might produce new > *.gwt.rpc policy files that the server must know. > > As it is a server side property and you don't know which server a > developer will use I don't think the IDE can help to add that parameter. > However if a developer uses "DevMode -superDevMode" then the embedded Jetty > server spawned by GWT should be configured with GWT-RPC in mind. > > -- J. > -- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/51d5f8bf-a881-4583-9ec8-b532e7b2ad01%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
