649c714006
switch hawkBit web server to Tomcat (was Jetty) Signed-off-by: Marinov Avgustin <Avgustin.Marinov@bosch.com>
34 lines
1.6 KiB
Markdown
34 lines
1.6 KiB
Markdown
# hawkBit User Interface
|
|
|
|
The hawkBit user interface is based on the Vaadin and Vaadin-Spring framework and allows to manage software updates and large scale roll-outs via a user interface.
|
|
|
|
## Debugging client-side code
|
|
### Debug using SuperDevMode
|
|
The SuperDevMode can be used to debug client side code without any browser plugin.
|
|
|
|
#### Using SuperDevMode with chrome :
|
|
|
|
- Add required maven dependencies
|
|
- Add vaadin-client-compiler dependency
|
|
- Set redirect property in the AppWidgetSet.gwt.xml module descriptor as follows
|
|
- < set-configuration-property name="devModeRedirectEnabled" value="true" />
|
|
- Create launch configuration for the SuperDevMode
|
|
- The main class to execute should be com.google.gwt.dev.codeserver.CodeServer.
|
|
- Add fully-qualified class name of widgetset (org.eclipse.hawkbit.ui.AppWidgetSet) as parameter
|
|
- Enable debug in chrome
|
|
- Chrome inspector window ▸ Click on settings icon ▸ Scripts ▸ Enable source maps option
|
|
- Run the SuperDevMode Code Server with the launch configuration created above
|
|
- Open http://localhost:8080/UI/?debug .Click on "SuperDev" button in debug console (Alternatively can directly add ?superdevmode parameter to URL)
|
|
- Widgetset is compiled and you can see the java code files loaded in 'Chrome inspector window ▸ Source tab'
|
|
|
|
|
|
#### Using SuperDevMode with Eclipse :
|
|
|
|
- Install the plugin from http://sdbg.github.io/p2
|
|
- Start the server and Super Dev Mode as mentioned above
|
|
- Create a new launch configuration in Eclipse
|
|
- Type is "Launch Chrome"
|
|
- http://localhost:8080/UI/?superdevmode
|
|
- Launch the new configuration in debug mode
|
|
- Now breakpoints in eclipse can be set
|