this sounds like a bug. the current way that betwixt rulesets work are about to be refactored so (personally speaking) i'm unlikely to fix this. of course, there's nothing to stop you (or anyone else) patching it yourself ;)
i had hoped to get on with refactoring this really soon but unfortunately the ASF is short of bandwidth at the moment and i'm spending a lot of time at the moment moving releases onto mirrors and archiving old releases. hopefully i'll able to get back to coding again next week if you're able to wait that long. otherwise, you could try the alpha1 release.
- robert
On Tuesday, September 2, 2003, at 03:12 AM, Daniel McAllansmith wrote:
Hi,
I'm using the latest (20030901) snapshot of betwixt.
When I register a bean class, that indirectly references itself via another
bean class, betwixt ends up recursing forever adding rules.
For example, ABean holds a Collection of members of type BBean, where BBean
has a property of type ABean holding its container.
In this situation I end up with repeated calls into
BeanRuleSet.addRule(String, Rule, ElementDescriptor, ReadContext) and
BeanRuleSet.addChildRules(String, ElementDescriptor, ReadContext) with
sucessively longer paths -
ABean/members/member/container/members/member/container...
So, is this just a bug in the BeanRuleSet code or is there some explicit mechanism I should be using to avoid the recursion?
Thanks Daniel
--------------------------------------------------------------------- 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]
