8.0.3 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
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.3 is an update for JBoss Developer Studio Integration Stack 8.0.2.
- It contains new features and fixes for the following released components:
- Teiid Designer 9.0.3.Final
- Fuse Tooling 7.3.1.Final
- BPEL 1.3.100.Final_1.0.5.Final
- It contains new features and fixes for the following JBoss Developer Studio Integration Stack 8.0.0 components released as Early Access:
- SwitchYard 2.0.1.Beta1
ImportantComponents 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.3
4. BPEL 1.3.100.Final_1.0.5.Final
5. Teiid Designer 9.0.3
- TEIIDDES-2606: Procedure parameter updated even when canceling the edit dialog
- TEIIDDES-2603: Cannot launch the Consume SOAP Web Service Wizard in Consume a SOAP Web Service Cheat Sheets.
- TEIIDDES-2599: Couple issues with Teiid Connection Importer
- TEIIDDES-2595: Swagger UI fails to load (hardcoded path to different war)
- TEIIDDES-2593: NPE during Consume SOAP Web Service action set
- TEIIDDES-2592: Connecting to remote server takes a very long time
- TEIIDDES-2583: Importing DDL with double-quoted table names removes segments of the name of the . delimiter is in string
- TEIIDDES-2580: Upgrade Modeshape jars to latest 3.8.x version
- TEIIDDES-2575: Change Browser Tab Icon to Teiid Lizard in Generated REST WARS
- TEIIDDES-2566: REST.war created with wrong bindings for composite primary keys
- TEIIDDES-2561: Swagger test UI shows incorrect hostname in Request URL value
- TEIIDDES-2560: Although DV 6.0(Teiid 8.4.1) is selected as teiid instance on JBDS, TD 9.0.1 uses grant-all in vdb.xml
- TEIIDDES-2557: Changing fields in new procedure dialogue in view model causes TD to hang
- TEIIDDES-2556: Password in "Select a JDBC source configuration" is completely ignored
- TEIIDDES-2553: Changing parameter types in REST connection results in wrong URL
- TEIIDDES-2552: REST connection profile wizard creates URL with parameters in wrong order
- TEIIDDES-2548: xml encoding/decoding destroys a sql query for Transformation in a view model
- TEIIDDES-2547: NPE when trying to use action Guides -> Model Teiid Data Source -> Create Source model from Teiid data source DDL
- TEIIDDES-2543: Rest procedure name null check problem
- TEIIDDES-2542: REST connection profile parameters settings problems (adding + deleting)
- TEIIDDES-2541: Issues with Rest connection profile security settings
- TEIIDDES-2538: Generate REST Virtual Procedure allows selecting a source model as the target
- TEIIDDES-2534: Model Refactoring: renaming folder fails when it contains a source model that has a dependent view model
- TEIIDDES-2533: Model Refactoring: view model is broken after moving source model to a different folder
- TEIIDDES-2531: Generate REST Virtual Procedure should allow setting the view XML tag names per table
- TEIIDDES-2530: Generate REST Virtual Procedure should use fully qualified names in the generated procedures
- TEIIDDES-2526: Import from SOAP wizard pops up multiple validation result messages
- TEIIDDES-2518: 1024x768 Input set editor issue - not all options are visible
- TEIIDDES-2497: Incorrect "Name in Source" when importing from JDBC Database using Informix
- TEIIDDES-2471: Assertion error trying to Delete a file
- TEIIDDES-2461: Allow using JBoss AS connection timeout property when trying to connect/find Teiid Server
- TEIIDDES-2447: Failed to import SalesForce Metadata
- TEIIDDES-2422: XSD model created in wrong folder when creating Web service model from WSDL
- TEIIDDES-2406: Provide option to set JNDI, instead of Connection Profile, in order to do data preview
- TEIIDDES-2399: Creating view model from source model with generate transformations results in orphaned annotated object reference to source
- TEIIDDES-2259: Edit VDB Data Role dialogue doesn't check off checkboxes properly
- TEIIDDES-2248: Teiid Connection import fails to parse DDL when table contains VARCHAR column with DEFAULT value
6. Fuse Tooling 7.3.1
- FUSETOOLS-1404: Missing artifact - ActiveMQ component
- FUSETOOLS-1391: When editing blueprint.xml, xml snippets disappearing and changing for no apparent reason.
- FUSETOOLS-1386: Source bundles don't contain resource files
- FUSETOOLS-1381: Inconsistent visibility with parent collection mappings
- FUSETOOLS-1379: Class and index mappings are wrong in certain cases
- FUSETOOLS-1363: Allow customization of model viewer tree when used on Transformation wizard pages
- FUSETOOLS-1355: Automatically map parent collections when a child field is mapped
- FUSETOOLS-1351: Support variable mapping to vectors
- FUSETOOLS-1350: Support expression mapping to vectors
- FUSETOOLS-1349: Support scalar to vector mapping
- FUSETOOLS-1344: Allow typing in text fields in New Fuse Transformation wizard
- FUSETOOLS-1339: Hiding diagram grid in Camel Editor does not work
- FUSETOOLS-1333: Errors in New Fuse Transformation Wizard are present as info messages
- FUSETOOLS-1331: New Fuse Transformation Wizard can be finished uncompleted
- FUSETOOLS-1330: New Fuse Transformation Wizard - Show only Camel/Dozer files
- FUSETOOLS-1314: NPE: set/delete breakpoint
- FUSETOOLS-1312: Wizard for creating new SAP DS doesn't display fields
7. SwitchYard 2.0.1
- SWITCHYARD-2730: SAP reference binding doesn't display values for IDoc List
- SWITCHYARD-2729: Put the 'Browse' button next to the text field in reference SCA binding
- SWITCHYARD-2728: NPE when you change reference SCA binding
- SWITCHYARD-2719: tooling/camel-mqtt: switchyard-mqtt feature is not added to features.xml
- SWITCHYARD-2718: tooling/camel-mqtt: Username and Password don't show up in reference binding properties
A. Revision History
|Revision 8.0.3-3||Tue Aug 25 2015||Misha Husnain Ali|
|Revision 8.0.3-2||Mon Aug 24 2015||Misha Husnain Ali|
|Revision 8.0.3-1||Mon Aug 24 2015||Misha Husnain Ali|
|Revision 8.0.3-0||Mon Aug 17 2015||Misha Husnain Ali|
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.