DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=35723>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=35723 Summary: [betwixt] [PATCH] add support for non-public setters Product: Commons Version: unspecified Platform: Other OS/Version: other Status: NEW Severity: enhancement Priority: P3 Component: Betwixt AssignedTo: [email protected] ReportedBy: [EMAIL PROTECTED] I have a model where certain setters are protected in order to enforce a certain usage pattern. (Parent.addChild(child) calls child.setParent(this), so I don't want child.setParent public.) Anyway, I could not round-trip this model with Betwixt without changing the setters to public. The attached patch adds support for forcing a method accessible when using a custom updater, which solves my problem. I added this to an existing test case, which also shows its usage. The test as is wasn't working and was off, but I turned it back on and only removed the offending part. I don't know why it wasn't working but didn't get into it. I had to do with custom updaters for adders. This patch doesn't do anything for non-public collection adders. This patch does not cause any test failures, and solves my problem, but I'll let others judge how well it fits into the existing code and whether it fits the spirit of Betwixt. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
