[
https://issues.apache.org/jira/browse/WOOKIE-383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13474955#comment-13474955
]
Sebastian M commented on WOOKIE-383:
------------------------------------
Thank you! It's working like a charm.
> Redeploying widget without id in config.xml creates new widget
> --------------------------------------------------------------
>
> Key: WOOKIE-383
> URL: https://issues.apache.org/jira/browse/WOOKIE-383
> Project: Wookie
> Issue Type: Bug
> Components: Wookie REST API
> Reporter: Sebastian M
> Fix For: 0.13.0
>
>
> I have a widget without an id in the config.xml. When deploying it to Wookie,
> it generates an own id.
> The Wookie REST API offers me a redeploying feature by performing an HTTP PUT
> request on /wookie/widgets/<widgetId> (e.g.
> /wookie/widgets/http%3A%2F%2Fincubator.apache.org%2Fwookie%2Fgenerated%2FEDB90FB8-C426-601B-8D60-7BDA095AF821
> )
> Now when I get the flatpack of the widget, modify it, and redeploy it using
> the current active widgetId in the URL (which was generated by Wookie),
> Wookie creates a new widget ID for it, and I have deployed it twice to wookie
> - with two different IDs. It seems to just deploy it from scratch, ignoring
> the passed widget ID in the URL.
> I don't know if this behaviour is intended or not but I would like to be able
> to redeploy a widget without an ID and replace the current one with the new
> widget file. Again I'm using the latest trunk version.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
