You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wookie.apache.org by "Paul Sharples (Commented) (JIRA)" <ji...@apache.org> on 2012/03/08 18:57:57 UTC
[jira] [Commented] (WOOKIE-324) POSTing a widget to wookie should
return its config.xml metadata
[ https://issues.apache.org/jira/browse/WOOKIE-324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13225337#comment-13225337 ]
Paul Sharples commented on WOOKIE-324:
--------------------------------------
I've made a start on this and the original config.xml data is now returned. Still to do is to build a hybrid response with the startfile, icons etc made absolute urls on the server.
> POSTing a widget to wookie should return its config.xml metadata
> ----------------------------------------------------------------
>
> Key: WOOKIE-324
> URL: https://issues.apache.org/jira/browse/WOOKIE-324
> Project: Wookie
> Issue Type: Improvement
> Components: Wookie REST API
> Affects Versions: 0.10.0
> Environment: n/a
> Reporter: Paul Sharples
> Assignee: Paul Sharples
> Fix For: 0.10.0
>
>
> At present when a widget is added to wookie using the POST method, a status code is returned. It would be a handy feature if as part of this process, wookie also returned the xml metadata (or perhaps, even other types susch as json) back with the response. This way a calling application has access to the internal config.xml data without having to parse it.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira