I think the subclassing suggestion is the easiest.
public class subclass extends superclass implements
theInterface {
// empty class declaration
}
-Richard
--- "Frank W. Zammetti" <[EMAIL PROTECTED]> wrote:
> It's funny, I started writing up an example with a
> subclass and an
> implemented interface and cloning and so on and so
> forth and as I got near
> the end I said "wait, this is stupid, just loop
> through with reflection as
> I and others suggested yesterday!"... Sometimes the
> "brute force" method
> really *is* the simplest and easiest :)
>
> --
> Frank W. Zammetti
> Founder and Chief Software Architect
> Omnytex Technologies
> http://www.omnytex.com
> AIM: fzammetti
> Yahoo: fzammetti
> MSN: [EMAIL PROTECTED]
>
> On Fri, October 28, 2005 3:56 pm, Dave Newton said:
> > Mick Knutson wrote:
> >
> >>Because I would have to modify generated code to
> do that. And it only
> >>implements serializable. Nothing else.
> >>
> >>
> > And you can't subclass it and have the subclass
> implement the interface?
> >
> > In any case, just loop through w/ reflection and
> check.
> >
> > I'm still confused though; are you calling methods
> on these classes
> > through reflection, which is why you won't catch
> these issues during
> > compilation?
> >
> > Dave
> >
> >
> >
> >
>
---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> [EMAIL PROTECTED]
> > For additional commands, e-mail:
> [EMAIL PROTECTED]
> >
> >
>
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> [EMAIL PROTECTED]
> For additional commands, e-mail:
> [EMAIL PROTECTED]
>
>
__________________________________
Yahoo! Mail - PC Magazine Editors' Choice 2005
http://mail.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
