[prev in list] [next in list] [prev in thread] [next in thread] 

List:       axis-user
Subject:    Re: JiBX and attachments
From:       Andreas Veithen <andreas.veithen () gmail ! com>
Date:       2009-03-31 19:38:25
Message-ID: b67458760903311238k68ee56a9nd85dbd111f51736a () mail ! gmail ! com
[Download RAW message or body]

I'm not very familiar with the databinding stuff in Axis2, but I know
something about MTOM in Axis2. Maybe you can illustrate your point by
some code snippets?

Andreas

On Tue, Mar 31, 2009 at 11:10, Stephan A. Maciej
<stephanm@datenfriedhof.net> wrote:
> Hi,
>
> is it possible to use JiBX and, at the same time MTOM, i.e. use attachments
> for transfering large blobs from and to an Axis2 web service?
>
> To me it looks like JiBX isn't able to handle the externalization of blobs
> into attachments natively. So I've tried writing a custom JiBX
> marshaller/unmarshaller helper class for handling Java objects that
> represent blobs.
>
> From what I've seen in the stub code generated by wsdl2java, a
> MessageContext is created before the marshalling takes place. MessageContext
> does have an addAttachment method, so I tried to simply call that method
> from my marshalling helper. However, that doesn't work because I have no
> access to the current message context
> (MessageContext.getCurrentMessageContext() returns null).
>
> So, what would be if the stub code generated by wsdl2java would expose the
> MessageContext to marshalling code? I haven't tried hand-editing the stub
> code yet, because I'm unsure if this scenario would actually lead to a
> working (and sane) mechanism to generate attachments for generated SOAP
> messages. Would it?
>
> Thanks,
>
> Stephan
>
> ----------------------------------------------------------------
> This message was sent using IMP, the Internet Messaging Program.
>
>
[prev in list] [next in list] [prev in thread] [next in thread]