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]>
