Hi All, I've been struggling with the current andromda-ejb cartridge on a particular issue. While I think generation of Impl classes is nice, in that inheritance is being used, the fact that the deployment descriptors need to be 'modified' after they are generated is not sitting well with me. I was trying to think of other ways to do it, and came up with the idea of delegating.
It's not exactly the 'Business Delegate' pattern, since the EJBs would be delegating to classes that implement the business logic, instead of the other way around. So, I don't know what to call it. The idea is this: The CMP and Session beans would be generated with business methods that are not abstract. Instead, when the session or entity context are set, the beans would create a delegate class (probably caching the class and passing on the entity and session context to it), and the implementation of the business methods would contain a call to the delegate instead of any implementation. The state the delegate would need to be aware of would be the session or entity context, and the reference to the 'owner' bean so that reentrant method calls could be made through the entity or session bean instead, in case there's interceptors for security and transactions involved. I guess I'm writing to ask if anyone else has thought of the problem this way, or if there would be any issues more severe than an extra method call indirection penalty. I think this would allow business method implementation classes without the need for any deployment descriptor modifications. Ideas? Cheers. -Neal ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Andromda-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/andromda-user
