-
Type:
Feature Request
-
Status: Closed (View Workflow)
-
Priority:
Minor
-
Resolution: Done
-
Affects Version/s: EAP 5.0.1
-
Fix Version/s: EAP_EWP 5.1.0
-
Component/s: Documentation, Web Services
-
Labels:None
-
Affects:Release Notes
A getter signature of a return type class affects whether the response would be MTOM(XOP Include) or inline string in case that MTOM is enabled.
The return type class has a DataHandler field like:
@XmlRootElement
@XmlType(name = "imageResult")
public class ImageResult implements Serializable {
...
private DataHandler tiff;
@XmlMimeType("application/octet-stream")
@XmlElement(name = "tiff")
public DataHandler getTiff()
public void setTiff(DataHandler tiff)
{this.tiff = tiff;}}
If getTiff() is modified to getSometing(), then the response would be inline string.
Because...
On deploy time, ParameterMetaData is marked as XOP=true.
It depends on org.jboss.ws.extensions.xop.jaxws.ReflectiveAttachmentRefScanner.scanBean() and scanGetterAnnotation() [1].
So if the getter's signature doesn't conform javabean getter constraint "getTiff", ReflectiveAttachmentRefScanner will miss to mark it XOP=true.
This constraint should be documented.