> I would very rarely find that a customer would be a totally reusable > component, each Industry would have different specifics fields / > requirements for that industry, so I would think that Juan is correct > here.
You�re right of course. It was just a simple example i cooked up. > To illustrate my example, think of a purchase order, or invoice or > creditor, each would require an Address component, and having CMR > relationships that span EJB components would be a very useful facility > for most if not all applicatons, it seems we are coding around the EJB > spec not with it! Yes it would. > IIRC the reason for this features non inclusion in the spec is that it > would be more difficult for the Container developers to code, but wasn't > one of the main reasons for Containment to make the developers job > easier? (with some other important reasons too). I guess so ;-) It would be really nice if I could link this reusable address component through CMR to my customer component. I don�t reaaly see a problem for the container developers however. If the address component is deployed before the customer there should not be much difficulty in doing this if the relationship is one way. > Just my 2c, flame me if you think otherwise :-) > > Oisin > > > > > > Second, no, CMR fields require to be on the same jar. I've raised the > > issue before on the list, as I believe it puts huge constraints on the > > ability to prepackage reusable components (such as, say, an Address EB > > that is most common in many systems). > > Here I more or less disagree. Imagine a ClientEJB component. You might > not > want all the information such as home address, delivery address, phones > etc in the same table. This is a perfect example of a reusable component > > that may use CMP & CMR. > > I Think it�s bad architecture desisions that drive people to create one > huge jar containing all entities (250 in tis case...) > > > > > The only way out(if it even applies) is to make some logical divisions > > in your design, and couple EBs loosely(managing the relationships > > yourself). > > I think, in component design, you can couple Entity Beans using CMR > which > makes design and developmente easier. > > > > ==========================================================================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".
