[
https://issues.apache.org/jira/browse/WOOKIE-171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12969736#action_12969736
]
Kris Popat commented on WOOKIE-171:
-----------------------------------
Have now uploaded a fix which means that illegal characters are stripped at the
point where wookie creates a folder for the widget. This fixed the problem on
windows with scheme only type ids such as somescheme:
These type of widgets with now load on windows and will also update correctly.
The other part of the issue with updates not working correctly for some widgets
has not been fixed, but the cause has been identified.
If a widget has no id or an id which doesn't currently pass the IRIValidator
test then a random id is generated for that widget.
When an updated version (or the same widget) is uploaded or hot deployed a new
random id is generated for the widget. As we also use the id to check if the
widget currently exists this type of widget is always uploaded never updated,
meaning that the older version of the same widget is in the system.
The question is do we alter the validation process for ids to allow more to
pass, do we find a different way of generating ids that don't conform or don't
exist which links it to the widget more closely or do we find a different way
of checking if the widget already exists?
> There is a suspected problem with the way the id handler of the manifest
> parser is managing odd characters
> ----------------------------------------------------------------------------------------------------------
>
> Key: WOOKIE-171
> URL: https://issues.apache.org/jira/browse/WOOKIE-171
> Project: Wookie
> Issue Type: Bug
> Components: Parser
> Affects Versions: 0.9.0
> Reporter: Kris Popat
> Assignee: Kris Popat
> Fix For: 0.9.0
>
>
> This problem has manifest itself in a couple of ways. There has been strange
> behaviour when uploading some of the w3c test widgets directly to the server
> rather than through the test rig. With the server running unix type systems
> the widget will not run correctly but on windows the widget will not load.
> The suspicion here is that the id handler is attempting to create folder
> names with path separators in them or other illegal characters.
> The other evidence pointing towards this issue is the update behaviour again
> on windows not working correctly. When the same widget is dropped into the
> hot deploy folder twice the second time wookie should update the widget, on
> windows, however, another installation of the widget is occuring.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
