51f93a538fb7ceeb82c7bd82cdb1910bccddbda2
java/com.sap.sailing.gwt.ui/Debug SailingGWT SDM on Chrome.launch
| ... | ... | @@ -0,0 +1,16 @@ |
| 1 | +<?xml version="1.0" encoding="UTF-8" standalone="no"?> |
|
| 2 | +<launchConfiguration type="com.github.sdbg.debug.core.chromeLaunchConfig"> |
|
| 3 | +<stringAttribute key="applicationArguments" value=""/> |
|
| 4 | +<stringAttribute key="applicationName" value=""/> |
|
| 5 | +<booleanAttribute key="launchFile" value="false"/> |
|
| 6 | +<listAttribute key="org.eclipse.debug.core.MAPPED_RESOURCE_PATHS"> |
|
| 7 | +<listEntry value="/com.sap.sailing.gwt.ui"/> |
|
| 8 | +</listAttribute> |
|
| 9 | +<listAttribute key="org.eclipse.debug.core.MAPPED_RESOURCE_TYPES"> |
|
| 10 | +<listEntry value="4"/> |
|
| 11 | +</listAttribute> |
|
| 12 | +<stringAttribute key="projectName" value="com.sap.sailing.gwt.ui"/> |
|
| 13 | +<booleanAttribute key="showLaunchOutput" value="false"/> |
|
| 14 | +<stringAttribute key="url" value="http://127.0.0.1:8888/gwt/Home.html"/> |
|
| 15 | +<stringAttribute key="urlQueryParams" value=""/> |
|
| 16 | +</launchConfiguration> |
wiki/super-dev-mode.md
| ... | ... | @@ -19,6 +19,8 @@ You can add "GWT.debugger();" statements to your Java code. |
| 19 | 19 | his will force the JavaScript debugger to stop at this statement. |
| 20 | 20 | So you don't have to manually open the file in the dev tools and set a break point. |
| 21 | 21 | |
| 22 | +In addition, there's a composite launch configuration "SailingGWT All SDM.launch" that will start SDM for the SailingGWT modules as well as the Security UI modules. |
|
| 23 | + |
|
| 22 | 24 | ## Using Eclipse debugger for GWT SuperDevMode |
| 23 | 25 | |
| 24 | 26 | Debugging Java Code in the browser is very inconvenient (e.g. you have to manually open the files you already opened in Eclipse). |
| ... | ... | @@ -29,16 +31,12 @@ Using Using Eclipse debugger for GWT SuperDevMode [[SDBG|http://sdbg.github.io/] |
| 29 | 31 | To start SDM debugging in Eclipse, do the following: |
| 30 | 32 | |
| 31 | 33 | * Start the backend as you would always do. |
| 32 | -* Start GWT Super Dev Mode by launching "SailingGWT sdm.launch". |
|
| 34 | +* Start GWT Super Dev Mode by launching "SailingGWT sdm.launch" or "SailingGWT All SDM.launch". |
|
| 33 | 35 | * Do not Click on the URLs provided in "Development view"! |
| 34 | -* Copy one of the URLs instead |
|
| 35 | -* Go to Run -> Run Configurations ... |
|
| 36 | -* Create a new configuration of type "Launch Chrome" |
|
| 37 | -* Paste the URL and select the UI project you launched SDM for |
|
| 38 | -* Save and run => A new instance of Chrome is started and you will see a debug session running in Eclipse |
|
| 36 | +* Run "Debug SailingGWT SDM on Chrome.launch" |
|
| 37 | +* A new instance of Chrome is started and you will see a debug session running in Eclipse |
|
| 39 | 38 | * Your Eclipse break points will now work in the running debug session. |
| 40 | - |
|
| 41 | -The created and save run configuration can be used for subsequent launches. |
|
| 39 | +* You are free to change the URL or navigate to other pages in the automatically openend browser window (debugging will go on) |
|
| 42 | 40 | |
| 43 | 41 | ### Noteworthy information & Troubleshooting |
| 44 | 42 |