[jbosstools-issues] [JBoss JIRA] (TOOLSDOC-345) NeedInfo: Distinction between Eclipse and JBDS/JBT Server Tools

[ https://issues.jboss.org/browse/TOOLSDOC-345?page=com.atlassian.jira.plug... ] Rob Stryker commented on TOOLSDOC-345: -------------------------------------- A "runtime" is an in-eclipse representation of a locally installed Application Server. In our case, a runtime includes some specific configuration elements, like what VM it uses, or what the configuration is. You may have multiple runtimes pointing to the same install location, but with different configuration choices, such as "all" instead of "default" for application server versions < 7. For AS >= 7, that option is replaced with what configuration file to use (standalone.xml, standalone-ha.xml, etc). A server represents a way to launch, publish to, and communicate with, a runtime. A server in the local mode represents a server communicating with a server running on the same machine. Many servers may use the same runtime but with different configuration items. These configuration items may include different launch arguments, different default publish locations, and other things of that nature. So for example, you may have Server1 backed by runtime Runtime1, which may pass in -DcustomSystemProperty=true, while Server2 (also backed by Runtime1) does not pass in such a property. So the server adapter indicates how eclipse should interact with the backing server that is launched. The new server wizard will create a runtime if none has been created yet. So if it's your first time using the new server wizard, the 2nd page will be the runtime details, and the 3rd page will be the server configuration. If you've already created a server of the same type before, then a runtime already exists. Page1 of the new server wizard will include a combo box where you may select which existing runtime to use, or, you may click a hyperlink to the left "Add..." which allows you to create a new runtime for the given server type. I suppose this is true, but the language confuses me a bit. Deleting a server from the servers view will not delete the server from your computer. It only deletes the in-eclipse representation of the server. You should think of a server adapter as a bunch of settings, launch arguments, etc, which help your IDE's server adapter know how to launch and communicate with the actual server. A local installation with the same setting files as the remote server is required locally, to ensure that when the IDE tries to figure out what ports to use to communicate with the remote server, it does not get faulty data. If your remote server's standalone.xml clearly says to use port 8080, but the local installation says to use 8181, then the IDE will attempt to communicate with the remote on 8181, and will fail. And, yes, you are right, that we do load jars from the local instance to use when *actually* communicating with the remote, so the common api and remote communication methods must match. Again, if its your first time using the new server wizard and you are in a clean workspace, the new server wizard will create a runtime which represents your local installation of JBoss, and a server which represents your remote server. The server adapter (which represents the remote instance) still requires a runtime, and so it uses the one representing the local appserver, assuming that it is equivilent to the remote. The rest of the settings are available either in the server editor or the launch configuration. You'll note that when in local mode, you do not need to set your configuration name / file in the server editor. When using a local-mode server adapter, it pulls this data from the runtime, where it already exists. When using a server set to remote-mode, the server editor will request you re-declare the server home directory, configuration name / file, etc. This is because it cannot be 100% assumed the user has everything 100% equal to the remote instance, specifically the home directory. Your local version might be in /home/mmurray/dev/jboss/etc, but your remote instance might live in /some/production/jboss/root. For our cases, having the same installation is close enough, so long as the user takes care that the ports match up and settings in the server editor make sense. Yep. -- 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