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=39349>. 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=39349 ------- Additional Comments From [EMAIL PROTECTED] 2006-04-25 09:04 ------- Sean, Thank you for your informative reply. I understand, why (1) is not an option at the moment. But from looking at the code, maybe you could reconsider (2). I think there is a solution that does not require the kind of class restructuring that you suggest. Currently, the org.jcp.xml.dsig.internal.dom.ApacheTransform class acts as the glue between the JSR105 and the Apache implementation. In the 'transformIt' method of this class, the respective Apache Transform is instantiated. It is in this method, where both the XMLCryptoContext and the Apache Transform Impl would be available at the same time. There it would be possible to set a URIResolver (that is a wrapper over the URIDereferencer of the XMLCryptoContext) to the Apache Transform object - provided such a setter is added to the class, which shouldn't be a problem because it doesn't break compatibility. In the Apache TransformXSLT 'enginePerformTransform' method the URIResolver would be accessible via _transformObject.getURIResolver(). What do you think about that? regards, Patrick -- 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.
