On Friday, October 18, 2002, at 07:22 PM, Greg Steuck wrote:
Paul> It /could/ be recoded slightly to drill into parent classesthis is about the use-case that i had. i think the main situations where it may be useful will involve the block being a container itself...
Paul> (qdox makes that easy), but I suspect there are more reasons
Paul> against than for.
Hmm, I just found a good reason for:
class AbstractFoo {
/**
* @phoenix:dependency name="MyService"
*/
public void service(ServiceManager manager) {
// does everything service() needs to do for
// all extending classes
}
}
/**
* @phoenix:block
*/
class BlockFoo {
// No way I could find to specify dependencies here
// short of overriding service with a dummy one calling
// super.service()
}
So I guess drilling down for dependencies (and maybe services) is a good
thing after all.
paul, is that feasible with qdox?
-pete
--
To unsubscribe, e-mail: <mailto:avalon-dev-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:avalon-dev-help@;jakarta.apache.org>
