After upgrading to MyEclipse 4.0 GA the option for deploying my webapp to Jetty 5 as an exploded archive is not available (grayed out). This was working great before. Does anyone know why this is so? Below are the details of my config.

Thanks!

-- Lionel

Windows XP Pro
Eclipse Version: SDK 3.1.0, Build id: I20050627-1435
Plugins installed: subclipse 0.9.34, Jinto 0.10.2
PDE plugins installed:
org.eclipse.pde.core_3.1.0.jar
org.eclipse.pde.runtime_3.1.0.jar
org.eclipse.pde.ui_3.1.0.jar
org.eclipse.pde_3.1.0.jar
org.eclipse.pde.build_3.1.0
org.eclipse.pde.doc.user_3.1.0
org.eclipse.pde.junit.runtime_3.1.0
org.eclipse.pde.source_3.1.0

MyEclipse Version: 4.0.0, Build id: 20050829-4.0.0-GA

Both Eclipse & Jetty5 are running under JDK 1.5.0_04

No pertinent exceptions appear in the Eclipse log file.

I believe it was removed because Jetty doesn't support deployment of exploded archives. Is this not the case? If there's some sort of configuration that makes Jetty support them, can you post it here and I'll try to ensure that the exploded support gets back into 4.0.1. In the interim, you can use <Custom Location> and place the exploded deployment where you like to work around the issue.

Thanks, that worked just fine.

As for configuring Jetty to handle exploded archives, try adding the following to your Jetty configuration file:

<Call name="addWebApplications">
<Arg></Arg>
<Arg><SystemProperty name="jetty.home" default="."/>/webapps/</Arg>
<Arg><SystemProperty name="jetty.home" default="."/>/etc/webdefault.xml</Arg>
<Arg type="boolean">true</Arg><!--extract WARs-->
</Call>

This XML snippet needs to go inside the <Configure class="org.mortbay.jetty.Server"> tag, which tells the startup code to call the method org.mortbay.jetty.Server.addWebApplications() with the 4 parameters supplied. Here's the API documentation for that method http://jetty.mortbay.org/javadoc/org/mortbay/jetty/Server.html.

-- Lionel

Lionel,

Thanks for the info. I'll see we make that available again in 4.0.1.

support-scott wrote:

Lionel, Thanks for the info. I'll see we make that available again in 4.0.1.

Scott, F.Y.I. I also have this problem in Jetty 4. This does support exploded deployment and always worked fine in pre 4.0 GA releases, so would be nice to have this fixed as well.

For now I'm using the Custom Location Deployment to work around this.

Thanks
David