Hi Ricardo, Yes, but I believe the user should handle these namespaces, if a customer needs to get a response in JSON format then the customer should use the JSON mapping, rather using XML mapping. [1]
[1] https://docs.wso2.com/display/DSS350/JSON+Mapping Thanks, Madhawa On Thu, Jul 27, 2017 at 2:24 PM, Ricardo De Souza <[email protected]> wrote: > Hi, > > I do not know if this is the correct channel if it is not please let me > know how I can request this improvements in the product. > > I got an error when trying to get the response in JSON format. > I created two queries with the same grouped by element and row name and no > namespace. The UI allows us to do this. > After adding a namespace for one of the queries it works. > My suggestion is to generate a unique namespace for the row namespace if > the user does not specify one. > > The error I got was: > > DS Code: DATABASE_ERROR > Source Data Service:- > Name: NorthwindDS > Location: \NorthwindDS.dbs > Description: N/A > Default Namespace: br.com.northwind > Current Request Name: _getemployee_employeeid > Current Params: {EmployeeID=8} > Nested Exception:- > DS Fault Message: Error in XML generation at StaticOutputElement.execute > DS Code: UNKNOWN_ERROR > Nested Exception:- > javax.xml.stream.XMLStreamException: Invalid Staring element > > Thanks > > > *Ricardo Souza | [email protected] <[email protected]> * > > > Solution Architect, Latin America | *WSO2* Inc. > > Mobile : +55 11 9 7563 8066 > > <http://wso2.com/signature> > -- *Madhawa Gunasekara* Senior Software Engineer WSO2 Inc.; http://wso2.com lean.enterprise.middleware mobile: +94 719411002 <+94+719411002> blog: *http://madhawa-gunasekara.blogspot.com <http://madhawa-gunasekara.blogspot.com>* linkedin: *http://lk.linkedin.com/in/mgunasekara <http://lk.linkedin.com/in/mgunasekara>*
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
