A bit of a provcative statement from a J2EE neophyte, perhaps. Following on from my quick note a few days ago (Daemonite: AXIS Web Services goes Beta 3) I've attempted to update the AXIS web service components to the beta3 release. The short of it is I failed miserably...
Having tinkered a fair bit and chatted to a few friends I think we'll have to wait for the next service pack to see an upgrade to the internal CFMX webservices module. Here's what I did and why things don't look so good.
Downloaded the latest binaries from the AXIS site (http://xml.apache.org/axis/index.html). Unpacked the zip file and hunted around for the AXIS jar file. For those (like me) who are not all that familiar with the Java jargon, a JAR (or Java ARchive) is like a ZIP file of class files and other bits. In fact, you can open up a JAR file with winzip. It makes for a convenient place to aggregate the components of your application when you are distributing it.
AXIS has several jars. The one I was after turned out to be:
Located the webservice.jar file in CFMX:
webservices.jar appears to contain all the content of the AXIS distribution in a single jar file.
Attempted to upgrade the class files for AXIS located in here with the class files in the AXIS distribution, by copying the class files into the webservices.jar from:
Thought I was a bloody genius when this worked but alas... MethodNotFoundException
I'm told that the API changes in Axis unfortunately affect the embedded JRun engine for CFMX. However, this is apparently necessary because Axis needs to be JAX-RPC compliant (thanks Clement).
So without a JRun patch it looks like my attempts are doomed to failure. Apparently, when JRun starts, it helps set some values in Axis when it's used as an embedded component... The MethodNotFoundException I get is probably causing the initialization to stop prematurely.
Oh well.. back to real work now.
Posted by modius at 07:16 PM | Permalink