On May 5, 2004, at 5:14 AM, Gregory Joseph wrote:
I can't seem to make any sense of these forwards, so if someone feels likeForwards are simply an abstraction over Jetspeed Links.
helping or giving examples. (reminder of my context: i need to create html
links between portlets, and keep the "tabs" (tabbed panes) in their right
state)
The idea is to centralize all changes to site navigation.
For example, say you have a portal site that has your Employee Benefits portlet on the Employee role page, Benefits tab.
Then management decides they don't like the portal site layout.
They want to re-organize the structure of your site.
You need to move the Employee Benefits portlet to the Benefits group page, Employee tab.
Now say you have Java code and velocity templates that reference this portlet with Jetspeed Links.
You would need the Jetspeed Links on to update all the Java code and all the velocity (or JSP) templates to point to the new location.
But if you used forwards to begin with in your Java and template code, then you would only have to change the forward file, and nothing else.
As for examples, see the example portlets:
ForwardDemo portlet - example of using forwards JSLinks portlet - lots of examples of Jetspeed Links
JSP1_1andJetspeedTagLib
JSP1_2andJetspeedTagLib
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
