Skip Headers

# Using EIS Interactions

Previous

Next

For an EIS root descriptor, you can define EIS interactions to invoke methods on an EIS.

TopLink represents EIS interactions using instances of `oracle.toplink.eis.interactions.EISInteraction`. These classes implement the `Call` interface and can be used wherever a `Call` can be used.

Table: EIS Interactions lists the type of EIS interactions that TopLink supports.

EIS Interactions

EIS Interaction Type | Description
--- | ---
`IndexedInteraction` | Defines the specification for a call to a J2C interaction that uses indexed records. Builds the input and output records from the arguments by position.
`MappedInteraction` | Defines the specification for a call to a J2C interaction that uses mapped records. Builds the input and output records from the arguments by name.
`XMLInteraction` | Specifies an instance of `MappedInteraction` that defines the specification for a call to a J2C interaction that uses XML records defined by the XML schema document (XSD) associated with the EIS project (for more information, see "Importing an XML Schema").
`QueryStringInteraction` | Specifies an instance of `MappedInteraction` that defines the specification for a call to a J2C interaction that uses a query string. Prefix arguments in the query string with a number sign ( `#` ) character.
`XQueryInteraction` | Specifies an instance of `XMLInteraction` that defines the specification for a call to a J2C interaction that uses XQuery. Translates the XQuery from the query arguments.

You can use TopLink to define an interaction for each basic persistence operation (`insert`, `update`, `delete`, `read object`, `read all`, or `does exist`) so that when you query and modify your EIS-mapped objects, the TopLink runtime will use the appropriate EIS interaction. For more information, see "Configuring Custom EIS Interactions for Basic Persistence Operations".

You can also use TopLink to define an interaction as a named query for read object and read-all object queries. These queries are not called for basic persistence operations; you can call these additional queries by name in your application for special purposes. For more information, see "Creating an EIS Interaction for a Named Query".