blob: da95e7686def09057889f0ad89094f9034ea4e40 [file] [log] [blame]
<!doctype HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1">
<!-- /*******************************************************************************
* Copyright (c) 2000, 2006 IBM Corporation and others.
* All rights reserved. This program and the accompanying materials
* are made available under the terms of the Eclipse Public License v1.0
* which accompanies this distribution, and is available at
* Contributors:
* IBM Corporation - initial API and implementation
*******************************************************************************/ -->
<link rel="stylesheet" type="text/css"
href="../../org.eclipse.wst.doc.user/common.css" >
<title>Web Tools Platform Limitations and Known Issues</title>
<h1>Web Tools Platform Limitations and Known Issues</h1>
<p>The following are limitations and known issues:</p>
<dt class="dlterm"><b>When using XDoclet the generation does not appear to run.</b></dt>
<dd><p>Cause: XDoclet has some limitations with long path names.</p>
<p>Solution: You should install Eclipse and the Web Tools Platform into a directory with a short
<dt class="dlterm"><b>When creating a Web service you may see a message similar to the following one:</b></dt>
<dd><p><samp>org.apache.axis.utils.JavaUtils isAttachmentSupported
WARNING: Unable to find required classes (javax.activation.DataHandler and
javax.mail.internet.MimeMultipart). Attachment support is disabled.
<p>Cause: Attachment support is disabled.</p>
<p>Solution: The Apache Axis tools should auto-detect the javax.activation classes provided you add
<samp>activation.jar</samp> to the build path of the project to which you are generating your Web service or client.
For services, you will also need to make sure <samp>activation.jar</samp> is available to the Tomcat JRE, either by
including it in the server's global classpath or by placing a copy of activation.jar into the target Web
project's <samp>lib/</samp> directory.
<dt class="dlterm"><b>Problems encountered publishing from dynamic Web projects with non-ASCII names</b></dt>
<p>Cause: Dynamic Web projects must have ASCII names. If non-ASCII characters are used as project names for dynamic Web projects,
the context root defaults to use the project name. This causes problems when trying to publish from the Web project.
<p>If you create a dynamic Web project with non Latin-1 characters (leaving the context root
to default to the project name containing non Latin-1 characters) and try to
publish, you will see an error message similar to "The requested resource is not available".</p>
<p>If a dynamic Web project containing a non-ASCII context root is used in an Axis1 Web service creation
scenario, you will see an error message similar to "Unable to deploy to Axis".</p>
<p>Solution: Use ASCII characters as the context root.</p>