Re: [soapbuilders] [ANN] Spray PolyMorph service
- Hi Steve,
> From: Steve Waring [mailto:swaring@...]Thank you. And I also thank you for special treatment
> Sent: Sunday, December 23, 2001 11:10 AM
> > Now, SOAP4R should get 100% in normal set, I hope. Would
> > you please re-re-re-run your test client again at your leisure?
> Looks good: your changes have removed the need for the
> "resume" tests. 
> I added a couple more tests;Interesting.
> The "(id = base64)" tests a multi-reference to an Array ofSince SOAP4R maps base64 data to a String for developer's
> bytes using the "special" inline rule  (serialization rule
> 6). SOAP4R echoes the value as a string. Note that Spray uses
> the type xsd:base64Binary not enc:base64, which may make this
> test invalid.
convenience, SOAP4R seems to lost type information.
Ruby's string can contain any data like:
$ ruby -e 'puts (( "\0" * 100 ).size)'
On the other hand, echoBase64 method in SOAP4R endpoint
returns base64 encoded string after converting it explicitly
> The "(pos - href href)" test is a form that Spray would neverMy understanding of ref-to-ref is in . The reason
> serialize, but may need to deserialize? My reading of the
> schema  is that it is valid for an element to have both id
> and href attributes, and I can not see anything in the rules
> that makes it illegal. An edited example is:
> <a href="#id1"/>
> <id1 id="id1" href="#id2"/>
> <id2 id="id2"><..../></id2>
why I think it is not allowed is the spec does not say
"it is allowed" explicitly. Others: how do you think?
In , I wrote "SOAP4R also supports ref-of-ref". You
nailed it's a lie. Possibly I broke href/id code. Good