 [All]
JBuilder 2007 Readme
Abstract: Release Notes for JBuilder 2007
Introduction
This document contains a subset of known problems, workarounds and tips for JBuilder 2007.
Check the JBuilder product site at http://jbuilder.codegear.com/ for any
additional JBuilder Release Notes
items that may have occurred subsequent to this document.
For more product information, refer to the JBuilder 2007 Help
online and the various links on the Welcome to CodeGear JBuilder 2007
menu item on the product Help
menu.
These resources describe the new features of JBuilder 2007. You can also find other plug-in specific help through the Eclipse Online Help
links.
System Requirements
The system requirements for each of the CodeGear JBuilder editions are listed below:
- 1 GB RAM recommended minimum
- 1.5 GB RAM recommended
- 700 MB to 1.2 GB hard disk space minimum (depending on the JBuilder 2007 edition), plus additional space during installation
- Intel® Pentium® 4/2.4 MHz or higher (or compatible)
- DVD-ROM drive
- High-resolution monitor (1024x768 or higher, 256 colors)
- Mouse or other pointing device
Windows® Operating System (ProjectAssist Server Installation):
- Microsoft® Windows® XP Professional (SP2)
- Microsoft® Windows® 2003 Server
Windows® Operating System (IDE or Assimilated TeamInsight Components):
- Microsoft® Windows® Vista 32-bit
- Microsoft® Windows® XP Professional (SP2)
- Microsoft® Windows® 2003 Server
- P4 2.4 GHz processor, or greater
- 1 GB RAM recommended
- Red Hat Linux 4.0
- Intel Processor
- 1 GB RAM recommended
- OS X Tiger
- 512 MB RAM minimum
- 768 MB RAM recommended
- 700 MB to 1.2 GB hard disk space minimum (depending on the JBuilder 2007 edition), plus additional space during installation
- Intel® Pentium®4/2.4 MHz or higher (or compatible)
- DVD-ROM drive
- High-resolution monitor (1024x768 or higher, 256 colors)
- Mouse or other pointing device
Windows® Operating System:
- Microsoft® Windows® XP Professional (SP2)
- Microsoft® Windows® Vista 32-bit
- Microsoft® Windows® 2003 Server
- P4 2.4 GHz processor, or greater
- 1 GB RAM recommended
- Red Hat Linux 4.0
Macintosh® (IDE or Assimilated TeamInsight Components)
- Intel Processor
- 1 GB RAM recommended
- OS X Tiger
[ top ]
Known Issues
These issues are organized by product area.
General
Project Migration
- [621] Legacy Java EE JBuilder project imports copy over generated sources for web services projects resulting
in compilation errors in JBuilder 2007.
Workaround: Remove the generated sources that were copied from the legacy project manually. Rebuild the project in JBuilder 2007.
- [2202] Legacy Java EE project import fails if the machine does not have an active internet connection.
Workaround: Ensure that the computer has an active internet network connection before
performing a legacy JBuilder Java EE project import.
[ top ]
Web Services
- [871] WebServices Client: Incorrect URL to client JSP when using the Run As menu to launch the client JSP. wrong URL is given:
http://localhost:8080/ejbjbWS30Web/servlet/AdminServlet/sampleSession1SessionProxy/TestClient.jsp
should be:
http://localhost:8080/ejbjbWS30Web/sampleSession1SessionProxy/TestClient.jsp
Workaround: Remove part /servlet/AdminServlet from URL manually.
- [2411] Geronimo Web Services: User cannot access web project using default context name when deploying a standalone web project
Workaround: Package the web project into an Enterprise Application project and deploy the Enterprise Application Archive (EAR).
[ top ]
Enterprise JavaBeans (EJB)
- Creating a standalone Java test client for EJBs: JBuilder 2007 provides code templates for
the initial context code required to lookup EJBs from a standalone Java client. Code templates are
prefixed by
gic. JBuilder 2007 provides code templates for all supported servers. To use the template:
- Type
gic, followed by Ctrl+Space to invoke the code template listing.
- Select the appropriate code template according to the server being tested.
- [785] EJB diagram: Double clicking on bean in model navigator does not open the diagram for a newly converted project.
Workaround: User can open diagram by double clicking on the diagram package and then
selecting the bean by double clicking on the bean (in model tree).
- [1384] EJB 3.0: Oracle 10.3.1.1 standalone server is looped on password inquiry if the server is not initialized previously.
Workaround: To use the Oracle OC4J 10.1.3.x application server, the user must perform a first
time initialization manually, according to readme provided with Oracle server.
After initial manual start and stop, OC4J can be used from JBuilder 2007.
- [1555] EJB 2.x: Failure to generate home interfaces when bean has home method that does not
start with ejbHome prefix, such as ejbHomename.
Workaround: Make sure all home methods have the ejbHome prefix appended to the name.
- [1639] XDoclet code generation fails if default JRE for workspace is set to JDK 1.4.
Workaround: Ensure that the default JRE for the workspace is set to JDK 5.0.
- [2320] Legacy Java EE project import fails to generate XDoclet annotations for business methods in session beans.
Workaround: Delete the imported project and re-import the project in the same workspace.
[ top ]
Optimizeit
Team Development with ProjectAssist and TeamInsight
The following are known problems in the various components installed during the ProjectAssist server installation. These can affect the use of these components by the
TeamInsight clients.
ProjectAssist Administration
- [1442] Japanese characters cannot be used
in the ProjectAssist Mail Notification email message.
- [1647] In some cases, removing more than one user at the same time (by multiselecting users) in the
ProjectAssist Configuration Editor can damage the stack file (.pacx file extension).
This requires manual editing of the file to recover. To avoid manual editing recovery, remove only one user at a time.
- [2561] Navigating back and forth in ProjectAssist File Wizard during a .pacx file install may cause inconsistent results in
subsequent relists of already scanned components.
Workaround: Cancel and re-scan.
- [2652] The caret and percent sign (^ and %) cannot be used in ProjectAssist project names. The use of these characters
causes problems in Subversion.
[ top ]
Liferay
- [1545] If first Pre-Installation Scan in the ProjectAssist Stack file install is skipped, the user cannot assimilate a running install of Liferay until
the user enters non-conflicting values.
Workaround: If you want to assimilate an existing Liferay installation, do not skip the first Pre-Installation Scan
during the ProjectAssist stack file installation. Perform at least the Minimal Scan during the first Pre-Installation Scan.
- [1943] When opening Bugzilla portlet through Liferay, the X-axis (Time)on the Trends tab starts with an old date.(1970-01-01)
- [2619] On some systems, the StarTeam portlets in the Liferay portal may not work immediately after an
install.
Workaround: If the StarTeam portlets do not work, reboot the computer which has the Liferay
server installed on it.
[ top ]
Continuum/Maven
Error: "The plugin 'com.borland.maven.mojo:qalab' does not exist or no valid version could be found"
The sample Maven 2 project generated by ProjectAssist uses a Maven 2 plugin
created by CodeGear. When ProjectAssist installs the Continuum component, it copies the com.borland.maven.mojo:qalab plugin
to the local Maven 2 repository.
Continuum runs as a service and where it looks for the local Maven repository varies
based on the particular configuration of Windows.
On some machines, the Borland plugin is copied to the wrong location.
It might look for the Maven repository in any of these locations:
c:\.m2\repositorywindowsdrive:\Documents and Settings\LocalService\.m2\repositorywindowsdrive:\windows\system32\config\systemprofile\.m2\repository
Workaround:
- Copy over the directory
com\borland\maven\mojo
Note: You must copy this and all of its descendents, starting at .m2\repository.
- If individual developers want to run Maven against a
ProjectAssist generated Maven 2 SampleProject, they need
to install the directory and descendants on their local machine.
- For users not running as a service, the
location of the Maven 2 repository is always
userhome\.m2\repository. For example, if you are logged on with username JDOE, and
assuming your Documents and Settings directory is on drive C:,
your Maven repository is located at
c:\Documents and
Settings\JDOE\.m2\repository.
- [1422]On initial startup, the Maven Archetype Wizard may take a long time to open.
This is an issue with the m2 plugin indexing both the remote
repository and the local .m2 directory. The first time the m2 plugin is loaded
in a new workspace, it builds these indexes and require more time to open.
- [1599]The Continuum build output page cannot display multibyte characters correctly.
Workaround: Click on Download as text to view the result in plain text
format.
- [2329]In assimilation cases where Continuum is not installed on the same machine as
Liferay, the project upload fails. Continuum requires access to the POM file. If there is a firewall
between Continuum and Liferay, the project addition fails.
Workaround:Open the Liferay port (8080) so that Continuum can
access the project file.
- [2629]By default, "Site goal" does not work since a dependent extensions section does not get added to the .pom file.
Workaround: Add the following in your build section to run "site" goal from Continuum on
JBuilder generated projects:
<build>
<extensions>
<extension>
<groupId>org.apache.maven.wagon</groupId>
<artifactId>wagon-webdav</artifactId>
<version>1.0-beta-1</version>
</extension>
</extensions>
</build>
[ top ]
CVS
- [2610] Corrupt characters may appear in the comment areas of the CVS Liferay portlet. This may be caused by
the default encoding of the server machine (used by Liferay) being different from
the encoding used when checking in the comment.
Workaround: A field exists on the CVS portlet Setup tab to specify type of encoding for comments.
[ top ]
Subversion
- [1599] The Subversion viewer Show file field cannot display international characters.
The Subversion viewer Diff to previous can display international characters only when the server character set
and the source file character set are identical.
- [1612] If the same Administrator is used for both Subversion and XPlanner but
a different password was entered for each component, then the Subversion Administrator
password is duplicated from the XPlanner password. It does not use the unique password originally specified.
[ top ]
Bugzilla
- [1299] When Bugzilla is installed as a ProjectAssist component, it exists in the
root url context (for example, http://myserver:8070, as opposed to
http://myserver:8070/bugzilla).
- [1418] At least one component name is required in the
Components field on the Projects
tab of ProjectAssist Designer to be able to enter bugs for a Bugzilla project.
Workaround: In the Components field for Bugzilla enter a single
component name, or a comma-separated list of component names. Spaces are allowed in component names. If you use quotes
around a component
name, the quotes are part of the component name in Bugzilla.
- [1608] Bugzilla webdotbase parameter is not set to use the installed WebDot, but
instead points to the default value set by the installation of
http://www.research.att.com/~north/cgi-bin/webdot.cgi/%urlbase%
Workaround: This is actually designed behavior -- the default value works to display local
and remote graphs. ProjectAssist installs a version of WebDot (graphviz 2.8) so that you
can optionally use this version for generating dependency graphs
locally. To generate dependency graphs locally:
- Select the Parameters link on the bottom of any
Bugzilla page.
- Select Dependency Graphs in the list of setting
groups on the left of the page.
- Follow the instruction for setting the webdotbase
parameter. You must specify the full path to
dot.exe in your
installed WebDot.
- [1943] When opening Bugzilla portlet through Liferay, the X-axis (Time)on the Trends tab starts with an old date.(1970-01-01)
- [2559 and 2649] When installing a Bugzilla project through ProjectAssist, you cannot specify a
default component or project name with a hyphen ('-') in it. Any such component does not get added
to Bugzilla.
Workaround: Use the Bugzilla web interface to add
the component and version for the new project. The component is added in this case.
[ top ]
Mylar
- [8]When working with Mylar and repositories that have already been configured,
a user name and password credentials sometimes disappears -- this happens for all
Mylar repository types.
Workaround: Open the repository properties and
re-add the credentials.
- [2153] XPlanner: If you have a query against a XPlanner, and synchronize while in the Task view,
the items and their decorators appear to repaint more than necessary.
[ top ]
StarTeam
- [2032]It is possible that extended characters may appear corrupted if the encoding for the characters displayed
in the Connections Parameters dialog does not match the default
encoding used by the operating system. Open this dialog by
selecting
Window | Show Views | Other | Star Team | Server Explorer,
right-click on the server in the server view and select Properties )
Workaround: Change the encoding in the "Connection Parameters" dialog to an appropriate value for the locale on which the user is running.
- [2619] On some systems, the StarTeam portlets in the Liferay portal may not work immediately after an
install.
Workaround: If the StarTeam portlets do not work, reboot the computer which has the Liferay
server installed on it.
[ top ]
MySQL
- [769] Note:
It is normal for Developers to have a No Access role for MySQL.
Although Developers have no direct access to databases, ProjectAssist services
that rely on those databases will work for TeamInsight members. Assigning the Developer
role for MySQL has no effect; only users assigned an Administrator role have
access privileges.
[ top ]
Samples
The JBuilder 2007 welcome screen provides links to samples on the web. Go to:
- Help | Welcome to CodeGear JBuilder 2007
- Scroll down and click on Samples and Wizards
[ top ]
Videos
The JBuilder 2007 welcome screen provides links to samples on the web. Go to:
- Help | Welcome to CodeGear JBuilder 2007
- Scroll down and click on Videos
[ top ]
Documentation and Getting Help
Installation Instructions
|
