Eclipse

Revision as of 19:40, 30 June 2011

Installing

Plugin discovery (Requires snapshot of Eclipse 3.7 and list of dependencies (see attached screenshot) The discovery uses central directory to list all the registered plugins but downloads it from our site.

Plugin standart install: http://www.caucho.com/eclipse . For snapshot: http://www.caucho.com/eclipse-snapshot

Creating a server runtime

Server runtime is synonymous to a class in java. Using one server runtime multiple servers can be configured. Basically, the runtime is resin distribution and 'servers' are RESIN_ROOTs

Runtimes are selected or created on the first page of "New Server" wizard. To create a new Runtime push "Add... " button.

License File

License is requested once per runtime and only if selected directory does not have any *.license files in RESIN_HOME/licenses

License is optional. Programmers can totally skip it.

Server Configuration

This page allows to choose method of publishing "git", "war" or exploded directory. All methods now require a username and a password which are now prefilled with 'admin' and 'password'. This is needed in order to restart an application automatically after deploying.

Host field on the first page defaults to localhost, but in case of remote deployment must be changed to that of remote Resin install.

Webapps directory

When prefixed with / or x:\ considered an absolute path, otherwise considered rooted at RESIN_ROOT.

Port

It must correspond to the HTTP port of Resin.

resin.xml configuration

The plugin uses default configuration supplied with Resin. For remote deployment and restart purposes it adds <resin:RemoteAdminService/>. For users it adds an admin-users.xml with the user supplied in the dialog.

The Resin Eclipse plugin is available on the Caucho Eclipse update site at http://caucho.com/eclipse. It is based on the WTP framework and features deployment modes for Resin 3.1 and 4.0.

Deployment styles

• .war file (default) - the plugin builds a .war file of your project, then starts Resin and copies the .war to the live deploy directory.
• Temporary directory - the plugin builds a .war file of your project, then starts Resin and copies the .war to a temporary deploy directory.
• In-place - the plugin starts Resin, then points it to server your project directly out of the workspace.
• Hot-deploy - (Resin 4.0 only) the plugin builds a .war file of your project, then starts Resin and uses Resin's Git deployment functionality to deploy

Options for configuration

• The very basic configuration that's included with the plugin itself
• The configuration in the "conf" subdirectory of the Resin home
• A configuration somewhere else in the file system (e.g. /etc/resin).

If you're starting a new project and don't need to do anything fancy, the first option is recommended, copying the configuration from the plugin. If you do need to use a custom configuration, you may need to modify it to recognize the variables that the plugin sets at runtime. The dialog box tells you what these variables are and how to set them, depending on which server profile you use.

Notes

• Eclipse must be run with a JDK, not simply a JRE, to use the Resin plugin.
• The Resin plugin must be run on Eclipse Galileo with Java EE.
• Windows Vista/7 users: administrator privileges may be required to install plugin.

References

• Resin Eclipse plugin snapshot (2009-08-18) - Blog post about using the plugin's Server configuration
• Remote deploy in Resin, Part 2 (2009-01-29) - Blog post about using host deploy