unable to open a related artifact link to unc path via Webui
I am creating work item links of type "Related Artifacts" to point to
unc path with syntax like file:///<hostname>/<share>/filename.extention.
Such links open fine when opened from the Eclipse based RTC Client.
However, the same link does not open from the WebUI.
Is it a bug?
unc path with syntax like file:///<hostname>/<share>/filename.extention.
Such links open fine when opened from the Eclipse based RTC Client.
However, the same link does not open from the WebUI.
Is it a bug?
Accepted answer
This is as designed behavior.
The "Add Related Artifact" wizard is implemented with respect of java lang URI API http://docs.oracle.com/javase/1.5.0/docs/api/java/net/URI.html
that implements the URI spec - http://www.ietf.org/rfc/rfc2396.txt
The fact that a given client - Eclipse, WebUI, other - is able to open such link - support such links syntax - is out of RTC Product scope.
As an example - the Eclipse Client is able to handle such file:/// syntax.
This behavior is confirmed by the fact that some browsers partially support such syntax - some others do not.
Some clients browser may have a add-on that knows how to handle such URI.
jazz.net work item: https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/210671
The "Add Related Artifact" wizard is implemented with respect of java lang URI API http://docs.oracle.com/javase/1.5.0/docs/api/java/net/URI.html
that implements the URI spec - http://www.ietf.org/rfc/rfc2396.txt
The fact that a given client - Eclipse, WebUI, other - is able to open such link - support such links syntax - is out of RTC Product scope.
As an example - the Eclipse Client is able to handle such file:/// syntax.
This behavior is confirmed by the fact that some browsers partially support such syntax - some others do not.
Some clients browser may have a add-on that knows how to handle such URI.
jazz.net work item: https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/210671