I ask this because I see some advantages to having access the active portlet within this tool for building links.
(From a Velocity perspective) As I see it the VelocityPortletControl could, within getContent(), extract the BaseJetspeedLink from the context AFTER the populateContext has been called. Once extracted from the newly built context, and the portlet has been built (logic is already there), call the BaseJetspeedLink.setPortlet() to populate the BaseJetspeedLink with the active portlet. BaseJetspeedLink.init() would need to set the activePortlet attribute to null so as to avoid any stale or invalid data. Have I missed something blatantly obvious, or is what I'm saying make sense? If everything appears cool with everyone else, I would like to make the above plus add a TemplateWithID() method to BaseJetspeedLink. Thanks, Scott
