Steve Loughran wrote:
It would be a useful little exercise. You could perhaps strip out all the wsdl-to-java generation for a run-time-only system, which should save space, and some of the other stuff. You'll still need commons-logging, but bind it to Java1.4 logging instead of log4j.
I look forward to see your results (and the axis-client) build file :)
I tried this a few weeks ago, I was curious since it comes up all the time. I dropped support for everything but Http on the transport layer, as much server stuff as I could, dropped support for attachments, and WSDL/Java generation. The jar size dropped by something like only 200 or 300k; I don't think it ever got below 1Mb. Dropping log4j doesn't save anything in the core jar, apart from the properties files (which shouldn't be in there anyway)
You can't completely get rid of the WSDL because its used for dynamic invocation, etc. The biggest chunk of code after these edits was the serialization/deserialization framework.
Anyway, I concluded that things are a bit too interconnected just now to separate a small client package out, for just the simplest use cases. You'd need to hack the code to make things better.
- Baz
