All Classes and Interfaces
Class
Description
ASM Generator base class
Store which beliefs are accessed in a method.
Base class for transferable information about BDI elements.
Abstract base class for plan body implementations.
Action for adopting a goal.
The APL is the applicable plan list.
Candidate info for mgoal.
Candidate info for mplan.
Candidate info for pojo plan.
Candidate info for rplan.
Candidate info for waitqueue.
Goal info that contains the mgoal and the parameter bindings.
Plan info that contains the mgoal and the parameter bindings.
Helper for creating nodes.
Helper for creating opcodes.
The bdi agent feature implementation for pojo agents.
Map a change info as Map:Entry.
Condition that tests if goal instances of an mgoal exist.
Init write for beliefs.
Init write for parameter.
Condition for checking the lifecycle state of a goal.
Condition that tests if goal instances of an mgoal exist.
Condition that tests if goal instances of an mplan exist.
Base class for non-bytecode-enhanced BDI agents.
Base class for non-bytecode-enhanced BDI agents.
Reads micro agent classes and generates a model from metainfo and annotations.
Redefines jadex.micro.annotation.Configuration
as annotations do not allow inheritance.
Configurations annotation.
Allows providing arguments when starting an agent.
Helper class to enhance BDI classes at buildtime.
A BDI failure exception indicates that a plan has failed.
Feature that ensures the agent created(), body() and killed() are called on the pojo.
Extracted start behavior.
Condition that tests if an expression evalutes to true.
Extracted start behavior.
Extracted start behavior.
Overrides the monitoring feature to add the logic for current state.
Overriden to allow for service implementations to be directly mapped to plans.
Feature for required services.
BDI step listener adds rule engine behavior to the component execution.
Belief listener adapter that implements empty all methods.
Transferable information about a belief.
This class generator keeps generated byte-code as byte[] to be post-processed
by other classes.
Marker for a capability class or variable.
Wrapper providing BDI methods to the user.
Event that is thrown in case of a bdi element change (belief, goal, etc.).
Plan body that is represented as complete class.
Plan body implementation as a component.
Describes a constructor.
Service mapper that uses the annotations in a goal.
Deliberation settings.
The easy deliberation strategy.
Helper object for publishing change events (beliefs, parameters).
The exclude mode determines when and if a plan is removed from the applicable plans list (APL).
Action for executing a plan step.
Find applicable candidates action - searches plans for a goal/event.
Let a class be used to represent goals of a BDI agent.
The goal API (IGoal) injection for a pojo goal.
Specify a custom method for generating plan candidates for a goal.
A goal creation condition can be annotated in the following ways,
which allow more or less fine-grained control over the condition
and the goal creation process.
Handler used for service-goal delegation.
An exception that indicates an aborted goal i.e.
An exception that may be thrown by a plan to
indicate a subgoal failure.
Specify a custom method for getting a callback when goal is finished.
Transferable information about a goal.
The inhibit annotation can be placed on a method of a goal class
to form a so called instance-level inhibition arc, i.e.
Annotation for goal parameters.
The goal parent (pojo) injection for a pojo goal.
Marker for a field or method that should act as
goal result.
Annotation to provide a custom select candidate functionality.
Mapping annotation for goals that helps creating
call parameters for a service invocation.
Mapping annotation for goals that helps feeding
back a result of a service invocation.
Interface for injecting agent methods into pojos.
Public methods for working with BDI agents.
Interface for BDI class enhancement/generation.
Common interface for micro- and xml-based BDI agent models.
Listener for observing beliefs.
The info objects for plan candidates.
Interface for goal deliberation strategies.
Base interface for all runtime elements.
External perspective for
Interface for finishable elements.
Interface for a bdi goal.
Methods internally called on the BDI agent feature.
Internal interface of the bdi lifecycle feature.
Abstraction for rplans and rgoals that act as plan.
The interface for all message events (concrete and referenced).
Info about a service invocation containing parameters and result.
The interface for parameters.
The internal interface for all elements with parameters.
Interface for all parameter sets.
User interface for plans.
Interface for plan body.
Used as part of a service plan, i.e.
Created by kalinowski on 16.08.16.
Created by kalinowski on 16.08.16.
Mapping, e.g.
Belief model.
The plan mbody.
The capability model.
Reference to an external capability.
Processable element based on a class.
Model element for conditions.
Represents an initial / end belief (set).
Initial / end goals and plans.
BDI configuration.
Model element for inhibitions.
Base element for model elements.
Reference to another element.
Implementation of a method as a plan body.
Goal model.
Representation of internal event.
Model element for a message.
The message direction.
Parameter model.
The message direction.
The message direction.
Base class for elements with parameters.
Modelelement for a plan.
Extended parameter to store mappings.
Base class for all elements that can be processed with means-end reasoning.
Model element for a service call.
Model element for a plan trigger.
Parameter info.
Plan has aborted.
An exception that may be thrown by a plan to
indicate its failure.
Transferable information about a plan.
Note that the plan precondition is executed before a plan is scheduled for execution.
Publish information for a goal.
Raw event allows to specify exactly on what condition to wait.
Runtime element for storing goal and plan instances.
Base element for all runtime elements.
Element that can be finished with processing.
Goal instance implementation.
The runtime message event.
Base element for elements with parameters such as:
- message event
- internal event
- goal
- plan
Runtime element of a plan.
Runtime element for all elements that can be processed via means-end reasoning.
The allowed states.
Helper methods for pojo BDI and BDI V3X models.
Action for selecting a candidate from the APL.
Annotation for a service plan, i.e.
Service trigger annotation.
A plan trigger states for which events or goals a plan should be selected.
Object that indicates on which elements a plan is waiting.