harishashim
|
Posted: November 09, 2009 18:40 by harishashim
|
|
Hello! I am using Netbeans 6,8 beta here with the latest Appengine (appengine-java-sdk-1.2.6) GWT (gwt-windows-1.7.1). Running the project is not a problem. Debugging is different story. It got stuck at [OUTPUT: Google App Engine] runserver-debug: [java] Listening for transport dt_socket at address: 8765 I know the port is correct. My silly work around is to debug sample guestbook project (which is not GWT). Stop it after it open the page (and the app engine server is already running in debug mode). And then debug the GWT project. This work, however I'm not comfortable with it. So would like to troubleshoot and maybe a way to fix this. Thanks in advance! Haris |
NBAppengine with GWT unable to debug
24 topics, 82 posts
» Share this
Replies: 4 - Last Post: November 21, 2009 23:53
by: marigan
by: marigan
showing 1 - 5 of 5
|
harishashim
|
Posted: November 09, 2009 18:48 by harishashim
|
|
Just to add that it is in the issue tracking as http://kenai.com/jira/browse/NBAPPENGINE-41 |
|
harishashim
|
Posted: November 10, 2009 09:20 by harishashim
|
|
After further troubleshooting it looks like for GWT debugging. There is a specific icon in Debug menu that initiate hosted mode debugging. Clicking this result to what I expect (and accomplish the same result as the silly work around). So at the moment I am a happy debugger  Yet still there is this question about what should happen when Debug icon in the toolbar is clicked (or CTR F5). At the moment it is not debugging. Thanks for all the views. Maybe there was no reply because GWT is not popular choice with nbappengine user? Just curious. Good day! |
|
harishashim
|
Posted: November 12, 2009 11:02 by harishashim
|
|
Clicking the icon does not really works. Debugging JDO result to exception. Another work arround is ... 1. Run the GWT project using the normal way (not debug, just run it) 2. Go to files window (CTR + 2), expand build xml and look for debug-connect-gwt-shell. 3. Run it by right click choose run. Still would like to know if other people is facing this problem (i.e. not able to debug GWT project) Hope that the info so far help other people with the same problem. Wish that all the info so far will be useful to the maintainer if he/she decide to troubleshoot this. Through debugging the ant script I believe that it got stuck at build-gwt.xml line 71 <nbdeploy debugmode="true" clientUrlPart="${client.urlPart}"/> <<<==== LINE 71 <antcall target="connect-debugger"/> <antcall target="debug-connect-gwt-shell"/> Unfortunately I don't really understand how this pile of steaming ant #$% function. At least the work arround works (for now!) Anyway it is hard to believe that I am the only person having this problem. Ether that or nobody using netbeans + appengine + GWT. Pity. |
Replies: 4 - Last Post: November 21, 2009 23:53
by: marigan
by: marigan
