[ http://issues.apache.org/jira/browse/CXF-109?page=all ]
Dan Diephouse reopened CXF-109:
-------------------------------
OK, this is a good start. While it accomplishes the goal of removing
isInSoapHeader, I think the semantics need tweaking. The bindinginfo itself
should be in charge of providing the body message parts and the soap message
parts.
For example:
public class BindingInfo ... {
public List<MessagePartInfo> getMessageParts(OperationInfo o) { ... }
public void setMessageParts(OperationInfo o, List<MessagePartInfo> parts) { ...
}
}
The WSDLServiceBuilder and the BindingInfoFactorys would be responsible for
setting this up. Similarly on the SoapBindingInfo:
public class SoapBindingInfo ... {
public List<MessagePartInfo> getHeaderMessageParts(OperationInfo o) { ... }
public void settHeaderMessageParts(OperationInfo o, List<MessagePartInfo>
parts) { ... }
}
These semantics align better with the WSDL model, are more intuitive to the
user, and I believe create more straightforward code in our interceptors, so
I'm reopening this issue.
> Remove isInSoapHeader() from service model
> ------------------------------------------
>
> Key: CXF-109
> URL: http://issues.apache.org/jira/browse/CXF-109
> Project: CXF
> Issue Type: Improvement
> Affects Versions: 2.0-M1
> Reporter: Dan Diephouse
> Assigned To: tli
> Fix For: 2.0-M1
>
>
> isInSoapHeader should NOT be part of the service model. We should pull down a
> list of body parts from the binding instead.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
