Re: SOAP::Lite and uri/urn

I always thought that URIs had to have two forward slashes after the protocol. You wrote only one.

Update Well I goofed. URN does not mean URI. It does however look like you are using a reserved character (slash) in your namespace identifier. A probable reformulation of your URN: urn:SOAPY:echo. You'll want to revisit RFC 2141 at http://www.ietf.org/rfc/rfc2141.txt. The grammar is right up front so it's not imposing or anything.

Seeking Green geeks in Minnesota

Comment on Re: SOAP::Lite and uri/urn Download Code

Replies are listed 'Best First'.
Re: Re: SOAP::Lite and uri/urn by Anonymous Monk on Jan 22, 2003 at 15:31 UTC
Thanks for the response. This morning I changed: `$NS = "urn:SOAPY/Echo";` [download] to `$NS = "SOAPY/Echo";` [download] and it worked with no errors.	[reply] [d/l] [select]
Re^3: SOAP::Lite and uri/urn by diotalevi (Canon) on Jan 22, 2003 at 17:15 UTC
That's good you don't get an error. I'm sceptical of this approach though. The parameter name is URI. You mentioned URNs. "SOAPY/Echo" isn't valid as either a URI or as a URN. Either that or it's ok as a relative URI fragment but all in all this just looks fishy to me. Seeking Green geeks in Minnesota	[reply]