CAPS 6: Mapping of Project Variables to Environment Constants is not Persistent from the Deployment Editor
Last updated on OCTOBER 25, 2016
Applies to:Oracle Java CAPS Enterprise Service Bus - Version R6 to R6 [Release 6.0]
Information in this document applies to any platform.
Checked for relevance on 06-Jun-2011.
***Checked for relevance on 21-June-2013***
Although it is possible to map Project variables to Environment constants, this binding is not preserved at the level of the deployment profile and therefore compilation errors occur when the code references Project variables.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms