but if I try to send for example an image in byte array written in a file .txt, the ebxml file received has the byte array with wrong characters.To transfer binary attachments, it is recommended to use JMS as AQ expects base64 encoded attachment XML and if you are including binary attachment as content in attachment XML then it may get corrupted during base64 encoding and decoding. If I am not wrong then PS3 (220.127.116.11) has a known bug related to this. In my blog, I included binary attachment as reference in the attachment XML. To know that how to post attachment over JMS, you may refer -
however is there a Http service in Oracle B2B to connect to send a "classical SOAP message"?Generic SOAP is not supported as of now. AFAIK, the next patch set (18.104.22.168.0) will have a support for it.
and where does ebMS XSD need to be loadedDo you mean ebMS attachment XSD? If yes then you may need to load it in file adapter to read the attachment XML. You may also hard-code attachment XML in a variable (for testing purpose) in BPEL, instead of reading it from a file location.