Stardust Release 3.0.0

Release 3.0.0 is a combined feature and maintenance release.

Supported Platforms

The following tables list all supported micro versions for:

Note
We do not expect any problems in all micro versions covered in the following tables of supported platforms, but we cannot strictly guarantee correct end-to-end system functionality in other platform versions than the Reference Test Platforms, as bugs in the platform code and problems introduced by combining different unforeseen micro-level versions of the different platform components could in rare cases introduce incorrect system behavior that is beyond our control. Refer to section Reference Test Platforms for a list of fine grained version information for our regression test platforms.

Supported Portal Platforms

The Stardust portals are currently supported on the following user agents:

User Agents Supported Versions
Internet Explorer (except Web Modeler and Rules Management perspectives) 9.0, 10, 11
Mozilla Firefox 34, 36 (note that future browser releases are not tested with Stardust yet and might cause issues)
Google Chrome 40, 41 (note that future browser releases are not tested with Stardust yet and might cause issues)

Supported Database Servers

The following database servers are currently supported by Stardust:

Server Supported Versions
Oracle 10g (deprecated), 11g R1 (11.1.0.6.0) (deprecated), 11g R2 (11.2.0.1.0), 12.1.1 (12c)
DB2 UDB 9.5, 9.7
Derby 10.9.1.0
MySQL 5.6
Sybase ASE 15.0
SQL Server 2008, 2012

Supported Application Servers

The following application servers are currently supported by Stardust:

Server Supported Versions
IBM WebSphere 7, 8 (8.0.0.5 or later)
Oracle WebLogic 10.3.3, 10.3.6, 12.1.2 (12c)
JBoss 7.1, EAP 6.2
Jakarta Tomcat 7

If you don't see your favorite database or application server in this list, please send a request to us. We continuously update the list of supported databases and application servers.

Supported Java Runtime

Vendor Supported Version
Oracle, Sun Java SE 6
Oracle JDK 7
IBM 32 Bit JRE 6.0 (together with WebSphere 7 / WebSphere 8)
Oracle JRockit 6 (together with Oracle 11g application server)

Other System Dependencies

Vendor Supported Version
Spring 3.2.4
Jackrabbit 2.6.1
Hazelcast 2.4

Reference Test Platforms

The following tables provide fine grained version information for our regression test platforms.

Reference Test Database Servers

The following database servers are currently tested as reference:

Server Supported Versions
Oracle 10.2.0, 11.2 R2
DB2 UDB 9.7.5
Derby 10.8.2.2
MySQL 5.1.59
Sybase ASE 15.7
SQL Server 2012

Reference Test Application Servers

The following application servers are currently tested as reference:

Server Supported Versions
IBM WebSphere 7.0.0.21, 8.0.0.3
Oracle WebLogic 10.3.3, 10.3.6, 12.1.1
JBoss 7.1.1, EAP 6.2
Jakarta Tomcat 7.0.41, 7.0.50, 7.0.54

New Features and Improvements

The following new features and bug fixes have been introduced with this release:

Portal Enhancements

The following Portal enhancements are available in this release:

Business Process Modeler Preview Functionality

The following functionality of the Business Process Modeler has been introduced as or is still customer technology preview only. Note that these previews may not be functionally complete and are not intended for production use.

The Stardust Portal provides a configuration switch to show or hide features that are provided as technology preview.

New Features and Bug Fixes

The following main features and bug fixes have been introduced with this release:

Bug-ID Description
Bug 468462 Update documentation for renamed Tomcat archetype.
Bug 468259 Change Default Portal Skin to modern Style
Bug 468256 Browser Modeler Enhancements
Bug 468255 Reporting Enhancements
Bug 468246 Correct the documentation link for "Creating a Stardust Runtime Environment with Apache Maven"
Bug 466522 Update example model versions to 3.0.0
Bug 453879 Shrink the available features in the Install Software dialog
Bug 450456 Continuous update of build scripts for Mars builds.
Bug 450452 Upgrade Stardust to 3.0.0 - Adjust facet version
Bug 444790 Provide support for MySQL database server versions 5.6 (drop support for 5.0,5.1)
Bug 417891 Archetype tc6-ipp-portal-war should be renamed to tc7-stardust-portal-war
Bug 409365 New model creation wizard wrong name and place
Bug 409362 Last dialog of "New CarnotWorkflowModel" is not closed
Bug 404991 HTTP Status 500, Portal - Process-Details View of process instance without starting user

Stardust API Changes

Deprecated API

The following API methods are deprecated:

API Changes

The following API changes have been performed with this release:

New interface Transition

A new interface Transition is introduced to provide workflow transition information like Id, source activity Id, target activity Id, condition and condition type.

New methods introduced for ProcessDefinition

The ProcessDefinition API is extended with the following methods to provide transition information:

Please refer to chapter Retrieving Transition Information in the Programming Guide for details.

Enhancements of class Activity

Class Activity is enhanced with gateway type information by the following methods and enum type:

Please refer to chapter Retrieving the Gateway Type of an Activity in the Programming Guide for details.

DocumentManagementService changes

To improve performance, now only DocumentManagementService calls that directly create or retrieve a document version are returning revisionId, revisionName and versionLabels. All other methods are returning no version labels and the revision id and revision name as org.eclipse.stardust.engine.core.spi.dms.RepositoryConstants.VERSION_VERSIONED = "VERSIONED", if the document has versions available.

Please refer to chapter Managing Documents and Folders in the Programming Guide for details.

RuntimeEnvironmentInformation object provides additional information

The RuntimeEnvironmentInfo object is enhanced with the following methods to provide additional information like timestamp of the last target archive time, audit trail UUID and name:

Method Return Value Parameter
getLastArchivingTime Long -
getAuditTrailUUID String -
getAuditTrailName String -

Deprecated Functionality

The XML Data type integration is deprecated and will not be provided in the Eclipse modeler in future releases. You can use the External Reference structured data type instead, which is equivalent to the XML Data type, with the difference that it supports XSD schema exclusively (no DTD specification). Please refer to section Using External XSD Types of chapter Defining Structured Types for details.

Upgrading from a Previous Release

This section covers upgrading necessary for upgrading from releases earlier than 5.0.0.

Breaking Changes

The following breaking changes have been introduced with version 5.0.0:

Default Portal Skin has changed to modern Style

The default skin for the Portal has changed to the modern skin. Please note that the screenshots provided in the documentation still show the old skin and will be adjusted in future releases.

Dropped Platforms and Platform Versions

The support for the following platforms or platform versions has been dropped with this release:

Newly supported Platforms

The following platform versions are supported since this release:

Known Issues and Restrictions with this Release

For general known issues and restrictions, please refer to the Troubleshooting section in the online documentation.

Known Issues

Cross Modeling: Renaming an imported Structured Data from a referenced Model causes Issues

Renaming an imported structured data from a referenced model in a cross-model scenario might lead to inconsistent behavior.

M2Eclipse - Missing HttpServlet class error occurs after creating a new Maven project based on archetypes

After creating a new project based on archetypes, a missing HttpServlet class error is displayed in the Problems view due to an issue with the m2e-wtp Eclipse plugin. The plugin enables the JavaServer Faces project facet, because it identifies JSF dependencies, and thus also applies additional files to the project. To avoid this issue, deselect the JSF Configurator option in the Maven preferences as described in section Deselecting the JSF Configurator option to avoid Missing HttpServlet class error of chapter Creating a Stardust Runtime Environment with Apache Maven.

JBoss 7.1 - javax.ws.rs.NotFoundException is thrown on server start-up

In case you get a java.lang.NoClassDefFoundError: javax.ws.rs.NotFoundException during server start-up with JBoss 7.1, make sure to upgrade the shipped RESTEasy stack to version 3.x. Upgrading to the new RESTEasy stack version prevents that the Stardust jax-rs 2.0 is overwritten by the JBoss 1.0 jax-rs API during deployment, which otherwise happens due to issue https://issues.jboss.org/browse/WFLY-1304.

Exception occurs during a JBoss Deployment with MySQL version 5.6

The MySQL 5.6 installation comes with the MySql Connector/J in version 5.1.34. If you deploy this JAR into JBoss as a module and include it in the standalone.xml file, you are facing a DuplicateServiceException.

This is a known issue for JBoss versions earlier than 8 (Module for MySQL JDBC driver with version 5.1.30+ needs <driver-class> in standalone.xml). As a workaround you can define a specific driver-class in the standalone.xml in the driver section as follows:

   <driver name="mysql" module="com.mysql">
      <driver-class>com.mysql.jdbc.Driver</driver-class>
      <xa-datasource-class>com.mysql.jdbc.jdbc2.optional.MysqlXADataSource</xa-datasource-class>
   </driver>
   

For details please refer to section Restrictions for a Deployment with MySQL Version 5.6 in the JBoss chapter of the Deployment Guide.

No Exception is thrown by modifyUser method when executed in mixed mode

If the modifyUser API is invoked in mixed mode (external and internal Authentication) to change the password and user information of an existing user, no Exception is thrown. The user information remains unchanged even though a successful response is provided.

Portal - Exception occurs when expanding a repository folder with a large number of child nodes in a JBoss environment

If you expand a repository folder having a number of child nodes that exceeds a maximum number of about 500 and you are using a JBoss server, the following Exception might occur:

JBWEB000065: HTTP Status 500 - JBWEB002004: More than the maximum number of request parameters (GET plus POST) for a single request (512) 
   were detected. Any parameters beyond this limit have been ignored. To change this limit, set the maxParameterCount attribute 
   on the Connector.

To resolve this issue, add the following property to your JBoss configuration:

<system-properties>
   <property name="org.apache.tomcat.util.http.Parameters.MAX_COUNT" value="1000"/> 
</system-properties>

WebLogic 11g - client side error occurs when deploying a process model from Console command

A client side error occurs in case you deploy a process model from the Console command in an EJB with DB2 environment.

To resolve this problem, set the following system property:

-Djavax.xml.stream.XMLInputFactory="com.ctc.wstx.stax.WstxInputFactory"

This forces to use the shipped woodstox implementation wstx-asl-3.2.8.jar.

Issues with modern skin

The modern skin has the following issues in Mozilla FireFox or Google Chrome:

Known Restrictions

Known Restriction in the Business Process Modeler

For a list of all known restrictions in the Business Process Modeler, please refer to section Restrictions in Modeler Functionality of chapter Compatibility and Analogy of Models.

Testing a Rule Set implementation

Note that you need a lifecycle management environment to be able to run and test a Rule Task implementing a Rule Set. Please contact our Sales Support Team for details.

Technical Rules editor code restriction

For the time being, you need to append _field to each variable in the code editor of a technical rule in the Rules Management perspective. Refer to chapter Defining Technical Rules for details.

UI Mashup application restrictions

UI Mashup applications have the following restrictions:

Limitations with JBoss 7.1

The following modifications need to be applied in the JBoss 7.1 server:

Due to an issue, the JBoss default JSF implementation cannot be changed as parameter WAR_BUNDLES_JSF_IMPL is not working in JBoss 7.1.1. (WAR file using WAR_BUNDLES_JSF_IMPL embedded in an EAR file fails deployment). This is caused by the issue: JSF Version retrieved from deployment unit instead of top level deployment unit.

As a workaround, in com/sun/jsf-impl/main module in jsf-impl-2.1.7-jbossorg-2.jar/META-INF: the .tld files have to be renamed to e.g. *-tmp.tld.

Limitations with JBoss 7.1 for EJB3 Deployment

While deploying JBoss 7.1 for EJB 3, the following exception may occur: org.jboss.msc.service.ServiceNotFoundException: Service service jboss.ejb.default-resource-adapter-name-service not found

For a successful deployment, add the following under <subsystem xmlns="urn:jboss:Domain:ejb3:1.4"> in the standalone.xml file.

<mdb>
   <resource-adapter-ref resource-adapter-name="hornetq-ra"/>
   <bean-instance-pool-ref pool-name="mdb-strict-max-pool"/>
</mdb>

Upgrading from a Previous Release

A runtime upgrade is not required for this release. For other upgrading issues introduced with earlier releases, please refer to chapter Upgrading to Later Versions. You will find all upgrading steps necessary for your specific version.

Previous Releases