Actions not identified/identifiable?

[Rod Widdowson]

> Was that something we consciously didn't do? 

In my memory, yes.  But unfortunately my memory doesn't extend to remembering why.  Of course my memory might also be faulty.  It
could be just as simple as that by the time we bottomed out the identifiable thing we were too far down the Action route.

> Also, my initial testing reveals an interesting fact: the IdentifiableBeanPostProcessor doesn't seem to be run on singletons, at
least not
> actions. Anywhere we have a non-prototype action bean in the flow bean files, they throw an error due to missing IDs, which goes
> away when I turn them into prototypes.
> 
> I don't think it's supposed to be working like that. We certainly have other singletons that I thought the processor was being
used
> with, so it seems like perhaps something webflow is interfering with, or there's something more subtle going on we probably should
> understand.

Absolutely I'd say.  I could believe something running on singletons only, but not vice versa.

And of course if we wanted to force Actions to be identifiable at zero cost we could always force a name in the base class's
doInitialize (setId(this.getClass.getName() + ":" + index++) or some such)

/Rod