Hibernate / EclipseLink Interview questions
What is EclipseLink's native Session API?
Session is EclipseLink's foundational, non-JPA API for interacting with a data source, predating its JPA support and still available as a lower-level alternative or complement to it. Different session types serve different roles: a DatabaseSession manages a direct connection for a single-user application, a ServerSession manages a shared connection pool for multi-threaded server applications, and a ClientSession represents one client's transactional interaction with a ServerSession.
While most modern applications interact with EclipseLink purely through JPA, the native Session API remains available (and JPA is actually implemented on top of it), which is why some advanced EclipseLink features, like certain cache coordination or session event listeners, are exposed at the Session level rather than through the JPA-standard API surface.
More Related questions...
