Hello Mark,
Turns out that we have a potential usability problem. RMF seems to
hang, if a namespace that RMF does not know about is referenced.
For example, the tool extensions may be provided with a namespace in
the root element:
xmlns:rtf="http://pror.org/presentation/rtf"
If RMF already knows about this URL, then everything works fine.
But if not, then the parser tries to retrieve the URLs content. If
this URL exists but contains information that can not be parsed
properly, then we may have a problem. As third parties can
contribute arbitrary presentations, we cannot control this.
The namespace given is a good example for that. The URL currently
redirects to eclipse.org, but to a web page, not a schema. If the
ReqIF file contains elements from this namespace, and the
presentation is not installed, then RMF hangs for roughly 20 minutes
(!).
So the first question is: Do we even want to resolve external
namespaces, and is there a way to disable it?
And the second question: If the first is not possible (or not a good
idea), can we reduce the timeout? I looked, but could not find such
an option.
And last, to prevent this problem at least for our own
presentations, I would propose to change the URLs for all
RMF-Presentations to http://eclipse.org/rmf/..., and to ensure that
these really exist. Obviously, this will break existing
presentations. Considering that you wanted to change the
ToolExtension-Handling and its URL as well, we should coordinate
this to make sure it happens at the same time.
Thanks,
- Michael
|