Greetings listfolk, Another developer in our group is creating several stateless session beans (A, B, C) that will all have the same interface (I). Initially he wanted to just set their names to all be the same using the ejb.interface tags:
@ejb.bean name="A" @ejb.interface remote-class="dd.ejb.session.IRemote) @ejb.bean name="B" @ejb.interface remote-class="dd.ejb.session.IRemote) Thus, each bean would have the same remote interface class. When they were generated, they'd overwrite the previous version with only the JNDI names being different (which we don't use, so they are effectively equivalent). This didn't seem to work, however. It looks like XDoclet is ignoring the tags entirely. Has anyone used these tags successfully? I have no spare cycles to delve into the templates and code to check myself, so I was hoping someone could simply say, "Yes, I use those tags and they work." Then I'd know where to look. That being said, I suggested a workaround that I suspect may actually be the more accepted pattern: using a business interface. Instead of sharing the same remote interface, each bean would generate its own interface that extends the business interface, I. This common interface would end up having the same signature as the gingival bean interfaces, but it seems like the "right thing" to do. It would require using the ejb.interface extends/local-extends tags, so I wanted to make sure that these ones work if the others don't. :) Has anyone else done this? Thanks! David Harkness Sr. Software Engineer Sony Pictures Digital Networks (310) 482-4756 ------------------------------------------------------- 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
