The SOAP spec defines two namespace URIs in Section 3 (http://www.w3.org/TR/SOAP/#_Toc478383492). These are the exact namespace URIs that must be used. For example, using any variation, such as not having the trailing '/', in an XML document would cause that document to fail validation against a schema.
Scott Nichol ----- Original Message ----- From: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, November 13, 2002 4:57 PM Subject: RE: Serializer + deployment descriptor > Scott, > > In the example you have given, the web service handles > http://xml.apache.org/soap gracefully by ridirecting > to http://xml.apache.org/soap/. I beleive similar graceful > handling should be implemented for finding type mapping. > In other words the trailing / should not cause finding > type mapping to fail -- since we know what the software > developer intended to do. From a user point of view > why should the trailing '/' be significant -- I am looking > for rationale behind the spec. If we find the rationale, > it may become apparent that the rationale may not apply > in type mapping situation. > > Soumen Sarkar. > > -----Original Message----- > From: Scott Nichol [mailto:snicholnews@;scottnichol.com] > Sent: Wednesday, November 13, 2002 11:00 AM > To: [EMAIL PROTECTED] > Subject: Re: Serializer + deployment descriptor > > > The URI spec is at http://www.ietf.org/rfc/rfc2396.txt. > > FWIW, trailing '/' is significant in the URL subset of URI. For > example, when I point Internet Explorer to http://xml.apache.org/soap, > the response it gets is > > HTTP/1.1 301 Moved Permanently > Date: Wed, 13 Nov 2002 18:53:18 GMT > Server: Apache/2.0.43 (Unix) > Location: http://xml.apache.org/soap/ > Content-Length: 308 > Connection: close > Content-Type: text/html; charset=iso-8859-1 > > <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> > <html><head> > <title>301 Moved Permanently</title> > </head><body> > <h1>Moved Permanently</h1> > <p>The document has moved <a > href="http://xml.apache.org/soap/";>here</a>.</p> > <hr /> > <address>Apache/2.0.43 Server at xml.apache.org Port 80</address> > </body></html> > > IE magically follows the redirection to show me a page, but I am > actually seeing http://xml.apache.org/soap/, not the exact URL I > originally requested. > > Scott Nichol > ----- Original Message ----- > From: <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Wednesday, November 13, 2002 1:20 PM > Subject: RE: Serializer + deployment descriptor > > > > I would like to get an explannation why putting a trailing > > '/' matter so much? From a semantic point of view, the following > > two namespace names > > > > http://schemas.xmlsoap.org/soap/encoding/ > > http://schemas.xmlsoap.org/soap/encoding > > > > looks the same and it is no fault of user > > that he could not get type mapping to work. > > > > Why should "simple ones that frustrate you the most" > > happen, with any software specification or implementation? > > > > Is this not a bug in some specification or implementation? > > > > Soumen Sarkar. > > > > -----Original Message----- > > From: Mattias Jiderhamn [mailto:mattias@;expertsystem.se] > > Sent: Wednesday, November 13, 2002 9:32 AM > > To: [EMAIL PROTECTED] > > Subject: RE: Serializer + deployment descriptor > > > > > > It's always the simple ones that frustrate you the most... > > > > Anyway, a HUGE thank you! > > > > > -----Original Message----- > > > From: Scott Nichol [mailto:snicholnews@;scottnichol.com] > > > Sent: Wednesday, November 13, 2002 6:26 PM > > > To: [EMAIL PROTECTED] > > > Subject: Re: Serializer + deployment descriptor > > > > > > > > > Try putting a trailing / on the encoding: > > > > > > http://schemas.xmlsoap.org/soap/encoding/ > > > > > > instead of > > > > > > http://schemas.xmlsoap.org/soap/encoding > > > > > > Scott Nichol > > > > > > ----- Original Message ----- > > > From: "Mattias Jiderhamn" <[EMAIL PROTECTED]> > > > To: <[EMAIL PROTECTED]> > > > Sent: Wednesday, November 13, 2002 4:12 AM > > > Subject: Serializer + deployment descriptor > > > > > > > > > > I am really, really tired of the fact that I can not get any type > > > mappings > > > > to work in the deployment desriptor. > > > > > > > > If I have the file: > > > > <isd:service xmlns:isd="http://xml.apache.org/xml-soap/deployment"; > > > > id="urn:ApiTest"> > > > > <isd:provider type="java" > > > > scope="Application" > > > > methods="isOk getIntPair getIntArray getIntPairArray > getNullObject > > > > getNullArray"> > > > > <isd:java class="se.exder.api.ApiTest" static="true" /> > > > > </isd:provider> > > > > <isd:faultListener> > > > > org.apache.soap.server.DOMFaultListener > > > > </isd:faultListener> > > > > > > > > <isd:mappings> > > > > <isd:map > encodingStyle="http://schemas.xmlsoap.org/soap/encoding"; > > > > xmlns:x="urn:ApiTest" qname="x:IntPair" > > > > javaType="se.exder.api.IntPair" > > > > > > > java2XMLClassName="org.apache.soap.encoding.soapenc.BeanSerializer" > > > > > > > > xml2JavaClassName="org.apache.soap.encoding.soapenc.BeanSerializer"/> > > > > </isd:mappings> > > > > </isd:service> > > > > > > > > and try to deploy it with > > > > java -classpath $CLASSPATH > > > org.apache.soap.server.ServiceManagerClient > > > > http://localhost/servlet/rpcrouter deploy filename.wsdd > > > > The mapping is never working (client says > > > > "java.lang.IllegalArgumentException: No Serializer found to > serialize > > > a > > > > 'se.exder.api.IntPair' using encoding style > > > > 'http://schemas.xmlsoap.org/soap/encoding/'") > > > > > > > > But if I input the exact same information in the admin page > > > > (/soap/deploy.jsp) everything works just fine. (See attached > > > sceenshots). > > > > > > > > I always undeploy the service before re-deploying. I have tried > the > > > latest > > > > build (2002-10-27) and I am still having the same problem. > > > > Why is this??? > > > > What can I do about it? > > > > > > > > > > > > > > ---------------------------------------------------------------------- > -- > > > -------- > > > > > > > > > > -- > > > > To unsubscribe, e-mail: > <mailto:soap-dev-unsubscribe@;xml.apache.org> > > > > For additional commands, e-mail: > <mailto:soap-dev-help@;xml.apache.org> > > > > > > > > > -- > > > To unsubscribe, e-mail: > <mailto:soap-dev-unsubscribe@;xml.apache.org> > > > For additional commands, e-mail: > <mailto:soap-dev-help@;xml.apache.org> > > > > > > > > > > -- > > To unsubscribe, e-mail: <mailto:soap-dev-unsubscribe@;xml.apache.org> > > For additional commands, e-mail: <mailto:soap-dev-help@;xml.apache.org> > > > > -- > > To unsubscribe, e-mail: <mailto:soap-dev-unsubscribe@;xml.apache.org> > > For additional commands, e-mail: <mailto:soap-dev-help@;xml.apache.org> > > > > > > > -- > To unsubscribe, e-mail: <mailto:soap-dev-unsubscribe@;xml.apache.org> > For additional commands, e-mail: <mailto:soap-dev-help@;xml.apache.org> > > -- > To unsubscribe, e-mail: <mailto:soap-dev-unsubscribe@;xml.apache.org> > For additional commands, e-mail: <mailto:soap-dev-help@;xml.apache.org> > > -- To unsubscribe, e-mail: <mailto:soap-dev-unsubscribe@;xml.apache.org> For additional commands, e-mail: <mailto:soap-dev-help@;xml.apache.org>
