Java client calling WSE 2.0 with DIME attachment

Question

I need to integrate with a legacy .NET Web Service that uses WSE 2.0 for WS-Security and DIME. The catch is I need to do this from a Java application.

I'm expecting that Axis2 works fine with the WS-Security because folks around here have done it before. It's the DIME that I'm concerned about. I see a reference to DIME at http://ws.apache.org/axis/java/client-side-axis.html, but I'm wondering if anyone has actually done this with Axis and a WSE 2.0 Web Service.

Answer 1

I can't tell you anything for sure from own expierence. And about every 2nd page on the "web" seems to state something different to this question.

So taking all together the following is all possible

1. Dime Support was dropped from 1.x to 2.x
2. Some kind of support in 2.x is there, possibly flaky
3. Support is there
4. No support at all is there
5. One of the provided links gives enough insight/code sample to get something useful going

Links to "Does Axis 2.0 support Dime"?

No. You have to switch back to 1.4

No some guy

large attachments in dime format -> btw the same guy which 2009 states he never has heard of Dime since 2002

Axis 1.x to Axis 2.1 port Dime -> againThe same guy 2006 posting something which looks like a port

Creating Apache Axis Java proxy classes that use DIME From some Adobe Docu site

J2EE Web Service Development with Attachments Using Axis -> The only real tutorial I found until now. But uses Axis 1.2.1

AttachmentProblems -> An Axis Wiki page stating problems with Dime attachment files > 1 MB

Answer 2

My investigation and experiments on this topic a year ago showed that Axis 2 doesn't supports DIME attachments despite the fact that there were some unclear notes in documentation and defines in the code. Now documentation is cleared up and there are no any notes on DIME support. But Axis 1.4 works with DIME attachments OK. Downgrade you Axis library to 1.4 if you can't force your partners to upgrade their service to support MTOM/XOP.

Answer 3

WSE 2.0 is hopelessly obsolete. If you must continue on using obsolete software, then you should at least upgrade to WSE 3.0, which is somewhat less obsolete.