Loading ...
Sorry, an error occurred while loading the content.
Advanced Search
Author
Subject
Message
Special notice only

443 results from messages in soapbuilders

Advanced Search
  • +1 w/ respect to test suites. Interop plug-fests have played a critical functional role since the nexus Web services and are still important. They demonstrate interop and factilate discussion and action w/ respect to the 'grey-er' areas. Orthogonally, the lack of test suites w/ respect to growing number WS-* specs is rather alarming (imo) not mention some of the RECs. IMHO the...
    Matt Long Oct 12, 2005
  • Sorry I forgot the '\n' after first comment. What I'm trying to emphasize is the case where '\n' exists in position relative to comment processing, i.e., post line feed normalization and prior to processing the comment. If post LF normalization = \n text \n then the canonical form is exactly the same. Meaning that when processing the comment, one cannot blindly [prepend | append...
    Matt Long Sep 15, 2005
  • Yes, but... (1) (a) is the xml to canonicalize (I introduced #xD, #xA after then closing tag) (2) (b) represents the xml post line feed normalization (3) (c) is the form I think is correct (4) (d) is the form when you mandate a prepend of \n to the 'that' comment, which I think is incorrect because the \n currently exists in position. (a) text \r\n (b) text \n (c) - Correct Form (I...
    wmatthewlong Sep 15, 2005
  • Fetching Sponsored Content...
  • All, Canonical Xml[1] states the following in Processing Model[2]: "...Comment Nodes - ...For canonical XML with comments, generate the opening comment symbol (). Also, a trailing #xA is rendered after the closing comment symbol for comment children of the root node with a lesser document order than the document element, and a leading #xA is rendered before the opening comment...
    wmatthewlong Sep 14, 2005
  • All, Are there any tests available for C14N (Inclusive and/or Exclusive) where the results are in bytes, i.e., not plain text? Thx, -Matt
    wmatthewlong Sep 13, 2005
  • --- In soapbuilders@^$1, Glen Daniels wrote: > We made an *awful* lot of progress in soapbuilders early on, I think > it's just unfortunate that attentions turned to WS-I and shied away from > any "potentially controversial" stuff like defining interoperable > recordsets/hashes. > > --Glen +1 My rant... In the earliest days, interop was ad hoc progressive and successful. I do...
    wmatthewlong May 12, 2005
  • Is anyone currently supporting [1]? Also, is this on the WS-I radar for addressing XML Signature interop? [1]http://www.w3.org/TR/2004/WD-xml-id-20041109/ Much Thx, -Matt Long
    wmatthewlong Dec 9, 2004
  • Then... wsdl:output/soap:body/@namespacevalue is not significant in terms of RPC, which means this is not awkward (which is my point that the authors would have had the intent that namespace is significant and localName is not in the RPC wrapper element) I wonder if omitted from WSDL how many toolkits would break as @namespaceis optional [a] [a] http://www.w3.org/TR/wsdl.html#_soap...
    mlong@bridgetonconsulting.com Jan 22, 2004
  • V1.1 says "name" is not significant (as Bob points out), but it is unclear whether that equates to fully qualified name. It would seem awkward that the namespace is significant and the localName is not significant in terms of RPC. It would be equally awkward that the WSDL uses a output/@namespacethat the service does not send for the rpc wrapper element. Maybe everybody is correct...
    mlong@bridgetonconsulting.com Jan 22, 2004
  • +1 Certainly this practice is compliant w/ spec(s) as Glen elegantly points out. I would isolate the practice as an interop issue much the same as hashtables and datasets between differing toolkits, i.e., not a great choice for interoperability for a public service. That said, in the field these issues sprout up ALL the time. Thx, -Matt Long Quoting Glen Daniels : > > > > > Hi...
    mlong@bridgetonconsulting.com Jan 7, 2004