|
||||||||||
PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |
java.lang.Objectorg.glite.security.voms.request.Request.State
org.glite.security.voms.request.BrokenRequest.BrokenState
Constructor Summary | |
BrokenRequest.BrokenState()
|
Method Summary | |
java.lang.String |
getDescription()
Return a description of this state. |
java.lang.String |
getName()
Return the short name of this state. |
boolean |
isComplete()
Return true if the request is complete, i.e. if no more state transitions are expected. |
Request.State |
processEvent(Event e)
Process the given event. |
Methods inherited from class org.glite.security.voms.request.Request.State |
getAcceptedEvents |
Methods inherited from class java.lang.Object |
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait |
Constructor Detail |
public BrokenRequest.BrokenState()
Method Detail |
public java.lang.String getName()
Request.State
It is not an error to have two different State classes with the same name, although this is usually not desirable.
getName
in class Request.State
public java.lang.String getDescription()
Request.State
It is not an error to have two different State classes with the same description.
getDescription
in class Request.State
public boolean isComplete()
Request.State
isComplete
in class Request.State
public Request.State processEvent(Event e) throws VOMSException
Request.State
The default implementation handles only TimeoutEvent
, and
only for incomplete states. Concrete states usually call
super.processEvent(e)
to fall back to the default
behaviour.
processEvent
in class Request.State
VOMSException
|
||||||||||
PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |