Added messages to the single resource bundle file and a writeInputStreamToFile() function

Author: mwooten

core/src/main/java/oracle/weblogic/deploy/util/FileUtils.java

@@ -7,6 +7,7 @@
 import java.io.ByteArrayOutputStream;
 import java.io.File;
 import java.io.FileInputStream;
+import java.io.FileOutputStream;
 import java.io.FilenameFilter;
 import java.io.IOException;
 import java.io.InputStream;
@@ -593,6 +594,24 @@ public static byte[] readInputStreamToByteArray(InputStream input) throws IOExce
         return outputStream.toByteArray();
     }
 
+    public static File writeInputStreamToFile(InputStream input, String fileName) throws IOException {
+        FileOutputStream fos = null;
+        File file = null;
+
+        try {
+            File tmpdir = new File(System.getProperty("java.io.tmpdir"));
+            file = new File(tmpdir, fileName);
+            byte[] byteArray = FileUtils.readInputStreamToByteArray(input);
+            fos = new FileOutputStream(file);
+            fos.write(byteArray);
+        }
+        finally {
+            if (fos != null) { fos.close(); }
+        }
+
+        return file;
+    }
+
     ///////////////////////////////////////////////////////////////////////////
     // Private helper methods                                                //
     ///////////////////////////////////////////////////////////////////////////

core/src/main/resources/oracle/weblogic/deploy/messages/wlsdeploy_rb.properties

@@ -1115,3 +1115,42 @@ WLSDPLY-20019=Filter entry in {0} has neither ID or path
 WLSDPLY-20020=Filter ID {0} is invalid
 WLSDPLY-20021=Filter path {0} does not exist
 WLSDPLY-20022=Error loading filter path {0}
+
+####################################################################
+#   Message number 09800 - 09999 wls-deploy-integration-test       #
+####################################################################
+WLSDPLY-09800=Running the {0} test 
+WLSDPLY-09801=Could not translate {0} test config file into a python dictionary
+WLSDPLY-09802=Test using the {0} file, produced the following test results: {1}
+WLSDPLY-09803={0} ({1}) ... ok
+WLSDPLY-09804={0} ({1}) ... failed: {2}
+WLSDPLY-09805=Internal error: {0} file is missing the plans dictionary key
+WLSDPLY-09806=Internal error: {0} is not a plan name in the plans map 
+WLSDPLY-09807=Error translating {0} file into a python dictionary: {1}
+WLSDPLY-09808=Could not access {0} file
+WLSDPLY-09809=Could not access {0} directory
+WLSDPLY-09810=Test produced {0} error, {1} warning, and {2} informational messages.
+WLSDPLY-09811=See the next {0} log messages for the details.
+WLSDPLY-09812={0} ({1}.{2}) VerificationException: {3} field cannot be missing
+WLSDPLY-09813={0} has a {1} test configuration type, but it must have a {2} test configuration type to be used for test config file verification
+WLSDPLY-09814=Error applying {0} test configuration overrides file: {1}
+WLSDPLY-09815=There is no plan named {0} in the {1} test configuration file
+WLSDPLY-09816=There is no settings named {0} in the {1} test configuration file
+WLSDPLY-09817={0} plan module has already been loaded, so using cached object
+WLSDPLY-09818={0} plan module has not been loaded yet. Attempting to load it...
+WLSDPLY-09819={0}.{1} is not valid for use as a plan module because it is not a subclass of unitttest.Test
+WLSDPLY-09820=Running {0} to {1} plan step as test number {2}
+WLSDPLY-09821=Running {0} type test for the {1} plan
+WLSDPLY-09822={0} plan module could not be imported: {1}
+WLSDPLY-09823={0} test configuration file contains an unsupported test configuration type: {1}. The currently supported types are: {2}
+WLSDPLY-09824=Unable to find {0} resource in the binary of the installable 
+WLSDPLY-09825=Unable to extract {0} file from the binary of the installable
+WLSDPLY-09826={0} ({1}) raised an error: {2}
+WLSDPLY-09827={0} test configuration is missing a required field: {1}
+WLSDPLY-09828={0} is a malformed metadata path; must be the name of a metadata field or a forward-slash delimited path to a metadata field
+WLSDPLY-09829=Metadata path to required field {0} contains a {1} token, but test configuration has no {2} field instances in it
+WLSDPLY-09830={0} is not one of the predefined wildcard fields: {1}
+WLSDPLY-09831=The predefined wildcard fields can only appear in the plans or settings section of a test configuration metadata file
+WLSDPLY-09832={0} exited with error code {1}
+WLSDPLY-09833={0} step did not write a model file to the {1} archive file
+WLSDPLY-09834={0} step did not write a {1} model file to the file system