...

<FONT face=Arial size=2>With the latest support for JRun, Jonas and Resin application servers, MyEclipse boasts over 20 application server connectors.  The new service releases (2.6.3 & 3.6.3) also offer support for Eclipse 3.0 M4 as well as 2.1.2.  These releases are available for Windows, Linux and Mac OS/X platforms.

Since not all application servers are created equal, it important that members review the connector notes for features, configuration guidelines and known issues to avoid unpleasant surprises. 

<H3>Resin2 Connector Notes<FONT face="Verdana, Arial, Helvetica, sans-serif" size=2> </H3>

<FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>This connector enables MyEclipse to manage a Resin2 server instance.

<FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>Key management features include:

1. <FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>launching and stopping a Resin instance from within MyEclipse
2. <FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>hot-swap debugging of Java code deployed to a Resin server
3. <FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>real-time synchronized exploded and packaged Web Project deployment
4. <FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>cold and hot server deployment/redeployment
5. <FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>XDoclet support for deployment descriptor management

<FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>Configuration:

1. <FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>Resin loads a DLL when it startup. If you experience a startup problem it may be caused by the Resin server not being able to locate the DLL which can be found in <resin-home>/bin. To make the Resin DLL available to the Resin JVM add <resin-home>/bin to Resin2’s Library Path preference page (see Window menu>Preferences>Application Servers>Resin2>Paths).
2. <FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>Resin must be configured to launch with a full JDK, not a JRE. All testing was performed using the Sun J2SDK1.4.2.

<FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>Known issues:

1. <FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>No integrated help documentation to define configuration and operation procedures.
2. <FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>Resin2 does not support a JSR045 compliant JSP container. Therefore, JSP debugging is <U>not available</U> for this server.
3. <FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>Undeploy of packaged Web Project (WAR) does not remove unpackaged WAR files.

<P class=MsoBodyTextIndent><FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>The Resin auto-deployment feature unpackages WARs found in the <resin-home>/deploy folder into a subdirectory with the name of the WAR file’s basename. When an auto-deployed WAR file is manually deleted from the <resin home>/deploy folder Resin does not detect the removal of the application and thus continues to execute the unpackaged WAR code elements. To resolve this problem, manually remove the unpackaged WAR folder from <resin-home>/deploy

<H3>Resin3 Connector Notes </H3>

<FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>This connector enables MyEclipse to manage a Resin3 server instance.

<FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>Key management features include:

1. <FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>launching and stopping a Resin instance from within MyEclipse
2. <FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>hot-swap debugging of Java code deployed to a Resin server
3. <FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>real-time synchronized exploded and packaged Web Project deployment
4. <FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>cold and hot server deployment/redeployment
5. <FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>XDoclet support for deployment descriptor management

<FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>Configuration:

1. <FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>When Resin is launched it loads a DLL. If you experience a startup problem due to a missing VF system it may be caused by the Resin server not being able to locate the DLL. This DLL is typically found in <resin-home>/bin. To make the Resin DLL available to the Resin JVM add <resin-home>/bin to Resin3’s Library Path preference page (see Window menu>Preferences>Application Servers>Resin3>Paths).
2. <FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>Resin must be configured to launch with a full JDK, not a JRE. All testing was performed using the Sun J2SDK1.4.2.

<FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>Known issues:

1. <FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>No integrated help documentation to define configuration and operation procedures.
2. <FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>While Resin3 claims to be a JSR045 compliant JSP container our testing was unable to access the JSP-Java sourcemap. Therefore, JSP debugging is <U>not available</U> for this server.
3. <FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>Resin3.0.3 for Windows failed all MyEclipse cold and hot deployment tests. The Resin 3.0.3 for Linux passed all deployment tests.
4. <FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>Undeploy of packaged Web Project (WAR) does not remove unpackaged WAR files.

<P class=MsoBodyTextIndent><FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>The Resin auto-deployment feature unpackages WARs found in the <resin-home>/deploy folder into a subdirectory with the name of the WAR file’s basename. When an auto-deployed WAR file is manually deleted from the <resin home>/deploy folder Resin does not detect the removal of the application and thus continues to execute the unpackaged WAR code elements. To resolve this problem, manually remove the unpackaged WAR folder from <resin-home>/deployelements. To resolve this problem, manually remove the unpackaged WAR folder from <resin-home>/deploy.

<H3>Jonas3 Connector Notes</H3>

<FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>This connector enables MyEclipse to manage a Jonas3 server instance.

<FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>Key management features include:

1. <FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>launching and stopping of a Jonas instance from within MyEclipse
2. <FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>hot-swap debugging of Java code deployed to a Resin server
3. <FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>real-time synchronized exploded and packaged Web Project deployment
4. <FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>cold server deployment/redeployment
5. <FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>XDoclet support for deployment descriptor management

<FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>Configuration:

<FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>Jonas must be configured to launch with a full JDK, not a JRE. All testing was performed using the Sun J2SDK1.4.2.

<FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>Known issues:

1. <FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>No integrated help documentation to define configuration and operation procedures.
2. <FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>Jonas3 does not support a JSR045 compliant JSP container. Therefore, JSP debugging is <U>not available</U> for this server.
3. <FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>The MyEclipse Deployment Agent relies o­n servers that support hot auto-deployment of WAR and EJB applications and dynamic EJB proxy generation. Jonas does not support either of these features at this time. Therefore, while the Jonas connector will allow you to deploy exploded and archived projects to a Jonas server, you must: a) manually run GenIC to generate EJB proxy classes and b) register the application through Jonas’ administration console for hot deployment.

<H3>JRun4 Connector </H3>

<FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>This connector enables MyEclipse to manage a JRun4 server instance.

<FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>Key management features include:

1. <FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>launching and stopping of a JRun instance from within MyEclipse
2. <FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>hot-swap debugging of Java code deployed to a JRun server
3. <FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>real-time synchronized exploded and packaged Web and EJB project deployment
4. <FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>cold and hot server deployment/redeployment
5. <FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>XDoclet support for deployment descriptor management

<FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>Configuration:

<FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>JRun must be configured to launch with a full JDK, not a JRE. All testing was performed using the Sun J2SDK1.4.2.

<FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>Known issues:

1. <FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>No integrated help documentation to define configuration and operation procedures.
2. <FONT face="Verdana, Arial, Helvetica, sans-serif" size=2>JRun4 does not support a JSR045 compliant JSP container. Therefore, JSP debugging is <U>not available</U> for this server.