Hi, > Do your methods need to be the exact same name? Maybe not for different class portlets, but I use the same portlet implementation configured in differentes way in my registry... so, same class action and same methods names.
>Jetspeed is based on Turbine - so its generally easier to use Turbine features to implement it... Sure, Turbine is very great! > although I am not sure how your suggestion would help. If I can, I will be proud to do it. >I think the problem you are getting is similar to the general problem people have with parameters to portlets, Sorry, but I don't think so! The problem comme from the call of ActionLoader in VelocityPortlet. This call is done for each VelocityPortlet on the page and it's none explicit call. So, if you call an action and pass one param eventsubmit_doSomething, all the action used by the velocity portlets will try to find the method doSomething. I think it's a problem to use the ActionLoader in this way in VelocityPortlet. This design song strange for me, but, maybe I miss something !? I will try to do my own class VelocityPortlet, an abstract class with BuildMaximiseContext(), BuildCustomiseContext(), BuildNormalContext() abstract method to overwrite. If that can help... Xa. -----Message d'origine----- De : Chris Kimpton [mailto:[EMAIL PROTECTED]] Envoye : lundi 18 mars 2002 22:02 A : Jetspeed Users List Objet : Re: problem with VelocityPortlet and VelocityPortletAction Hi, > > In fact, the problem come from VelocityPortlet. In getContext > method of > VelocityPortlet, the action is load each time. > When you call an action and pass the param eventsubmit_doAdd, all > the > VelocityPortlet present on your page, will be execute the methods > doAdd of > there VelocityPortletAction's. Do your methods need to be the exact same name? > > I'm sorry, but I dont understand why VelocityPortlet use the Action > mechanisme of turbine? Why not just write an abstract > VelocityPortlet with > BuildMaximiseContext(), BuildCustomiseContext() > BuildNormalContext() method > to overwrite ? > Jetspeed is based on Turbine - so its generally easier to use Turbine features to implement it... although I am not sure how your suggestion would help. I think the problem you are getting is similar to the general problem people have with parameters to portlets, if several of your portlets look for a parameter, say userid, then when that is passed to the page, all of them with see that parameter. For now it is probably best to use distinct field names/method names, if you can. HTH, Chris ===== http://wc2002.kimptoc.net - someone has got to win... __________________________________________________ Do You Yahoo!? Yahoo! Sports - live college hoops coverage http://sports.yahoo.com/ -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
