You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

addons-troubleshooting.asciidoc 1.9KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657
  1. ---
  2. title: Troubleshooting
  3. order: 6
  4. layout: page
  5. ---
  6. [[addons.troubleshooting]]
  7. = Troubleshooting
  8. If you experience problems with using add-ons, you can try the following:
  9. * Check the [filename]#.gwt.xml# descriptor file under the the project root
  10. package. For example, if the project root package is
  11. [filename]#com.example.myproject#, the widget set definition file is typically
  12. at [filename]#com/example/project/AppWidgetset.gwt.xml#. The location is not
  13. fixed and it can be elsewhere, as long as references to it match. See
  14. <<../clientside/clientside-module#clientside.module,"Client-Side
  15. Module Descriptor">> for details on the contents of the client-side module
  16. descriptor, which is used to define a widget set.
  17. * Check the [filename]#WEB-INF/web.xml# deployment descriptor and see that the
  18. servlet for your UI has a widget set parameter, such as the following:
  19. +
  20. ----
  21. <init-param>
  22. <description>UI widgetset</description>
  23. <param-name>widgetset</param-name>
  24. <param-value>com.example.project.AppWidgetSet</param-value>
  25. </init-param>
  26. ----
  27. +
  28. Check that the widget set class corresponds with the [filename]#.gwt.xml# file
  29. in the source tree.
  30. * See the [filename]#VAADIN/widgetsets# directory and check that the widget set
  31. appears there. You can remove it and recompile the widget set to see that the
  32. compilation works properly.
  33. * Use the [guilabel]#Net# tab in Firebug to check that the widget set (and theme)
  34. is loaded properly.
  35. * Use the ?debug parameter for the application to open the debug window and check
  36. if there is any version conflict between the widget set and the Vaadin library,
  37. or the themes. See
  38. <<../advanced/advanced-debug#advanced.debug,"Debug Mode
  39. and Window">> for details.
  40. * Refresh and recompile the project. In Eclipse, select the project and press F5,
  41. stop the server, clean the server temporary directories, and restart it.
  42. * Check the Error Log view in Eclipse (or in the IDE you use).