>Isn't it worth the extra ease of use to teach WKTXSerializer that an >onXXX attribute indicates a listener method addition and it should >search through the available listener interfaces to find a matching >method?
But how would it know where to look, and which interfaces constituted "listener" interfaces? I think Todd's solution is pretty elegant, and I don't think that users will find it difficult to use, especially since the syntax is consistent with other WTKX constructs (specifically, static setters).
