> In a well separated layer design, applicative layer should be independant of > persistance layer. So the use of a OODBMS or A RDBMS should not influate > modeling in the application layer. > Entity beans are clearly violating this separation rule. I totally agree. > But from what i've > understood so far, session beans were designed to model process rather than > concept. Moreover, they have no persistance. So how can you use them to model > real-world entities ? You have understood it the same way it seems most people have. We model our use cases as session beans and it is working just fine giving us the facade we need for distributed performance. Trying to use session beans to model entities would IMHO be like forcing the square thing through the circular hole - it can be done but that is not how it was meant to be. Regards Marcus Ahnve Sun Java Center Sweden
begin:vcard n:Ahnve;Marcus tel;cell:+46-(0)70-723 90 73 tel;fax:+46-(0)8-623 90 05 tel;home:+46-(0)8-656 48 89 tel;work:+46-(0)8-623 90 73 x-mozilla-html:TRUE url:www.sun.se org:Sun Microsystems AB;Sun Java Center adr:;;Esbogatan 18;Kista;Stockholm;164 94;Sweden version:2.1 email;internet:[EMAIL PROTECTED] title:Java Consultant fn:Marcus Ahnve end:vcard
