Fix ressource leak

[gpl/argeo-slc.git] / runtime / org.argeo.slc.specs / src / main / java / org / argeo / slc / execution / ExecutionFlowDescriptor.java

diff --git a/runtime/org.argeo.slc.specs/src/main/java/org/argeo/slc/execution/ExecutionFlowDescriptor.java b/runtime/org.argeo.slc.specs/src/main/java/org/argeo/slc/execution/ExecutionFlowDescriptor.java
index 187c3658966c29789fae23376c88af8ac34c7c0b..73b74a312761813c55875bfef02fe5d96b817d2f 100644 (file)
--- a/runtime/org.argeo.slc.specs/src/main/java/org/argeo/slc/execution/ExecutionFlowDescriptor.java
+++ b/runtime/org.argeo.slc.specs/src/main/java/org/argeo/slc/execution/ExecutionFlowDescriptor.java
@@ -1,5 +1,5 @@
 /*
- * Copyright (C) 2010 Mathieu Baudier <mbaudier@argeo.org>
+ * Copyright (C) 2007-2012 Argeo GmbH
  *
  * Licensed under the Apache License, Version 2.0 (the "License");
  * you may not use this file except in compliance with the License.
@@ -13,7 +13,6 @@
  * See the License for the specific language governing permissions and
  * limitations under the License.
  */
-
 package org.argeo.slc.execution;
 
 import java.io.Serializable;
@@ -21,27 +20,24 @@ import java.util.Map;
 
 /**
  * 
- *         Implements both archetype and implementation of a given
- *         process.
- * 
- *         At specification time, <code>executionSpec</code> represents the spec
- *         of the parameters accepted by the process, with, among others: type,
- *         default value and, optionally, possible values for each parameter. Thus
- *         ExecutionSpec might be a huge object. Note that when marshalling only
- *         a reference to a specific ExecutionSpec is stored in the XML to
- *         optimize performance and avoid redundancy between various
- *         ExecutionFlowDesciptor that might have the same ExecutionSpec.
- * 
- *         At runtime, we build a RealizedFlow which references an
- *         ExecutionFlowDescriptor. As it happens AFTER marshalling /
- *         unmarshalling process, the ExecutionSpec is null but we manage to
- *         retrieve the ExecutionSpec and store it in the RealizedFlow, whereas
- *         set values of the parameters are stored in the <code>values</code>
- *         map.
+ * Implements both archetype and implementation of a given process.
  * 
- * @author bsinou
+ * At specification time, <code>executionSpec</code> represents the spec of the
+ * parameters accepted by the process, with, among others: type, default value
+ * and, optionally, possible values for each parameter. Thus ExecutionSpec might
+ * be a huge object. Note that when marshalling only a reference to a specific
+ * ExecutionSpec is stored in the XML to optimize performance and avoid
+ * redundancy between various ExecutionFlowDesciptor that might have the same
+ * ExecutionSpec.
  * 
+ * At runtime, we build a RealizedFlow which references an
+ * ExecutionFlowDescriptor. As it happens AFTER marshalling / unmarshalling
+ * process, the ExecutionSpec is null but we manage to retrieve the
+ * ExecutionSpec and store it in the RealizedFlow, whereas set values of the
+ * parameters are stored in the <code>values</code> map.
  * 
+ * Generally, values object are either a <code>PrimitiveAccessor</code> or a
+ * <code>RefValue</code> but can be other objects.
  */
 public class ExecutionFlowDescriptor implements Serializable {
        private static final long serialVersionUID = 7101944857038041216L;
@@ -65,10 +61,18 @@ public class ExecutionFlowDescriptor implements Serializable {
                return name;
        }
 
+       /**
+        * @deprecated will be removed in SLC 2.x, the path should be the part of
+        *             the name with '/'
+        */
        public String getPath() {
                return path;
        }
 
+       /**
+        * @deprecated will be removed in SLC 2.0, the path should be the part of
+        *             the name with '/'
+        */
        public void setPath(String path) {
                this.path = path;
        }