How can I tell Apache Axis 1.4 not to look for a transport client properties instance (an implementation of org.apache.axis.components.net.TransportClientProperties) and instead supply my own?
My problem is that both my Eclipse plugin and another Eclipse plugin are using Axis 1.4, which, via Apache Discovery, looks for a system property to determine which implementation of TransportClientProperties to use, and the other plugin sets that property to the name of its own class. My plugin can't use that class - it can't even load it. It should just use the default implementation supplied with Axis 1.4.
Should I subclass an existing transport and supply it via an EngineConfiguration when I create my instance of org.apache.axis.client.Service? Or should I subclass Service itself? I'm unsure of where to hook in to circumvent the system-property-based discovery mechanism.