You could create another interface that represents the methods in the superclass, and then have the local interface include that in its extends clause.
hth dim ----- Original Message ----- From: "Ryan Marsh" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, July 16, 2002 5:46 AM Subject: [Xdoclet-user] phantom interface methods > I have an abstract class (we'll call it AbstractEJB.java) which all of > my entity beans extend. It has some basic features that I would like all > of my entity beans to exhibit. One example is an ejbCreate(String uuid) > method. > > Lets say I create SomeBean.java (to be processed by xdoclet) which > subclasses AbstractEJB.java. A problem arises because I want a method > defined in the parent class (AbstractEJB) to show up in the interfaces > that Xdoclet generates for SomeBean *BUT* I don't want to override the > implementation of AbstractEJB's methods when I redefine the method in > SomeBean simply so that xdoclet sees it and the @ejb:create-method tag. > > So essentially I want to tag up a method defined in a superclass without > overridding its implementation. Any ideas? > > -ryan > -- > Humans are the unfortunate result of a local maximum in the > fitness landscape. > > www.ryanmarsh.com > > > > ------------------------------------------------------- > 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 > ------------------------------------------------------- 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
