Java CAPS 6 Release Notes

What's New in This Release

The Java CAPS 6 release includes the following new features:

NetBeans 6.1 Based Tooling

• Complete backward compatible support for repository-based applications
• JCA Adapter support in EJB Web Services
• QoS enhancements in JBI Composite Application Editor
• Support for Solaris, Linux and Mac

Runtime on Sun Java Application Server 9.1 UR2 Patch 1

• Support for Repository, Java EE and JBI applications
• Application Configuration

Bidirectional Reuse by means of JBI Bridge

Solid Management Foundation

• Rich set of management APIs
• Scriptable with an JS-223 compliant scripting language
• Enterprise Manager enhanced for use with the Sun Java Application Server 9.1
• Integrated JBI management in the Sun Java Applicaton Server 9.1 console and CLI

Improved Installation Experience

• Simple installation with a set of preloaded components
• Multi-platform support: Windows, Solaris, AIX, Linux and Mac
• Service tag registration

New JCA Adapter Pack that caters to the integrations needs of Java EE developers

• File, JMS, Batch, Oracle, Oracle Applications, JDBC, Siebel, TCP/IP, SAP BAPI and SAP ALE
• Available as a separate component in MEP Project

Cluster enabled JBI runtime with Systemic Quality Improvements

BPEL 2.0 runtime is faster and scalable and includes a configurable QOS

New Master Date Management (MDM) Suite

• Bulk matching and loading tool
• Service enabled
• Source extraction support by means of the Data Integrator
• New and enhanced Master Index Data Manager GUI
• Full XA Support
• Extensible matching and standardization engine

Additional JBI components available for preview

• File Binding Component
• JMS Binding Component
• XSLT Service Engine
• IEP Service Engine
• SQL Serice Engine

The JBI components from Open ESB are available for preview. They are not supported as part of Java CAPS 6.

List of New Product Names

Java CAPS 6 features the following new product names:

Software Requirements

Supported Platforms

For a list of supported platforms for Java CAPS 6, see Planning for Java CAPS Installation, Java CAPS Supported Operating Systems

Known Issues with Supported Platforms

Supported Browsers

For a list of supported browsers for Java CAPS 6, see Planning for Java CAPS Installation, System Requirements

Known System-related Issues

Interoperability

Interoperability testing between Java CAPS 6 and the Java Enterprise System (JES) has been completed for the following products:

Known Interoperability Issues With Sun Java System Access Manager

6690970 No Support for HTTP Binding Component Authentication with Access Manager in Legacy Mode

6695565 No Support for HTTP Binding Component Authentication for x.500 Suffix Naming Convention

6707146 The Default Access Manager Setup Provided by Java CAPS does not Work with Federated Access Manager 8.0

Known Interoperability Issues With Sun Java Portal Server

6662622 Worklist Manager Portlet from Java CAPS 5.1.3 does not Deploy on Portal Server 7

Known Interoperability Issues With Sun Java Application Server

External Systems Supported in Java CAPS 6

Known Issues with Installation

6676062 STCMS Input Screen of Java CAPS Installer Does Not Select Red Hat Enterprise Linux AS Release 4 by Default

Problem Summary On Solaris and Windows machines, the Java CAPS installer automatically selects the operating system or platform type. When using a Red Hat Enterprise Linux AS Release 4 machine, the installer makes no selection and remains at 'do not install.'

Workaround Select Red Hat Enterprise Linux AS Release 4.

6698061 Repository Does Not Start When Installed as a Service on Windows Vista

Problem Summary The repository does not start when installed as a service on Windows Vista. The repository service manager hangs, displaying message 'Starting repository server'.

Workaround None. See https://issues.apache.org/bugzilla/show_bug.cgi?id=41564 for a description of a known Tomcat bug. Window Vista changed its service implementation. Tomcat 4 (Repository) and 5 (EM) cannot be installed as services in Vista.

6706840 Installer Hangs for Red Hat Enterprise Linux 5

Problem Summary When installing on Red Hat Enterprise Linux 5, the installer hangs when you click done.

Workaround If the installer does not close after you select 'done' then select the 'x' button in the right-hand top corner. A new window will open with the message 'installation not complete.' Select 'okay.'

Known Issues with Sun Enterprise Service Bus

6660165 Messages Truncated When Using Web Service Client

Problem Summary When a JCD that is built as a web service receives the message from the JCD that is calling it, the message is truncated.

Workaround Truncate the date with slash r (\r).

6670699 Scroll Bars are not Present when BP/CMap Graphic is Enlarged in Firefox Browser

Problem Summary When the User zooms in on the BP or CMap, the User cannot view any portions of the enlarged BP or CMap that extend past the borders of the original frame, as scroll bars do not appear in a Firefox browser. Scroll bars will appear in Internet Explorer when the enlarged graphic exceed the dimensions of the original frame if the SVG Viewer is installed.

Workaround User must resize the BP or CMap to fit into a single window frame.

6684782 Upload of .sar Files Fail on AIX 5.3 Due to catalog.xml Exception

Problem Summary The upload of .sar files fail on AIX 5.3 due to catalog.xml exception:

install:
[EdModuleInstall] Module: HL7OTDLibrary
[EdModuleInstall] Repository directory: InstallManager/edesigner/modules/
[EdModuleInstall] ED directory: modules/
[EdModuleInstall] Distributed URL: http://iecaix1.india.sun.com:12240/repository/Repository
[EdModuleInstall] Connecting to Repository: http://iecaix1.india.sun.com:12240/Repository
[EdModuleInstall] Adding Module: HL7OTDLibrary
[EdModuleInstall] local temp catalog.xml path : /Venkat/JavaCAPS6-20080404-0500/upload/C47791EFDB65E9CA700F658FE105F266/gsr56466/_tmpcatalog.xml
[EdModuleInstall] retrieving catalog.xml from repository
[EdModuleInstall] Error while reading the Catalog.xml org.xml.sax.SAXParseException: Premature end of file.

BUILD FAILED
file:/Venkat/JavaCAPS6-20080404-0500/upload/C47791EFDB65E9CA700F658FE105F266/gsr56466/install.xml:35: Premature end of file.

Total time: 9 seconds

Workaround None. Use Java EE 5 SDK with AIX 5.3. The Java EE 6 SDK is not supported for AIX 5.3 and Java CAPS 6.

6695408 The OTD Tester does not Launch to Open Transactions for OTD Libraries

Problem Summary The OTD Tester does not launch to open transactions for OTD libraries. The OTD Tester does not handle dependent JAR files correctly, especially JAR files for Forest API-based OTDs and B2B OTDs.

Workaround Modify the netbeans.conf file to add the following option into the netbeans_default_options: -J-Dantlrmaxaltblklines=3000

1. Open the netbeans.conf inside the $CAPS_INSTALL_DIR$/netbeans/etc directory using a text editor, replace $CAPS_INSTALL_DIR$ with the actual CAPS install directory
2. Locate the line that starts with 'netbeans_default_options=' and add the following option to the very end of the line and replace $CAPS_INSTALL_DIR$ with the actual CAPS install directory. Make sure this option is inside the closing double quote that is the last character of the line.

   --cp:p $CAPS_INSTALL_DIR$/.netbeans/caps/modules/com-stc-antlrimpl.jar
   

This instructs NetBeans to prepend the com-stc-antlrimpl.jar to the IDE's classpath so that the antlr classes supplied by this JAR file, which the B2B OTD libraries depend on, will take precedence over NetBean's default antlr.

6699303 NetBeans Throws SocketTimeOutException When Creating a Branch

Problem Summary Netbeans throws SocketTimeOutException when creating a Branch.

Workaround Increased the repository connection timeout from 15000 to 60000.

6700931 Username Token with Digest is not Supported

Problem Summary Users cannot open properties to test the password digest for the username token. Support for PasswordDigest style Username/Token is not fully integrated across NetBeans, WSIT and GlassFish security.

6702401 Mapping of Project Variables to Environment Constants is not Persistent from the Deployment Editor

Problem Summary Although it is possible to map Project variables to Environment constants, this binding is not preserved at the level of the deployment profile. There will be compilation errors at any place in code that references Project variables.

Workaround Project variables cannot be used to map to Environment constants. Convert Project variables to constants that are equivalent to Environment constants.

6704168 The "Copy" Menu Option Does not Work in HL7 OTD Library

Problem Summary The "copy" menu option does not work in the HL7 OTD Library.

Workaround Use the command line option of 'Control+C' or select the 'copy' icon from the tool bar.

6706429 User Must Restart Domain After Enabling Persistence for Alert Management

Problem Summary If the user enables persistence for alert management without restarting the domain, alerts that are generated into the persistence database do not reach the Enterprise Manager.

Workaround Restart the domain at least once after enabling persistence.

6706907 The Check Out Dialog Box Lacks Expected Functionality When Using Windows Vista

Problem Summary When checking out from the Environment or Logical Host on the Windows Vista platform, the 'select all,' 'None' buttons and the recurse check box are missing from the check out dialog.

Workaround User must manually select and check out components at the component level, not from the parent node.

6706921 6706921 env.sh does not set PATH on Unix

Problem Summary env.sh does not set PATH on Unix systems. User expects PATH=$ENGINE_HOME/bin:$JAVA_HOME/bine:$PATH. If the path is not set, samples and other excecutables are not available.

Workaround Manually set PATH on Unix systems.

6708514 Project with Imported WSDL Fails While Creating JCD on Red Hat Enterprise Linux 5

Problem Summary Java CAPS project with imported WSDL fails with the following exception while creating a new JCD on Red Hat Enterprise Linux 5:

SEVERE [com.stc.otd.fcw.jce.FogBeanProvider]: can't get root java type
java.io.IOException: Permission denied

Workaround None

Known Issues with Sun Composite Page Designer

6624231 Portlets do not Display Properly with the Mozilla/Firefox Browser

Problem Summary User generated a portlet for a project found in the tutorial. It operates when deployed on portal server in the application server web container (using a Solaris 10 x86 zone), but it does not render properly in Mozilla/Firefox.

Workaround The skew will be less visible if the portlet is 'thin' rather than 'thick.'

Known Issues with Sun Data Integrator

6681744 Import of eTL 51x Project by Means of Command Line Results in Exception

Problem Summary Importing an eTL 51x project by means of the command line results in an exception.

Workaround When importing 51x projects, the User must set NB_HOME, DB_DRIVERS_HOME, ETL_MIGRATION_CLASSPATH and DB_DRIVER_PATH variables as shown below. Exceptions still persist if the eTL collaborations contain database tables. There are no issues when flat files are used.

set NB_HOME=C:/JavaCAPS6/netbeans
set DB_DRIVERS_HOME=C:/JavaCAPS6/.netbeans/caps/modules/ext

set ETL_MIGRATION_CLASSPATH=%NB_HOME%/ide9/modules/org-netbeans-modules-project-ant.jar;
%NB_HOME%/ide9/modules/org-netbeans-modules-projectuiapi.jar;
%NB_HOME%/ide9/modules/org-netbeans-modules-projectapi.jar;
%NB_HOME%/platform8\lib\org-openide-util.jar;
%NB_HOME%/soa2/modules/org-netbeans-modules-etl-editor.jar;
%NB_HOME%/soa2/modules/org-netbeans-modules-etl-project.jar;
%NB_HOME%/platform8\modules\org-openide-dialogs.jar;
%NB_HOME%/platform8\core\org-openide-filesystems.jar;
%NB_HOME%/ide9/modules/org-netbeans-modules-db.jar;
%NB_HOME%/platform8\modules\org-openide-nodes.jar;
%NB_HOME%/platform8\modules\org-openide-text.jar;
%NB_HOME%/xml2\modules\org-netbeans-modules-xml-validation.jar;
%NB_HOME%/ide9\modules\org-netbeans-api-xml.jar;
%NB_HOME%/soa2\modules\org-netbeans-modules-soa-ui.jar;
%NB_HOME%/\platform8\modules\org-openide-loaders.jar;
%NB_HOME%/platform8\modules\org-openide-windows.jar;
%NB_HOME%/platform8\modules\org-openide-awt.jar;
%NB_HOME%/xml2\modules\org-netbeans-modules-xml-xam-ui.jar;%NB_HOME%/platform8\modules\org-openide-options.jar;

set DB_DRIVER_PATH=%DB_DRIVERS_HOME%/db2adapter/db2builder.jar;
%DB_DRIVERS_HOME%/stc/ewaycommon/com.stc.ewayrepositoryapi.jar;
%DB_DRIVERS_HOME%/../com-stc-bpms-common.jar;%DB_DRIVERS_HOME%/../com-stc-log4j.jar;
%DB_DRIVERS_HOME%/otd/com.stc.otd.fwbuildapi.jar;
%DB_DRIVERS_HOME%/stc/ewaycommon/com.stc.ewayutils.jar;
%DB_DRIVERS_HOME%\oracleadapter\oraclebuilder.jar;
%DB_DRIVERS_HOME%/sqlserveradapter/sqlserverbuilder.jar;
%DB_DRIVERS_HOME%/sybaseadapter/sybasebuilder.jar;

Workaround Restart the Repository, and rerun the import command.
Workaround Alternatively, import the project by means of the NetBeans GUI.

6694617 Imported eTL 51x Project with Fixed Width Tables Fails at Runtime

Problem Summary Importing eTL 51x projects with fixed width tables fails at runtime. Runtime test resulted in a java.sgl.SQLException.

Workaround If execution of the imported eTL project fails due to the exception 'java.sql.SQLException: LOADTYPE property required in organization clause,' then open the *.etl (collaboration) file and verify that the 'ORGPROP_LOADTYPE' attribute is listed for each flat file table that is used. If the ORGPROP_LOADTYPE attribute is missing, then manually add it and save, and then re-run the project.

<attr name="ORGPROP_LOADTYPE" type="java.lang.String" value="FIXEDWIDTH" />
<attr name="ORGPROP_LOADTYPE" type="java.lang.String" value="DELIMITED" />

6685093 Sun Data Integrator Application Configuration Does Not Meet Systemic Qualities Requirements

Problem Summary There are no interactions from the Sun Java Application Server administration console to the JBI sun-etl-engine properties.

6703351 Import of eTL 51x Project Results in org.axiondb.parser.ParseException at Runtime

Problem Summary Imported eTL 51x project. The eTL collaboration failed with exception at runtime.

[excerpted from server.log]
[#|2008-05-15T16:13:42.315-0700|SEVERE|sun-appserver9.1|com.sun.etl.engine.impl.InitTask|_ThreadID=80;
_ThreadName=INIT_0;_RequestID=e9232c23-3285-4776-aef1-b62688f66a63;
|java.sql.SQLException: org.axiondb.parser.ParseException: Parse error at line 1, column 472.  
Encountered: false - java.sql.SQLException: org.axiondb.parser.ParseException: Parse error at line 1, 
column 472.  Encountered: false
	at org.axiondb.util.ExceptionConverter.convert(ExceptionConverter.java:68)
	at org.axiondb.jdbc.BaseAxionStatement.parseCommand(BaseAxionStatement.java:165)
	at org.axiondb.jdbc.AxionStatement.executeUpdate(AxionStatement.java:143)
	at com.sun.etl.engine.impl.InitTask.doExecute(InitTask.java:234)
	at com.sun.etl.engine.impl.InitTask.execute(InitTask.java:304)
	at com.sun.etl.engine.impl.InitTask.process(InitTask.java:122)
	at com.sun.etl.engine.impl.ETLTaskThread.run(ETLTaskThread.java:161)
	at java.lang.Thread.run(Thread.java:595)
|#]

Workaround MashupDB does not understand when the TextQualifier property of the target table is set as a single quote ('). When the TextQualifier property is set to single quote, set the corresponding property to two single quotes, that is , ('').

6704176 Unable to Drag and Drop from Palette after Installing and Creating an eTL Collaboration

Problem Summary User unable to drag and drop from the Palette after installing and creating an eTL collaboration.

Workaround Save and close the eTL collaboration. When you reopen the eTL collaboration, the Palette works as expected.

6704221 'Truncate Before Load' Does not Work with Target Tables That Have User Defined Table Names

Problem Summary Truncate Before Load = true does not work when the 'User Defined Table Name' field is set on Database target tables. The table size doubles instead of truncating.

Workaround None.

6705843 Migrating 51x eTL Project Using eTLMigrationTool Fails to Build and Generate .ear File Using Command Line

Problem Summary While testing migration of an eTL 51x project sampleeInsightCSV510 using eTLMigrationTool, command line codegen fails to generate .ear file.

Workaround Use the NetBeans GUI for migration of eTL 51x projects.

6707522 A Change in the Value of sun-etl-engine in the Loggers Properties does not Change Log and Message Levels in the server.log

Problem Summary A change in the value of the sun-etl-engine in the Loggers Properties form INFO to FINEST does not Change Log and Message Levels in the server.log

Workaround None

6707599 Using AppConfig to Configure eTL Collaboration Does Not Successfully Execute at Runtime

Problem Summary When using AppConfig to configure an eTL collaboration that contains flat file tables to point to a different database or machine for runtime than for design time, the value of DATADIR does not fall back to AxiondbDataDirectory, the sun-etl-engine properties setting.

Workaround For successful execution at runtime, manually set the value of the path for DATADIR.

Known Issues with Sun Master Index

6700854 MIDM Cannot Compare Source Records from Two Different EUID Records

Problem Summary When comparing two EUID records, you can not compare source records from each EUID to see if they should be merged. To merge two LIDs, the user has to look for some source records to view, write down the system and the local ID number of the source records to compare, and then look them up on the Source Records Merge page.

Workaround Use EO Compare from the dashboard. Compare required EOs and click corresponding 'view sources' to compare source records from two different EUID records.

Note You still cannot view the source records from different EUIDs at the same time unless you know the system and local ID number. When using EO Compare, you have to toggle between the source records in one EUID and the source systems in the other EUID.

6710301 User With Newly Defined Role Cannot Log in to MIDM

Problem Summary When you create a new user role in midm-security.xml and create a new user profile with that role, the new user cannot log in to the MIDM.

Workaround After building the master index project containing the new user role, expand the master index *-war project > Web Pages > WEB-INF. Open web.xml, and add the new role to the role-name list in the auth-constraint element. Scroll to the security-role list and add the new role to the list. For example:

<auth-constraint>
   <role-name>Administrator</role-name>
   <role-name>MyNewRole</role-name>
...

<security-role>
    <role-name>MyNewRole</role-name>
...

Now open sun-web.xml, and add the new role to the security-role-mapping list. For example:

<security-role-mapping>
   <role-name>MyNewRole</role-name>
   <group-name>MyNewRole</group-name>
</security-role-mapping>

Known Issues with the JBI Bridge

6683017 Composite Application Project Failed to Deploy from JBI Bridge

Problem Summary A JCD called the JBI web service with the JBI Bridge. Both the repository-based project and the JBI project built successfully. However, the Composite Application project that contained the two projects successfully built but filed to deploy with the following error message:

ERROR:  Starting service assembly filed

Testing revealed that the Service Assembly (SA) deployment JMX call times out.

Workaround Manually start the SA using the JBI Manager.

6646537 JBI Bridge does not Work with Abstract WSDL

Problem Summary The build process for the JBI bridge works only if the WSDL used by an eInsight process contains the binding and service sections.

Workaround The User can edit the WSDL by using the modern WSDL editor to add the appropriate binding and then reimport the WSDL back to Classic.

6654477 Single-part input/output Literals are not Supported Between BPEL 1.0 and BPEL 2.0 Engines Across the JBI Bridge

Problem Summary Due to WS-I non-compliance in the Java EE Service Engine, single-part input/output literals are not supported between BPEL 1.0 and BPEL 2.0 engines across the JBI Bridge.

Workaround None

Known Issues with Sun Adapters

Known Issues with Communications Adapters

6702711 Open Environment Properties and CMP To Import and Build MSMQ Projects from Java CAPS 5.1.3 and Earlier

Problem Summary The MSMQ eWay implemented the connection pooling feature. Changes to the template and additional properties are added to the external system.

Workaround To import and build MSMQ projects from Java CAPS 5.1.3 and earlier, the user must open environment properties and CMP to build.

Known Issues with Database Adapters

6674397 The Database Table Locks if the Application Server Goes Down During the Middle of the XA Transaction

Problem Summary User imported the project and changed the settings to point to user's database. User than built and deployed the project. User started and stopped the application server in the middle of the transaction. The JCD threw an exception. User reconnected to Adapters with the database once the application server resumed. User executed a select query on the table using a SQL server client, but the table was locked, and the query did not return any results.

Workaround Restart the database to release the lock.

6697220 Problems Observed on Inbound Configuration for HTTP and PeopleSoft Adapters

Problem Summary There is no LDAP support for inbound configuration of HTTP, Siebel, and PeopleSoft Adapters.

Workaround None.

Known Issues with NetBeans 6.1

Using NetBeans Plugins

Java CAPS 6 is tested and certified to work with NetBeans plugins that are installed by the Java CAPS Installer. Installing any other NetBeans plugins or plugin updates to your NetBeans IDE can cause compatibility issues. This recommendation does not apply to plugins or updates that you get from Java CAPS Support.

When starting NetBeans IDE, you may be prompted to install updates for the third-party plugins in your IDE. Do
not install them.

To avoid being prompted in the future, please follow the instructions below:

1. Select 'Tools -> Plugins' from the NetBeans IDE menu bar.
2. In the 'Plugin' window, select the 'Settings' tab.
3. Make sure that only "CAPS Repository Update Center" is selected. Deselect any other Update Centers.
4. Select 'Close' to save your changes, and close the Plugin window.

If you wish to use other NetBeans plugins, backup the ".netbeans" directory, which can be found in the top level Java CAPS Install directory of your NetBeans installation. Alternatively, use a separate NetBeans installation to try other plugins that are not included with Java CAPS 6.

If you need to restore a backed up .netbeans directory, make sure that your NetBeans IDE isn't running. Then remove the current .netbeans directory and replace it with the backed up directory.

NetBeans IDE 6.1 Release Notes

The known issues with NetBeans 6.1 are located on the NetBeans.org website at NetBeans IDE 6.1 Release Notes

Known Issues with Sun Java System Application Server 9.1 Update 1-9.1 Update 2

6684658 h4. 6684658 The stcms Server stcms Server doe not Shutdown Properly when Sun Java System Application Server is run as a Windows Service

Problem Summary The stcms server doe not shutdown properly when Sun Java System Application Server is run as a Windows service. Even after stopping the service, stcms is still present in the Windows task manager.

Workaround If you install Java CAPS 6 on Windows, and you intend to run Java CAPS as a Windows service, then add the following line to domain.xml after installation:

<jvm-options>-Dcom.sun.enterprise.server.ss.ASQuickStartup=false</jvm-options>

6684658 The STCMS Server does not Shutdown Properly when Sun Java System Application Server is run as a Windows Service

Problem Summary The stcms server doe not shutdown properly when Sun Java System Application Server is run as a Windows service. Even after stopping the service, stcms is still present in the Windows task manager.

Workaround If you install Java CAPS 6 on Windows, and you intend to run Java CAPS as a Windows service, then add the following line to domain.xml after installation:

<jvm-options>-Dcom.sun.enterprise.server.ss.ASQuickStartup=false</jvm-options>

The known issues with Sun Java System Application Server 9.1 Update 1 and Update 2 are described in the Sun Java System Application Server 9.1 Update 1-9.1 Update 2 Release Notes, which is published with the Sun Java System Application Server 9.1 Update 1-9.1 Update 2 documentation collection on http:\\docs.sun.com.

Known Issues with JBI Components from Open ESB

Known Issues with Globalization (G11N)

6738600 Cannot create Logical Host with JDK 1.6 in NetBeans

Problem Summary Adding a logical host to an environment fails with XML error. "Element type "section" must be followed ...."

Workaround Install or find JDK 1.5 on the machine. Open netbeans\etc\netbeans.conf file in editor and specify JDK1.5 home for "netbeans_jdkhome=" line.

6665213 Multi-byte Chinese Characters are Garbled in Repository

Problem Summary Multi-byte Chinese characters display as questions marks in the Repository when the browser locale is 'zh-cn.' The page charset is incorrectly set to 'windows-1252.'

Workaround Use the Internet Explorer 7 browser for proper display of multi-byte Chinese characters.

6677837 Browser Crashes when Creating Connector Connection Pool on Solaris 10 with zh_TW Locale

Problem Summary Browser crashes when User tries to set up New Connector Connection Pool. This problem was limited to Solaris 10 with the zh_TW locale.

Workaround Access the application server administration URL from the Linux or Windows operating systems.

6714310 Chinese: The Java CAPS Components Library Does not Open by Default

Problem Summary The Java CAPS Components Library does not open by default when Java CAPS 6 is installed.

Workaround To open the Java CAPS Component Library, select 'Open Project' from the 'File' pull-down menu. Then select 'CAPS Component Library' from the default NetBeans folder.

6713494 Japanese: Sun Composite Page Designer Page Does Not Work

Problem Summary After creating a new page layout or importing an exisitng page layout
the page layout does not open. The error message specifies 'a project element was not specified, import could be
be executed,' followed by fatal null pointer exception. The same message occurs whether or not the page layout is imported or created new.

Workaround None

6712724 Chinese: User Cannot View XSD Definition

Problem Summary User cannot view XSD definition after creating it. User installed Java CAPS and created a new xsd definition. User created a listtype under 'XSDDefinition' User is unable to set 'ItemType' value in property list. After saving and restarting NetBeans, it is shadow and the User cannot view the xsd definition anymore.

Workaround None

Open ESB Issue 367 Cannot Show JBI Components with Status Condition in non-English Locale

Problem Summary The Administration Console does not show JBI Components with the status Condition in non-English kocales. If you select 'JBI Components" and 'Show All," the JBI components are displayed correctly.
However, if you select either the 'Started,' 'Stopped' or 'Shutdown' option, no components are shown.

Workaround None

Open JBI Components Issue 573 The BPEL Service Engine Configuration Tab has '???'Characters in the Configuration Tab

Problem Summary The BPEL Service Engine Configuration Tab displays '???' characters in the Chinese version. The ant script that creates the jbi_zh_CN.xml file from the translated properties files does not preserve the unicode escape characters.

Workaround None.

Documentation Issues

The documentation for Java CAPS 6 is available on the Sun Developer Network (SDN)at http://developers.sun.com/javacaps/ and on Sun's documentation website, http://docs.sun.com.

• Install Topics for Java CAPS 6
• Upgrade Topics for Java CAPS 6
• Design Topics for Java CAPS 6
• Configuration Topics for Java CAPS 6
• Deployment Topics for Java CAPS 6
• Monitor Topics for Java CAPS 6
• Administration Topics for Java CAPS 6
• Troubleshooting Topics for Java CAPS 6
• Java CAPS 6 Reference Collection