Isuru the guy who implemented JSON support in axis2 send some patches to jettision. I'll get the details from him and send it to you.
Thanks, Keith. On Mon, May 5, 2008 at 11:02 PM, Cristian Bullokles < [EMAIL PROTECTED]> wrote: > I don't know how to do that because in jettison page they don't have a > mailing list or something similar. > > > > > > On Mon, May 5, 2008 at 1:53 PM, keith chapman <[EMAIL PROTECTED]> > wrote: > > > Can we commit those fixes to jettison? > > > > Thanks, > > Keith. > > > > > > On Mon, May 5, 2008 at 9:32 PM, Cristian Bullokles < > > [EMAIL PROTECTED]> wrote: > > > > > sorry to jettison owners.. > > > > > > > > > > > > On Mon, May 5, 2008 at 1:01 PM, Cristian Bullokles < > > > [EMAIL PROTECTED]> wrote: > > > > > > > Well Keith, > > > > Seems like error is not in JSON support for Axis2. > > > > I've modified the jettison library and all is working fine, > > > > in both formats (Mapped and BadgerFish). > > > > I sent an email to the jetty owners in order to check if the > > > > lines modified don't cause problems in other kind of messages. > > > > > > > > > > > > Regards > > > > > > > > > > > > > > > > On Sun, May 4, 2008 at 11:41 AM, keith chapman < > > > > [EMAIL PROTECTED]> wrote: > > > > > > > > > Hi Cristian, > > > > > > > > > > Nice to hear that you got something working. The current > > > > > Formatters don't support that. BTW I know the guy who implemented JSON > > > > > support in axis2. I will be meeting him next week. I will ask him the > > > > > reasoning behind implementing it this way. For now you should be able > > > > > to > > > > > implement your requirement by hacking one of the above formatters. > > > > > > > > > > Thanks, > > > > > Keith. > > > > > > > > > > > > > > > On Sun, May 4, 2008 at 7:49 PM, Cristian Bullokles < > > > > > [EMAIL PROTECTED]> wrote: > > > > > > > > > > > Thanks Keith, > > > > > > Looks like something has started working. > > > > > > When i use: > > > > > > http://localhost:8080/axis2/services/Version/getVersion?response=application/json/badgerfish > > > > > > It works and return: > > > > > > > > > > > > {"ns:getVersionResponse":{"@xmlns":{"ns":"http:\/\/axisversion.sample"},"ns:return":{"$":"Hello > > > > > > I am Axis2 version service , My version is 1.4"}}} > > > > > > Now my problem is that i don't want to get namespaces > > > > > > in responses, but when i've used > > > > > > > > > > > > http://localhost:8080/axis2/services/Version/getVersion?response=application/json > > > > > > I've received the same fault. > > > > > > > > > > > > {"Fault":"<soapenv:Fault > > > > > > xmlns:soapenv=\"http:\/\/www.w3.org\/2003\/05\/soap-envelope\"><soapenv:Code><soapenv:Value>soapenv:Receiver<\/soapenv:Value><\/soapenv:Code><soapenv:Reason><soapenv:Text > > > > > > xml:lang=\"en-US\">Mapped formatted JSON with namespaces are not > > > > > > supported > > > > > > in Axis2. Make sure that your request doesn't include namespaces or > > > > > > use the > > > > > > Badgerfish > > > > > > convention<\/soapenv:Text><\/soapenv:Reason><soapenv:Detail > > > > > > \/><\/soapenv:Fault>"} > > > > > > > > > > > > You think that we can't use json format without > > > > > > namespaces using get? > > > > > > I need to create my own formatter? > > > > > > > > > > > > Thanks > > > > > > Cristian > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Sun, May 4, 2008 at 5:31 AM, keith chapman < > > > > > > [EMAIL PROTECTED]> wrote: > > > > > > > > > > > > > Hi Cristian, > > > > > > > > > > > > > > There are two json notations supported in axis2. > > > > > > > application/json/badgerfish and application/json. In this case > > > > > > > you need to > > > > > > > use the former. Add both formatters to your axis2.xml as below, > > > > > > > > > > > > > > <messageFormatter contentType="application/json" > > > > > > > > > > > > > > class="org.apache.axis2.json.JSONMessageFormatter"/> > > > > > > > <messageFormatter > > > > > > > contentType="application/json/badgerfish" > > > > > > > > > > > > > > class="org.apache.axis2.json.JSONBadgerfishMessageFormatter"/> > > > > > > > > > > > > > > Then you can try > > > > > > > c/badgerfish<http://localhost:8080/axis2/services/Version/getVersion?response=application/json> > > > > > > > > > > > > > > I updated the above module to map application/json/badgerfish > > > > > > > to ?response=json and application/json to > > > > > > > ?response=application/json > > > > > > > > > > > > > > Thanks, > > > > > > > Keith. > > > > > > > > > > > > > > > > > > > > > On Sun, May 4, 2008 at 1:12 AM, Cristian Bullokles < > > > > > > > [EMAIL PROTECTED]> wrote: > > > > > > > > > > > > > > > Now looks like the parser is working the response is json > > > > > > > > format but allways is a fault. like that: > > > > > > > > > > > > > > > > {"Fault":"<soapenv:Fault > > > > > > > > xmlns:soapenv=\"http:\/\/www.w3.org\/2003\/05\/soap-envelope\"><soapenv:Code><soapenv:Value>soapenv:Receiver<\/soapenv:Value><\/soapenv:Code><soapenv:Reason><soapenv:Text > > > > > > > > xml:lang=\"en-US\">Mapped formatted JSON with namespaces are > > > > > > > > not supported > > > > > > > > in Axis2. Make sure that your request doesn't include > > > > > > > > namespaces or use the > > > > > > > > Badgerfish > > > > > > > > convention<\/soapenv:Text><\/soapenv:Reason><soapenv:Detail > > > > > > > > \/><\/soapenv:Fault>"} > > > > > > > > > > > > > > > > My request is only a get from a browser: > > > > > > > > > > > > > > > > > > > > > > > > http://localhost:8080/axis2/services/Version/getVersion?response=application/json > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Sat, May 3, 2008 at 12:43 AM, keith chapman < > > > > > > > > [EMAIL PROTECTED]> wrote: > > > > > > > > > > > > > > > > > Hi Cristian, > > > > > > > > > > > > > > > > > > Have you engaged DynamicResponseHandler on the version > > > > > > > > > service? If you want to engage this blobally (That will > > > > > > > > > effect all services > > > > > > > > > running on your system) you can do so by adding <module > > > > > > > > > ref="DynamicResponseHandler"/> to your axis2.xml. > > > > > > > > > > > > > > > > > > Thanks, > > > > > > > > > Keith. > > > > > > > > > > > > > > > > > > > > > > > > > > > On Sat, May 3, 2008 at 1:53 AM, Cristian Bullokles < > > > > > > > > > [EMAIL PROTECTED]> wrote: > > > > > > > > > > > > > > > > > > > Hi all > > > > > > > > > > I've modified the axis2.xml file adding this > > > > > > > > > > lines: > > > > > > > > > > > > > > > > > > > > <messageFormatters> > > > > > > > > > > <messageFormatter > > > > > > > > > > contentType="application/json" > > > > > > > > > > > > > > > > > > > > class="org.apache.axis2.json.JSONMessageFormatter"/> > > > > > > > > > > > > > > > > > > > > <messageBuilders> > > > > > > > > > > <messageBuilder contentType="application/json" > > > > > > > > > > > > > > > > > > > > class="org.apache.axis2.json.JSONOMBuilder"/> > > > > > > > > > > > > > > > > > > > > Also as Keith said in a previous thread I've > > > > > > > > > > compiled and installed the module dynamic response: > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > http://wso2.org/repos/wso2/trunk/commons/dynamic-response/ > > > > > > > > > > > > > > > > > > > > Then i've restarted tomcat and all continues working > > > > > > > > > > at the same way, when i tried: > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > http://localhost:8080/axis2/services/Version/getVersion?response=application/json > > > > > > > > > > > > > > > > > > > > I've received the same XML response: > > > > > > > > > > > > > > > > > > > > <ns:getVersionResponse> > > > > > > > > > > <ns:return> > > > > > > > > > > Hello I am Axis2 version service , My version is 1.4 > > > > > > > > > > </ns:return> > > > > > > > > > > </ns:getVersionResponse> > > > > > > > > > > > > > > > > > > > > I'm using axis2 1.4 in tomcat6. > > > > > > > > > > > > > > > > > > > > Any idea? I need a JSON response when I invoke using > > > > > > > > > > REST with response=application/json > > > > > > > > > > > > > > > > > > > > Regards > > > > > > > > > > Cristian > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > > Keith Chapman > > > > > > > > > Senior Software Engineer > > > > > > > > > WSO2 Inc. > > > > > > > > > Oxygenating the Web Service Platform. > > > > > > > > > http://wso2.org/ > > > > > > > > > > > > > > > > > > blog: http://www.keith-chapman.org > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > Keith Chapman > > > > > > > Senior Software Engineer > > > > > > > WSO2 Inc. > > > > > > > Oxygenating the Web Service Platform. > > > > > > > http://wso2.org/ > > > > > > > > > > > > > > blog: http://www.keith-chapman.org > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > Keith Chapman > > > > > Senior Software Engineer > > > > > WSO2 Inc. > > > > > Oxygenating the Web Service Platform. > > > > > http://wso2.org/ > > > > > > > > > > blog: http://www.keith-chapman.org > > > > > > > > > > > > > > > > > > > > > > -- > > Keith Chapman > > Senior Software Engineer > > WSO2 Inc. > > Oxygenating the Web Service Platform. > > http://wso2.org/ > > > > blog: http://www.keith-chapman.org > > > > -- Keith Chapman Senior Software Engineer WSO2 Inc. Oxygenating the Web Service Platform. http://wso2.org/ blog: http://www.keith-chapman.org
