[ https://issues.jboss.org/browse/TOOLSDOC-345?page=com.atlassian.jira.plug... ] Michelle Murray commented on TOOLSDOC-345: ------------------------------------------ Email from Rob (9th April, 2013): Support for Port detection by reading the standalone.xml (or whatever config file is chosen) Port offset detection for AS7 (ie, users can start their server with a port offset of 100 or 200 or whatever, which means if standalone.xml says '8080' the real port is '8180') Deployment to a remote server (integration with eclipse RSE) Integration with JMX tools (MBean Explorer view and its editors) Support for a 'single file' or 'single folder' deployment (right-click on any file in the workspace and make it deployable) SAR projects EJB3 classpath container (right-click any project, go to classpath, add an ejb 3.0 classpath container) Basically almost all of the features that you see are provided via hooks into wtp. WTP provides the framework, but when compared to generic server, we have better implementations. So "publishing" is not unique, but we use project archives (jbt project in server repo) to make sure deployment is much faster (we use incremental updates) than generic server (which uses ant). When using 'run as -> run on server" on a web project, for example, we also make sure to not open the browser until the server assures us the module is properly deployed. If you open too fast (or use generic server) you'd get a 404 since the webapp is not fully deployed yet. Generic server for jboss also is able to tell if the server is up, and it works, but it's not optimal and doesn't give enough choices. We allow choices on how to do this (jmx / as7 management request, or web port polling, etc). So ... thats what I got so far ;) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira