On 2010-07-08 17.43, Stanislav Muhametsin wrote:
Actually, now that I'm thinking about it, it might get too confusing between using class cast and getRole(...). At least at the start. Maybe the class casting as getting a role could be dropped altogether in favor of getRole(...) method, which could do all the checking? Would it be too cumbersome or inefficient?
We had something like that in the beginning, but dropped it. What is the usecase you're looking at for having this?
/Rickard _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
