357 | | |
358 | | |
359 | | |
360 | | = Genius2 sources == |
| 357 | = Debugging = |
| 358 | Debugging can be done in several ways |
| 359 | * From Eclipse EE: |
| 360 | * Place your party source code in the Eclipse workspace |
| 361 | * Place a breakpoint in your party's code |
| 362 | * Run the partiesserver directly from Eclipse EE , in Debug mode. |
| 363 | * Run a session or tournament in which you want to debug your party. |
| 364 | * Eclipse will halt server execution and switch to debugging when it hits your breakpoint |
| 365 | * Be aware of the automatic time-outs that will still be enforced while you are debugging. This includes tomcat session time-outs. |
| 366 | * Using a stand-alone runner (normal Eclipse for Java developers, no EE needed) |
| 367 | * Have your party's source code in the Eclipse workspace |
| 368 | * Run the stand-alone command directly in your eclipse workspace |
| 369 | * Eclipse will halt server execution and switch to debugging when it hits your breakpoint |
| 370 | * time-outs may still be enforced while you are debugging but you avoid the Tomcat session time-out. |
| 371 | |
| 372 | |
| 373 | = Genius2 sources = |