All modified and completed EABs must be placed into a separate JAR file and specified to the CA Gen Build Tool for inclusion into the application's EAR file.
If the EABs are not resolved, the application fails at runtime with a 'class not found' exception.
Java requires all references to external classes be resolved at compile time. Consequently, the CA Gen Build Tool will compile all EAB stubs and place them in the JAR files. During application assembly, these classes are removed from the JAR files. This is required since many application servers will search the JAR containing the calling action block before looking to an external JAR file where the completed EAB class file is actually located.
The replacement of completed EAB (for the EAB skeletons) in the original generation directory is not supported due to the likelihood of subsequent generations overwriting the completed EABs.
|
Copyright © 2013 CA.
All rights reserved.
|
|