The "WCB: JSP front-end design" forum contains threads on issues that are related to JSP front-end design while programming a WCB (WebManager Component Bundle). The Presentation & Element component contain JSPs that will be used for front-end rendering. Ask your questions related to these JSPs here. Some example topics: integration of AJAX, use of the taglibs, how to handle multiple websites, and so forth.
Are you maybe trying to create a database link, but working around the 'external database'-pages functionality, where the editor can just search for the parameter when creating the link?
The wm:link-tag (inside the presentation JSP) could also do this kind of things, but why need it?
Use case is that the editors want to track links with omniture. For this to be possible they need to add an parameter to the links. Any way this is possible within webmanager?
What I usually see is that a Javascript function simply changes all URLs found in a page. Some page specific code is defined and added to every (relevant) URL found in the DOM of the page. E.g. external links are determined and prepended with a clickout counter.
The script is usually added to the page presentation.
It gives extra options but it doesn't solve the problem he mentioned. The solution Michel gives would a parameter based on what type the link is. If it's a mediaitem use this and if its a page use that.
What we would like to see is a solution where you can add a parameter like a omniture tag. So you can link to a page like www.gx.nl/web/show?omniture=var1 Currently you can only do this by using an external url.
That is indeed what I want to do. The url only solution of the L tag is not going to help us as we do not want to bother this. There seems to be a request in jira (GXWM-10262) to fix this so I just hope it will be picked up soon.
Just a little offtopic heads-up: mind the caching system here! All these links will be unique, so something has to be done to prevent a unexpected big cache here.
Workaround: If the link-building proces is 'page' specific (so all links on that page should get ?omniture=var1) a Javascript function that simply changes all URLs found in that page (or div/span) might just do the trick. You can use page labels to send the 'omniture=var1' into the javascript.
We know about the caching. It was one of the reasons I told them they probably didn't want to do it, but they still insisted on it.
The links are not page specific. They can have multiple links on one page with different omniture tags linking to multiple pages. On another page you could have the same page links but with different omniture tags so it is really hard to fix this with javascript since there isn't any logic to build.
If you could add parameters while creating a link it would fix everything. You can already do this with the wm:link tag by adding your own variables.
This website (GXdeveloperweb.com) may discuss or contain opinions,
(sample) coding, software or other information that does not include GX
official interfaces, instructions or guidelines and therefore is not
supported by GX. Changes made based on this information are not
supported. GX will not be held liable for any damages caused by using
or misusing the information, software, instructions, code or methods
suggested on this website, and anyone using these methods does so at
his/her own risk. GX offers no guarantees and assumes no responsibility
or liability of any type with respect to the content of this website,
including any liability resulting from incompatibility between the
content of this website and the materials and services offered by GX.
By using this website you will not hold, or seek to hold, GX
responsible or liable with respect to the content of this website.