I have an application with a lot of generated SQL, data access, mapping
and client object code.

I am not ready to hand that over to JBoss or other servers and
primarily wish to use an application server for executing SQL and
business logic in a service orientated fashion.

Some reference data caching but *no* session management.

With that in mind I have been testing using entity beans only.

My typical entity is not actually tied to any database, caches nothing
and just executes SQL.

I use an entity bean since it persists forever and I am guessing it is
much lighter on the server to do that instead of creating a session
bean per client.  Why have 1000 beans when you could have one?

I assume there is no concurrency issues since everything is a local
variable - except for the data access objects which are never written
to - they just have methods executing connections, sql, etc.

Does this sounds reasonable?  Perhaps I could make my beans read only
and that would further enhance performance.

thanks

Tim