If you attachments are reasonably sized (smaller than available RAM), then there should not be an issue carrying them in the message payload. If you're worried about performance, I would consider that transforming attachments is probably insignificant compared to the cost of storing them in the database.
Starting with the most important question, do you need to access or transform the attachments in your BPEL process? The reason I ask is because BPEL does not offer much support for accessing and manipulating large binary objects. Moreover, the Ode architecture is not optimized for handling such large objects -- it does not use streaming APIs -- so I believe you would be better off managing them outside of the engine. alex On 3/27/07, wolfgang10 <[EMAIL PROTECTED]> wrote:
Do I understand you right that there is no way to access the properties or attachments of the normalized message within ode? I guess the bpel engine would really be a bottleneck then in many scenarios. Every time I passed around a normalized message I would have to transfer the properties and attachments in one of the ways you mentioned. This would require amending the original message and adding the required data at each boundary of servicemix and ode. Is there no better way? Wolfgang Alex Boisvert wrote: > > There are a few options.... > > 1) Use Base64-encoded values in your message payload > 2) Pass around HTTP URLs pointing to your attachment > 3) Use the ESB's handler chains to bind your attachments to the message on > its way out. > > alex > > > On 3/27/07, wolfgang10 <[EMAIL PROTECTED]> wrote: >> >> >> Hello, >> >> Is it possible to process attachments in ode? >> Assume I use ode-jbi in servicemix. I receive a message which is sent >> over >> the esb as a normalized message. That is, it has an xml part and a binary >> attachment. What if I want to send the attachment to an external party >> using >> bpel. Is that possible? >> >> Thanks >> Wolfgang >> -- >> View this message in context: >> http://www.nabble.com/Attachment-tf3474259.html#a9696340 >> Sent from the Apache Ode User mailing list archive at Nabble.com. >> >> > > -- View this message in context: http://www.nabble.com/Attachment-tf3474259.html#a9697138 Sent from the Apache Ode User mailing list archive at Nabble.com.
