Register and start PMapper for a container and a connection factory if
another mapper is not registered with the same container and the same
connection factory.
instance pool management (list of available JSessionContext objects)
Contexts are pooled only for Stateless Session beans because for Stateful
sessions a newInstance() is required by the spec.
Obtain the java.security.Principal that identifies the caller. throws a
java.lang.IllegalStateException for message driven bean because there is
no security context available (EJB v2.0, chapter 14.5.1)
get the Map that was built from visiting the lexical query tree This map
allows to get the org.objectweb.medor.api.Field from its name (ident or
path).
This class implements methods which permit to get informations about Java Types:
the JDBC Types associated
the ResultSet.getXXX() methods associated
the PreparedStatement.setXXX() methods associated
(The Java Type may be or not a primitive type)
This class extends the JEntityContext of the JOnAS container in order to take
in consideration the fact that the container manages PName instances and not
primary keys.
Generic interposed class for Message Driven Beans This class presents these
interfaces, depending on object reached: ServerSession interface to the
ServerSessionPool MessageDrivenContext interface to the bean instance
MessageListener interface to the JMS Session Runnable interface to the
ThreadPool
Generic interposed class for Message Endpoints This class presents these
interfaces, depending on object reached: MessageDrivenContext interface to
the bean instance
Generic interposed class for Message Endpoints This class presents these
interfaces, depending on object reached: MessageDrivenContext interface to
the bean instance
This class implements javax.ejb.SessionContext interface. it should be
implemented by JStatefulContext and JStatelessContext depending if the beans
is stateful or stateless.
This method is call in first during a read operation in order to indicate
the size of the gen class. if the value is equals to -1 then that means
the data support is unable to known the size of the relation in advance.
register a Context on the transaction, as a Synchronization. this will be
used later to store instance state when needed : before a finder, or at
beforeCompletion, and to release instance at commit.
Try to store all entity bean instances modified in the transaction
this method has been introduced to fix bug #305711
it's, may be, bad for performance
3.1.5 Translating EJB Deployment Descriptors A reference to a
PolicyConfiguration object must be obtained by calling the
getPolicyConfiguration method on the PolicyConfigurationFactory
implementation class of the provider configured into the container.
3.1.5.2 Translating the EJB exclude-list An EJBMethodPermission object
must be created for each method element occurring in the exclude-list
element of the deployment descriptor.
3.1.5.1 Translating EJB method-permission Elements For each method
element of each method-permission element, an EJBMethodPermission object
translated from the method element must be added to the policy statements
of the PolicyConfiguration object.
3.1.5.3 Translating EJB security-role-ref Elements For each
security-role-ref element appearing in the deployment descriptor, a
corresponding EJBRoleRefPermission must be created.
Nothing to do:
Already taken into account in EjbqlVariableVisitor at the variables parsing,
so, just push the OP_IGNORE in the stack
empty_collection_comparison_expression ::= collection_valued_path_expression IS [ NOT ] EMPTY