on 5/27/03 4:06 AM Sylvain Wallez wrote:
...
>>void callAction(name,map) -> invoques the action indicated by the given >>name and pass the given map as model >> >>NOTE: I personally believe that the getComponent() method removes all >>needs for the callAction() method. I foresee a future where the >>callAction() method will be deprecated. I would personally go the extra >>mile and avoid having it there altogether, but since there is no easy >>way to plugin new avalon components at runtime (at least, not as easier >>as plugging in different actions into the sitemap), I'm in favor of >>leaving it for now, until 'real blocks' will make it unnecessary. > > Same feeling. So what about removing it now ? We can also consider that > the current state of things is that components are "semi-pluggable" : we > cannot add new classes to the classpath dynamically, but we can declare > new components, and particularily actions, dynamically just by changing > the sitemap. So I don't see the real need for callAction().
I'm all in favor or removing this. What do others think?
Can you clarify how one would lookup and call an action without it? What is the "id" of a component? It's role? It's sitemap hint? It's fully qualified classname? I get the feeling it's none of these, or some combination of these?
The migration path out of actions will be less painful if at first people can easily call their action code from the flow (obvious to you I'm sure). Understanding clearly how this is to be done will help me get a feel for how painful this will be for non-insiders.
Geoff
