> Has anyone in here already successfully tackled such a problem ? "Successful" is probably a bit too much for me to claim, but I managed to hack my way out of a circular reference problem. It's quite likely this is specific to my scenario, but I was making decisions by analysing classes, and when I had a circular reference (e.g. between j.l.Class and j.l.Constructor) I basically deferred the decision until all the other information had been collected, and hoping that it could be made in spite of the circular reference. Fortunately in my scenario, the problem didn't appear to often, so this has sufficed so far.
It is however, really hacky, and I'd love to hear about general solutions for tackling circular references. +1, Good question. Regards, Graham Allan -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
