You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wink.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2009/09/01 19:38:32 UTC

[jira] Commented: (WINK-69) Consider an Abdera Provider

    [ https://issues.apache.org/jira/browse/WINK-69?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12750003#action_12750003 ] 

Hudson commented on WINK-69:
----------------------------

Integrated in Wink-Trunk-JDK1.5 #127 (See [http://hudson.zones.apache.org/hudson/job/Wink-Trunk-JDK1.5/127/])
    Add Apache Abdera Provider

See []


> Consider an Abdera Provider
> ---------------------------
>
>                 Key: WINK-69
>                 URL: https://issues.apache.org/jira/browse/WINK-69
>             Project: Wink
>          Issue Type: New Feature
>          Components: Common
>            Reporter: Bryant Luk
>
> There are probably other Providers that we can look at but just bringing this first one out there.
> Since Abdera is also used for ATOM support, can we look into writing Apache Wink @Provider code?  I'm not suggesting any more standard built-in providers.  These should just be a lightweight one/two class addition with some tests.
> Maybe we can add an optional module for "nice to have" providers and then maybe add submodules underneath for each provider type?  I think we'd have to consider how to package these optional ones up to make it easier on developers.
> Not 0.1 blocking.

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