Outside of much reading on the subject, I haven't had a chance to get my fingers dirty with EJB yet. Therefore, please correct me on this if I've misunderstood something. It appears to me that the ability to build a robust distributed object model with Entity Beans is hampered by the fact that (as far as I can see) you can't easily map relationships between entities, both aggregation and inheritance. I get the impression that some of the work that went into the EJB 2.0 spec is attempting to rectify that, by specifying class/object entity relationships in the deployment descriptor. It seems odd to specify this here, but I guess it makes some sense. Does IBM or BEA, or any other real EJB product, provide added value by supporting relationship specifications? If so, do any of them come close to what is being specified in EJB 2.0? -- =============================================================================== David M. Karr ; [EMAIL PROTECTED] ; w:(425)487-8312 ; TCSI & Best Consulting Software Engineer ; Unix/Java/C++/X ; BrainBench CJ12P (6/12/2000) =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
