[
https://issues.apache.org/jira/browse/WOOKIE-176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13091063#comment-13091063
]
Scott Wilson commented on WOOKIE-176:
-------------------------------------
I'm not sure its going to be possible to solve this satisfactorily - you could
make a best guess based on things like the title, description or even inspect
the file contents to get some sort of match % but I'm not sure I'd trust such
an algorithm to not make mistakes, potentially overwriting other widgets.
Perhaps we should just warn admins when they try to submit widgets which have
no identifiers, or provide a configuration option to reject widgets with no ID.
> Find an improved method for updating unidentified widgets
> ---------------------------------------------------------
>
> Key: WOOKIE-176
> URL: https://issues.apache.org/jira/browse/WOOKIE-176
> Project: Wookie
> Issue Type: Improvement
> Components: Parser
> Affects Versions: 0.9.0
> Reporter: Kris Popat
> Fix For: 0.9.1
>
>
> This issue is a follow-on from issue 171 which identified some problems with
> the manifest parser's handling of ids.
> Currently widgets that have no id or have an id which doesn't pass the
> IRIValidator test won't update when re-uploaded or re-deployed.
> This is because the in these cases a random id is being generated and it is
> ids which are used to indentfy if a widget already exists.
> We need to find a better method to identify and compare incoming widgets with
> ones already in the system - particularly as ids are an optional feature in
> the widget specification.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
