AFAIK MTOM support in Axis2 XMLBeans data binding is broken for some time (my apologies if somebody fixed it recently)... People are not much motivated for supporting XMLBeans as it does not have the native binary support as ADB+Axiom has and all the binary data needs to be encoded back and forth to & from base64 when supporting MTOM with XML beans.
thanks, Thilina On Fri, Aug 15, 2008 at 7:45 AM, Damin <[EMAIL PROTECTED]> wrote: > > Currently using MTOM with ADB running through Axis2 http transport web > service in WebSphere 6.x - works great! Thanks. > > Need to support MQ interface running same service, cannot use Axis2 JMS > because running in J2EE WebSphere Container (the ole' setMessageListener() > problem that app server vendors imposed on the J2EE specification). So, > ADB > and MTOM appear to be out for this interface. > > You guys got any idea how to do this? > > 1) Have done XMLBeans with XOP from MQ (in 2 passes) before without Axis2. > Could do this, but the folks I work for want the same business code to be > run for both http and mq transports - novel idea. > 2) Cannot figure out how to get XMLBeans to do XOP running through Axis2, > it keeps making the binary data Base64 encoded instead of XOP - anyone > solved this. > > Looking for some directions/ideas at this point and thanks for your > replies. > > Damin > -- > View this message in context: > http://www.nabble.com/Binary-Data%2C-http-and-jms%2C-WebSphere-6.x-tp18997365p18997365.html > Sent from the Axis - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Thilina Gunarathne - http://thilinag.blogspot.com
