We have been asked to promote ICO usage and we heard many wonderful statements about how fast it is.
Unfortunately migration to ICO is not painless and often you will discover ICO limitation especially in handling the Java code embedded in your mapping.
I therefore decided to share all my findings that has been already shared with SAP through proper SAP messages and in some cases fixed with patch releases.
Pseudo code reported below could be used to change the content type and the name of the attachments or even only 1 of the attributes :
where
Attachment could be retrieved through
InputAttachments inputAttachments = globalContainer.getInputAttachments();
……some code…
scanning the entire vector of content IDs we could easily get the content ID of every single attachment
Attachment attachment = inputAttachments.getAttachment(contentId);
and therefore its content and content type
similar code is referenced here:
http://scn.sap.com/message/14160371#14160371
http://scn.sap.com/community/pi-and-soa-middleware/blog/2013/07/01/retaining-soap-adapter-attachment...
The attachment name is not reflected in the SOAP attachment name,as result missing the information about name and extension. Test has been performed with Advanco SFTP adpter.
The attachment handling might result in doubled attachment if using below reported instruction
Code:outputAttachments.removeAttachment(contentId);
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
8 | |
5 | |
5 | |
4 | |
4 | |
4 | |
4 | |
4 | |
3 | |
3 |