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/02 07:53:32 UTC
[jira] Created: (WINK-161) Make SyndContent/AtomContent support
Object values instead of String
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.
[jira] Issue Comment Edited: (WINK-161) Make
SyndContent/AtomContent support Object values instead of String
Posted by "Michael Elman (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WINK-161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12752102#action_12752102 ]
Michael Elman edited comment on WINK-161 at 9/7/09 4:49 AM:
------------------------------------------------------------
xhtml is actually xml. It is surrounded with div element.
text and html should be strings.
was (Author: elman):
xhtml is actually xml. It is be surrounded with div element.
text and html should be strings.
> 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.
[jira] Commented: (WINK-161) Make SyndContent/AtomContent support
Object values instead of String
Posted by "Nick Gallardo (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WINK-161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12750442#action_12750442 ]
Nick Gallardo commented on WINK-161:
------------------------------------
Fair enough... a *slight* oversimplification. :)
I'm thinking mostly of the model where you set a JAXB object in the AtomContent when the type is "xml".
For the others ("text", "html", "xhtml"), what object types were you thinking would be set? Streams? If so, can an assumption for a first pass be that the content in each is properly formatted (escaped, etc.)?
> 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.
[jira] Resolved: (WINK-161) Make SyndContent/AtomContent support
Object values instead of String
Posted by "Michael Elman (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WINK-161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Elman resolved WINK-161.
--------------------------------
Resolution: Fixed
> 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.
[jira] Commented: (WINK-161) Make SyndContent/AtomContent support
Object values instead of String
Posted by "Nick Gallardo (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Closed: (WINK-161) Make SyndContent/AtomContent support
Object values instead of String
Posted by "Michael Elman (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WINK-161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Elman closed WINK-161.
------------------------------
> 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.
[jira] Commented: (WINK-161) Make SyndContent/AtomContent support
Object values instead of String
Posted by "Michael Elman (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WINK-161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12750433#action_12750433 ]
Michael Elman commented on WINK-161:
------------------------------------
bq. 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.
I wish it was that simple... :)
> 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.
[jira] Commented: (WINK-161) Make SyndContent/AtomContent support
Object values instead of String
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WINK-161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12752516#action_12752516 ]
Hudson commented on WINK-161:
-----------------------------
Integrated in Wink-Trunk-JDK1.5 #134 (See [http://hudson.zones.apache.org/hudson/job/Wink-Trunk-JDK1.5/134/])
Making SyndContent/AtomContent support Object values instead of String. See []
> 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.
[jira] Commented: (WINK-161) Make SyndContent/AtomContent support
Object values instead of String
Posted by "Michael Elman (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WINK-161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12752102#action_12752102 ]
Michael Elman commented on WINK-161:
------------------------------------
xhtml is actually xml. It is be surrounded with div element.
text and html should be strings.
> 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.