About Question enthuware.ocejws.v6.2.158 :
Moderators: Site Manager, fjwalraven
-
- Posts: 25
- Joined: Wed Jun 24, 2015 7:26 am
- Contact:
About Question enthuware.ocejws.v6.2.158 :
Correct answer:The attachments in SwA are not part of the XML infoset. With MTOM they are.
Explanation: One of the benefits of MTOM and XOP is that the attachments are part of the SOAP message. This makes the use of WS-Security features easier and interoperability better
but in follow url https://docs.oracle.com/javaee/5/tutori ... bnbhg.html
that Attachments are part of the SOAP message too,
see fig. Figure 19-2 in the url and below
Explanation: One of the benefits of MTOM and XOP is that the attachments are part of the SOAP message. This makes the use of WS-Security features easier and interoperability better
but in follow url https://docs.oracle.com/javaee/5/tutori ... bnbhg.html
that Attachments are part of the SOAP message too,
see fig. Figure 19-2 in the url and below
-
- Posts: 429
- Joined: Tue Jul 24, 2012 2:43 am
- Contact:
Re: About Question enthuware.ocejws.v6.2.158 :
True, but they are not part of the XML Infoset and that is the difference between SwA and MTOM.that Attachments are part of the SOAP message too,
MTOM is effectively SwA+XOP.
XOP is the key to this, it describes how you can serialize SOAP messages with binary content and still preserve the XML Infoset.
Or in other words: for a SOAP endpoint the MTOM attachments are just embedded SOAP elements.
Regards,
Frits
-
- Posts: 124
- Joined: Wed Feb 12, 2014 2:44 am
- Contact:
Re: About Question enthuware.ocejws.v6.2.158 :
Hello ,
1- Spelling issue "attachents" should be "attachment".
2- Can you please let me understand what you mean "XML infoset" here ?
1- Spelling issue "attachents" should be "attachment".
2- Can you please let me understand what you mean "XML infoset" here ?
-
- Posts: 429
- Joined: Tue Jul 24, 2012 2:43 am
- Contact:
Re: About Question enthuware.ocejws.v6.2.158 :
- Fixed: Thanks!
- Check this nice explanation:
Regards,
Frits
-
- Posts: 2
- Joined: Sun Oct 30, 2016 2:45 am
- Contact:
Re: About Question enthuware.ocejws.v6.2.158 :
Hi,
Just to confirm, I was under the impression that swaRef attachments were encoded whereas MTOM were not. Would this not increase the size of the data being transferred using swaRef making the first option correct?
Thanks.
Just to confirm, I was under the impression that swaRef attachments were encoded whereas MTOM were not. Would this not increase the size of the data being transferred using swaRef making the first option correct?
Thanks.
-
- Posts: 429
- Joined: Tue Jul 24, 2012 2:43 am
- Contact:
Re: About Question enthuware.ocejws.v6.2.158 :
Hi,
Just look at the example response for this WebService:
Regards,
Frits
No, the swaRef attachments are not encoded. They are sent as MIME attachments which can have any content.Just to confirm, I was under the impression that swaRef attachments were encoded whereas MTOM were not.
Just look at the example response for this WebService:
Code: Select all
@WebService
public interface GifService {
public @XmlAttachmentRef DataHandler getGifImage(String name);
}
Regards,
Frits
-
- Posts: 2
- Joined: Sun Oct 30, 2016 2:45 am
- Contact:
Re: About Question enthuware.ocejws.v6.2.158 :
Hi Frits,
Thanks for your quick reply. Perhaps I'm getting confused between SwA in general and swaRef? The solution to enthuware.ocejws.v6.2.142 indicated the below:
Thanks for your quick reply. Perhaps I'm getting confused between SwA in general and swaRef? The solution to enthuware.ocejws.v6.2.142 indicated the below:
With MTOM (unlike SwA) the binary data is not encoded in the attachment.
-
- Posts: 429
- Joined: Tue Jul 24, 2012 2:43 am
- Contact:
Re: About Question enthuware.ocejws.v6.2.158 :
That explanation is not correct. I have removed "unlike SwA" from the explanation.The solution to enthuware.ocejws.v6.2.142 indicated the below:
With MTOM (unlike SwA) the binary data is not encoded in the attachment.
Thanks for your feedback!
Frits
Who is online
Users browsing this forum: No registered users and 90 guests