dims 2003/03/19 05:02:36
Modified: java/src/org/apache/axis/client Service.java
Log:
javadoc patch from "Daniel Elenius" <[EMAIL PROTECTED]>
Revision Changes Path
1.87 +23 -0 xml-axis/java/src/org/apache/axis/client/Service.java
Index: Service.java
===================================================================
RCS file: /home/cvs/xml-axis/java/src/org/apache/axis/client/Service.java,v
retrieving revision 1.86
retrieving revision 1.87
diff -u -r1.86 -r1.87
--- Service.java 17 Mar 2003 14:52:09 -0000 1.86
+++ Service.java 19 Mar 2003 13:02:35 -0000 1.87
@@ -720,6 +720,29 @@
* now, this is basically a no-op. Putting it in now so that we can make
* lazy engine instantiation work, and not have to duplicate every single
* Service constructor with a EngineConfiguration argument.
+ * <p>
+ * If you need to use a non-default <code>EngineConfiguration</code>, do
+ * the following before calling the Service constructor:<p><code>
+ *
+ *
AxisProperties.setProperty(EngineConfigurationFactory.SYSTEM_PROPERTY_NAME,
+ * "classname.of.new.EngineConfigurationFactory");
+ * </code><p>
+ * Where the second parameter is the name of your new class that implements
+ * <code>EngineConfigurationFactory</code> and a<code><br>
+ * public static EngineConfigurationFactory newFactory(Object param)
+ * </code>
+ * method. See <code>EngineConfigurationFactoryDefault</code> for an example
+ * of how to do this.<p>
+ *
+ * This way, when the Service class constructor calls<br><code>
+ *
+ * EngineConfigurationFactoryFinder.newFactory().getClientEngineConfig()
+ * </code>
+ * the getClientEngineConfig() of your own EngineConfigurationFactory will be
+ * called, and your configuration will be used in the constructed Service
object.<p>
+ *
+ * Another way is to use the "discovery" method of
+ * <code>EngineConfigurationFactoryFinder</code>.
*
* @param config the EngineConfiguration we want to use.
*/
