Hello all, I have a question regarding taking some legacy code and exposing it as an EJB, automatically generating the necessary code. I would like to do it slightly differently than is shown in the XDoclet examples. It's important that my legacy class not be a subclass of one of the EJB classes (Entitybean, etc.) as I want my legacy code to be as separate from the middleware as possible. The legacy code is also used in stand alone, non-distributed environments. Perhaps this capability already exists in Xdoclet, if it does not, hopefully you can point me in the right direction to extending Xdoclet in the right way. I am also open to other suggestions to the requirement I lay out below.
What I would like to do is take an existing component, wrap it up inside a bean (EntityBean for instance) and only expose a certain number of methods remotely or locally. So, instead of making the main class with my business logic a subclass of javax.ejb.EntityBean (as the Xdoclet examples show), I would like another class created that extends EntityBean, and has my legacy class an instance variable. This class will contain all of the methods I wish to expose, delegating calls to the instance variable. I would like to do this by using XDoclet tags inside my legacy class, without it extending a based Bean class. I am interested in hearing from others if this is possible and any problems I might run into taking this approach. I'm concerned instance pooling may become a problem here. Sincerely, jim ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user
