Questo contenuto non è disponibile nella lingua selezionata.
Chapter 3. Changes
3.1. Changes to Red Hat JBoss Data Virtualization Copia collegamentoCollegamento copiato negli appunti!
Copia collegamentoCollegamento copiato negli appunti!
- Installation
- In 5.x releases, Red Hat JBoss Data Virtualization depended on the Red Hat JBoss Services Oriented Architecture Platform (SOA-P). In this release, Red Hat JBoss Data Virtualization is installed on the Red Hat JBoss Enterprise Application Platform (EAP) directly. Users will be able to install on top of an existing JBoss EAP installation or with a fresh installation.
- In 5.xs releases, Red Hat JBoss Data Virtualization could operate under a number of profiles. In this release, Red Hat JBoss Data Virtualization can be installed in one of the two JBoss EAP modes: standalone mode (default) or domain mode (for clustering).
- Quickstarts
- Quickstarts now rely on Maven instead of Apache Ant.
- Tooling Support
- Teiid Designer and ModeShape Tools plugins for Red Hat JBoss Developer Studio will support both version 5 and 6 of JBoss Data Virtualization.
- Week Function
- Red Hat JBoss Data Virtualization now consistently returns the ISO 8601 standard for WEEK. Previously, "locale" had been used by default for many databases. This could potentially break functionality for users of databases such as h2, SQL Server and Sybase.
- ibm.jdk Dependency Missing from org.jboss.security.negotiation Module
- The ibm.jdk dependency is not added to the org.jboss.security.negotiation module, including the patched version in the .overlay directory. As this is not fixed in Red Hat JBoss EAP, you will have to manually add the dependency every time you patch EAP if you want to make use of it.