Red Hat Training

A Red Hat training course is available for Red Hat JBoss Developer Studio

8.0.0 Release Notes

Red Hat JBoss Developer Studio Integration Stack 8.0

Information about this release of JBoss Developer Studio Integration Stack

Red Hat Customer Content Services

Abstract

These release notes contain important information related to JBoss Developer Studio Integration Stack. New features and resolved issues of this product release are detailed here.

1. About Red Hat JBoss Developer Studio Integration Stack

Red Hat JBoss Developer Studio Integration Stack is a set of Eclipse-based development tools. It further enhances the IDE functionality provided by JBoss Developer Studio, with plug-ins specifically for use when developing for other Red Hat JBoss products.
JBoss Fuse Development plug-ins provide tooling for Red Hat JBoss Fuse, specifically for integrating and developing software components that work with Apache ServiceMix, ActiveMQ and Camel.
JBoss Business Process and Rules Development plug-ins provides design, debug and testing tooling for developing business processes for Red Hat JBoss BRMS and Red Hat JBoss BPM Suite. For more information, see the Red Hat JBoss BRMS Getting Started Guide and Red Hat JBoss BPM Suite Getting Started Guide.
JBoss Data Virtualization Development plug-ins provide a graphical interface to manage various aspects of Red Hat JBoss Data Virtualization instances, including the ability to design virtual databases and interact with associated governance repositories. For more information, see the Red Hat JBoss Data Virtualization User Guide.
JBoss Integration and SOA Development plug-ins provide tooling for developing, configuring and deploying SwitchYard and Fuse applications to Red Hat JBoss Fuse Service Works, Red Hat JBoss Fuse and Fuse Fabric containers, Apache ServiceMix, and Apache Karaf instances. For more information, see the Red Hat JBoss Fuse Service Works User Guide, Red Hat JBoss Fuse Tooling User Guide and Red Hat JBoss Fuse Tooling Tutorials.
JBoss Developer Studio Integration Stack and JBoss Developer Studio are released asynchronously and current information on each of the JBoss Developer Studio Integration Stack components can be found in the associated Red Hat JBoss product documentation. The documentation is available from https://access.redhat.com/site/documentation/ on the Red Hat Customer Portal.

2. About this Release

JBoss Developer Studio Integration Stack 8.0.0 is an upgrade of JBoss Developer Studio Integration Stack 7. The upgrade has three purposes:
  • It supports Eclipse Luna (4.4).
  • It contains new features and fixes for the following released components:
    • ModeShape 3.7.0.Final
    • Teiid Designer 9.0.1.Final
  • It contains new features and fixes for the following JBoss Developer Studio Integration Stack 8.0.0 components released as Early Access:
    • BPEL 1.3.100
    • BPMN2 Modeler 1.1.1
    • Fuse Tooling 7.3.0.Beta2
    • SwitchYard 2.0.0.Beta1

    Important

    Components of JBoss Developer Studio Integration Stack that are still under development and released as Early Access may not be immediately visible in the Software/Update tab under JBoss Developer Studio Integration Stack. To list early access components, in the Software/Update tab click the Enable Early Access check box and review the Early Access Features declaration.
For a complete list of components in this release, together with information about operating systems, chip architectures and Java developer kits supported by this release, see https://access.redhat.com/articles/1351903 on the Red Hat Customer Portal.

3. JBDS-IS 8.0.0

  • JBTIS-241: JBDSIS 7.0.0 fails to install Teiid, Designer, Client into JBDS 8.0.0.alpha
  • JBTIS-245: Please update JBTIS TP dependencies to Luna Alpha1
  • JBTIS-292: Karaf cannot be started in debug
  • JBTIS-293: Fuse tooling Luna build fails at runtime - Framework Event error - javax.xml.bind.annotation.adapters
  • JBTIS-294: JBTIS build fails because SwitchYard is not compatible with EMF Compare 3.0
  • JBTIS-312: Generate source bundles for IS component features.
  • JBTIS-322: Missing dependency for teiid JBDSIS 8.0.0
  • JBTIS-333: Mirror BPMN2 Modeler 1.1.1 and update JBTIS TP/ JBTIS composites
  • JBTIS-353: Save progress is stopped in JBDS BPMN Tooling
  • JBTIS-361: JBDS IS 8 Beta1 features not showing up in EA view
  • JBTIS-369: Update jbosstools bpel to include newer eclipse bpel and include in IS
  • JBTIS-378: Update bpmn2 for IS beta2 TP and aggregate - bpmn2 feature source bundle
  • JBTIS-381: Update JDV components for JBDSIS 8.0.0.GA/ 4.2.0.Final

4. BPEL 1.3.100

Important

This component is released as Early Access and it is still under development. You are encouraged to use the features of this component and to give feedback but be aware that the features are not fully supported, not guaranteed to work correctly, and subject to removal at any time, for any reason.
  • Bug 404117: Cannot set date (deadline expression) in Wait and OnAlarm

5. BPMN2 Modeler 1.1.1

Important

This component is released as Early Access and it is still under development. You are encouraged to use the features of this component and to give feedback but be aware that the features are not fully supported, not guaranteed to work correctly, and subject to removal at any time, for any reason.
  • Bug 417015: Missing 'drools' expression language for conditions.
  • Bug 417654: Element selection should not be reset when switching back from source.
  • Bug 425689: Multiple outgoing sequence flows of a task.
  • Bug 427470: Refactor validation classes to allow Target Runtimes to override specific BPMN 2.0 core constraints.
  • Bug 432046: Unclear how to set AdHocSubProcess completion condition. Hide Sub Process property tab for AdHoc Sub Process.
  • Bug 435763: IReconnectionFeature don't work with custom links.
  • Bug 439149: Tab switching between Process and SubProcess diagrams causes incorrect diagram to be drawn.
  • Bug 439929: Problems with importing WSDL that contains embedded XSD
  • Bug 440827: Unable to remove participant process (whitebox)
  • Bug 441057: Exception while creating connection form node to another connection
  • Bug 442752: Connecting two elements from Palette with Sequence flow
  • Bug 442789: Unable to set Message for Rceive Task
  • Bug 443072: Strange behavior of 'Append *' context menu
  • Bug 443140: Source for catch Link Events should be automatically configured
  • Bug 443173: In Condition Expression editor, "Condition Language" field doesn't show previously set value
  • Bug 444257: Validation of 'Data Object' connected to 'Script Task'
  • Bug 444373: Missing attribute StandardLoopCharacteristics in Preferences
  • Bug 445017: Regression: Tool Profile selection no longer works
  • Bug 445139: jBPM Simulation Parameters are not saved
  • Bug 445230: Appearance preferences not persisted between sessions
  • Bug 446154: Unable to set onEntry/onExit script for embedded AdHocSubprocess
  • Bug 446156: Non jbpm options present in the editor when jbpm runtime is selected
  • Bug 447659: Unable to delete Input Data Mapping of User Task
  • Bug 448073: Unable add more imports to *.bpmn2 model
  • Bug 448573: Error during adding element 'Lane' from category 'Swimlanes'.
  • Bug 448947: Modeler generates wrong xml after adding local process variable
  • Bug 450826: Wrong validation of Event Sub-Process.
  • RH Bug 1113139: Special characters are not allowed in the Task GroupID
  • RH Bug 1139130: Signal "ID" should be renamed in the eclipse BPMN designer in the same way as web designer
  • RH Bug 1144961: "Script language" for Actors and I/O Parameters
  • RH Bug 1146739: save progress is stopped
  • RH Bug 1147940: Incorrect validation of Ad Hoc process.
  • RH Bug 1149515: Bpmn2 Diagram Editor which comes with JBDS Integration Stack does not provide facility of writing On Entry / On Exit scripts for custom service tasks
  • RH Bug 1150060: Don't use targetNamespace prefixes for BPMN2 object ID references
  • RH Bug 1150074: Add logic to properly display Start Events "Is Interrupting" and Boundary Events "Cancel Activity" attributes.
  • RH Bug 1155707: changed name of DataOutput for CatchEvents, and DataInput for ThrowEvents to "event".
  • RH Bug 1168846: change "Called Activity" label to "Called Element".
  • RH Bug 1172177: Business Rule Task should support I/O Parameter mapping
  • RH Bug 1173140: Process id is not modifiable (for jBPM plugin only)
  • RH Bug SWITCHYARD-2484: SY Service Task generates wrong data input references
  • JBTIS Bug 332: update poms to generate source bundles

6. Fuse Tooling 7.3.0

Important

This component is released as Early Access and it is still under development. You are encouraged to use the features of this component and to give feedback but be aware that the features are not fully supported, not guaranteed to work correctly, and subject to removal at any time, for any reason.

7. SwitchYard 2.0.0

Important

This component is released as Early Access and it is still under development. You are encouraged to use the features of this component and to give feedback but be aware that the features are not fully supported, not guaranteed to work correctly, and subject to removal at any time, for any reason.
  • SWITCHYARD-1655: SwitchYard->Configure Capabilities menu makes additional changes to pom for SY project
  • SWITCHYARD-1733: FTP, SFTP, FTPS binding pages need revamp to break up huge tab
  • SWITCHYARD-1770: Visual editor not closed when project deleted
  • SWITCHYARD-1835: Period attribute is mandatory for SQL service bindings
  • SWITCHYARD-1848: Missing scrollbars in new binding dialogs
  • SWITCHYARD-1851: Duplicate transformers showing up in soap-addressing quickstart
  • SWITCHYARD-1855: Editing ESB interface removes service name
  • SWITCHYARD-1862: Mark JNDI Name as required in JCA binding for reference
  • SWITCHYARD-1873: Cannot set start and end time in quartz binding
  • SWITCHYARD-1893: Maven plugin creates empty switchyard.xml after upgrading of configuration version
  • SWITCHYARD-1910: Error marker on component reference when using ReferenceInvoker
  • SWITCHYARD-1922: It is impossible to change route implementation in Properties view
  • SWITCHYARD-1924: Unify link behaviour in Properties view
  • SWITCHYARD-1942: A typo in "New SwitchYard Project" wizard of SwitchYard tooling
  • SWITCHYARD-1944: Server port field in SOAP binding wizard a bit too eager with ":"
  • SWITCHYARD-1947: Renaming of a component by F2 requires mouse over the component label
  • SWITCHYARD-1948: Component service/reference Security Policy is not updated correctly in Properties View
  • SWITCHYARD-1949: Allow user to edit property name
  • SWITCHYARD-1975: The attribute schemaType is not written to switchyard.xml for DTD validation
  • SWITCHYARD-1988: Background of Properties dialog repeats on y-axis in Rules and BPMN implementation
  • SWITCHYARD-2008: NLS unused message
  • SWITCHYARD-2046: Switchyard project errors after restarting JBDS
  • SWITCHYARD-2090: Lack of binding name in editor should not be an error
  • SWITCHYARD-2120: Java facet sticks at 1.6 despite workbench settings
  • SWITCHYARD-2123: It is impossible to change BPEL File
  • SWITCHYARD-2125: SwitchYard Debugger - not triggering breakpoints on bean-service quickstart unit tests
  • SWITCHYARD-2126: Debugger raises NullPointerException
  • SWITCHYARD-2127: Debugger type checkboxes do not function - results in error
  • SWITCHYARD-2153: Please ensure Tooling provides security-compatible switchyard.xml
  • SWITCHYARD-2168: SAP binding ui clean-up
  • SWITCHYARD-2173: Mail binding account type not saved by mail binding wizard if imap
  • SWITCHYARD-2174: Tooling refers to non-existent pom property for bundled projects
  • SWITCHYARD-2176: Tooling generates features.xml with wrong repository URL
  • SWITCHYARD-2191: Swapping implementations is broken for Camel routes
  • SWITCHYARD-2195: SOAP Binding: Server Port field no longer manages colon properly
  • SWITCHYARD-2197: Camel JMS binding not setting connection factory field to default when created
  • SWITCHYARD-2207: Variable names and values are blank during debugging
  • SWITCHYARD-2210: Advanced property table for bindings doesn't support nested properties
  • SWITCHYARD-2242: NPE when adding an item to Globals, Inputs, Outputs, Faults for an unnamed operation
  • SWITCHYARD-2247: Wrong Resource Adapter Type is displayed if generic resource adapter is used on inbound JCA
  • SWITCHYARD-2249: Changing of Resource Adapter Type to Generic RA causes configuration loss
  • SWITCHYARD-2250: JMS Processor Properties are not refreshed
  • SWITCHYARD-2253: SwitchYard Tooling doesn't accept WildFly 8.x as Target Runtime
  • SWITCHYARD-2257: SOAP Binding - Headers Type not defaulting to VALUE
  • SWITCHYARD-2271: SwitchYard validadator does not detect dozer transformation in model
  • SWITCHYARD-2274: It is not possible to configure jndiName for outbound JCA
  • SWITCHYARD-2291: "WSDL file from Java" does not work when project is not built
  • SWITCHYARD-2301: New project wizard add superfluous property to pom.xml
  • SWITCHYARD-2303: New project wizard needs to add property/plugin config for DynamicImport-Package
  • SWITCHYARD-2310: WSDL generation failed with 2.0.0.Alpha2
  • SWITCHYARD-2322: Problems with Camel component validator in tooling
  • SWITCHYARD-2337: NPE when closing SY editor
  • SWITCHYARD-2341: Broken layout of File, FTP, FTPS, SFTP bindings
  • SWITCHYARD-2364: Validation breakpoint fails on resume in SwitchYard Debugger
  • SWITCHYARD-2366: Tooling tests fail because of missing lifecycle mappings
  • SWITCHYARD-2380: Generated project POM errors on issue with switchyard-plugin with BOM dependencies
  • SWITCHYARD-2386: "Java files from wsdl" not working
  • SWITCHYARD-2387: Some corrections for Camel, MQTT, SAP
  • SWITCHYARD-2389: Tools should generate an error when library version is incompatible with config version
  • SWITCHYARD-2390: Use BOM checkbox enablement does not update when using target runtimes
  • SWITCHYARD-2405: Directory should be optional in FTP/SFTP/FTPS
  • SWITCHYARD-2411: Errors in bundle projects created by tooling
  • SWITCHYARD-2423: Additional URI parameters are not refreshed in Properties view
  • SWITCHYARD-2426: Broken layout in CXF binding
  • SWITCHYARD-2430: Empty Host URI in MQTT causes xsi:nil="true"
  • SWITCHYARD-2437: Using SwitchYard BOM dependency is disabled by default
  • SWITCHYARD-2439: Transform debugging throws a conditional breakpoint error
  • SWITCHYARD-2440: Exception in error log when editing time in quartz, atom and rss binding
  • SWITCHYARD-2453: JCA binding doubles some properties
  • SWITCHYARD-2454: JMS binding complains about missing queue name even if topic is set
  • SWITCHYARD-2457: SOAP Binding: exceptions in error log when editing threshold
  • SWITCHYARD-2483: Cannot add an existing Camel implementation
  • SWITCHYARD-2485: NPE when you delete library version in project creation wizard
  • SWITCHYARD-2486: SwitchYard Context View not showing logical content

8. Teiid Designer 9.0.1

  • TEIIDDES-1037: Data types inported from flat file partially implemented in wizard
  • TEIIDDES-2022: UDF Jar Path deleted from Create User Defined Function dialog
  • TEIIDDES-2125: REST procedures created in designer prior to version 8, don't transfer the properties
  • TEIIDDES-2165: User can not use '.' for VDB name in order to version the VDB
  • TEIIDDES-2174: Hard Coded teiid jdbc server port 31000
  • TEIIDDES-2213: JDBC Importer with PostgreSQL function that returns table imports parameters incorrectly
  • TEIIDDES-2224: web service returns 500 when concurrent access
  • TEIIDDES-2230: Update 8.6.x Designer branch to build Teiid 8.7 version client from Teiid 8.7.x branch
  • TEIIDDES-2285: Unable to scroll wizard window when creating web service war
  • TEIIDDES-2299: LDAP import dialog very slow
  • TEIIDDES-2306: Unable to change constant data type in Expression Builder
  • TEIIDDES-2324: Rest Importer: Use invokeHTTP procedure with Named Parameters
  • TEIIDDES-2331: Issues with renaming Source Model (8.3.4.CR1 and 8.6.0 + Windows 7)
  • TEIIDDES-2341: Starting server does not result in full Teiid connection requiring Refresh action
  • TEIIDDES-2344: Empty error message in insert procedure transformation
  • TEIIDDES-2345: Using VARIABLES.ROWCOUNT in update procedure causes validation error
  • TEIIDDES-2348: Ctrl+v in Transformation editor pastes twice
  • TEIIDDES-2349: Changes to project imported from zip cached even after deleting and reimporting
  • TEIIDDES-2359: Teiid Designer sends header-accept="application/xml" when trying to import from REST JSON
  • TEIIDDES-2376: On windows environment, renamig a source model file's name using JBDS will broke a view model which uses the renamed source model
  • TEIIDDES-2379: A view should not be allowed to set the materialization target to itself
  • TEIIDDES-2380: New Model Wizard doesn't copy view model with global temporary table properly
  • TEIIDDES-2383: Transformation editor removes cache hint in SQL
  • TEIIDDES-2385: Error when generating SOAP WAR with WS-Security
  • TEIIDDES-2386: Missing menu items for transformation editor
  • TEIIDDES-2387: Weird behaviour when creating parameters for procedure
  • TEIIDDES-2391: IllegalArgumentException when trying to edit expression using Expression Builder
  • TEIIDDES-2392: Don't allow override name to be the same name as existing translator name
  • TEIIDDES-2396: Renaming a source model does not fullly update import statements to view models
  • TEIIDDES-2400: NPE creating a structural copy of a source model in the new model wizard
  • TEIIDDES-2403: Relax BIRT version range to 4.4.0 from 4.4.1
  • TEIIDDES-2404: "Preview Data" throws Exception, when user select jdbc driver which is not located under C dirive
  • TEIIDDES-2409: Cannot set Content via Element in Webservice operation input and output
  • TEIIDDES-2410: Import from REST JSON generates incorrect SQL query(extra quote)
  • TEIIDDES-2415: Import -> Web Service Source >> Source and View Model (REST) Parameter handling and parsing errors
  • TEIIDDES-2417: Import from SOAP Web Service - preselected profile can not be edited
  • TEIIDDES-2423: Add description to constraint option in Add/Edit Row Filter Definition
  • TEIIDDES-2424: Add actions to open Teiid Designer community Examples web page
  • TEIIDDES-2430: TD has problems to "Test JDBC connection" when there is ";" (semicolon) in password
  • TEIIDDES-2431: Designer generated REST WAR handles the LOBS incorrectly
  • TEIIDDES-2432: Import from REST JSON - procedure returns empty table.

A. Revision History

Revision History
Revision 8.0.0-2Wed Apr 01 2015Misha Husnain Ali
Updated for splash page.
Revision 8.0.0-1Tue Feb 17 2015Michelle Murray
Generated for GA

Legal Notice

Copyright © 2015 Red Hat, Inc.
This document is licensed by Red Hat under the Creative Commons Attribution-ShareAlike 3.0 Unported License. If you distribute this document, or a modified version of it, you must provide attribution to Red Hat, Inc. and provide a link to the original. If the document is modified, all Red Hat trademarks must be removed.
Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.
Linux® is the registered trademark of Linus Torvalds in the United States and other countries.
Java® is a registered trademark of Oracle and/or its affiliates.
XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
MySQL® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
Node.js® is an official trademark of Joyent. Red Hat Software Collections is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
The OpenStack® Word Mark and OpenStack logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation's permission. We are not affiliated with, endorsed or sponsored by the OpenStack Foundation, or the OpenStack community.
All other trademarks are the property of their respective owners.