@Phon: I found something useful in EJB3 trailblazer
http://trailblazer.demo.jboss.com/EJB3Trail/services/apptrans/index.html
Im testing the loadlevel solution with a simple application:
There are 4 entities A,B,C,D.
A has OneToMany associations with both B and D (C extends A, i'll use it for
oth
IMHO the load-level solution is the best: fast, effective and clean.
I have a question, probably a little off-topic (however it's about ejb3
design)... :)
Im approaching to design the server "session side" of an application.
I've already done the "persistence side" using entity bean and it is q
I found this post in the EJB/JBoss forum (probably the wrong one), but I think
it could be a nice argument to be deepened.
"Ciovo" wrote :
| I'm building an application using ejb3 and jboss 4, and I'm trying to
understand what is the best way to handle the communication between a remote
clie
