Sunday, November 17, 2013

Development Environment, -noserver

Hi,
  
   I need additional information about the -noserver option. I have an embedded jetty server that needs to run on its own
since I have multiple GWT components enclosed in different projects that fit into different places (Putting all GWT
components within the very same project and use the embedded jetty is not an option for me).

Reading the explaination about the -noserver option I seam to quite miss a point (or at least I am not sure if my
understanding is correct). So please help me out.

I do not understand how things work when the GWT's Jetty is not start up.
From reading the source, I catched that a second port (something in the 9xxx) is created.

But I do not understand how serving a page with my very own server instance and viewing it in a browser (or Selenium)
will trigger a debug session. What do I miss here?

My first guessing is that GWT still creates some sort of server I need to connect to within the browser and every request
is handed over to my own server beside GWT related requests.

Can someone please clearify this? It would be very good if I can just startup the dev server and run a certain GWT project
to debug the component in isolation.


Thanks for reading,


Martin (Kersten),
Germany

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/groups/opt_out.

0 Comments:

Post a Comment

Subscribe to Post Comments [Atom]

<< Home


Real Estate