I am posting the following questions and notes for second time because there is now so much new topics because of the new book.
I see from your previous reply that your book contains a lot of apendices (including annotation reference). It is a good idea. According my knowledge I think one of very good features in EJB 3.0 is using of extended persistence context and interceptors. I am very glad about this improvement. My question are :
1. Do you subscribe mentioned topics in more details ?
2. Is already possible to create custom annotation with interceptor functionality ?
3. Is already possible to have REQUIRED attribute for let's say just one "finalization" method like bookSeats() in the case of STATELESS session bean ? (other methods before this final would be run without transaction context - transactional attribute for a bean is NOT_SUPPORTED and because of that all transaction would be queued and processed just in the final method). As well as I know there were some talks about this in EJB 3.0 Expert Group. So far it is possible only for STATEFUL session beans and I completely agree with that. I do not think it is good idea to put it into stateless session bean.
SUN Certified Enterprise Architect SUN Certified Business Component Developer SUN Certified Developer For Java Web Services SUN Certified Programmer SUN Certified Web Component Developer SUN Certified Mobile Application Developer
We discuss about extended persistence context in Chapter 9 and then provide an example how to use it as a caching mechanism in Chapter 13. When using XPC, all db updates are queued and performed when peristence context is flushed in @Remove method in stateful session beans.
Interceptors (both business method and lifecycle) are covered indepth in Chapter 5.