jgoodyear commented on PR #1784: URL: https://github.com/apache/cxf/pull/1784#issuecomment-2040206237
I've been diving deep into a more generic methodology. I'm beginning to hit a fundamental problem; when we detect, regardless of ordering, getter/setter pairs with correct signatures, we end up finding matches on IBM and the other JVMs, hence failing the testMismatchedOverriddenBeans test case (it expects due to ordering to not have a pair). The check pairs routine is predicate on the ordering being a specifically lined up in order to not throw the illegal argument exception. This leads to the question - if we ignore ordering, then the check routine will not throw an exception in our testMismatchedOverriddenBeans test case. We can throw an exception if NO pairing is found to be possible. Should that be the correct behavoir for BeanSpector? Otherwise, we're back to having to decide an ordering of methods from Class.getMethods for the behavoir to be 'correct'. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
