1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17 package org.apache.geronimo.ews.ws4j2ee.wsutils;
18
19 import org.apache.axis.EngineConfiguration;
20 import org.apache.axis.Handler;
21 import org.apache.axis.deployment.wsdd.WSDDProvider;
22 import org.apache.axis.deployment.wsdd.WSDDService;
23
24 /***
25 * refering to axis comment of pluggable providers
26 * Look for file META-INF/services/org.apache.axis.deployment.wsdd.Provider
27 * in all the JARS, get the classes listed in those files and add them to
28 * providers list if they are valid providers.
29 * Here is how the scheme would work.
30 * A company providing a new provider will jar up their provider related
31 * classes in a JAR file. The following file containing the name of the new
32 * provider class is also made part of this JAR file.
33 * META-INF/services/org.apache.axis.deployment.wsdd.Provider
34 * By making this JAR part of the webapp, the new provider will be
35 * automatically discovered.
36 *
37 * @author Srinath Perera(hemapani@opensource.lk)
38 */
39 public class WSDDJavaEWSProvider extends WSDDProvider {
40 public static final String PROVIDER_EWS = "ews";
41
42 public String getName() {
43 return PROVIDER_EWS;
44 }
45
46 public Handler newProviderInstance(WSDDService service,
47 EngineConfiguration registry)
48 throws Exception {
49 return new org.apache.geronimo.ews.ws4j2ee.wsutils.EWSProvider();
50 }
51 }