更新时间:2023-09-11 21:57:58
前一段时间我遇到了同样的问题,我看了一下Guicyfruit代码并决定提取所需的内容.这导致了三堂课.
I came across this same issue a while back and I had a look at the Guicyfruit code and decided to extract what I needed. This resulted in three classes.
首先,我们需要一个注释,我们可以使用该注释来注释我们的Web服务终结点.
First we need an annotation that we can use to annotate our web service endpoint with.
GuiceManaged.java
import java.lang.annotation.Documented;
import java.lang.annotation.ElementType;
import java.lang.annotation.Retention;
import java.lang.annotation.RetentionPolicy;
import java.lang.annotation.Target;
import javax.xml.ws.spi.WebServiceFeatureAnnotation;
import com.google.inject.Module;
import com.sun.xml.ws.api.server.InstanceResolverAnnotation;
@Retention(RetentionPolicy.RUNTIME)
@Target(ElementType.TYPE)
@Documented
@WebServiceFeatureAnnotation(id = GuiceManagedFeature.ID, bean = GuiceManagedFeature.class)
@InstanceResolverAnnotation(GuiceManagedInstanceResolver.class)
public @interface GuiceManaged {
Class<? extends Module>[] modules();
}
第二,我们需要上面注释中提到的GuiceManagedFeature.
Second we need the GuiceManagedFeature mentioned in the annotation above.
GuiceManagedFeature.java
import javax.xml.ws.WebServiceFeature;
import com.sun.xml.ws.api.FeatureConstructor;
public class GuiceManagedFeature extends WebServiceFeature {
public static final String ID = "any.string.will.do.here";
@FeatureConstructor
public GuiceManagedFeature() {
this.enabled = true;
}
@Override
public String getID() {
return ID;
}
}
第三,我们创建实际的解析器.
And third we create the actual resolver.
GuiceManagedInstanceResolver.java
import java.util.ArrayList;
import java.util.List;
import javax.xml.ws.WebServiceContext;
import org.slf4j.Logger;
import org.slf4j.LoggerFactory;
import com.google.inject.AbstractModule;
import com.google.inject.Guice;
import com.google.inject.Injector;
import com.google.inject.Module;
import com.sun.xml.ws.api.message.Packet;
import com.sun.xml.ws.api.server.WSEndpoint;
import com.sun.xml.ws.api.server.WSWebServiceContext;
import com.sun.xml.ws.server.AbstractMultiInstanceResolver;
public class GuiceManagedInstanceResolver<T> extends AbstractMultiInstanceResolver<T> {
private static final Logger LOGGER = LoggerFactory.getLogger(GuiceManagedInstanceResolver.class);
private static Injector injector;
private transient WSWebServiceContext webServiceContext;
public GuiceManagedInstanceResolver(final Class<T> clazz) {
super(clazz);
}
@Override
public T resolve(final Packet request) {
final T instance = injector.getInstance(this.clazz);
injector.injectMembers(instance);
return instance;
}
@SuppressWarnings("rawtypes")
@Override
public void start(final WSWebServiceContext wsWebServiceContext, final WSEndpoint endpoint) {
super.start(wsWebServiceContext, endpoint);
this.webServiceContext = wsWebServiceContext;
synchronized (GuiceManagedInstanceResolver.class) {
if (injector == null) {
final List<Module> moduleInstances = new ArrayList<Module>();
final Class<? extends Module>[] modules = this.clazz.getAnnotation(GuiceManaged.class).modules();
for (final Class<? extends Module> moduleClass : modules) {
try {
moduleInstances.add(moduleClass.newInstance());
} catch (final InstantiationException exception) {
LOGGER.error("Could not instantiate guice module [{}]", moduleClass.getName());
} catch (final IllegalAccessException e) {
LOGGER.error("Could not instantiate guice module [{}]", moduleClass.getName());
}
}
moduleInstances.add(new AbstractModule() {
@Override
protected void configure() {
this.bind(WebServiceContext.class).toInstance(GuiceManagedInstanceResolver.this.webServiceContext);
}
});
injector = Guice.createInjector(moduleInstances);
}
}
}
}
上面的示例使用SLF4J进行日志记录,但是当然可以根据需要使用任何东西.
The above example uses SLF4J for logging but it's of course up to you to use whatever you wish.