Type	NEW
Priority	LOW
Status	CLOSED

Topic	XmlBlaster provides an own classloader for its plugins.
Des cription	Assume you write a new plugin for xmlBlaster with conflicting jar files, e.g. you have your own ORB or XML classes. The PluginClassLoader has its own classpath, which is specified in the xmlBlaster.properties file. The xmlBlaster.jar file is attached to this classpath at the end (with lowest priority).
Configure	Property Default / Example Description Implemented ProtocolPlugin[SOAP][1.0] org.xmlBlaster.protocol.soap.SoapDriver,\ classpath=soap/jdom.jar:soap/log4j-core.jar:\ soap/log4j.jar:soap/saw.jar:\ soap/soap.jar:soap/xerces.jar This example loads a SOAP plugin with the SOAP specific jar files attached. NOTE: Configuration parameters are specified on command line (-someValue 17) or in the xmlBlaster.properties file (someValue=17). See requirement "util.property" for details. Columns named Impl tells you if the feature is implemented. Columns named Hot tells you if the configuration is changeable in hot operation.
Todo	Write some TestCase!?
See REQ	util.classloader.ClassLoaderFactory
See API	org.xmlBlaster.util.classloader.PluginClassLoader
See API	org.xmlBlaster.util.classloader.ClassLoaderFactory
See API	java.net.URLClassLoader

This page is generated from the requirement XML file xmlBlaster/doc/requirements/util.classloader.PluginClassLoader.xml

Back to overview