xWeb Namespace
The namespace of xWeb is http://www.avectra.com/2005.
Since this namespace is in the form of a URL, a common confusion and mistake is that this is the URL of the xWeb web service. http://www.avectra.com/2005 is not the URL of the web service. It is not the location of the schema.
The URL of xWeb endpoint is in the following form:
https://netforumsite/xweb/secure/netForumXML.asmx
where netformsite is the actual host name of the netFORUM application, for example, www.abcde.org.
Formatting Requests with Namespace
Many of the complex xWeb Objects such as Shopping Cart Object, Registrant Object require setting the namespace correctly when these Objects are passed as parameters to web methods.
When you send a request, you have two options.
You can set a default namespace in the parameter you pass, as shown on lines 9 and 24. This option is preferable because it's shorter and easier to read by a human for troubleshooting/diagnostics.
Alternately, you can provide a namespace for every element, for example:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns="http://www.avectra.com/2005/">
<soapenv:Header>
<ns:AuthorizationToken>
<ns:Token>?</ns:Token>
</ns:AuthorizationToken>
</soapenv:Header>
<soapenv:Body>
<ns:WEBCentralizedShoppingCartGetEventFees>
<ns:oRegistration>
<ns:CurrentKey>?</ns:CurrentKey>
<ns:Registrant>
<ns:reg_prod_qty>?</ns:reg_prod_qty>
<ns:reg_key>?</ns:reg_key>
<ns:reg_cst_key>?</ns:reg_cst_key>
<!-- additional elements omitted for brevity -->
</ns:Registrant>
<ns:Individual>
<ns:ind_cst_key>?</ns:ind_cst_key>
<ns:ind_prf_code>?</ns:ind_prf_code>
<ns:ind_first_name>?</ns:ind_first_name>
</ns:Individual>
<!-- additional Data Object nodes omitted for brevity -->
</ns:oRegistration>
<ns:oCOE>
<ns:CurrentKey>?</ns:CurrentKey>
<ns:Invoice>
<ns:inv_key>?</ns:inv_key>
<ns:inv_proforma>?</ns:inv_proforma>
<ns:inv_code>?</ns:inv_code>
<!-- additional elements omitted for brevity -->
</ns:Invoice>
<!-- additional Data Object nodes omitted for brevity -->
</ns:oCOE>
</ns:WEBCentralizedShoppingCartGetEventFees>
</soapenv:Body>
</soapenv:Envelope>
Either of these requests will work. The major difference between the two is that in the first request, we default the namespace in the parameter, and we omit the namespace for the elements within each parameter. This line will default the namespace for all elements within the parameter:
<oRegistration xmlns="http://www.avectra.com/2005/">
You must do this for each parameter.
Namespaces in xWeb Responses
When most xWeb web methods return a response, the response provides a default namespace, as shown here in the <AuthorizationToken> node on line 4 and the <WEBCentralizedShoppingCartGetEventFeesResponse> node on line 9.