You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wink.apache.org by "Mike Rheinheimer (JIRA)" <ji...@apache.org> on 2010/02/11 16:56:28 UTC
[jira] Created: (WINK-254) AtomEntrySyndEntry content unavailable
in Wink client
AtomEntrySyndEntry content unavailable in Wink client
-----------------------------------------------------
Key: WINK-254
URL: https://issues.apache.org/jira/browse/WINK-254
Project: Wink
Issue Type: Bug
Components: Client
Affects Versions: 1.1
Reporter: Mike Rheinheimer
Fix For: 1.1
The content data in AtomEntrySyndEntry does not use the expected provider in the Wink client due to the fact that the client app execution thread is outside the scope of the providers cache. To remedy this, we need a way to set the providers on the content object so that they are used during unmarshalling when a client app calls entry.getValue
Will upload patch and commit fix shortly.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (WINK-254) AtomEntrySyndEntry content unavailable in
Wink client
Posted by "Mike Rheinheimer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WINK-254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mike Rheinheimer closed WINK-254.
---------------------------------
> AtomEntrySyndEntry content unavailable in Wink client
> -----------------------------------------------------
>
> Key: WINK-254
> URL: https://issues.apache.org/jira/browse/WINK-254
> Project: Wink
> Issue Type: Bug
> Components: Client
> Affects Versions: 1.1
> Reporter: Mike Rheinheimer
> Fix For: 1.1
>
> Attachments: WINK-254.patch
>
>
> The content data in AtomEntrySyndEntry does not use the expected provider in the Wink client due to the fact that the client app execution thread is outside the scope of the providers cache. To remedy this, we need a way to set the providers on the content object so that they are used during unmarshalling when a client app calls entry.getValue
> Will upload patch and commit fix shortly.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WINK-254) AtomEntrySyndEntry content unavailable
in Wink client
Posted by "Mike Rheinheimer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WINK-254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mike Rheinheimer updated WINK-254:
----------------------------------
Attachment: WINK-254.patch
> AtomEntrySyndEntry content unavailable in Wink client
> -----------------------------------------------------
>
> Key: WINK-254
> URL: https://issues.apache.org/jira/browse/WINK-254
> Project: Wink
> Issue Type: Bug
> Components: Client
> Affects Versions: 1.1
> Reporter: Mike Rheinheimer
> Fix For: 1.1
>
> Attachments: WINK-254.patch
>
>
> The content data in AtomEntrySyndEntry does not use the expected provider in the Wink client due to the fact that the client app execution thread is outside the scope of the providers cache. To remedy this, we need a way to set the providers on the content object so that they are used during unmarshalling when a client app calls entry.getValue
> Will upload patch and commit fix shortly.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (WINK-254) AtomEntrySyndEntry content unavailable
in Wink client
Posted by "Mike Rheinheimer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WINK-254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mike Rheinheimer resolved WINK-254.
-----------------------------------
Resolution: Fixed
Committed in 909044.
> AtomEntrySyndEntry content unavailable in Wink client
> -----------------------------------------------------
>
> Key: WINK-254
> URL: https://issues.apache.org/jira/browse/WINK-254
> Project: Wink
> Issue Type: Bug
> Components: Client
> Affects Versions: 1.1
> Reporter: Mike Rheinheimer
> Fix For: 1.1
>
> Attachments: WINK-254.patch
>
>
> The content data in AtomEntrySyndEntry does not use the expected provider in the Wink client due to the fact that the client app execution thread is outside the scope of the providers cache. To remedy this, we need a way to set the providers on the content object so that they are used during unmarshalling when a client app calls entry.getValue
> Will upload patch and commit fix shortly.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (WINK-254) AtomEntrySyndEntry content unavailable
in Wink client
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WINK-254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12832553#action_12832553 ]
Hudson commented on WINK-254:
-----------------------------
Integrated in Wink-Trunk-JDK1.5 #261 (See [http://hudson.zones.apache.org/hudson/job/Wink-Trunk-JDK1.5/261/])
: fix SyndContent to support use of providers during client call to getValue
> AtomEntrySyndEntry content unavailable in Wink client
> -----------------------------------------------------
>
> Key: WINK-254
> URL: https://issues.apache.org/jira/browse/WINK-254
> Project: Wink
> Issue Type: Bug
> Components: Client
> Affects Versions: 1.1
> Reporter: Mike Rheinheimer
> Fix For: 1.1
>
> Attachments: WINK-254.patch
>
>
> The content data in AtomEntrySyndEntry does not use the expected provider in the Wink client due to the fact that the client app execution thread is outside the scope of the providers cache. To remedy this, we need a way to set the providers on the content object so that they are used during unmarshalling when a client app calls entry.getValue
> Will upload patch and commit fix shortly.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.