java.lang.Object
nectar.reda.server.action.AdminAction
nectar.reda.recordeditor.server.GetForumRootRecords
- public class GetForumRootRecords
- extends nectar.reda.server.action.AdminAction
| Fields inherited from class nectar.reda.server.action.AdminAction |
|
| Methods inherited from class java.lang.Object |
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait |
GetForumRootRecords
public GetForumRootRecords()
- Creates a new instance of GetForumRootRecords
execute
public void execute(nectar.reda.client.action.ClientAction action,
nectar.reda.server.Session session)
throws nectar.reda.client.action.ClientActionException
getRootCategories
private java.util.List getRootCategories(java.lang.Long project)
throws nectar.reda.client.action.ClientActionException
getRootForums
private java.util.List getRootForums(java.lang.Long project)
throws nectar.reda.client.action.ClientActionException
isHeavyAction
public boolean isHeavyAction()
- Description copied from class:
nectar.reda.server.action.AdminAction
- Let's the ActionPump that is going to execute this action know whether this
action will probably require a long time or not to complete. Any "blocking"
actions, ie, actions that make database queries, access files, or depend on
the actions of another thread to execute should return true for this method.
All actions that are very simple, for example looking up a status variable
that's loaded in memory should return true.
The behaviour of the ActionPump may be affected by the result of this method,
executing not heavy actions in the same thread as the ServerInstance that
reads and writes Action objects from and to the network. Heavy Actions are
passed to a pool thread that execute actions separately. This mechanism allows
much faster response for simple actions, taking advantage of the asynchronic
response pattern inherent to Reda StreamLayers...
If this method is not overridden, it will return false by default.