On our project, we were thinking of considering the Session Beans at the same level of granularity as a 'process', meaning we consider that network calls and EJB overhead are involved and want our Session Beans to be at a very high-level of abstraction in terms of the services that they offer (and, we organize the services using the object-oriented paradigm). Within these EJB Session beans, we create local Java objects from our object model. This question came to mind because of patterns such as 'Session Wraps Entity Beans'. This makes me think that EJB Session Beans are being used at levels of granularity that are lower than what I would be used to. If entity beans are used (without using JDO or local interfaces), this pattern suggests that we can capture interactions and/or filtering of data from entity beans using a session bean that is defined solely for this purpose. In other words, instead of my high-level Session Bean directly using entity beans, my high-level Session Bean would instead use another Session Bean that encapsulated the Entity Bean(s). So ... this other Session Bean that wraps the Entity Bean(s) is at a level of granularity that's lower than I'm used to ..... Is this correct? Thanks, Bill Leonard =========================================================================== 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".
