Hi Stephanos, Unfortunately, it's really on the service provider to fix their broken implementation. You can of course get your client to work by patching the Axis2 code (it is open source after all :)) to remove the checks, but that would be sort of like patching a TCP stack to ignore window size requests.... (i.e. just wrong :))
--Glen On 10/18/2010 6:27 AM, Stephanos Piperoglou wrote: > > Hi guys, > > I'm using Axis2 to create a client for a web service that requires a custom > SOAP header with an unqualified name. Now, I know this breaks the SOAP spec > that requires a namespace for all header blocks, but unfortunately that's how > this service works and there's not much I can do about it. I've added a > handler to add the header with a null namespace and I get this axiom > exception: > > Exception in thread "Main Thread" _org.apache.axiom.om.OMException_: All the > SOAP Header blocks should be namespace qualified > at > org.apache.axiom.soap.impl.llom.soap11.SOAP11HeaderImpl.addHeaderBlock(_SOAP11HeaderImpl.java:65_) > > > Is there any way to bypass this check and force an unqualified header through? > > Regards, > Stephanos Piperoglou > Price Control > GTO - BAC IT > +44 20 754 59007 > > This mail is transmitted to you on behalf of the Great East London Software > Company > Diese Post wird Ihnen im Namen der Great East London Software Company > übermittelt > > > --- > > This e-mail may contain confidential and/or privileged information. If you > are not the intended recipient (or have received this e-mail in error) please > notify the sender immediately and delete this e-mail. Any unauthorized > copying, disclosure or distribution of the material in this e-mail is > strictly forbidden. > > Please refer to http://www.db.com/en/content/eu_disclosures.htm for > additional EU corporate and regulatory disclosures. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
