[SWS-442] Generated WSDL file does not contain xmime attribute "expectedContentTypes" present in xsd files. Created: 30/Oct/08  Updated: 04/May/12  Resolved: 18/Dec/08

Status: Closed
Project: Spring Web Services
Component/s: None
Affects Version/s: 1.5.4
Fix Version/s: 1.5.6

Type: Bug Priority: Major
Reporter: navin bhat Assignee: Arjen Poutsma
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 3d
Time Spent: Not Specified
Original Estimate: 3d

Spring Web Services 1.5.4
Apache Maven 2.0.9
Eclipse 3.3.2,Windows XP SP2

Attachments: File WSDL and Servlet Config Files.zip    


The attachment contains the following files,
1)Normal0.xsd-- schema file containing "xmime:expectedContentTypes" attribute.
2)Normal1.xsd-- schema file.
3)MyService.wsdl-- WSDL file generated using "org.springframework.ws.wsdl.wsdl11.DefaultWsdl11Definition" class.
4)spring-ws-servlet.xml-- Servlet config file used for generation of wsdl.

In spring-ws-servlet.xml file,
"org.springframework.ws.wsdl.wsdl11.DefaultWsdl11Definition" bean generates the wsdl file from the schemaCollection bean which uses the "org.springframework.xml.xsd.commons.CommonsXsdSchemaCollection" class.

The Normal0.xsd file,
uses the xmime:expectedContentTypes="application/octet-stream" attribute to specify binary data, but the wsdl generated by "org.springframework.ws.wsdl.wsdl11.DefaultWsdl11Definition" class does not contain the xmime attribute.The generated wsdl file "MyService.wsdl" is attached.

Without xmime attribute in generated wsdl file the client code generation will not have Datahandler class.

It is also observed that when i use "org.springframework.xml.xsd.SimpleXsdSchema" class for specifying xsd file, the xmime attribute is reflected in wsdl file.But this class cannot be used for multiple xsd files.

Kindly let me know if more info is required,

Thanks in advance ,
Navin Bhat

Comment by Arjen Poutsma [ 18/Dec/08 ]

I am pretty sure this is a Commons Xml Schema bug, though I will investigate further.

Comment by Arjen Poutsma [ 18/Dec/08 ]

Actually, it wasn't a Commons Xml schema bug, but a SWS bug.

Could you please try a recent (as of tonight) snapshot and try again?

Comment by Arjen Poutsma [ 04/May/12 ]

Closing old issues

Generated at Sun Dec 16 08:09:49 UTC 2018 using JIRA 7.9.2#79002-sha1:3bb15b68ecd99a30eb364c4c1a393359bcad6278.