Tom Jordahl wrote:
i think it may help also to make this code easier to refactor into
WSDL2Antything ...
We already fully support this kind of thing with the WSDL2.java
architecture that is in place. Just add your own back end.
--
Tom Jordahl
Macromedia Server Development
Maybe the wsdl2 bit could remain in the axis codebase, but the build
file tweaked to generate a new jar that only had the stuff needed for
wsdl generation; this would only be for third parties, not axis users.
the other area for factoring out would be tcpmon; this is entirely self
contained and is a tool of widespread value. I dont see that including
it in every release of axis.jar fundamentally benefits end users or
anyone shipping axis in their app.
Having it as a self contained app, maybe even with java web start
support (*) would be cool.
-steve
(*) jws is not mandatory, this is how we autoretrieve tcpmon from the m2
repository for a demo of dynamic download and deploy in smartfrog.
sfConfig extends Compound {
sfSyncTerminate true;
library extends Maven2Library {
}
commons-logging extends JarArtifact {
library LAZY PARENT:library;
project "commons-logging";
version "1.0.4";
sha1 "f029a2aefe2b3e1517573c580f948caac31b1056";
md5 "8a507817b28077e0478add944c64586a";
}
axis extends JarArtifact {
library LAZY PARENT:library;
project "axis";
version "1.1";
sha1 "edd84c96eac48d4167bca4f45e7d36dcf36cf871";
}
tcpmonitor extends Java {
classname "org.apache.axis.utils.tcpmon";
classpath [
LAZY axis:absolutePath,
LAZY commons-logging:absolutePath];
}
}
