>The biggest problem with this is that in EJBQL I now have to use o.sb_name to refer >to the field. > >Is there a better way to do this?
Nope, that's pretty much the proper way to do things. Using sb_name in the EJB-QL really isn't that big of an issue is it? Especially if you follow a standard convension for how you rename the field. I generally just put an underscore "_" after the name, ie setName_(). But whatever works for you. The important thing is that the EJB-QL isn't visible to the client code, so information hiding is still successful. In the end Entity Beans really aren't a great data layer anyway, as they don't support "view" layer of objects, requiring you to write code to create and populate value objects by hand, which can be quite tedious. If you're already committed to using an Oracle database, you might consider looking at BC4J (Oracle Business Components for Java), which is a much better designed data layer all around. BC4J supports adding a view layer and adding validation logic to entities, which takes away much of the tedious hand coding that slows you down. Doug =========================================================================== 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".
