Hi, Just started using GWT 2.0, etc...
I was successful in deploying the same web app to an external server and just added: ?gwt.codesvr=localhost:9997 Eclipse in its "Development Mode" tab showed that FF connected and everything is great. Now, my real app uses CLIENT-CERT as its authentication method and obviously works over SSL. I didn't think there would be any difference as the code server is not going through any of that authentication while trying to connect back to Eclipse. But no such luck... First, Eclipse suspiciously outputs 2 URLs for me to copy: http://locahost:8888/MyApp.html?gwt.codesvr=my-local-ip:9997 http://locahost:8888/authenticationError.jsp?gwt.codesvr=my-local-ip:9997 Even so, I open up FF and navigate to the real URL, appending the gwt.codesvr parameter Eclipse told me about: https://locahost/MyApp/MyApp.html?gwt.codesvr=my-local-ip:9997 The app loads just fine in the browser and everything works... Except that Eclipse doesn't show that anyone connected to its code server. Making simple string changes to the code doesn't make it show up in the running FF (after a refresh). Something tells me that somehow the CLIENT-CERT authentication gets in the way. Does anyone know what to do about this situation? I can't develop without the mode that connects me back to the client java code and I can't get rid of the CLIENT-CERT as my server-side code depends on being able to pull some info from the certificate to function. Please help! Thanks, Yaakov.
-- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
