Yup, you are right. I was confused since the example were talking about FooBar and Foo in the same context. Therefore I thought this was a more general question.
Sorry about the confussion! /Jakob > -----Opprinnelig melding----- > Fra: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] På vegne av [EMAIL PROTECTED] > Sendt: 18. september 2006 15:00 > Til: RIFE users list : questions, bug reports and suggestions. > Emne: Re: SV: [Rife-users] *MetaData classes and inheritance > > I'm also interested in this question.. > Note: I'm a different Fred than the Fred who asked this > question, just to avoid any confusion :) > > > You say you have FooBar that extends Foo. What has this to do with > > this question? > > It has everything to do with the question. FooBar and Foo are > the model classes, and FooBarMetaData and FooMetaData are the > classes that describe the constraints related to FooBar and > Foo. The idea is to instrument the model classes with meta > data while keeping that information separate from the model > classes. For this to work, the meta data classes > *must* be in the same package and have the same name with a > "MetaData" suffix. > > I think perhaps you misunderstood the question, because your > answer relates to general Java principles. However, as Fred > mentioned, there is more at work here, a classloader that > does some magic for you. > So this blurs the results. > > I also tried the same kind of scenario and had some > unexpected results, thus my interest in this question. > > Best regards, > Frederic > -- > > [EMAIL PROTECTED] > > _______________________________________________ > Rife-users mailing list > Rife-users@uwyn.com > http://lists.uwyn.com/mailman/listinfo/rife-users > _______________________________________________ Rife-users mailing list Rife-users@uwyn.com http://lists.uwyn.com/mailman/listinfo/rife-users
