[ https://issues.jboss.org/browse/JASSIST-144?page=com.atlassian.jira.plugi... ] Shigeru Chiba commented on JASSIST-144: --------------------------------------- Hmm... any good work-around? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JASSIST-144?page=com.atlassian.jira.plugi... ] Paul Pogonyshev edited comment on JASSIST-144 at 8/23/11 11:27 AM: ------------------------------------------------------------------- Maybe in the long run you should deprecate {{ProxyObject}} and create a new interface {{Proxy}}. Replacement methods for {{getHandler}} and {{setHandler}} would accept a dummy argument of type declared in the Javassist package, so these wouldn't clash with actual user methods. Also, you should probably avoid Java pseudo-property argument convention to avoid this stuff from shining through {{java.beans.Introspector}}. Don't see any solution without breaking back-compatibility. was (Author: doublep): Maybe in the long run you should deprecated {{ProxyObject}} and create a new interface {{Proxy}}. Replacement methods for {{getHandler}} and {{setHandler}} would accept a dummy argument of type declared in the Javassist package, so these wouldn't clash with actual user methods. Also, you should probably avoid Java pseudo-property argument convention to avoid this stuff from shining through {{java.beans.Introspector}}. Don't see any solution without breaking back-compatibility. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JASSIST-144?page=com.atlassian.jira.plugi... ] Steve Ebersole commented on JASSIST-144: ---------------------------------------- Personally, I think the best approach is a method whose name does not match the Java Bean spec where that method is likely to get mixed in with such a bean. Something like {{obtainHandler}} or if you want to make it explicitly clear that this is a mixed-in method {{$$$obtainHandler$$$}} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JASSIST-144?page=com.atlassian.jira.plugi... ] Steve Ebersole commented on JASSIST-144: ---------------------------------------- For my own reference (sanity) and background see https://hibernate.onjira.com/browse/HHH-5731 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JASSIST-144?page=com.atlassian.jira.plugi... ] Steve Ebersole commented on JASSIST-144: ---------------------------------------- Well considering the API ({{ProxyObject#setHandler}}) is in fact the problem, I also do not see how you can do this without changing the API :) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JASSIST-144?page=com.atlassian.jira.plugi... ] Shigeru Chiba closed JASSIST-144. --------------------------------- -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JASSIST-144?page=com.atlassian.jira.plugi... ] Shigeru Chiba commented on JASSIST-144: --------------------------------------- If a target class has getHandler, Javassist does not add getHandler(). So proxifying that class does not cause any problem. On the other hand, since setHandler added by Javassist takes a javassist.util.proxy.MethodHandler object, it should be able to coexist with other setHandler methods, which take different type of parameters. I mean, it would safely overload other setHandler methods. Sorry, this workaround is slightly complex but I hope the description above makes the trick clear. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira