I'm currently working on my first EJB3 project (actually my first
project involving EJB at all).
So I wrote an entity bean and a statless bean. So far so good. Then I
wrote a servlet where I want to use my session bean so I included

In the normal world of JDBC, dealing with a transaction is trivial -
get a connection, set the auto commit to false, do your stuff, call
commit() if you're happy, call rollback() if you're sad, and close.
Connection Pools are supposed to avoid the overhead of repeated

Just to understand better...I'm studying EBJ 3.0, session beans,
entities and JBoss to write web and distribuited applications for my
University coruse of Web Architecture. I'm studying a lot of
documentation and as a reference I'm reading the book "Mastering EJB

I am developing a server in JBoss 4.0.5 and I have a client done in
Microsoft .Net 2 platform.
I can't make them communicate. Any suggestion?
Thanks a lot.

I was trying the first EJB example of the book "Mastering Enterprise
Java Beans". After building the bean and deploying it successfully I
had many problems making the client work. The client code is very
simple