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

[jira] Commented: (WINK-161) Make SyndContent/AtomContent support Object values instead of String

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

Nick Gallardo commented on WINK-161:
------------------------------------

Big +1 from me.  This would be a huge help in terms of usability.  There's also potential for performance benefits.

Seems like you could just grab the content type and the object type and use that to do the same Provider resolution that is done for normal return types.  



> Make SyndContent/AtomContent support Object values instead of String
> --------------------------------------------------------------------
>
>                 Key: WINK-161
>                 URL: https://issues.apache.org/jira/browse/WINK-161
>             Project: Wink
>          Issue Type: Improvement
>          Components: Common
>    Affects Versions: 0.1
>            Reporter: Michael Elman
>            Assignee: Michael Elman
>             Fix For: 0.2
>
>
> Currently SyndContent/AtomContent accepts only String values.
> So if the user wants to put there xml content, he needs first serialize it String, and then add it.
> Another problem that we have is complexity in our Atom providers.
> It would very nice if we'll be able to handle content as Object and serialize it to required form using the Providers.

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