You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@axis.apache.org by Kasun Indrasiri <ka...@gmail.com> on 2007/05/17 20:06:23 UTC
JSON Support for Axis2C
Hi all,
I have been working on the initial development phase of the JSON
support for Axis2C project. (GSoC 2007 project). I used a JSON Object
model which is available on http://oss.metaparadigm.com/json-c/ and
using that object model I have implemented few components where we can
give the JSON string and get the relevant JSON object. So, any valid
JSON string can be converted to an in-memory JSON object.
Since the JSON string cannot be parsed inline using neither Badgerfish
nor Mapped, conversion of JSON string to JSON object is the initial
stage of the project. After forming the JSON object, the object should
be passed to the StAX parser. I designed a single StAX parser which
can use the either 'Badgerfish' or 'Mapped' conventions to parser the
JSON object and the convention should be initialize when the parser is
creating. Also I thoroughly studied about the two conventions and
areas where we have to be more conscious when we are parsing JSON
strings.
I planned to implement the StAX parser for a specific convention as an
initial step. In a generic StAX parser there should be a 'next'
method. So, in this case, as we call the 'next' method the parser
should traverse (or move) through the given JSON object and the
relevant StAX events should be triggered. These days I'm working on
the design and the implementation of that part.
I have few doubts regarding the license JSON-C implementation.
I want to clarify that whether I can use this free JSON-C
implementation with Apache license. Therefore I included the copyright
notice below.
------------------------------------------------------------------------------------------------------------------
Copyright (c) 2004, 2005 Metaparadigm Pte Ltd
Permission is hereby granted, free of charge, to any person obtaining a
copy of this software and associated documentation files (the "Software"),
to deal in the Software without restriction, including without limitation
the rights to use, copy, modify, merge, publish, distribute, sublicense,
and/or sell copies of the Software, and to permit persons to whom the
Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included
in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
BRIAN PAUL BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN
AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
------------------------------------------------------------------------------------------------------------------
I'm so pleased to have any of your comments and guidelines regarding
this project.
Thanks,
Kasun Indrasiri.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
Re: JSON Support for Axis2C
Posted by Samisa Abeysinghe <sa...@gmail.com>.
Samisa Abeysinghe wrote:
> Kasun Indrasiri wrote:
>> Hi all,
>> I have been working on the initial development phase of the JSON
>> support for Axis2C project. (GSoC 2007 project). I used a JSON Object
>> model which is available on http://oss.metaparadigm.com/json-c/ and
>> using that object model I have implemented few components where we can
>> give the JSON string and get the relevant JSON object. So, any valid
>> JSON string can be converted to an in-memory JSON object.
>> Since the JSON string cannot be parsed inline using neither Badgerfish
>> nor Mapped, conversion of JSON string to JSON object is the initial
>> stage of the project. After forming the JSON object, the object should
>> be passed to the StAX parser. I designed a single StAX parser which
>> can use the either 'Badgerfish' or 'Mapped' conventions to parser the
>> JSON object and the convention should be initialize when the parser is
>> creating. Also I thoroughly studied about the two conventions and
>> areas where we have to be more conscious when we are parsing JSON
>> strings.
>> I planned to implement the StAX parser for a specific convention as an
>> initial step. In a generic StAX parser there should be a 'next'
>> method. So, in this case, as we call the 'next' method the parser
>> should traverse (or move) through the given JSON object and the
>> relevant StAX events should be triggered. These days I'm working on
>> the design and the implementation of that part.
> Have you looked into our wrapper API for StAX parsing? I think you
> should have a look into that API before starting any work on this,
> because you need to plug that into the Axis2/C engine.
>> I have few doubts regarding the license JSON-C implementation.
>>
>> I want to clarify that whether I can use this free JSON-C
>> implementation with Apache license. Therefore I included the copyright
>> notice below.
> This looks OK to me. However, best is to ask the ASF license
> specialists, write to license@apache.org
> You can also have a look at the arcives to see if this has been
> already discussed:
> http://issues.apache.org/eyebrowse/SummarizeList?listName=license@apache.org&by=thread
>
Well the above link is broken, the archive is really here:
http://mail-archives.apache.org/mod_mbox/archive-license/
>
> Samisa...
>
--
Samisa Abeysinghe : http://www.bloglines.com/blog/samisa
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
Re: JSON Support for Axis2C
Posted by Samisa Abeysinghe <sa...@gmail.com>.
Kasun Indrasiri wrote:
> Hi all,
> I have been working on the initial development phase of the JSON
> support for Axis2C project. (GSoC 2007 project). I used a JSON Object
> model which is available on http://oss.metaparadigm.com/json-c/ and
> using that object model I have implemented few components where we can
> give the JSON string and get the relevant JSON object. So, any valid
> JSON string can be converted to an in-memory JSON object.
> Since the JSON string cannot be parsed inline using neither Badgerfish
> nor Mapped, conversion of JSON string to JSON object is the initial
> stage of the project. After forming the JSON object, the object should
> be passed to the StAX parser. I designed a single StAX parser which
> can use the either 'Badgerfish' or 'Mapped' conventions to parser the
> JSON object and the convention should be initialize when the parser is
> creating. Also I thoroughly studied about the two conventions and
> areas where we have to be more conscious when we are parsing JSON
> strings.
> I planned to implement the StAX parser for a specific convention as an
> initial step. In a generic StAX parser there should be a 'next'
> method. So, in this case, as we call the 'next' method the parser
> should traverse (or move) through the given JSON object and the
> relevant StAX events should be triggered. These days I'm working on
> the design and the implementation of that part.
Have you looked into our wrapper API for StAX parsing? I think you
should have a look into that API before starting any work on this,
because you need to plug that into the Axis2/C engine.
> I have few doubts regarding the license JSON-C implementation.
>
> I want to clarify that whether I can use this free JSON-C
> implementation with Apache license. Therefore I included the copyright
> notice below.
This looks OK to me. However, best is to ask the ASF license
specialists, write to license@apache.org
You can also have a look at the arcives to see if this has been already
discussed:
http://issues.apache.org/eyebrowse/SummarizeList?listName=license@apache.org&by=thread
Samisa...
--
Samisa Abeysinghe : http://www.bloglines.com/blog/samisa
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org