I actually hadn't thought about it in that way, Benson. Generally, we're looking to build some flexible libraries and services that will be inter-operable amongst different applications, so we may have to support calls from other libraries (like YUI, for example) for JSON format. I'm just doing some experimenting now, as nothing is written in stone as of yet.
-----Original Message----- From: Benson Margulies [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 15, 2008 7:18 AM To: [email protected] Cc: Vespa, Anthony J Subject: RE: Issues with JSON based Service and Jettison On Tue, 2008-01-15 at 00:32 -0500, Liu, Jervis wrote: > First of all, you need to set wrapped style to false, wrapped style true won't work with JSON (I noticed that you already set wrapped to false). What happened is Jettison reads input stream to a W3C Document, then this W3C Document is used to create a new XMLInputStream. From this point on, the following CXF interceptors will presume they are deal with a normal XML input e.g. the XML section embedded in a soap body. > > Let's take a concrete example. An inputstream of "{"acme.Book":{"acme.name":"CXF in Action "}}" is transferred to a org.w3c.dom.Document of <Book><name>CXF in Action</name></Book> by Jettison first, then the Document object will be marshaled to a Book object. The wrapper I am talking about is referring to the operation name wrapper of doc-lit wrapped style. For example, if you set wrapped style to true, in order to marshal the Document to Book object successfully, the Document's content need to be <addBook ><Book><name>CXF in Action</name></Book></addBook> instead. > Anthony: is the reverse of this what you originally imagined that the JavaScript support might do?
