On Jan 13, 2:02 pm, Chris Ramsdale <[email protected]> wrote:
> On Wed, Jan 13, 2010 at 11:48 AM, Yaakov <[email protected]> wrote:
> > 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:...
>
> Not entirely sure what's going on with your auth mechanisms, but if you want
> to avoid launching 2 code servers (e.g. MyApp.html and
> authenticationError.jsp), you can specify the following in your program
> args:
>
> -startupUrl http://localhost:8888/MyApp.html

Interesting. Are you sure this makes sense in the context of GWT 2.0?
Given that it specified the same port number for both pages, it
doesn't seem like it would be starting 2 different code servers. My
guess is that Eclipse GWT plugin just scanned the war directory for
publicly accessible pages and "suggested" URLs that I might use to
access each one of them.

> > 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
>
> Did you mean to leave off the port?

You mean from 'localhost'? Yes, I did. It's httpS, so it's the
standard 443 port.

BTW, it's possible that I figured out what the problem is exactly. I
think some old dependecies are still part of the app (GWT 1.7) and
THAT is why it's not connecting... So, in the end, it might not have
anything to do with the CLIENT-CERT... It doesn't make sense that it
should have anything to do with it.

Once I fix what I think needs to be fixed, I'll respond to the thread
with an update. Thanks for taking the time to respond.

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 [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.


Reply via email to