- All Known Implementing Classes:
public interface INavigationRedirector
The interface that redirects the original URL that initiated the navigation
to a different URL. You do not have to implement a redirector for your
navigation connector. However, you can only register a redirector at the
same time that you register a navigation connector.
The prefix can either be an indication for a connector or a definition of
A redirector is responsible for translating the URL from the original URL
to another URL format. The returned object should always contain both the
URL and the new prefix. If the new prefix is a connector prefix, no
additional redirection is required. If the prefix is a redirector prefix,
then cascading redirection is required.
Note: A redirector is bound to a specific prefix, and is registered together
with the connector registration.
For example, when calling the client-side eventing
pcd:portal_content/portal/firstPage is not recognized by any registered
connector. This URL should first be redirected using the PCD redirector
implementation. Assume that in this case, the returned value contains the ROLES
prefix, so the URL can now be processed.
Examples of redirectors are:
- ROLESH (represents PCD hash code URLs) to PCD
- PCD to ROLES
- ROLESH to ROLES
- See Also:
INavigationRedirectorResult redirect(String oldURL,
- Redirects the specified URL to a format that can be read by either
one of the connectors or by another redirector implementation.
Note: A redirector must return a new prefix for the returned URL.
oldURL - the original URL, without its prefix
environment - the user context
- the translated URL and its new prefix
NamingException - if the original URL is not found
This class can be accessed from:
Copyright 2011 SAP AG Complete Copyright Notice