| Frank Swarbrick 2007-05-29, 9:55 pm |
| >>> On 5/28/2007 at 8:36 PM, in message
<5c1hsnF2uuqhfU1@mid.individual.net>,
Pete Dashwood<dashwood@removethis.enternet.co.nz> wrote:
> On the web service from Java...
> I see the real problem as being able to access COM from Java (Once you
> establish connection to the SOAP COM proxy, the rest is just stamp
> collecting :-)). Bearing this in mind, I found that IBM are offering an
> approach that is free and looks very useful. I have downloaded their
> Bridge2Java software from the article "Bridging the gap to COM"
>
> http://www.ibm.com/developerworks/j...brary/j-bridge/
>
> From my web searches I found a number of offerings that did the same;
> some
> of them were really excellent, but expensive...
>
> If I can find some time and need a break from C# and Web stuff, I'll
> attempt
> to implement the Java link to the web service.
>
> However, it might be interesting to compare the IBM approach with the
> Axis
> one, so please do it if you have time or need to bury yourself in
> something
> that may help to take your mind off your immmediate problems. (In the
> course
> of my life I have found working to be a very useful therapy when trauma
> strikes...but that might just be me.)
I've only been browsing this thread, so maybe I'm not understanding, but why
do you feel the need to use COM from Java to be able to do SOAP stuff?
There is Java support out there for SOAP. Specifically, the
org.apache.soap.* and org.apache.soap.rpc.* packages. (I'm sure there are
others.)
My only experience with this is utilizing a simple demo to access a
mainframe SOAP service from my PC, but it works.
Frank
|