org.jboss.net.axis
public class: AttacheableService [javadoc |
source]
java.lang.Object
org.jboss.net.axis.AttacheableService
All Implemented Interfaces:
Referenceable
The attacheable service implementation
allows to bind axis service instances into JNDI
without loosing the configuration link to their engine/deployer.
Configuration pointers are reinstalled
by a dedicated context attribute that allows to identify a
target configuration when deserialized by the associated
ServiceFactory.
Also see:
- ServiceFactory
- since:
26.04.02 -
- author:
< - a href="mailto:Christoph.Jung@infor.de">Christoph G. Jung
- version:
$ - Revision: 1.1.2.2 $
| Field Summary |
|---|
| protected String | serviceClass | the real axis service implementation that
regularly looses its configuration |
| protected String | rootContext | this is what we need to find the important part, which is the
engine configuration, again. |
| Constructor: |
public AttacheableService(String serviceClass,
String rootContext) {
this.serviceClass = serviceClass;
this.rootContext = rootContext;
}
Creates a new ServiceFactory. Parameters:
service - the axis service
|
| Method from org.jboss.net.axis.AttacheableService Summary: |
|---|
|
getReference |
| Method from org.jboss.net.axis.AttacheableService Detail: |
public Reference getReference() {
Reference myRef =
new Reference(serviceClass, ServiceFactory.class.getName(), null);
myRef.add(new StringRefAddr(Constants.CONFIGURATION_CONTEXT, rootContext));
return myRef;
}
|