This is a lot of code to go through just to see what you are trying to do.
You can always go the long way, which is to simply issue a change in this field on every possible listener attached to the ones controlling it. There are alternatives as well depending on the overall picture, things like DocumentListeners and change listeners can be added to work the other way around. So instead of directly calling a change to acomponent.setText for example, you then chain the .addDocumentListener to a JTextField's document, so whenever it changes you can capture the change in the documentlistener handler. That can then be used to control another textfield, so this has the benefit of keeping them separate so that a change in xJTextField doesn't need to concern itself with changing yJTextField. If that makes sense. You can do it with straight action listeners themselves as well, these are stackable event handlers, so one is triggered and then the next, and so on. It just depends on exactly what you want to do for what you want to change. I typically use change and action listeners over most other types, but if I were doing something like a pattern match for input (I've done this with barcode scanners for example), I use documentlisteners to trigger as the text is being input into the field instead of needing to click something.
header('HTTP/1.1 420 Enhance Your Calm');