public abstract class Change extends Object
Batch. For now it has two purposes:ServerController to turn model changes
into actual server runtime (re)configuration operations.| Modifier and Type | Method and Description |
|---|---|
abstract void |
accept(BatchVisitor visitor)
Perform an operation in acceptor-visitor pattern.
|
Change |
getBatchCompletedAction() |
List<OsgiContextModel> |
getContextModels()
Get a list of associated context models.
|
OpCode |
getKind() |
void |
registerBatchCompletedAction(Change action)
If during action/change handling, the visitor (action invoker) decides there's another action to perform
but in separate thread (next "tick" of single event thread), this is the way to register such action.
|
void |
uninstall(List<Change> operations)
|
public Change(OpCode kind)
public OpCode getKind()
public abstract void accept(BatchVisitor visitor)
visitor - public List<OsgiContextModel> getContextModels()
Get a list of associated context models.
Usually the list comes from associated model being ADDed and usually doesn't make sense when a change
concerns more models. Special scenario is to get a list of new context models associated with existing
element model after it has been removed (from previous list of associated contexts) in the same Batch.
public void uninstall(List<Change> operations)
Change may be reversed, which is handy when rolling back existing Batch. A single
change may be a no-op during uninstallation (like for example welcome files), but also may consist of
more uninstallation changes - like OsgiContextModelChange which has to follow unregistrations of
dynamic servlets/filters/listeners.public void registerBatchCompletedAction(Change action)
action - public Change getBatchCompletedAction()
Copyright © 2006–2024 OPS4J - Open Participation Software for Java. All rights reserved.