JBoss at work is a good book,


I read JBoss at Work and PHP,Ajax,

These are my favorite sentence of these books.

JBoss at work

More specifically, we'll look at EJB components that must run inside an EJB container.

"If all you're got is a hammer, every problem tends to look like a nail!" said Bruce Tate, author of Better, Faster,Lighter Java.

But if your buisiness process require transactions or if you have externaml remote clients, you shuld consider useing an EJB --see the good reasons below.
・Distributed transactions
・Component security
・Asynchronous processing
・Remote access
・Declarative transactions

We encourage you to look at your system-level and Business requirements before using EJBs.

Transactions should be atomic- if one of the steps fail, all grouped activities should roll back to their initial state.

There are three types of EJBs.
1.Session Beans 2.Message-Driven Beans 3.Entiry Beans

Remote access uses RMI, which requires object(used as parameters or return values) to be serializable.


It's worth knowing that unless you need to specify an exact version of JavaScript, you can normally omit the


and just use


to start the interpretation of the JavaScript.

Ajax originally meant "Asynchronous JavaScript and XML", but that phrases is already a bit outdated.

By default, PHP documents end with the extension ".php"

 echo "Hello World.";

If you have only PHP code in a file, you may omit the closing


This can be good practice, as it will ensure you have no excess whitespace leaking from your PHP files(especially important when writing object-oriented code).

PHP is quire simple language with roots in C and Perl, yet it looks like Java.

I read ...

JBoss at Work: A Practical Guide

JBoss at Work: A Practical Guide

Learning PHP, MySQL, JavaScript, and CSS: A Step-by-Step Guide to Creating Dynamic Websites

Learning PHP, MySQL, JavaScript, and CSS: A Step-by-Step Guide to Creating Dynamic Websites