The Webtop URL parameter is a simple prefix. The object ID is appended to the
URL to generate the display URLs for each object. In some cases this might not
be general enough. A customer wants to use CenterStage URLs of the form
http://<server>/CenterStage/content/<repository>/;/<r_object_id>?version=T
The most obvious solution is to allow parameters like the Livelink connector
does:
http://<server>/CenterStage/content/<repository>/;/{0}?version=T
A related issue is that Webtop is very forgiving about incomplete DRLs and
returns a 200 response rather than a 404. Other URL patterns might be not work
as well, so we may need a more flexible approach to URL validation.
Original issue reported on code.google.com by jla...@google.com on 16 Jun 2010 at 7:21
Original issue reported on code.google.com by
jla...@google.com
on 16 Jun 2010 at 7:21