To be more precise Francois is suggesting you use PageLinks with a
context and handle the "actions" in the destination page onActivate.
If that really doesn't fit your use case I suppose another avenue to
explore would be to expose the pages' resources:
(This could go in a base class.)
@Inje
Chris Lewis wrote:
[...] For example, say I have a handful of pages in my app (Logout,
NewUpload, NewComment), and I want my component to be able to create
links to these pages that would trigger an action.
I don't see how this is possible with actionlink. It seems that
actionlinks always fire
