CAA V5 Encyclopedia |
What's New?News in CAA V5R19 C++ and Java |
|
| Technical Article | ||
AbstractSome enhancements or maintenance reasons require changes regarding tools or methodologies. This article lists them, and points to the corresponding documentation.
|
The following is new with V5R19.
Starting with V5R19, Windows 32-bit code generation on Windows 64-bit platforms is supported.
The following Authorized APIs are available from CAA V5R19 onwards:
[Top]
Authorized API changes compared to CAA V5R19 at the general availability level are described:
Deprecated APIs can be found in:
Some interfaces have been moved from ObjectModelerBase into the new ObjectModelerSystem and ObjectModelerNavigator frameworks.
Modules using the moved Authorized APIs should have the listed module added to
their LINK_WITH statement of their Imakefile.mk file and add the listed
framework as a prerequisite in the IdentityCard of their frameworks. The CAA
Multi-Workspace Application Builder - mkmk (MAB) automatically takes this modification
into account and only displays a WARNING, but adding the right framework and module
to the IdentityCards and Imakefile.mk is highly recommended.
| Authorized API | Framework | Module |
|---|---|---|
| booleanDef.h | ObjectModelerSystem | CATOMY |
| CATIGraphLink.h | ObjectModelerNavigator | CATObjectModelerNavigator |
| CATIGraphNode.h | ObjectModelerNavigator | CATObjectModelerNavigator |
| CATINavigateFilter.h | ObjectModelerNavigator | CATObjectModelerNavigator |
| CATINavigateObject.h | ObjectModelerNavigator | CATObjectModelerNavigator |
| CATINavigateProvider.h | ObjectModelerNavigator | CATObjectModelerNavigator |
| CATINavigContainer.h | ObjectModelerNavigator | CATObjectModelerNavigator |
| CATINavigElement.h | ObjectModelerNavigator | CATObjectModelerNavigator |
| CATINavigModify.h | ObjectModelerNavigator | CATObjectModelerNavigator |
| CATINavigNodeCtrl.h | ObjectModelerNavigator | CATObjectModelerNavigator |
| CATInterfaceEvents.h | ObjectModelerSystem | CATOMY |
| CATIRedrawEvent.h | ObjectModelerNavigator | CATObjectModelerNavigator |
| CATNavigController.h | ObjectModelerNavigator | CATObjectModelerNavigator |
| CATNavigInstance.h | ObjectModelerNavigator | CATObjectModelerNavigator |
| CATNodeExtension.h | ObjectModelerNavigator | CATObjectModelerNavigator |
| CORBAAnyDef.h | ObjectModelerSystem | CATOMY |
| CosLifeCycleServices.h | ObjectModelerSystem | CATOMY |
| CosNaming.h | ObjectModelerSystem | CATOMY |
| LifeCycleObject.h | ObjectModelerSystem | CATOMY |
| octetDef.h | ObjectModelerSystem | CATOMY |
| sequence.h | ObjectModelerSystem | CATOMY |
| sequence_CATBaseUnknown_ptr.h | ObjectModelerSystem | CATOMY |
| sequence_CORBAAny.h | ObjectModelerSystem | CATOMY |
| sequence_octet.h | ObjectModelerSystem | CATOMY |
[Top]
PRODUCT package: in the VPMItemInstance class, the following attributes are changed:
[Top]
The following enhancements are available in the CAA Encyclopedia from CAA V5R19 onwards:
New articles in V5R19 modelers or RADE tools:
[Top]
The following is new with CAA V5R18.
The IRIX operating system is not supported any longer, starting with V5R18.
In V5R18, like in V5R17, the following common sense rule now produces build errors: when a C++ header file is in ProtectedInterfaces, it cannot include header files located in a folder with a lower level of visibility, like PrivateInterface for example. Such architecture inconsistencies are reported as build errors the following way:
# mkmk-ERROR: xxx\ProtectedInterfaces\Xxx.h : PROTECTED file cannot use yyy\PrivateInterfaces Yyy.h as include since it is PRIVATE.
They don't prevent to actually build the application but it is strongly recommended to correct them.
The following modelers are available from CAA V5R18 onwards:
The following Authorized APIs are available from CAA V5R18 onwards:
[Top]
Authorized API changes compared to CAA V5R18 at the general availability level are described:
Deprecated APIs can be found in:
[Top]
A new class is added in the APLECO package: V5R18_CO_Exclusion.
[Top]
The following enhancements are available in the CAA Encyclopedia from CAA V5R18 onwards:
New articles in V5R18 modelers or RADE tools:
[Top]
The following is new with CAA V5R17.
In V5R17, the following common sense rule now produces build errors: when a C++ header file is in ProtectedInterfaces, it cannot include header files located in a folder with a lower level of visibility, like PrivateInterface for example. Such architecture inconsistencies are reported as build errors the following way:
# mkmk-ERROR: xxx\ProtectedInterfaces\Xxx.h : PROTECTED file cannot use yyy\PrivateInterfaces Yyy.h as include since it is PRIVATE.
They don't prevent to actually build the application but it is strongly recommended to correct them.
[Top]
The following modelers are available from CAA V5R17 onwards in ENOVIA V5 VPM:
[Top]
The following Authorized APIs are available from CAA V5R17 onwards:
[Top]
Authorized API changes compared to CAA V5R17 at the general availability level are described:
Deprecated APIs can be found in:
[Top]
No changes in ENOVIA LCA exposed metadata between V5R17 and V5R16.
[Top]
The following enhancements are available in the CAA Encyclopedia from CAA V5R17 onwards:
The Web Services home page is reorganized according to the supported platforms, points to new technical articles and use cases, and is now divided into:
The new Machining Algorithms modeler appears in the DELMIA Off-line Programming solution.
New articles in existing V5R17 modelers or RADE tools:
[Top]
The following is new with CAA V5R16.
| In order to help customers' and partners' applications comply with the CAA
V5 usage rules described in the CAA Encyclopedia, our offering is refined by
better aligning the CAA build time media content with the CAA Encyclopedia content.
Thus, starting with V5R15, non-CAA Authorized APIs previously located in the
ProtectedInterfaces folders are no longer available from the CAA build time
media. While enriching the CAA Authorized APIs offering with new CAA APIs matching
new needs, we will continue to deliver with CAA RADE a more and more secure
development environment by protecting CAA applications from the risks of using
non-CAA Authorized APIs. As a reminder, CAA RADE tools prevent the usage of undocumented resources located in ProtectedInterfaces starting with V5R12. In some cases, the CAA RADE tools may not have detected all uses of the non-CAA authorized APIs. To ensure that all non-CAA Authorized APIs have been detected, CAA RADE V5R15 provides a new audit tool. Launch it before attempting to build your CAA applications. Please refer to the following article for further information on how to use this audit tool. Please contact your local support if you need assistance. |
You also refer to the CAA V5R16 news highlights for more information.
[Top]
Web services are now avaliable in V5R16. refer to the Web Services home page.
The following modelers are available from CAA V5R16 onwards:
[Top]
The following Authorized APIs are available from CAA V5R16 onwards:
[Top]
Authorized API changes compared to CAA V5R16 at the general availability level are described:
Deprecated APIs can be found in:
[Top]
Two changes in ENOVIA LCA metadata:
[Top]
The following enhancements are available in the CAA Encyclopedia from CAA V5R16 onwards:
New articles in existing V5R16modelers or RADE tools:
[Top]
The following is new with CAA V5R15.
| In order to help customers' and partners' applications comply with the CAA
V5 usage rules described in the CAA Encyclopedia, our offering is refined by
better aligning the CAA build time media content with the CAA Encyclopedia content.
Thus, starting with V5R15, non-CAA Authorized APIs previously located in the
ProtectedInterfaces folders are no longer available from the CAA build time
media. While enriching the CAA Authorized APIs offering with new CAA APIs matching
new needs, we will continue to deliver with CAA RADE a more and more secure
development environment by protecting CAA applications from the risks of using
non-CAA Authorized APIs. As a reminder, CAA RADE tools prevent the usage of undocumented resources located in ProtectedInterfaces starting with V5R12. In some cases, the CAA RADE tools may not have detected all uses of the non-CAA authorized APIs. To ensure that all non-CAA Authorized APIs have been detected, CAA RADE V5R15 provides a new audit tool. Launch it before attempting to build your CAA applications. Please refer to the following article for further information on how to use this audit tool. Please contact your local support if you need assistance. |
[Top]
The following Authorized APIs are available from CAA V5R15 onwards:
[Top]
Authorized API changes compared to CAA V5R15 at the general availability level are described:
Deprecated APIs can be found in:
[Top]
ENOVIA LCA exposed metadata changes are described in:
As a reminder, all metadata changes, whether metadata is exposed or not, are described in:
[Top]
The following enhancements are available in the CAA Encyclopedia from CAA V5R15 onwards:
New articles in existing V5R15modelers or RADE tools:
[Top]
The following is new with CAA V5R14.
| Warning: The location of the CAA Authorized APIs have changed from V5R12 onwards. This has impacts on your applications. Refer to CAA Authorized APIs to know about this. |
| Framework | Deprecated | To be used from V5R14 |
|---|---|---|
| GeometricObjects | CATGeoFactory::CreateNurbsCurve | CATGeoFactory::CATCreateNurbsCurve |
| GeometricObjects | CATGeoFactory::CreatePNurbs | CATGeoFactory::CATCreatePNurbs |
| GeometricObjects | CATGeoFactory::CreateNurbsSurface | CATGeoFactory::CATCreateNurbsSurface |
| GeometricObjects | CATNurbsCurve::Set | CATNurbsCurve::SetData |
| GeometricObjects | CATNurbsSurface::Set | CATNurbsSurface::SetData |
| GeometricObjects | CATPNurbs::Set | CATPNurbs::SetData |
| GeometricObjects | CATSplineCurve::SetOnePoint | CATSplineCurve::ReplaceOnePoint |
| GeometricObjects | CATSplineCurve::SetOneTangent | CATSplineCurve::ReplaceOneTangent |
| GeometricObjects | CATPSpline::SetOnePoint | CATPSpline::ReplaceOnePoint |
| GeometricObjects | CATPSpline::SetOneTangent | CATPSpline::ReplaceOneTangent |
| GeometricObjects | CATPSpline::SetOneParameter | CATPSpline::ReplaceOneParameter |
The new CATMathNurbsSurfaceTools.h and CATMathNurbsCurveTools.h in the GeometricOperators framework can be used to deal with mathematical non-C2 Nurbs entities, to evaluate them, and to break them into C2 model entities.
[Top]
The following modelers are available from CAA V5R14 onwards:
[Top]
The following RADE tools is available from CAA V5R14 onwards:
[Top]
The following Authorized APIs are available from CAA V5R14 onwards:
[Top]
Authorized API changes compared to CAA V5R14 at the general availability level are described:
Deprecated APIs can be found in:
[Top]
ENOVIA LCA exposed metadata changes are described in:
As a reminder, all metadata changes, whether metadata is exposed or not, are described in:
[Top]
The following enhancements are available in the CAA Encyclopedia from CAA V5R14 onwards:
New articles in existing V5R14modelers or RADE tools:
[Top]
The following is new with CAA V5R13.
| Warning: The location of the CAA Authorized APIs have changed. This has impacts on your applications. Refer to CAA Authorized APIs to know about this. |
adl_admin_site -init_db -db SID -db_user adl -db_type dept -db_size
? -target_dir /tmpThe following modelers are available from CAA V5R13 onwards:
[Top]
The following Authorized APIs are available from CAA V5R13 onwards:
[Top]
Authorized API changes compared to CAA V5R13 at the general availability level are described:
Deprecated APIs can be found in:
[Top]
ENOVIA LCA exposed metadata changes are described in:
As a reminder, all metadata changes, whether metadata is exposed or not, are described in:
[Top]
The following enhancements are available in the CAA Encyclopedia from CAA V5R13 onwards:
New articles in existing V5R13 modelers or RADE tools:
[Top]
The following is new with CAA V5R12.
| Warning: The location of the CAA Authorized APIs have changed. This has impacts on your applications. Refer to CAA Authorized APIs to know about this. |
The following modelers are available from CAA V5R12 onwards:
[Top]
The following RADE tool is not available any longer:
[Top]
The following Authorized APIs are available from CAA V5R12 onwards:
[Top]
Authorized API changes compared to CAA V5R11 at the general availability level are described:
[Top]
ENOVIA LCA exposed metadata changes are described in:
As a reminder, all metadata changes, whether metadata is exposed or not, are described in:
[Top]
The following enhancements are available in the CAA Encyclopedia from CAA V5R12 onwards:
New articles in existing V5R12 modelers or RADE tools:
[Top]
The following is new with CAA V5R11.
The following modelers are available from CAA V5R11 onwards:
[Top]
The following RADE tools is available from CAA V5R11 onwards:
[Top]
The following Authorized APIs are available from CAA V5R11 onwards:
[Top]
Authorized API changes compared to CAA V5R11 at the general availability level are described:
Deprecated APIs can be found in:
The Authorized APIs that were up to now supplied with the LiteralFeatures framework are moved to the KnowledgeInterfaces framework. Before rebuilding your applications that use these Authorized APIs, make sure that the KnowledgeInterfaces framework is declared in the IdentityCard.h files of your frameworks.
Some interfaces have been moved from MechanicalModeler into the new ConstraintModeler and ConstraintModelerInterfaces frameworks.
Modules using the moved Authorized APIs should have the listed module added to
their LINK_WITH statement of their Imakefile.mk file and add the listed
framework as a prerequisite in the IdentityCard of their frameworks. The CAA
Multi-Workspace Application Builder - mkmk (MAB) automatically takes this modification
into account and only displays a WARNING, but adding the right framework and module
to the IdentityCards and Imakefile.mk is highly recommended.
|
Authorized API |
Framework |
Module |
| CATDimMath.h.h | ConstraintModeler | CATConstraintModeler |
| CATDimTempCst.h | ConstraintModeler | CATConstraintModeler |
| CATDimVisualizationAdapter.h | ConstraintModeler | CATConstraintModeler |
| CATICstFactory.h | ConstraintModeler | CATConstraintModeler |
| CATMfPossibleCst.h | ConstraintModeler | CATConstraintModeler |
| CATFeatureType.h | ConstraintModelerInterfaces | CATConstraintModelerItf |
| CATIAncestry.h | ConstraintModelerInterfaces | CATConstraintModelerItf |
| CATIBloc.h | ConstraintModelerInterfaces | CATConstraintModelerItf |
| CATICst.h | ConstraintModelerInterfaces | CATConstraintModelerItf |
| CATICstData.h | ConstraintModelerInterfaces | CATConstraintModelerItf |
| CATLISTV_CATICst.h | ConstraintModelerInterfaces | CATConstraintModelerItf |
The following enhancements are available in the CAA Encyclopedia from CAA V5R11 onwards:
New articles in existing V5R11 modelers or RADE tools:
[Top]
The following is new with CAA V5R10.
The following modelers are available from CAA V5R10 onwards:
[Top]
The following Authorized APIs are available from CAA V5R10 onwards:
[Top]
Authorized API changes compared to CAA V5R10 at the general availability level are described:
Deprecated APIs can be found in:
Following the split of the Visualization framework in V5R9, the
Print
framework has been split into two frameworks and some CAA Authorized API Authorized
APIs have been moved to the new
PrintBase
framework. Modules using the moved Authorized APIs should have the CATPrtBase module
added to their LINK_WITH statement of their Imakefile.mk file and add
the PrintBase framework as a prerequisite in the IdentityCard of their frameworks.
The CAA Multi-Workspace Application Builder - mkmk (MAB) automatically takes this
modification into account and only displays a WARNING, but adding the PrintBase
framework to the IdentityCard is highly recommended.
AddPrereqComponent("PrintBase", Protected);
LINK_WITH statement
of their Imakefile.mk
LINK_WITH = CATPrintBase
Before V5R10 the TTRS modeler Authorized APIs were located in the MecModInterface and MechanicalModeler frameworks. From V5R10 onwards, they are now in the framework CATTTRSInterfaces. The CAA Multi-Workspace Application Builder - mkmk (MAB) does NOT take this modification into account. To be able to build their applications on V5R10, the clients of the TTRS modeler must do the following modifications:
AddPrereqComponent("CATTTRSInterfaces", Protected);
LINK_WITH
statement of their Imakefile.mk
LINK_WITH = CATTTRSItf \
CATTTRSUUID
to avoid runtime stability problems during V5R10, insert those modules before
the reference to the CATMecModInterfaces module (that may even have become useless).
[Top]
The following enhancements are available in the CAA Encyclopedia from CAA V5R10 onwards:
Removed articles: articles dealing with documents and workshops have been removed. CAA doesn't allow to create new types of documents, and thus workshop can't be created. The following articles are removed from V5R10:
New articles in existing V5R10 modelers or RADE tools:
[Top]
The following is new with CAA V5R9.
The DELMIA brand now includes CAA V5 Authorized APIs for the following solutions:
The following modelers are available from CAA V5R9 onwards:
[Top]
[Top]
The following Authorized APIs are available from CAA V5R9 onwards:
[Top]
Authorized API changes compared to CAA V5R9 at the general availability level are described:
Deprecated APIs can be found in:
To provide a light visualization solution, the Visualization framework
has been split into two frameworks and some CAA Authorized APIs have been moved
to the new VisualizationBase framework. Modules using the moved Authorized APIs
should have the CATViz module added to their LINK_WITH statement of
their Imakefile.mk file and add the VisualizationBase framework as a prerequisite
in the IdentityCard of their frameworks. The CAA Multi-Workspace Application Builder
- mkmk (MAB) automatically takes this modification into account and only displays
a WARNING, but adding the VisualizationBase framework to the IdentityCard is highly
recommended.
Some CAA Authorized APIs have been moved from the MechanicalCommands framework
into the new InteractiveInterfaces framework. Modules using the moved Authorized
APIs should have the CATInteractiveInterfaces module added to their LINK_WITH
statement of their Imakefile.mk file and add the InteractiveInterfaces framework
as a prerequisite in the IdentityCard of their frameworks. The CAA Multi-Workspace
Application Builder - mkmk (MAB) automatically takes this modification into account
and only displays a WARNING, but adding the InteractiveInterfaces framework to the
IdentityCard is highly recommended.
[Top]
The following enhancements are available in the CAA Encyclopedia from CAA V5R8 onwards:
New articles in existing V5R9 modelers:
[Top]
The following is new with CAA V5R8.
The following modelers are available from CAA V5R8 onwards:
The Electrical platform is made up of the Electrical modeler.
[Top]
The following RADE tools are available from CAA V5R8 onwards:
[Top]
The following Authorized APIs are available from CAA V5R8 onwards:
[Top]
Authorized API changes compared to CAA V5R8 at the general availability level are described:
Deprecated APIs can be found in:
[Top]
The following enhancements are available in the CAA Encyclopedia from CAA V5R7 onwards:
New articles:
[Top]
The following is new with CAA V5R7.
The following modelers are available from CAA V5R7 onwards:
[Top]
The following RADE tools are available from CAA V5R7 onwards:
Note that the Software Configuration Manager is renamed as the Source Code Manager (SCM).
[Top]
Authorized API changes compared to CAA V5R6 at the general availability level are described:
For portability purpose, method arguments of type boolean have been
changed to CATBoolean. This change is visible in the signatures of
about 140 methods but, with the current set of typedefs, has no impact on applications
that were developed in V5R6 and before. As the boolean typedef is not part of the
CAA V5 Authorized APIs, it is strongly recommended for applications to use CATBoolean
instead.
[Top]
The following enhancements are available in the CAA Encyclopedia from CAA V5R7 onwards:
New articles:
[Top]
If an application stores the way to build an object, and gives the mean to replay this definition, it expects that the replay always gives the same result. Up to now, the software modifications could lead to slightly different results. To avoid this situation, the current software configuration of an operator must be given at the operator creation, so that an operator can be replayed with a given software configuration. This is the operator versioning.
As now an operator must know the configuration software on which it must run, this argument becomes mandatory. The detailed principle of the operator versioning as well as the correspondence table between the old signatures and the new signatures for the operators is described in The Versioning of the Topological Operators
[Top]
| [1] | Sun Java Packages for Windows and Solaris |
| [2] | IBM Java Package for Aix |
| [3] | HP Java Package for HP-UX |
| [4] | SGI Java Package for Irix |
| [Top] | |
| Version: 14 [Apr 2008] | V5R19 Update |
| Version: 13 [Apr 2007] | V5R18 Update |
| Version: 12 [Apr 2006] | V5R17 Update |
| Version: 11 [Jun 2005] | V5R16 Update |
| Version: 10 [Mar 2005] | V5R15 Update |
| Version: 9 [Jun 2004] | V5R14 Update |
| Version: 8 [Nov 2003] | V5R13 Update |
| Version: 7 [Jul 2003] | V5R12 Update |
| Version: 6 [Mar 2003] | V5R11 Update |
| Version: 5 [Oct 2002] | V5R10 Update |
| Version: 4 [Jun 2002] | V5R9 Update |
| Version: 3 [Dec 2001] | V5R8 Update |
| Version: 2 [May 2001] | V5R7 Update |
| Version: 1 [Nov 2000] | Document created |
| [Top] | |
Copyright © 1999-2006, Dassault Systèmes. All rights reserved.
Special Notices
CAA V5 CATIA |
CAA V5 DELMIA |
CAA V5 ENOVIA