You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wink.apache.org by "Michael Elman (JIRA)" <ji...@apache.org> on 2009/09/15 12:31:57 UTC

[jira] Created: (WINK-182) Move json.org support to a separate module

Move json.org support to a separate module
------------------------------------------

                 Key: WINK-182
                 URL: https://issues.apache.org/jira/browse/WINK-182
             Project: Wink
          Issue Type: Improvement
          Components: Common
    Affects Versions: 0.1
            Reporter: Michael Elman
            Assignee: Michael Elman
             Fix For: 0.2


Following this discussion: http://n2.nabble.com/DISCUSS-JSON-implementations-td3635734.html#a3635734
Let's move json.org support to a separate module.

This issue may rise the following backward compatibility issues:
* JSONUtils is not internal class, but it will be moved.
* There would be no automatic json providers registered.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (WINK-182) Move json.org support to a separate module

Posted by "Michael Elman (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/WINK-182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Elman resolved WINK-182.
--------------------------------

    Resolution: Fixed

> Move json.org support to a separate module
> ------------------------------------------
>
>                 Key: WINK-182
>                 URL: https://issues.apache.org/jira/browse/WINK-182
>             Project: Wink
>          Issue Type: Improvement
>          Components: Common
>    Affects Versions: 0.1
>            Reporter: Michael Elman
>            Assignee: Michael Elman
>             Fix For: 0.2
>
>
> Following this discussion: http://n2.nabble.com/DISCUSS-JSON-implementations-td3635734.html#a3635734
> Let's move json.org support to a separate module.
> This issue may rise the following backward compatibility issues:
> * JSONUtils is not internal class, but it will be moved.
> * There would be no automatic json providers registered.
> * json.org was used to produce badgerfish format out of JAXB. Actually it was done using Wink's inner ContentHandler. This won't be supported anymore. But badgerfish is still supported by jettison.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (WINK-182) Move json.org support to a separate module

Posted by "Michael Elman (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/WINK-182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Elman updated WINK-182:
-------------------------------

    Description: 
Following this discussion: http://n2.nabble.com/DISCUSS-JSON-implementations-td3635734.html#a3635734
Let's move json.org support to a separate module.

This issue may rise the following backward compatibility issues:
* JSONUtils is not internal class, but it will be moved.
* There would be no automatic json providers registered.
* json.org was used to produce badgerfish format out of JAXB. Actually it was done using Wink's inner ContentHandler. This won't be supported anymore. But badgerfish is still supported by jettison.

  was:
Following this discussion: http://n2.nabble.com/DISCUSS-JSON-implementations-td3635734.html#a3635734
Let's move json.org support to a separate module.

This issue may rise the following backward compatibility issues:
* JSONUtils is not internal class, but it will be moved.
* There would be no automatic json providers registered.


> Move json.org support to a separate module
> ------------------------------------------
>
>                 Key: WINK-182
>                 URL: https://issues.apache.org/jira/browse/WINK-182
>             Project: Wink
>          Issue Type: Improvement
>          Components: Common
>    Affects Versions: 0.1
>            Reporter: Michael Elman
>            Assignee: Michael Elman
>             Fix For: 0.2
>
>
> Following this discussion: http://n2.nabble.com/DISCUSS-JSON-implementations-td3635734.html#a3635734
> Let's move json.org support to a separate module.
> This issue may rise the following backward compatibility issues:
> * JSONUtils is not internal class, but it will be moved.
> * There would be no automatic json providers registered.
> * json.org was used to produce badgerfish format out of JAXB. Actually it was done using Wink's inner ContentHandler. This won't be supported anymore. But badgerfish is still supported by jettison.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (WINK-182) Move json.org support to a separate module

Posted by "Hudson (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/WINK-182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12755469#action_12755469 ] 

Hudson commented on WINK-182:
-----------------------------

Integrated in Wink-Trunk-JDK1.5 #150 (See [http://hudson.zones.apache.org/hudson/job/Wink-Trunk-JDK1.5/150/])
    remove JSON providers.
See []


> Move json.org support to a separate module
> ------------------------------------------
>
>                 Key: WINK-182
>                 URL: https://issues.apache.org/jira/browse/WINK-182
>             Project: Wink
>          Issue Type: Improvement
>          Components: Common
>    Affects Versions: 0.1
>            Reporter: Michael Elman
>            Assignee: Michael Elman
>             Fix For: 0.2
>
>
> Following this discussion: http://n2.nabble.com/DISCUSS-JSON-implementations-td3635734.html#a3635734
> Let's move json.org support to a separate module.
> This issue may rise the following backward compatibility issues:
> * JSONUtils is not internal class, but it will be moved.
> * There would be no automatic json providers registered.
> * json.org was used to produce badgerfish format out of JAXB. Actually it was done using Wink's inner ContentHandler. This won't be supported anymore. But badgerfish is still supported by jettison.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Closed: (WINK-182) Move json.org support to a separate module

Posted by "Michael Elman (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/WINK-182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Elman closed WINK-182.
------------------------------


> Move json.org support to a separate module
> ------------------------------------------
>
>                 Key: WINK-182
>                 URL: https://issues.apache.org/jira/browse/WINK-182
>             Project: Wink
>          Issue Type: Improvement
>          Components: Common
>    Affects Versions: 0.1
>            Reporter: Michael Elman
>            Assignee: Michael Elman
>             Fix For: 0.2
>
>
> Following this discussion: http://n2.nabble.com/DISCUSS-JSON-implementations-td3635734.html#a3635734
> Let's move json.org support to a separate module.
> This issue may rise the following backward compatibility issues:
> * JSONUtils is not internal class, but it will be moved.
> * There would be no automatic json providers registered.
> * json.org was used to produce badgerfish format out of JAXB. Actually it was done using Wink's inner ContentHandler. This won't be supported anymore. But badgerfish is still supported by jettison.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.