Your Development & Design Resource
IBM XPages Developers: Do you get the full URL from your XSPUrl?
03/07/2012 04:40:00 PM by Chris Toohey
Sometimes it's finding out what the problem actually is that's the biggest key to finding the solution.
I spent some time today writing an article on using URL fragments to create anchor tags in tabbedPanel Control-based XPages applications... only to find that the XSPUrl's
getFragment() method wouldn't return the actual fragment from the URL.
Or, in other words...
When I hit http://dominoguru.com/demo/sxt.nsf/demo_XSPUrl.xsp?open#foo, I can't get a handle on #foo via the SSJS method designed to do that very thing!
From the Domino Designer Help Database:
The fragment identifier follows the # character after the URL proper and identifies a location in the URL content.
No matter how many times I try it... I get nothing. But I don't think the problem has anything to do with the
First, I put together a simple demo XPage, with a single computed text Control:
<?xml version="1.0" encoding="UTF-8"?>
From there, I started hitting some variants of the URL:
|Simple URL||demo_XSPUrl.xsp||Click Here|
|QueryString Parameters||demo_XSPUrl.xsp?blah=foo||Click Here|
|Simple URL with Fragment||demo_XSPUrl.xsp#foo||Click Here|
|QueryString Parameters with Fragment||demo_XSPUrl.xsp?blah=foo#foo||Click Here|
So... it's the
XSPUrl that's broken?!
I tested this in 8.5.1 and 8.5.2 (with 8.5.3 testing coming later tonight), and got the same results. What do you get? Let me know in the comments on this post. Perhaps (and quite frankly, I hope this is the case) I'm the only one seeing this... and there are certainly workarounds that we can employ... but knowing limitations like this are extremely important!