Follow Techotopia on Twitter

On-line Guides
All Guides
eBook Store
iOS / Android
Linux for Beginners
Office Productivity
Linux Installation
Linux Security
Linux Utilities
Linux Virtualization
Linux Kernel
System/Network Admin
Programming
Scripting Languages
Development Tools
Web Development
GUI Toolkits/Desktop
Databases
Mail Systems
openSolaris
Eclipse Documentation
Techotopia.com
Virtuatopia.com

How To Guides
Virtualization
General System Admin
Linux Security
Linux Filesystems
Web Servers
Graphics & Desktop
PC Hardware
Windows
Problem Solutions
Privacy Policy

  




 

 

Eclipse Web Tools Guide
Previous Page Home Next Page

Limitations of J2EE development tools

This topic outlines current known limitations and restrictions for J2EE tooling.

Spaces not supported in JAR URIs within an enterprise application

Spaces are not supported in the URI for modules or utility JAR files in an enterprise application. The "Class-Path:" attribute of a MANIFEST.MF file in a JAR file or module is a space-delimited list of relative paths within an enterprise application. A JAR file would not be able to reference another JAR file in the EAR if the URI of the referenced JAR file contained spaces.

Enterprise application project names should not contain DBCS characters

When you create an enterprise application project, it is recommended that you do not give it a name that contains double-byte character set (DBCS) characters.

Java™ build path updates when removing the dependency on a Utility JAR file

When removing the dependency on a Utility JAR, the corresponding Java project will be removed from the Java build path only if the dependent JAR is still referenced by the EAR project. For example, suppose you create a J2EE 1.3 Web project and EAR along with the JUnit Java Example project. Next, add the JUnit project as a Utility JAR in the EAR, then add JUnit as a Java JAR Dependency of the Web project. If you then wanted to remove the dependency between JUnit and the Web project, remove the Java JAR Dependency from the Web project first, then remove the Utility JAR from the EAR. Follow this order to ensure that this works correctly.

Java JAR Dependencies page fails to update Java build path

The Java JAR Dependencies page is not synchronized with the Java build path page in the project properties dialog. Therefore, a change applied in one may not be reflected in the other within the same dialog session. There are also some instances where flipping back and forth between the pages will cause the update from one to cancel out the update from another when the OK button is clicked or if the Apply button is clicked prior to the OK button. Typically this will appear as if a JAR dependency was added, but the project did not get added to the Java build path. The workaround is to reopen the properties dialogs, switch to the JAR dependency page, clear and re-select the dependent JAR files, then click OK.

'Invalid project description' error when using a non-default project location for a new J2EE project

When you create a new J2EE project (including Java, enterprise application, Dynamic Web, EJB, application client, and connector projects), you cannot use a project location that is already used by another project in the workbench. If you choose a project location that is used by another project, the wizard displays an "Invalid project description" error dialog or message. If after you receive this message you then select a valid project location by clicking the Browse button, the project creation will still not finish. The workaround is to click Cancel and reopen the project creation wizard.

 
 
  Published under the terms of the Eclipse Public License Version 1.0 ("EPL") Design by Interspire