Super Dev Mode: Is there a way to start the Super Dev Mode with a server other than the embedded Jetty?

1,262 views
Skip to first unread message

monkeyboy

unread,
Jul 4, 2012, 4:03:28 PM7/4/12
to google-we...@googlegroups.com
I am developing for App engine and I'd like to use the Super Dev Mode together with the App Engine development server. Is there a way to do it similar to the "-server" switch in the standard dev mode.

Thomas Broyer

unread,
Jul 4, 2012, 7:28:59 PM7/4/12
to google-we...@googlegroups.com

On Wednesday, July 4, 2012 10:03:28 PM UTC+2, monkeyboy wrote:
I am developing for App engine and I'd like to use the Super Dev Mode together with the App Engine development server. Is there a way to do it similar to the "-server" switch in the standard dev mode.

Actually, Super Dev Mode does not run any server-side code, you *have* to use an external server for your servlets, there's no "embedded Jetty" in Super Dev Mode (other than the one used to serve the dynamically compiled JS, which you don't need to care about) 

monkeyboy

unread,
Jul 5, 2012, 4:28:06 AM7/5/12
to google-we...@googlegroups.com
Thanks Thomas for the clarification.
I now understand that I must have two servers running one for app engine and the other for the code. I managed to make them work, however now I have a problem with GWT-RPC serialization. The code server compiled draft version does not contain the required server policies with the appropriate name (the *.gwt.rpc files). There is the same number of policies in the original compiled version and in the draft version but they have different filenames. Now the server complains it can't find the appropriate serialization policies. How can I fix this?

Thomas Broyer

unread,
Jul 5, 2012, 12:42:26 PM7/5/12
to google-we...@googlegroups.com


On Thursday, July 5, 2012 10:28:06 AM UTC+2, monkeyboy wrote:
Thanks Thomas for the clarification.
I now understand that I must have two servers running one for app engine and the other for the code. I managed to make them work, however now I have a problem with GWT-RPC serialization. The code server compiled draft version does not contain the required server policies with the appropriate name (the *.gwt.rpc files). There is the same number of policies in the original compiled version and in the draft version but they have different filenames. Now the server complains it can't find the appropriate serialization policies. How can I fix this?

That's a known issue, and you can search the group archives for some clever solutions by other GWT users.

Brian Slesinsky

unread,
Jul 14, 2012, 2:34:59 PM7/14/12
to google-we...@googlegroups.com
Well actually, I didn't know that Super Dev Mode has a problem with GWT-RPC (though it makes sense in retrospect that there might be a problem). I'm having trouble searching for the workarounds. Can someone collect this information and create an issue in the issue tracker?

- Brian 

Paul Robinson

unread,
Jul 16, 2012, 3:50:35 AM7/16/12
to google-we...@googlegroups.com
Brian,

I believe Thomas is referring to my posts in this thread:
    https://groups.google.com/d/topic/google-web-toolkit/ZugfWpwnXJs/discussion

The idea is that, since the code server provides http access to all the compiled code including gwt.rpc files, you can modify your regular tomcat/jetty server to get the gwt.rpc files from the code server.

Paul

Brian Slesinsky

unread,
Jul 16, 2012, 1:10:03 PM7/16/12
to google-we...@googlegroups.com
On Mon, Jul 16, 2012 at 12:50 AM, Paul Robinson <ukcu...@gmail.com> wrote:
> I believe Thomas is referring to my posts in this thread:
>
> https://groups.google.com/d/topic/google-web-toolkit/ZugfWpwnXJs/discussion
>
> The idea is that, since the code server provides http access to all the
> compiled code including gwt.rpc files, you can modify your regular
> tomcat/jetty server to get the gwt.rpc files from the code server.

Okay, created a bug for this:
http://code.google.com/p/google-web-toolkit/issues/detail?id=7522
Reply all
Reply to author
Forward
0 new messages