|
View:
New views
3 Messages
—
Rating Filter:
Alert me
|
|
|
URL Template IssuesI'm using Beehive as the basis for a set of portlets running on WebLogic Portal Server 10.2.
When I click on any action link, an anchor representing that page link is being automatically created and embedded on the end of the URL [1], which causes the page to jump to that location. My usability team would prefer that the browser stays at the top of the page so that the navigation elements are always available. Walking through the debugger, it appears that the anchor reference is being stored as a URL fragment element, which I thought would be written to the {url:fragment} token in the URL templates. However, the URLs defined in the beehive-url-template-config.xml [2] don't include that token - so I'm not sure why the fragment is being appended to the URL. I've confirmed that the patterns defined in the file are being used, so it's not that the file is ignored. I can't seem to figure out where the fragment is coming from or how to stop it from rendering. Thanks for any help, Dan Turkenkopf [1] Example URL: https://www.mysite.com/context/myportal.portal?page=my_portal_page#myactionlink [2] See attached file <?xml version="1.0" encoding="UTF-8"?> <url-template-config xmlns="http://beehive.apache.org/netui/2004/server/url-template-config" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://beehive.apache.org/netui/2004/server/url-template-config ,DanaInfo=.awfdpenrGm6msm0utPv5ATx25.3H+url-template-config.xsd"> <url-template> <name>default</name> <value> /{url:path}?{url:queryString}{url:currentPage} </value> </url-template> <url-template> <name>default-complete</name> <value> /{url:prefix}/{url:path}?{url:queryString}{url:currentPage} </value> </url-template> <url-template> <name>portlet-default</name> <value> /{url:path}?{url:queryString}{url:currentPage} </value> </url-template> <url-template> <name>portlet-secure-default</name> <value> /{url:path}?{url:queryString}{url:currentPage} </value> </url-template> <url-template> <name>portlet-action</name> <value> /{url:path}?{url:queryString}{url:currentPage} </value> </url-template> <url-template> <name>portlet-secure-action</name> <value> /{url:path}?{url:queryString}{url:currentPage} </value> </url-template> <url-template> <name>portlet-resource</name> <value> /{url:path}?{url:queryString} </value> </url-template> <url-template> <name>portlet-secure-resource</name> <value> /{url:path}?{url:queryString} </value> </url-template> <!-- Templates for consuming remote portlets --> <url-template> <name>wsrp-default</name> <value> /{url:path}?{url:queryString}&wsrp-urlType={wsrp-urlType}&wsrp-url={wsrp-url}&wsrp-requiresRewrite={wsrp-requiresRewrite}&wsrp-navigationalValues={wsrp-navigationalValues}&wsrp-navigationalState={wsrp-navigationalState}&wsrp-interactionState={wsrp-interactionState}&wsrp-mode={wsrp-mode}&wsrp-windowState={wsrp-windowState}&{weblogic-passthru} </value> </url-template> <url-template> <name>wsrp-secureDefault</name> <value> /{url:path}?{url:queryString}&wsrp-urlType={wsrp-urlType}&wsrp-url={wsrp-url}&wsrp-requiresRewrite={wsrp-requiresRewrite}&wsrp-navigationalValues={wsrp-navigationalValues}&wsrp-navigationalState={wsrp-navigationalState}&wsrp-interactionState={wsrp-interactionState}&wsrp-mode={wsrp-mode}&wsrp-windowState={wsrp-windowState}&{weblogic-passthru} </value> </url-template> <url-template> <name>wsrp-blockingAction</name> <value> /{url:path}?{url:queryString}&wsrp-urlType=blockingAction&wsrp-url={wsrp-url}&wsrp-requiresRewrite={wsrp-requiresRewrite}&wsrp-navigationalValues={wsrp-navigationalValues}&wsrp-navigationalState={wsrp-navigationalState}&wsrp-interactionState={wsrp-interactionState}&wsrp-mode={wsrp-mode}&wsrp-windowState={wsrp-windowState}&{weblogic-passthru} </value> </url-template> <url-template> <name>wsrp-render</name> <value> /{url:path}?{url:queryString}&wsrp-urlType=render&wsrp-url={wsrp-url}&wsrp-requiresRewrite={wsrp-requiresRewrite}&wsrp-navigationalValues={wsrp-navigationalValues}&wsrp-navigationalState={wsrp-navigationalState}&wsrp-interactionState={wsrp-interactionState}&wsrp-mode={wsrp-mode}&wsrp-windowState={wsrp-windowState}&{weblogic-passthru} </value> </url-template> <url-template> <name>wsrp-resource</name> <value> /{url:path}/resource?{url:queryString}&_nfpb=true&_portlet.renderResource=true&wsrp-urlType=resource&wsrp-url={wsrp-url}&wsrp-requiresRewrite={wsrp-requiresRewrite}&wsrp-resourceID={wsrp-resourceID}&wsrp-preferOperation={wsrp-preferOperation}&wsrp-resourceState={wsrp-resourceState}&wsrp-resourceCacheability={wsrp-resourceCacheability}&{weblogic-passthru} </value> </url-template> <url-template> <name>wsrp-secureBlockingAction</name> <value> /{url:path}?{url:queryString}&wsrp-urlType=blockingAction&wsrp-secureURL=true&wsrp-url={wsrp-url}&wsrp-requiresRewrite={wsrp-requiresRewrite}&wsrp-navigationalValues={wsrp-navigationalValues}&wsrp-navigationalState={wsrp-navigationalState}&wsrp-interactionState={wsrp-interactionState}&wsrp-mode={wsrp-mode}&wsrp-windowState={wsrp-windowState}&{weblogic-passthru} </value> </url-template> <url-template> <name>wsrp-secureRender</name> <value> /{url:path}?{url:queryString}&wsrp-urlType=render&wsrp-secureURL=true&wsrp-url={wsrp-url}&wsrp-requiresRewrite={wsrp-requiresRewrite}&wsrp-navigationalValues={wsrp-navigationalValues}&wsrp-navigationalState={wsrp-navigationalState}&wsrp-interactionState={wsrp-interactionState}&wsrp-mode={wsrp-mode}&wsrp-windowState={wsrp-windowState}&{weblogic-passthru} </value> </url-template> <url-template> <name>wsrp-secureResource</name> <value> /{url:path}/resource?{url:queryString}&_nfpb=true&_portlet.renderResource=true&wsrp-urlType=resource&wsrp-secureURL=true&wsrp-url={wsrp-url}&wsrp-requiresRewrite={wsrp-requiresRewrite}&wsrp-resourceID={wsrp-resourceID}&wsrp-preferOperation={wsrp-preferOperation}&wsrp-resourceState={wsrp-resourceState}&wsrp-resourceCacheability={wsrp-resourceCacheability}&{weblogic-passthru} </value> </url-template> </url-template-config> |
|
|
Re: URL Template IssuesThis feature is a Desktop property called "scrollToWindow" you can
disable it in the admin tools for that desktop Dan Turkenkopf wrote: > I'm using Beehive as the basis for a set of portlets running on > WebLogic Portal Server 10.2. > > When I click on any action link, an anchor representing that page link > is being automatically created and embedded on the end of the URL [1], > which causes the page to jump to that location. My usability team > would prefer that the browser stays at the top of the page so that the > navigation elements are always available. > > Walking through the debugger, it appears that the anchor reference is > being stored as a URL fragment element, which I thought would be > written to the {url:fragment} token in the URL templates. However, > the URLs defined in the beehive-url-template-config.xml [2] don't > include that token - so I'm not sure why the fragment is being > appended to the URL. > > I've confirmed that the patterns defined in the file are being used, > so it's not that the file is ignored. > > I can't seem to figure out where the fragment is coming from or how to > stop it from rendering. > > Thanks for any help, > > Dan Turkenkopf > > [1] Example URL: > https://www.mysite.com/context/myportal.portal?page=my_portal_page#myactionlink > > [2] See attached file > > Notice: This email message, together with any attachments, may contain > information of BEA Systems, Inc., its subsidiaries and affiliated > entities, that may be confidential, proprietary, copyrighted and/or > legally privileged, and is intended solely for the use of the > individual or entity named in this message. If you are not the > intended recipient, and have received this message in error, please > immediately return this by email and then delete it. |
|
|
|
| Free embeddable forum powered by Nabble | Forum Help |