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=40512>. 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=40512 ------- Additional Comments From [EMAIL PROTECTED] 2006-09-14 17:06 ------- > What do you think? I think your reasons for the new method are good! But I still think we need to preserve compatibility (esp. binary). This change breaks binary compat in a service provider API that has been in XMLSec since the first release. Users should be able to depend on that API (especially since it was designed for them to plug in their own Transform implementations) being stable over the long run. Compatibility is really important IMHO across all APIs. We have too many users now, they need to be able to trust us that this software will continue to work and they don't have to keep modifying their code to keep up with the latest revisions. And maybe we should start thinking about starting an XMLSec 2 that cleans up some of these issues and ties better with JSR 105 and streaming implementations :) > The only main problem with your solution is that when someone want to create a > Transform the compiler will not force to implement any method. True. We could log a warning though if it throws an UnsupportedExc. > If there is enough push for the 3. I will implement this. But I still think it > should be better to document the change. > > Regards, > Raul -- 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.
