DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13769>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13769 Group G: SwA/DIME (attachments) WSDL Problems Summary: Group G: SwA/DIME (attachments) WSDL Problems Product: Axis Version: 1.0 Platform: All URL: http://www.whitemesa.net/r4/interop4.html OS/Version: All Status: NEW Severity: Blocker Priority: Other Component: WSDL processing AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Here's the note from Sam to axis-dev: (http://marc.theaimsgroup.com/?l=axis-dev&m=103461290307024&w=2) Looking at the 4 WSDL documents defined as part of Group G at http://www.whitemesa.net/r4/interop4.html, I've encountered the following: 1) The WSDL appears to correctly specify xsd:base64Binary. Somehow, internal to WSDL2Java, this gets mapped to soap-enc:base64Binary, which does not exist. There are all sorts of places where this could be intercepted and converted into soap-enc:base64. Anybody have a preference? 2) wsdl.toJava.Utils.getMIMETypeQName doesn't handle the case where the mimeName is application/octetstream, and whenever this routine returns null wsdl2Java ends up with a NPE. Mapping it to Constants.MIME_PLAINTEXT does get WSDL2Java to process these WSDLs successfully, but the corect fix is probably to define a MIME_OCTETSTREAM. 3) I see nothing in WSDL2Java which detects dime:message, and sets call.ATTACHMENT_ENCAPSULATION_FORMAT appropriately. While this seems straightforward enough, I need to figure out what open vs closed for message layout means to Axis. - Sam Ruby
