![]() |
There are two goals in the pom.xml, which triggers the hosted mode.
The following lists the complete list of the current esb-console/console/pom.xml
maven project goals:
The section of interest in the maven project esb-console/console/pom.xml
is listed below:
<!-- plugin goals -->
<goals>
<goal>mergewebxml</goal>
<!--goal>i18n</goal-->
<goal>compile</goal>
<!--goal>debug</goal-->
<!--goal>gwt</goal-->
<!--goal>test</goal-->
</goals>
as shown below:
<!-- plugin goals -->
<goals>
<goal>mergewebxml</goal>
<!--goal>i18n</goal-->
<goal>compile</goal>
<!--goal>debug</goal-->
<goal>gwt</goal>
<!--goal>test</goal-->
</goals>
as shown below:
<!-- plugin goals -->
<goals>
<goal>mergewebxml</goal>
<!--goal>i18n</goal-->
<goal>compile</goal>
<goal>debug</goal>
<!--goal>gwt</goal-->
<!--goal>test</goal-->
</goals>
Note that the GWT Hosted mode debug port is set to 8000 in the esb-console/console/pom.xml
.
<properties>
<gwtVersion>1.5.2</gwtVersion>
<debugPort>8000</debugPort>
<glassfish.home>C:/JavaCAPS6/appserver</glassfish.home>
</properties>
If you want to change the GWT debug port, make the change in the esb-console/console/pom.xml
. You can now set breakpoints in your GWT code and debug the esb-console client code in GWT hosted mode.
Then run
mvn clean install
Go to your IDE, and debug remotely by connecting to the debug port set in the esb-console/console/pom.xml
.
![]() |
This will open the GWT Host in Suspended mode. You should now be able to set breakpoints in your GWT code and debug your plugin application.
Note: While debugging, GWT Hosted Mode runs its own embedded Tomcat with the web app root at esb-console/console/target/tomcat/webapps/ROOT/