Enver

The mustUnderstand is not part of the schema. I'm guessing the schema
applies to the SOAP body, but the mustUnderstand headers are part of
the headers. Neither Axis nor Axis2 needs the schema at runtime.

Can you attach an example SOAP message and the exceptions?

Paul



On 4/11/07, Enver ALTIN <[EMAIL PROTECTED]> wrote:
Hi,

I'm trying to implement 3GPP MM7[1] DeliverReq service. After
importing the xsd and creating the wsdl file by hand I was able to
generate required code using Eclipse. That was easy.

But I'm in a weird situation that's a bit hard to explain. Given that:

  * I have absolutely no control over the XML schema.
  * I have absolutely no control over the clients that will connect to
the DeliverReq port I'll be providing.
  * Both clients and the service port will be in extremely restrictive
networks where firewalls only permit access to hosts and ports
specified; even DNS is not allowed. Thus, both ends don't have access
to XML Schema.
  * MM7 requires SOAP mustUnderstand="1"

These clients can actually connect to the port I provide, and the SOAP
header and body looks sane. But... Axis spits out fireworks of
exceptions about the mustUnderstand thing, I guess that's because XML
schema is not available at runtime.

So here comes the question. Can I just download the xsd and deploy it
along with my webapp and configure 'something' so it will just use the
existing schema?

Another comes. What if the folks at 3gpp accidentally move the xsd
file to some other folder? Will my service stop working?

Thanks a lot,

[1] 
http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-6-MM7-1-4.xsd
--
Enver

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




--
Paul Fremantle
VP/Technology, WSO2 and OASIS WS-RX TC Co-chair

http://bloglines.com/blog/paulfremantle
[EMAIL PROTECTED]

"Oxygenating the Web Service Platform", www.wso2.com

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to