Jitendra Kotamraju wrote:
> Shouldn't you return null since the content type changes for each
> messasge ? On the other hand, if the method returns null, the content
> is buffered. At present transport calls this method only one time, and
> one could write XOP message to transport without buffering. With a
> change in the interface, we could do that.
I think only thing that needs to change is the boundary between each
message, I mean each call to getContentType will give a different
boundary value in the Content-Type string. I have to correct the else
condition, it should be checking for SOAP 1.2.
>
> Can the XOPEncoder extend MimeEncoder to use the MIME packaging
> functionality ?
Probably. I thought and will see what can be the common abstraction
between these 2.
-vivek.
>
> Jitu
>
>> public String getStaticContentType() {
>> if (version.compareTo(SOAPVersion.SOAP_11) == 0) {
>> return
>> "Multipart/Related;type=\"application/xop+xml\";type" +
>> soap11ContentType + ";" + boundary + "start-info="
>> + soap11ContentType;
>> } else {
>> return
>> "Multipart/Related;type=\"application/xop+xml\";type" +
>> soap12ContentType + ";" + boundary + "start-info="
>> + soap12ContentType;
>> }
>> }
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cvs-unsubscribe_at_jax-ws-sources.dev.java.net
> For additional commands, e-mail: cvs-help_at_jax-ws-sources.dev.java.net
>
--
Vivek Pandey
Web Services Standards and Technologies
Sun Microsystems Inc.