|
WebLogic Integration | |||||||||
PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
SUMMARY: INNER | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |
The interface that a plugin must implement to define a new event node type.
Method Summary | |
int |
activate(EventContext eventContext,
ExecutionContext execContext)
Activate this event. |
void |
fixup(com.bea.wlpi.evaluator.ExpressionParser parser)
The framework calls this method after parsing the template definition. |
int |
trigger(EventContext eventContext,
ExecutionContext execContext)
Trigger this event. |
Methods inherited from interface com.bea.wlpi.common.plugin.PluginObject |
load |
Methods inherited from interface org.xml.sax.ContentHandler |
characters,
endDocument,
endElement,
endPrefixMapping,
ignorableWhitespace,
processingInstruction,
setDocumentLocator,
skippedEntity,
startDocument,
startElement,
startPrefixMapping |
Method Detail |
public int activate(EventContext eventContext, ExecutionContext execContext) throws WorkflowException
EventContext.activateEvent(com.bea.wlpi.server.common.ExecutionContext, java.lang.String, java.lang.String, java.lang.String, java.lang.String)
.
Plugins are responsible for recording the necessary information in a
plugin-specific way, and for providing an
event handler to perform the run-time matching
based on these criteria. If the plugin does not rely on the
WebLogic Process Integrator generic JMS event listener it is not
required to provide an event handler.
eventContext
- The event node context. This object provides access
to run-time event related services such as event watch registration.execContext
- The execution context. This object provides access
to the runtime context, including the template ID, template definition
ID, workflow instance ID, event data, and various services related to
workflow enactment.ExecutionContext.CONTINUE
or
ExecutionContext.STOP
.trigger(com.bea.wlpi.server.plugin.EventContext, com.bea.wlpi.server.common.ExecutionContext)
public int trigger(EventContext eventContext, ExecutionContext execContext) throws WorkflowException
EventContext.removeEventWatch(com.bea.wlpi.server.common.ExecutionContext)
from this
method, to place the event node to the non-listening state. Plugins
that do not use the default event watch registration and matching
services must deactivate whatever plugin-supplied event watch record
they established for this node in the prior activate(com.bea.wlpi.server.plugin.EventContext, com.bea.wlpi.server.common.ExecutionContext)
call.
They are also required either to provide an
event handler if the event arrives via the WebLogic
Process Integrator generic JMS event listener, or to implement their
own listener service by whatever means (TCP/IP socket, RMI, polling
etc.).
eventContext
- The event node context. This object provides access
to run-time event related services such as event watch registration.execContext
- The execution context. This object provides access
to the runtime context, including the template ID, template definition
ID, workflow instance ID, event data, and various services related to
workflow enactment.ExecutionContext.CONTINUE
or ExecutionContext.STOP
.activate(com.bea.wlpi.server.plugin.EventContext, com.bea.wlpi.server.common.ExecutionContext)
public void fixup(com.bea.wlpi.evaluator.ExpressionParser parser) throws WorkflowException
parser
- The expression parser to use.
|
WebLogic Integration | |||||||||
PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
SUMMARY: INNER | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |