Embarcadero® JBuilder™ 2008 Release 2 Release Notes

Abstract: This document contains a subset of known problems, workarounds and tips for JBuilder 2008 R2.

In This Article

Embarcadero® JBuilder™ 2008 Release 2

Release Notes

Introduction

This document contains a subset of known problems, workarounds and tips for JBuilder 2008 R2.

For updates to these notes, see http://dn.embarcadero.com/article/39378.

For more product information, refer to the JBuilder 2008 R2 Help online and the various links on the Welcome to JBuilder 2008 R2 menu item on the product Help menu. These resources describe the new features of JBuilder 2008 R2. You can also find other plug-in specific help through the Eclipse Online Help links.

 

Table of Contents

What's New

  • Eclipse 3.4.1 support

    JBuilder 2008 R2 is based on Eclipse Ganymede 3.4.1. Please refer to the following link, and search for What's New to see new features in Eclipse Ganymede 3.4.1 (What's New in Eclipse Ganymede 3.4).

  • Capabilities/Profiles

    Capabilities/Profiles is an extension of Eclipse's Capabilities. To reduce clutter in the workbench and to more narrowly focus your views, UI elements (such as menus and tool buttons) are grou ped into Capabilities. They can then be selectively enabled or disabled. Collections of Capabilities are grouped into Profiles. JBuilder 2008 R2 comes with predefined Profiles and you can create your own. Profiles enable fast UI switching. To edit JBuilder Prof iles, click the UI Profiles drop-down menu on the status bar and click Edit Profiles.

  • Getting Started Wizard

    The Getting Started wizard helps configure the workspace to work effectively with JBuilder. It opens the first time you launch JBuilder in a new or existing workspace. Among other things, the wizard allows you to disable and enable serveral features to reduce UI clutter and improve performance.
     

  • Feature Navigator

    Feature Navigator guides you through existing IDE features. Under features where it is appropriate, help topics and one or more cheat sheets are provided to help define the workflow(s) using the UI e lements that make up that feature. The Feature Navigator is helpful to explore what features are new in a particular version of JBuilder, as well as helpful for users new to JBuilder but know the task they would like to complete.

  • Tagging

    The ability to tag resources is now available in all Java projects in a workspace. Tags are typically used to group related resources. They provide an organizational and navigational mechanism for the application. Use the Tags view to create tags, link resources to tags and focus certain IDE views on resources linked to a tag. Tags now support rules that define java type patterns that can apply to java files in your workspace that will get dynamically added to provided or specified tags.  Some basic rules are defined and can be viewed in the Reorganize Tags and Links view. To bring up this view click on the dropdown menu in the Tags view and select Reogranize Tags and Links.

  • Enable Java Modeling

    Java modeling can be enabled for any Eclipse Java project by right clicking on the project in the Package Explorer and select Enable Java Modeling.

  • Model Scope Selection
The Model Scope Selector view in the Modeling perspective allows you to exclude classes from the diagram reducing clutter and memory footprint. Child members of java classes are now hidden automatically in diagrams when a complexity threshold is reached. Classes with hidden member elements can be expanded and collapsed to view/hide member elements using the "Show/Hide All Members" toolbar button. The threshold can be configured in workspace settings. To edit the threshold, click Window|Preferences. Expand Modeling and click on Scope to modify settings for viewing/hiding child members in a class diagram.
 
  • Export/Import Workspace Settings

    Export/Import Wizard allows teams to share a common workspace configuration, as well as rapidly reconstruct an existing workspace. To open the wizard select File | Export or Import | General | Workspace Settings.

  • Export Jar file with dependency checking

    This wizard allows you to export project(s) and library dependencies into a JAR file on the local file system. To open the wizard select File | Export and select Java | JAR file with dependency checking.

  • Generation of EJB test client for EJB 2.x and 3.0 session beans

    The EJB Test Client is a simple standalone java class with mean method that can be used to test EJBs with remote interfaces.

  • DTO/Session Facade and client generation for EJB 2.x and 3.0 entity beans

    The DTO/Session Facade wizard generates data transfer objects (DTOs) for EJB 2.x entity beans. It generates a session facade and delegate for both EJB 2.x and 3.0 entity beans. It also provides the option to generate either a Struts or JSF web client or a standalone java client. The wizard for EJB 2.x entity beans are opened by right-clicking on an entity bean in the EJB diagram and selecting the option Run DTO/Session Facade wizard. The wizard for EJB 3.0 entity beans are opened by right-clicking on an entity bean in the EJB diagram and selecting the option Run Session Facade wizard.

[ top ]

    Updating Your Product License

    License updates include new or modified license attributes. There are three ways to update the JBuilder License:

    • Manual license updates
    • Scheduled license updates
    • Software update

    To manually update your license:

    1. Open Help | JBuilder Licensing | License Updates.
      The license update selection window opens.
    2. From the License update selection window, select the license(s) you wish to update.
    3. Click OK.

    If an update is available, a message is returned describing the new license. Click OK to update. There is also a message returned when there is no update available.

    To schedule license updates:

    1. Open Window | Preferences | Licensing.
    2. Check Enable automatic license update.
    3. Select a schedule option in the Automatic License Update Schedule box.

    The final way to update your license happens when you update the software. At this time you are automatically asked if you would like to update your license.

    [ top ]

    Blackfish SQL

    Below is new information regarding Blackfish SQL.

    •  

    Installing Blackfish SQL on Red Hat Enterprise Linux 5.0

    The Blackfish installer on Red Hat Enterprise Linux 5.0 requires that all libraries to run a Swing based Java application to be installed. Install the required X libraries for Swing Development. In particular, the RPM package libXp-1.0.0-8.i386.rpm should be installed. This package can be found on "disk 2" of the Red Hat Enterprise Linux 5.0 distribution media, in the Server directory.

[5615] How to Make a Blackfish SQL Database Transactional

The Mac and Microsoft® Windows™ Vista installer for Blackfish SQL 8 does not make the sample databases transactional. This prevents the databases from being accessed from JDBC or SQL unless the database is opened in read-only mode. Use the following steps to make sample databases transactional:

  1. Launch JdsExplorer from [BFSQL-INSTALL-DIR]/bin/JdsExplorer.
  2. Use File | Open to open a database.
    Sample databases can be found in the [BFSQL-INSTALL-DIR]/samples/JDataStore/datastores.
  3. Select a database to open.
  4. Enter sysdba for user and masterkey for the password.
  5. Use the TxManager|Install menu to make the database transactional.
  6. Press OK on the Tx Manager properties dialog.
  7. Close the JdsExplorer.

Install, Startup, and Licensing

  • [4550 and 4698] Install fails to complete and JBuilder fails to launch with a JVM error,
    Cannot reserve more then 1136mb of memory for JBuilder on certain machine configurations.
    Workaround: This is a 2-step workaround.
    1. Edit the file JBuilder.ini in the root of the JBuilder install directory and add the parameter:
      -vm jre\jre\bin\javaw.exe
    2. Run JBuilder_Home/reset_Jbuilder.bat

    Reference: https://bugs.eclipse.org/bugs/show_bug.cgi?id=188968.

  • Clean option on startup with new plugins: If you use a workspace that was created by an earlier version of JBuilder or Eclipse, the IDE should be launched with the -clean option on the command line:

    jbuilder.exe -clean

    This procedure is recommended whenever there are new plugin versions being executed. Using the clean option on the command line during startup removes caches and preferences in the workspace that might cause problems for the newer plugins.
  • [5425] Headless features require JBuilder to be licensed using full GUI - in order to run any command line tools or other headless features of JBuilder, JBuilder must first be licensed using the full GUI mode.

     
  • [5427] - Some data-aware frameworks are missing when upgrading an Enterprise License. For example: If you upgrade your license from JBuilder Professional to JBuilder Enterprise, you should run JBuilder with the -clean switch after you have entered the new license.
    1. If running JBuilder, exit the program.
    2. Go to a command prompt/terminal window.
    3. Navigate to the directory where JBuilder is installed, typically c:\JBuilder2008 R2 on Windows, [userhomedirectory]/JBuilder2008 R2 on Linux, or /Applications/JBuilder2008 R2/JBuilder.app/Contents/MacOS/JBuilder on Mac.
    4. Launch JBuilder with -clean, jbuilder.exe -clean on Windows, ./JBuilder.bin -clean on Linux, and ./JBuilder -clean on Mac.

    You only need to do this once, after you upgrade your license. After that, you can and should launch JBuilder the way you usually do.

[ top ]

Application Factory

  • [4423] A Problem reporting window opens stating that Could not restore workbench layout when opening JBuilder 2007 workspaces in JBuilder 2008 R2.
    Workaround: For each perspective being used, reset the perspective to the default view by selecting Window | Reset Perspective
  • [4299] Adobe Acrobat Reader should be installed before attempting to open the PDF-format report for data-aware applications from within the IDE .
  • [3954] When trying to invoke Code Insight (the context sensitive popup windows in the JavaScript Editor) while editing Application Factory scripts displays the following error The compilation unit is not in build path of a JavaScript project
    Workaround: To disable this message, select Window | Preferences | JavaScript | Editor | Content Assist | Advanced and uncheck Other JavaScript Proposals and Type Proposals.
  • [4569] When pressing the Export Module button to create a new application module from the module editor, manual changes to readme.html and cheatsheets.xml need to be saved File | Save prior to doing an Application Module export in order for them to get included in the built module.
  • [5618] The tagx file doesn't get updated after linking a note to a tag.
    Workaround:
    1. Create a new application factory project.
    2. Create a new note and tag.
    3. Link the note to the tag and view the tagx file.
    //exp: The tagx file is updated to show that the note is linked with the tag.
    //act: The tag entry isn't updated with the note id.

    If you update the tagx file (by adding another tag, note, etc.), the file updates.

[ top ]

Application Generator

  • [2732] Data-aware applications require that the project Java runtime "JRE System Library" be a full JDK in order to build the project successfully.
  • [4770] When you generate CRUD artifacts for one entity, generation of CRUD artifacts for related entities is NOT performed automatically. After CRUD generation Web-page for selected entity will be up-to-date and correct, but the links from this page to pages for related entities will not always work as expected until you explicitly invoke CRUD generation for related entities. Typical cases when broken link can occur:
    • You have entities A and B with 1:M or M:N relation link. You generate CRUD for entity A. Web page with list of entity A has link to page for entity B, but this link will not work until you generate CRUD for entity B also.
    • You have entities A and B without relation link. You generate CRUD for both of them. Then you add relation link between them you need to regenerate CRUD for both entities, otherwise Web link between pages will not work as expected.
    • Same applies for Tag cloud generation. After generation of tag cloud you will have correct tag cloud and tag list page, but the links from tag list page to entity page will not work correct until you regenerate CRUD for entity.
  • [5349] Compass search works incorrectly - Lucene supports escaping special characters that are part of the query syntax. Below are the current list special characters:
        + - && || ! ( ) { } [ ] ^ " ~ * ? : \
    To escape these character use the \ before the character. For example to search for (1+1):2 use the query:
        \(1\+1\)\:2
    For more information about search query syntax see http://lucene.apache.org/java/2_0_0/queryparsersyntax.html
  • [5342] Starting/deploying data-aware applications can sometimes timeout after 45 seconds. Although the server will usually start after several tries, the timeout can be changed through Window | Preferences | Server, Server timeout delay = Unlimited.
  • [4686] Compass: For a ParseException when trying to find by date field: Date format is defined in the compass-for-entityName.cmp.xml file of web application. By default java.util.Date type use MM/dd/yyyy format, java.sql.Timestamp - yyyy-MM-dd-HH-mm-ss.
  • [5589] After running Integration tests against a test database, to return back to the original database go to Project | Properties | Data-Aware Web Application Settings | Database settings, reselect correct database connection and click OK.

[ top ]

Project Migration

  • [621] Legacy Java EE JBuilder project imports copy over generated sources for web services projects resulting in compilation errors in JBuilder 2008 R2. Workaround: Remove the generated sources that were copied from the legacy project manually. Rebuild the project in JBuilder 2008 R2.
     
  • [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.

Web Services

  • [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).
  • [7524] AtLeap: Deployment fails using Geronimo 2.1.x due to lack of memory Workaround: For Geronimo (2.1.x), the server runtime launch configuration should be modified and Java VM memory should be increased. It worked when I added the following parameters to VM arguments in the launch configuration: -Xms256m -Xmx896m
  • [7617] AtLeap: Compilation errors occur when generating the AtLeap module on Macintosh with Geronimo (2.1.x/1.1.1). Workaround: Edit the VM arguments for the Geronimo server by double clicking on the server in the Servers view and add VM argument -Xmx512M.
     
  • [7582] AtLeap/JBoss/Linux: Setting up the target runtime and default server for JBoss does not enable the Next button. Workaround: Switch to another server and back to JBoss.
     

[ top ]

Enterprise JavaBeans (EJB)

  • [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 2008 R2.
  • [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.
     
  • [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.
  • [4969] Work around for performance issue with EJB Modeling - Use the option
    Windows | Preferences | EJB Modeling Prioperties | Source Synchronization to "Delay, ms" to tune based on the size of your application for better performance.
  • [5087] In some conditions a problem marker Target bean is not defined for ejb relationship can appear even if there are no errors in the source code and an entity relationship is correctly defined.
    Workaround:
    1. If autobuild option is on, switch it off.
    2. Open "Project/Clean..." dialog, select your EJB projects, uncheck option
      "Start a build immediately"
      and perform clean.
    3. Open your project properties, open Builders page and switch off
      "EJB Validation Builder"
      Confirm changes.
    4. Restore autobuild option or manually build EJB projects.
  • [6904] Macintosh: Build fails after adding the JBoss client library to an EJB project. Workaround: Create the client in a separate project from the server project(do not add Client library to the server project).
  • [7186] Test Clients for EJB 2.1 Entity and Session Beans do not work on Apache Geronimo v.2.1.
    The reason is the following bug in Geronimo v.2.1: https://issues.apache.org/jira/browse/GERONIMO-4237
  • [7187] Exception after deploying Test Clients for EJB 3.0 Entity Beans on Geronimo Server v2.1.

    Workaround: For Geronimo (2.1.x), the server runtime launch configuration should be modified:

    1. Check that Group Id, Artifact Id, Version, and Artifact Type were currently set in Geronimo Deployment descriptors for EJB 3.0 project (openejb-jar.xml) and for web project (geronimo-web.xml). Notice that Artifact Id must be different.
    2. Add server dependencies in web project's Geronimo Deployment descriptor for EJB project. After this step descriptor may appear as shown below:
    <web:web-app xmlns:app="http://geronimo.apache.org/xml/ns/j2ee/application-2.0"
    xmlns:client="http://geronimo.apache.org/xml/ns/j2ee/application-client-2.0"
    xmlns:conn="http://geronimo.apache.org/xml/ns/j2ee/connector-1.2"
    xmlns:dep="http://geronimo.apache.org/xml/ns/deployment-1.2"
    xmlns:ejb="http://openejb.apache.org/xml/ns/openejb-jar-2.2"
    xmlns:name="http://geronimo.apache.org/xml/ns/naming-1.2"
    xmlns:pers="http://java.sun.com/xml/ns/persistence"
    xmlns:pkgen="http://openejb.apache.org/xml/ns/pkgen-2.1"
    xmlns:sec="http://geronimo.apache.org/xml/ns/security-2.0"
    xmlns:web="http://geronimo.apache.org/xml/ns/j2ee/web-2.0.1">
    <dep:environment>
    <dep:moduleId>
    <dep:groupId>default</dep:groupId>
    <dep:artifactId>web</dep:artifactId>
    <dep:version>1.0</dep:version>
    <dep:type>car</dep:type>
    </dep:moduleId>
    <dep:dependencies>
    <dep:dependency>
    <dep:groupId>default</dep:groupId>
    <dep:artifactId>ejbProject</dep:artifactId>
    <dep:version>1.0</dep:version>
    <dep:type>car</dep:type>
    </dep:dependency>
    </dep:dependencies>
    </dep:environment>
    <web:context-root>/GeronimoWeb</web:context-root>
    </web:web-app>
  • [7283] Test Clients for EJB 3.0 Session Beans do not work on WebSphere 6.1 .

    Workaround: For the IBM WebSphere 6.1 Application Server you must do the following additional steps to correct the application:

    1. Start server and deploy project.
    2. Check that IBM JRE is set for client's project. The IBM JRE is located in the Application Server installation directory.
    3. Generate client's stub library:
      • Go to the "bin" directory in Application Server installation directory.
      • Run the following command:
      createEJBStub 
      "WebSphere_server_profile_directory"/installedApps/"domain_name"Node01Cell
      /"project_name".ear/"project_name"-was.jar
    4. For client's project add in classpath:
      "project_name"-was.jar(step 3)
  • [7731] Test Clients for EJB 2.x Session Beans do not work on WebSphere 6.1 .

    Workaround: For the IBM WebSphere 6.1 Application Server you must do the following additional steps to correct the application:

    1. Start server and deploy project.
    2. Check that IBM JRE is set for client's project. The IBM JRE is located in the Application Server installation directory.
    3. For client's project add the following Application Server generated library:
      "WebSphere_server_profile_directory"/installedApps/"domain_name"Node01Cell
      /"project_name".ear/"project_name"-was.jar
  • [7812] Test Clients for EJB 2.1 Entity Beans do not work on Apache Geronimo v.1.1.1.

    Workaround: For the Geronimo v.1.1.1 server, you must do the following additional steps to correct the application:

    1. Check that Group Id, Artifact Id, Version, and Artifact Type were currently set in Geronimo Deployment descriptors for EJB project(openejb-jar.xml) and for web project(geronimo-web.xml). Notice that Artifact Id must be different.
    2. Add server dependencies in web project's Geronimo Deployment descriptor for EJB project. After this step descriptor may appear as shown below:  
      <web:web-app xmlns:app="http://geronimo.apache.org/xml/ns/j2ee/application-2.0"
      xmlns:client="http://geronimo.apache.org/xml/ns/j2ee/application-client-2.0"
      xmlns:conn="http://geronimo.apache.org/xml/ns/j2ee/connector-1.2"
      xmlns:dep="http://geronimo.apache.org/xml/ns/deployment-1.2"
      xmlns:ejb="http://openejb.apache.org/xml/ns/openejb-jar-2.2"
      xmlns:name="http://geronimo.apache.org/xml/ns/naming-1.2"
      xmlns:pers="http://java.sun.com/xml/ns/persistence"
      xmlns:pkgen="http://openejb.apache.org/xml/ns/pkgen-2.1"
      xmlns:sec="http://geronimo.apache.org/xml/ns/security-2.0"
      xmlns:web="http://geronimo.apache.org/xml/ns/j2ee/web-2.0.1">
      <dep:environment>
      <dep:moduleId>
      <dep:groupId>default</dep:groupId>
      <dep:artifactId>web</dep:artifactId>
      <dep:version>1.0</dep:version>
      <dep:type>car</dep:type>
      </dep:moduleId>
      <dep:dependencies>
      <dep:dependency>
      <dep:groupId>default</dep:groupId>
      <dep:artifactId>ejbProject</dep:artifactId>
      <dep:version>1.0</dep:version>
      <dep:type>car</dep:type>
      </dep:dependency>
      </dep:dependencies>
      </dep:environment>
      <web:context-root>/GeronimoWeb</web:context-root>
      </web:web-app>
    3. Check that value of tag <web:context-root> in geronimo-web.xml is the same as value of tag <display-name> in web.xml.
    4. Create table in DB related to tested entity bean, if needed.
    5. On diagram add EJB reference from session facade bean to tested entity bean.
    6. 6) In EJB project modify java file related to generated session facade bean:
      • Go to the lookup_TestedEntityName_Home() method? where
      TestedEntityName_Home

      is the name of your entity bean .

      • Replace ENTITY_NAME constant value to "java:comp/env/_EJB_REF_", where
      _EJB_REF_

      is the name of EJB reference created on step 5.

    7. Go to the web project's properties. Open "Java EE module dependencies" page. Click "Add external jars" and select following file -
      _GERONIMO1.1_INSTALL_DIR_/repository/openejb/openejb-core/2.1.1/openejb-core-2.1.1.jar
  • [7835] Test Clients for EJB 2.1 and 3.0 Entity Beans do not work on IBM WebSphere 6.1 with EJB 3.0 feature pack (Embarcadero) 

    Workaround: For the IBM WebSphere 6.1 Application Server, you must do the following additional steps to correct the application:

    For EJB 3.0:  

    1. For EJB project check that your persistence.xml is correctly configured.
    2. Start server and deploy the EJB project.
    3. Check that your WebSphere Application Server does not have the following problem:
       http://www-01.ibm.com/support/docview.wss?uid=swg24014758 
    4. Check that IBM JRE is set for client project.

      It usually locates in Application Server installation directory.

    5. Generated client's stub library:
      • Go to the "bin" directory in Application Server installation directory.
      • Run the following command:
      createEJBStubs 
      "WebSphere_server_profile_directory"/installedApps/"domain_name"Node01Cell
      /"project_name".ear/"project_name"-was.jar
    6. Go to the web project's properties.
      Open "Java EE module dependencies" page.
      Click "Add external jars" and select "project_name"-was.jar .

    7. Create table in DB related to tested entity bean, if needed.
    8. Deploy client project.  

    For EJB 2.x:

    1. Start server and deploy the EJB project.
    2. Check that IBM JRE is set for client's project. It usually locates in Application Serve installation directory.
    3. Go to the web project's properties.
      Open "Java EE module dependencies" page.
      Click "Add external jars" and select
      "WebSphere_server_profile_directory"/installedApps/"domain_name"Node01Cell/"project_name".ear/"project_name"-was.jar 
    4. Create table in DB related to tested entity bean, if needed.
    5. On diagram add EJB reference from session facade bean to tested entity bean.
    6. In EJB project modify java file related to generated session facade bean:
      • - Go to the lookup_TestedEntityName_Home() method where _TestedEntityName_ is the name of your entity bean
      • - Replace ENTITY_NAME constant value to "java:comp/env/_EJB_REF_",
        where _EJB_REF_ is the name of EJB reference created on step 5.
    7. Deploy client project.

[ top ]

J Optimizer

  • [5348] On Linux platform, J Optimizer cannot compare Request Analyzer snapshots if the LD_LIBRARY_PATH is not set to include [optimizeit-install-path]/eclipse/optimizeit-agent/lib and [optimizeit-install-path]/eclipse/optimizeit-agent/ext/strace/lib directories

[ top ]

Third Party

  • [5372] ClearCase - users have reported issues with the ClearCase plugin that ships with JBuilder. IBM offers an improved version of the ClearCase plugin. If you use ClearCase with JBuilder we recommend that you download it from http://www.ibm.com/developerworks/rational/library/content/03July/2500/2834/ClearCase/clearcase_plugins.html.
  • [2870] In some cases when a JPA modeling project is under subversion VCS, modification of entities brings up a Subversion lock dialog.
    To avoid it edit \.metadata\.plugins\org.eclipse.core.runtime\.settings\com.tssap.selena.model.platform.eclipse.prefs file and add a line UseHookForTeamOperations=false.
  • [5322] JBoss Tools HTML Editor - On Linux systems, opening an HTML file for the first time in a workspace with the JBoss Tools HTML Editor may not work. If it fails, try restarting JBuilder. Select File | Switch Workspace | Other, and click OK to restart in the same workspace. If it still fails, follow the steps at http://labs.jboss.com/wiki/JBosstoolsVisualEditorFAQ to make sure you have the correct libstcd version installed on your machine.
  • [5652] The Java Script editor opens a dialog when code completion is invoked. This happens when typing a javascript varaibale followed by a '.'
    Workaround: Turn off all completion proposals in Windows | Preferences | Java Script | Editor | Content Assist | Advanced.
  • [7268] EJB Session Facade Wizard: Deploy JSF test client on JBoss 4.2 fails. JBoss 4.2 does not support web container 2.5 (the same issue with JSF Data-Aware Apps on JBoss 4.2)

[ top ]

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

  • [2085] 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.
  • [2836] Dates selected via the date picker UI in Xplanner are not formatted correctly. Workaround: users will need to enter the date manually in the date fields using the format yyyy-mm-dd instead of using the UI to select the dates.

[ 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.
  • [6663] The Liferay portal fails to load in an external IE browser under Win 2003 (IE6 and IE7). Loads okay with FireFox and from w/in ProjectAssist. Loads okay under WinXP/IE7.
  • [8290] Liferay's StarTeam task portlet shows up as inactivated. Workaround : After installing the component stack, the <StarTeam>\SDK\lib files need to be copied into the <ProjectAssist home> (c:\Embarcadero by default)\ProjectAssist\Liferay-portal-tomcat-jdk\shared\lib.

[ top ]

Continuum/Maven

  • [1344] The following error can occur while running Maven:

    Error: "The plugin 'com.borland.maven.mojo:qalab' does not exist or no valid version could be found"

    Error: "The plugin 'com.codegear.maven:optimizeit-test-coverage-plugin' does not exist or no valid version could be found"

    Error: "The plugin 'com.codegear.maven:together-reports-plugin' does not exist or no valid version could be found"

    The sample Maven 2 project generated by ProjectAssist can use one or more Maven 2 plugins. When ProjectAssist installs the Continuum component, it copies the above plugins 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 plugins are copied to the wrong location.

    It might look for the Maven repository in any of these locations:

    1. c:\.m2\repository
    2. windowsdrive:\Documents and Settings\LocalService\.m2\repository
    3. windowsdrive:\windows\system32\config\systemprofile\.m2\repository

    Workaround:

    1. The plugins, along with cached copies of other plugins used by ProjectAssist, are in [ProjectAssist install dir]\projectassist\eclipse\plugins\com.borland.dsib.project[version number]\components\SampleProject\.m2.zip. Unzip that file into the .m2 directory that Continuum is using as its Maven repository. If prompted to overwrite any existing files when unzipping, you should do so.
    2. 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.
    3. 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>
  • [6642] Build failure occurs when issuing Continuum build "verify site-deploy" without internet access. Workaround: Run the build a second time.

[ 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.

[ 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:
    1. Select the Parameters link on the bottom of any Bugzilla page.
    2. Select Dependency Graphs in the list of setting groups on the left of the page.
    3. 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)
     

[ top ]

Mylyn

  • [8]When working with Mylyn and repositories that have already been configured, a user name and password credentials sometimes disappears -- this happens for all Mylyn repository types.
    Workaround: Open the repository properties and re-add the credentials.

[ top ]

StarTeam

  • [6946] Liferay does not list any files for the StarTeam Repository.
     
The ProjectAssist installer no longer installs StarTeam support. To install "ProjectAssist Support for StarTeam":
  1. Launch the product
  2. Click Help | Software Updates
  3. Click on the Available Software tab
  4. Expand the node labeled either "JBuilder Update Site", or labeled http://www.jbuilderupdatesite.com/2008r2. Then expand the node "StarTeam Support". Select the "ProjectAssist Support for StarTeam". Note: Select the "JBuilder Support for StarTeam" node if you are using JBuilder.
  5. Click on the Install button.
  6. Follow the rest of the steps, including accepting the license agreement.
  7. Restart the product after the install completes.
To enable the StarTeam portlets in the Liferay portal:
  1. In a web browser, go to http://www.borland.com/downloads/download_starteam.html,and download "StarTeam 2008 SDK Runtime for Windows". Note the value of "2008" will be whatever the current StarTeam version is. If you already have the StarTeam SDK Runtime installed, go to step 4. Otherwise continue with step 2.
  2. Install it. You can install before or after you run a ProjectAssist install.
  3. After you have run a ProjectAssist install, shut down Liferay. To shut down Liferay, go to the \bin directory, and run shutdown.bat. This will by default be C:\Embarcadero\ProjectAssist\liferay-portal-tomcat-jdk5-4.0.0. Or you can also click on the "Stop Liferay" link in the "Links to Installed Components" editor in ProjectAssist.
  4. Go to the lib directory where the StarTeam SDK Runtime was installed. By default, that is something like, depending on the version of StarTeam, C:\Program Files\Borland\StarTeam SDK 2008\lib.
  5. Copy all of the .jar files in the above StarTeam lib directory to \shared\lib. You may need to create the lib directory; shared should already exist.
  6. Restart Liferay, by running startup.bat, or by clicking on the "Start Liferay" link in the "Links to Installed Components" editor in ProjectAssist.
  7. If you have run the ProjectAssist install more than once, and have installed more than one instance of Liferay, then you will need to repeat the previous 3 steps for every instance of Liferay that has StarTeam portlets
  • [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.
  • [8297] PATI: Admin user that gets added with StarTeam stack does not have any default rights to StarTeam Portlets. Workaround: Right click on the AccessRights column next to StarTeam and grand "Admin" rights. Currently you can only grant Developer rights.
  • [8310] PATI: StarTeam : Cannot create a new task from Mylyn connector. Workaround: Create tasks from outside.

[ 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 2008 R2 welcome screen provides links to samples on the web. Go to:

  1. Help | Welcome to JBuilder 2008 R2
  2. Scroll down and click Samples and Wizards

[ top ]

Videos

The JBuilder 2008 R2 welcome screen provides links to videos samples on the web. Go to:

  1. Help | Welcome to JBuilder 2008 R2
  2. Scroll down to Videos and Video Tutorials

[ top ]

Documentation and Getting Help

For the JBuilder FAQ, Videos, and all the other latest JBuilder 2008 R2 information, please visit http://www.embarcadero.com/products/jbuilder/index.php

[ top ]

Installation Instructions

For installation instructions, see install.html in your [JBuilder2008 R2Directory].

[ top ]

v2008 R203311530

Published on: 4/6/2009 3:58:48 PM

Server Response from: ETNASC03

Copyright© 1994 - 2013 Embarcadero Technologies, Inc. All rights reserved.