Yes, agreed, no other uses in our code. Outside this list, someone expressed a concern for users who referenced getActions() from their code (other than their page flow controller implementation) and upgraded to the current code base. I wasn't sure if there was a specific reason to leave it off. Thanks.
On 5/10/06, Daryl Olander <[EMAIL PROTECTED]> wrote:
I think the rule I made was that if something wasn't called anywhere in the framework I didn't provide a public accessor. So you can add it if you need it for some reason. I didn't see any uses of it when I looked. Has someone requested it? On 5/10/06, Carlin Rogers <[EMAIL PROTECTED]> wrote: > > Hi Daryl, > > I was looking at the change for BEEHIVE-1069 where some methods on the > PageFlowController were renamed so they aren't picked up as JavaBean > properties... > > http://svn.apache.org/viewcvs?rev=378742&view=rev > > PageFlowController: getSharedFlows(), getCurrentPageInfo(), > getPreviousPageInfo(), getPreviousActionInfo() > FolowController: getModuleConfig(), getActions() > > However, with the changes I did not notice a replacement public method, > theActions(). Was there a reason to omit this one? If not, I can go ahead > and add it. > > Thanks, > Carlin >
