search

javaee / metro-jax-ws

https://javaee.github.io/metro-jax-ws/
Other
132 stars 68 forks source link

MTOM with Axis2 clients & .Net clients #358

Closed glassfishrobot closed 17 years ago

glassfishrobot commented 17 years ago

We're in the process of trying to get Axis2 1.2 and .Net (WSE 3.0) clients running against our JAXWS server. In using JAXWS 2.1.1 we have no issues using MTOM with Axis2 1.2, but our .Net client runs into issues that was fixed by Bug 312. Unfortunately with the code fixed in #312 we now run into an issue with our Axis2 clients.

With Axis2 1.2 client running against a JAXWS 2.1.2M1 release we now receive a NullPointerException:

Excepetion occurred null java.lang.NullPointerException at org.apache.axiom.attachments.Attachments.getSOAPPartContentID(Attachments.java:331) at org.apache.axiom.attachments.Attachments.(Attachments.java:178) at org.apache.axis2.builder.BuilderUtil.createAttachmentsMap(BuilderUtil.java:407) at org.apache.axis2.builder.MIMEBuilder.processDocument(MIMEBuilder.java:35) at org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:130) at org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:77) at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:356) at org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:294) at com.sandvine.reporting.ReportingServicesStub.RunTimeSeriesReport(ReportingServicesStub.java:156) at com.sandvine.reporting.client.AxisRunTimeSeriesReport.main(AxisRunTimeSeriesReport.java:130)

The thread at http://forums.java.net/jive/thread.jspa?threadID=22605&tstart=45 seemed to indicate that it's a discrepancy in the interpretation of the MTOM spec. Is JAXWS 2.1.2M1 now compatible with the spec and this is now an Axis2 issue?

Thanks, Brendan

Environment

Operating System: All Platform: All

Affected Versions

[2.1.2]

glassfishrobot commented 17 years ago

Reported by breekie@java.net

glassfishrobot commented 17 years ago

jitu@java.net said: Assigning it to Vivek.

glassfishrobot commented 17 years ago

vivekp@java.net said: As part of #312 fix, we started writing Content-Id in the root MIME part and avoided writing start parameter as we always write the root part as the first MIME part. This is as per the MTOM and various RFC (2045 and 2387). so we are doing as per standards. I guess Axis client is not liking it. Its just a bug on them probably you should report there.

Anyway, since writing start parameter, although unnecessary and adds very little to the processing on the receiving side. So I have put a fix to write 'start' parameter on the Multipart/Related content-type, hopefully your axis client starts working with this.

glassfishrobot commented 17 years ago

breekie@java.net said: I've tested against our Axis2 client deployment and it now works! Thanks for all the support and quick turn around time, it's very much appreciated.

glassfishrobot commented 17 years ago

Was assigned to vivekp@java.net

glassfishrobot commented 7 years ago

This issue was imported from java.net JIRA JAX_WS-358

glassfishrobot commented 17 years ago

Marked as fixed on Thursday, June 21st 2007, 10:07:29 pm