Monday Jul 30, 2012

If you didn't know what is coming in EJB 3.2...

This is the list of changes in the latest EJB 3.2 draft:



  • Support for the following features has been made optional in this release and their description is moved to a separate EJB Optional Features document:

    • EJB 2.1 and earlier Entity Bean Component Contract for Container-Managed Persistence

    • EJB 2.1 and earlier Entity Bean Component Contract for Bean-Managed Persistence

    • Client View of an EJB 2.1 and earlier Entity Bean

    • EJB QL: Query Language for Container-Managed Persistence Query Methods

    • JAX-RPC Based Web Service Endpoints

    • JAX-RPC Web Service Client View


  • Support for local asynchronous session bean invocations and non-persistent EJB Timer Service has been added to the EJB 3.2 Lite set of features

  • Restriction on obtaining the current class loader has been removed

  • Access to Java I/O has been relaxed, replacing ‘must not’ with ‘should exercise caution’

  • Lifecycle callback interceptor methods of stateful session beans can now be executed in a transaction context (determined by the lifecycle callback method's transaction attribute)

  • It is now possible to completely disable passivation of a specific stateful session bean

  • TimerService API has been extended for an ability to query all active timers in the same EJB module

  • Default rules for designating implemented interfaces for a session bean as local or as remote business interfaces has been relaxed to include more than one interface (see examples in the document for the detailed rules)

  • List of standard activation properties for JMS message-driven beans has been extended to match the changes in the JMS 2.0 specification

  • A unique identifier of a JMS message-driven bean can be now looked up by a standard name by the JMS resource adapter to construct a subscription name

More details and get involved


If you are interested in reading the latest draft, it is available for download on the EJB spec java.net project page: http://java.net/projects/ejb-spec. On this page you can also subscribe to the users mailing list to read the ongoing discussions and provide your input.

Monday May 05, 2008

Using EJB Timers in GlassFish V3 TP2

In this blog I'll explain how you can enable and use EJB Timer support in GlassFish V3 TP2.


If you hadn't done so yet, read first Mahesh's blog about Installing EJB Container in GlassFish V3 and using EJB 3.1 in GlassFish V3 TP2.

Enabling TimerService.


1. Change pool-name for the JDBC resource named jdbc/__TimerPool to point to the same connection pool as the one you are using for the rest of your data. You can do this either by editing the domain.xml file (and restarting the server), or via AdminGUI console (http://localhost:8080/admin/).

2. Start the database (or make sure it is running).

3. Deploy EJB Timer application that is located under <your-installtion>/glassfish/modules/ejb/ejb-timer-service-app-10.0-tp-2-SNAPSHOT.war. The aplication has been set up to use JPA with the default JPA provider, and to create the table on the first access.

4. Test that the TimerService has been started by accessing the following URL: http://localhost:8080/ejb-timer-service-app/timer

If everything went right, you'll see this screen:




Using TimerService.


All EJB 3.0 Timer features are supported with the exception of injection of TimerService using @Resource annotation. You can lookup TimerService via java:comp/TimerService.

Thursday Dec 08, 2005

Java Persistence Examples in GlassFish

The Example page for Java Persistence in GlassFish now has a Java EE version of the Java SE example with an app client (for the invocations) and a Stateless Session bean (for the business logic).
The page has been slightly redesigned for a better flow of information.
About

Marina Vatkina

Search

Top Tags
Categories
Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today
News

No bookmarks in folder

Blogroll
Related Links