Re: dynamic title in portlet
More info below. --- Dan Moore <[EMAIL PROTECTED]> wrote: > Hi, > > I'm running Jetspeed 1.5. Like some other folks, I have a need to > dynamically change the title of a portlet, based on information > passed > in to it. I'm trying to write Velocity portlets, so all of the > information needed to set the title is obtained in the Action class, > in > the buildNormalContext() method. I did some looking around on the > mailing list, and it appears that, due to the lifecycle of Jetspeed 1 > portlets, this is not easy to do. > > I found one post that seemed to help: > http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]&msgNo=1113 > But, when implementing the proposed solution, it became clear to me > that VelocityPortlet.getContent() writes to output rather than > returning a String that can be stored as suggested in the above mail. > > So, as I see it, the only way I can change the title, via the Action > class, is by: > > 1. Calling getContent twice in jetspeed.vm (which, will, if I don't > have a cached portlet, call buildNormalContent twice). Surround the > first call with HTML comment characters so the user doesn't see it. And this method doesn't work for me, because it breaks the Customizer. (The Customizer apparently outputs HTML comment characters, which close the comment around the first call.) Dan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
dynamic title in portlet
Hi, I'm running Jetspeed 1.5. Like some other folks, I have a need to dynamically change the title of a portlet, based on information passed in to it. I'm trying to write Velocity portlets, so all of the information needed to set the title is obtained in the Action class, in the buildNormalContext() method. I did some looking around on the mailing list, and it appears that, due to the lifecycle of Jetspeed 1 portlets, this is not easy to do. I found one post that seemed to help: http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]&msgNo=1113 But, when implementing the proposed solution, it became clear to me that VelocityPortlet.getContent() writes to output rather than returning a String that can be stored as suggested in the above mail. So, as I see it, the only way I can change the title, via the Action class, is by: 1. Calling getContent twice in jetspeed.vm (which, will, if I don't have a cached portlet, call buildNormalContent twice). Surround the first call with HTML comment characters so the user doesn't see it. 2. Hack VelocityPortlet so that you can get to some part of the Action class via the jetspeed.vm template. Am I missing anything obvious? Is there an easier way to have a dynamic title? Dan PS Thanks much for putting Jetspeed together. I'm really digging how configurable and well documented it is. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Jetspeed 1 or 2
It all depends on the time frame of your product release. Jetspeed-2 is not as ready as Jetspeed-1 is in terms of customization, documentation and available UI features. The J2 framework is mature and the UI and customization is catching up. If you start developing a Web Portal now J2 should definitely be your choice. If you need something to show now or lets say by the end of the year you could as well consider the "hybrid" approach. The latest Jetspeed-1 CVS contains Fusion (soon to be officially released) which allows you to run J2 (JSR-168 compliant) portlets in J1. The advantage of the Fusion approach is that you can develop J2 portlets while using the advanced customization features of J1. Once J2 is ready your migration issues would be minimal because your business logic (Portlets) won't change. I used this approach for our recent projects and it works pretty well. Roger Daniel Pardo wrote: Hi, Im beginning to develop a web application with jetspeed 1.5, and im learning all the process. But: Might I forget 1.5 and begin with Jetspeed 2? There are enought documentation for develop in jetspeed 2 environment? What is your opinion? Thanks a lot from Spain, Daniel Pardo - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Handling errors in customize mode
Hello - We are writing a portlet in Jetspeed 1.5 for which we are providing our own customizer (provides.customization=true.) The customizer has a number of data entry fields, which the user could fill in incorrectly. We would like to validate the entered data in an action method (doUpdate() for example,) and return them to the customize screen if there is an error. Is there a way to return the user to the customize view from your doX() methods? I have tried a number of things... none of which seemed to work. This is pretty much a show-stopper for us at the moment... any help would be greatly appreciated! Thanks, Eric Olson
Jetspeed 1 or 2
Hi, Im beginning to develop a web application with jetspeed 1.5, and im learning all the process. But: Might I forget 1.5 and begin with Jetspeed 2? There are enought documentation for develop in jetspeed 2 environment? What is your opinion? Thanks a lot from Spain, Daniel Pardo - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
