Release 3.0.0 is a combined feature and maintenance release.
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.
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) |
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 |
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.
| 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) |
| Vendor | Supported Version |
|---|---|
| Spring | 3.2.4 |
| Jackrabbit | 2.6.1 |
| Hazelcast | 2.4 |
The following tables provide fine grained version information for our regression test platforms.
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 |
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 |
The following new features and bug fixes have been introduced with this release:
The following Portal enhancements are available in this release:
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.
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 |
The following API methods are deprecated:
| Method | Return Value | Parameter |
|---|---|---|
| getModel | DeployedModel | - |
AdministrationService
| Method | Return Value | Parameter |
|---|---|---|
| deployModel | DeploymentInfo | String model, int predecessorOID |
| overwriteModel | DeploymentInfo | String model, int modelOid |
| deployModel | DeploymentInfo | String model, String configuration, int predecessorOID, Date validFrom, Date validTo, String comment, boolean disabled, boolean ignoreWarning |
| overwriteModel | DeploymentInfo | String configuration, int modelOID, Date validFrom, Date validTo, String comment, boolean disabled, boolean ignoreWarnings |
QueryService
| Method | Return Value | Parameter |
|---|---|---|
| getAllModelDescriptions | List<DeployedModelDescription> | - |
| getAllAliveModelDescriptions | List<DeployedModelDescription> | - |
| getActiveModelDescription | DeployedModelDescription | - |
| getActiveModel | DeployedModel | - |
| findFirstDocument | Document | DocumentQuery query |
| getAllDocuments | Documents | DocumentQuery query |
UserService
| Method | Return Value | Parameter |
|---|---|---|
| isInternalAuthentified | boolean | - |
| invalidate | User | String account |
DocumentManagementService
| Method | Return Value | Parameter |
|---|---|---|
| versionDocument | Document | String documentId, String versionLabel |
| updateDocument | Document | Document document, boolean createNewRevision, String versionLabel, boolean keepLocked |
| updateDocument | Document | Document document, byte[] content, String encoding, boolean createNewRevision, String versionLabel, boolean keepLocked |
| findDocumentsByName | List<Document> | String namePattern |
| findDocuments | List<Document> | String xpathQuery |
Activity
| Method | Return Value | Parameter |
|---|---|---|
| getDefaultPerformerID | String | - |
| getDefaultPerformerName | String | - |
AttributeOrder
| Method | Return Value | Parameter |
|---|---|---|
| getAttribute | String | - |
DmsPrincipal
| Method | Return Value | Parameter |
|---|---|---|
| DmsPrincipal | constructor | String name |
ExternalUserConfiguration
| Method | Return Value | Parameter |
|---|---|---|
| getGrantedModelParticipants | Collection | - |
HistoricalState
| Method | Return Value | Parameter |
|---|---|---|
| getPerfomer | Participant | - |
| getOnBehalfOf | Participant | - |
LoginProvider - Interface is deprecated
Note
| Method | Return Value | Parameter |
|---|---|---|
| getUserOid | long | - |
Participant
| Method | Return Value | Parameter |
|---|---|---|
| getPartitionOID | short | - |
| getPartitionId | String | - |
| getModelOID | int | - |
| getElementOID | int | - |
| getAllSuperOrganizations | List | - |
| getNamespace | String | - |
ParticipantAssociationFilter
| Method | Return Value | Parameter |
|---|---|---|
| forModelParticipant | ParticipantAssociationFilter | String participantID |
| forModelParticipant | ParticipantAssociationFilter | String participantID, boolean recursively |
| inUserGroup | ParticipantAssociationFilter | String groupID |
| forUser | ParticipantAssociationFilter | String account |
| forTeamLeader | ParticipantAssociationFilter | String roleId |
PerformingInBehalfOfFilter
| Method | Return Value | Parameter |
|---|---|---|
| forModelParticpants | PerformingOnBehalfOfFilter | Set<String> participantIDs |
| forModelParticpant | PerformingOnBehalfOfFilter | String participantID, boolean recursively |
| forModelParticpant | PerformingOnBehalfOfFilter | String participantID |
| forUserGroup | PerformingOnBehalfOfFilter | String groupID |
PerformingParticipantFilter
| Method | Return Value | Parameter |
|---|---|---|
| USER_ROLES_AND_ORGANIZATIONS | static field | - |
| forModelParticipant | PerformingParticipantFilter | String participantID |
| forModelParticipant | PerformingParticipantFilter | String participantID, boolean recursively |
| forUserGroup | PerformingParticipantFilter | String groupID |
| PerformingParticipantFilter | constructor | String participantID |
| PerformingParticipantFilter | constructor | String participantID, boolean recursively |
| PerformingParticipantFilter | constructor(private) | Kind filterKind, final String participantID, boolean recursively |
ProcessInstanceQuery
| Method | Return Value | Parameter |
|---|---|---|
| STARTING_DOMAIN_OID | static field | - |
| CURRENT_DOMAIN_OID | static field | - |
UnsupportedFilterException
| Method | Return Value | Parameter |
|---|---|---|
| UnsupportedFilterException | constructor | String message |
| UnsupportedFilterException | constructor | String message, FilterCriterion filter |
User
| Method | Return Value | Parameter |
|---|---|---|
| getRealmOID | long | - |
| getRealmID | String | - |
| addGrant | void | String id |
| removeGrant | void | String id |
WorkflowExceptiom
| Method | Return Value | Parameter |
|---|---|---|
| getRootCause | PublicException | - |
The following API changes have been performed with this release:
A new interface Transition is introduced to provide workflow transition information like Id, source activity Id, target activity Id, condition and condition type.
The ProcessDefinition API is extended with the following methods to provide transition information:
List<Transition> getAllTransitions(); - gets all transitions defined for this process definitionList<Transition> getIncomingTransitions(Activity activity); - returns the list of all transitions having as target the specified activityList<Transition> getOutgoingTransitions(Activity activity); - returns the list of all transitions having as source the specified activityTransition getTransition(String transitionId); - gets the specified transitionActivity getSourceActivity(Transition transition); - gets the source activity for the specified transitionActivity getTargetActivity(Transition transition); - gets the target activity for the specified transitionPlease refer to chapter Retrieving Transition Information in the Programming Guide for details.
Class Activity is enhanced with gateway type information by the following methods and enum type:
enum GatewayType - enumeration for gateway types (AND, OR, XOR)GatewayType getJoinType(); - gets the flow join type for this activityGatewayType getSplitType(); - gets the flow split type for this activityPlease refer to chapter Retrieving the Gateway Type of an Activity in the Programming Guide for details.
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.
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 | - |
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.
This section covers upgrading necessary for upgrading from releases earlier than 5.0.0.
The following breaking changes have been introduced with version 5.0.0:
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.
The support for the following platforms or platform versions has been dropped with this release:
The following platform versions are supported since this release:
For general known issues and restrictions, please refer to the Troubleshooting section in the online documentation.
Renaming an imported structured data from a referenced model in a cross-model scenario might lead to inconsistent behavior.
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.
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.
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.
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.
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>
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.
The modern skin has the following issues in Mozilla FireFox or Google Chrome:
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.
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.
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 applications have the following restrictions:
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.
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>
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.