[
https://issues.jboss.org/browse/JASSIST-144?page=com.atlassian.jira.plugi...
]
Paul Pogonyshev commented on JASSIST-144:
-----------------------------------------
Actually, a client can use a new boolean property on {{ProxyFactory}} to decide if he
wants current {{ProxyObject}} interface (with this problem, the default), or a new
{{Proxy}} interface which wouldn't have this bug. This way only aware clients will
notice the change at all and thus there will be no compatibility break. Updated clients,
e.g. Hibernate, can require Javassist >= 3.where-this-is-released, then set
{{useNewProxyInterface}} or whatever property on {{ProxyFactory}} they use and then drop
usage of {{ProxyObject}} completely. Old clients will not notice anything.
ProxyObject#setHandler interferes with business methods of the same
name
------------------------------------------------------------------------
Key: JASSIST-144
URL:
https://issues.jboss.org/browse/JASSIST-144
Project: Javassist
Issue Type: Feature Request
Affects Versions: 3.12.0.GA
Reporter: Steve Ebersole
Assignee: Shigeru Chiba
Being reported by Hibernate/JPA users ->
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