The wsdd axis configuration file is currently read as a file from the file system. It would be much more convenient if this could be read as a resource from within the corresponding connector jar. Unfortunately, Axis's FileProvider implementation does not really support this properly. The FileProvider(InputStream) constructor does not properly close the input stream at any point, and in any case allows it to be read only once. The ability to look through the class path is present but starts with the Axis classes (which are not in the connector jar) and also seems to leak file handles.
The proper implementation therefore involves someone writing their own ResourceProvider class, implementing EngineConfiguration, with all the right characteristics. This is straightforward but obviously requires testing against a SharePoint instance before it could be committed - or, at least, confirmation the the wsdd configuration is being picked up properly.