So there you are: a production error was reported … in your code (of all places) … but no one knows what release the code came from?
Wouldn’t it be great if it was easy to link deployed composites to their Subversion location and revision?
This article show an approach based on ‘Subversion keywords expansion’. This is illustrated with the following steps:
Let’s get started:
In composite.xml, add the below lines after the properties for productVersion and compositeID that JDeveloper already added: Read the complete article here.
For regular information on Oracle SOA Suite become a member in the SOA & BPM Partner Community for registration please visit www.oracle.com/goto/emea/soa (OPN account required) If you need support with your account please contact the Oracle Partner Business Center.