[
https://jira.jboss.org/jira/browse/JBWS-2708?page=com.atlassian.jira.plug...
]
Magesh Kumar B updated JBWS-2708:
---------------------------------
Description:
Consider a complex type
<complexType name="ArrayOfSwaRef">
<sequence>
<element maxOccurs="unbounded" minOccurs="0"
name="swaRef" nillable="true" type="wsi:swaRef"/>
</sequence>
</complexType>
Using wsconsume the type is mapped to the class:
@XmlAccessorType(XmlAccessType.FIELD)
@XmlType(name = "ArrayOfSwaRef", propOrder = {
"swaRef"
})
public class ArrayOfSwaRef {
@XmlAttachmentRef
protected List<DataHandler> swaRef;
....
}
Although if such a construct is allowed is debatable as API
http://java.sun.com/javase/6/docs/api/javax/xml/bind/annotation/XmlAttach... says
that the filed/property must always map to a DataHandler class, jbossws-native misses to
scan such parameter types properly and eventually the Content-Type is never set to
multipart/related on the wire.
was:
Consider a complex type
<complexType name="ArrayOfSwaRefs">
<sequence>
<element maxOccurs="unbounded" minOccurs="0"
name="swaRef" nillable="true" type="wsi:swaRef"/>
</sequence>
</complexType>
Using wsconsume the type is mapped to the class:
@XmlAccessorType(XmlAccessType.FIELD)
@XmlType(name = "ArrayOfSwaRef", propOrder = {
"swaRef"
})
public class ArrayOfSwaRef {
@XmlAttachmentRef
protected List<DataHandler> swaRef;
....
}
Although if such a construct is allowed is debatable as API
http://java.sun.com/javase/6/docs/api/javax/xml/bind/annotation/XmlAttach... says
that the filed/property must always map to a DataHandler class, jbossws-native misses to
scan such parameter types properly and eventually the Content-Type is never set to
multipart/related on the wire.
XmlAttachmentRef annotation on List<DataHandler> is not
identified as an Attachment part
----------------------------------------------------------------------------------------
Key: JBWS-2708
URL:
https://jira.jboss.org/jira/browse/JBWS-2708
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: jbossws-native
Affects Versions: jbossws-native-3.1.2
Reporter: Magesh Kumar B
Assignee: Magesh Kumar B
Fix For: jbossws-native-3.2.0
Consider a complex type
<complexType name="ArrayOfSwaRef">
<sequence>
<element maxOccurs="unbounded" minOccurs="0"
name="swaRef" nillable="true" type="wsi:swaRef"/>
</sequence>
</complexType>
Using wsconsume the type is mapped to the class:
@XmlAccessorType(XmlAccessType.FIELD)
@XmlType(name = "ArrayOfSwaRef", propOrder = {
"swaRef"
})
public class ArrayOfSwaRef {
@XmlAttachmentRef
protected List<DataHandler> swaRef;
....
}
Although if such a construct is allowed is debatable as API
http://java.sun.com/javase/6/docs/api/javax/xml/bind/annotation/XmlAttach... says
that the filed/property must always map to a DataHandler class, jbossws-native misses to
scan such parameter types properly and eventually the Content-Type is never set to
multipart/related on the wire.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira