Peter Royal wrote: > > see > http://www.mail-archive.com/avalon-dev@jakarta.apache.org/msg05192.html > for the most recent thread on this. > > It appears that the SourceResolver never made it out of scratchpad.
Yupp, I just started with integrating the SourceResolver back into Cocoon. The current CVS of Cocoon is able to use the SourceResolver but I'm not happy with the Source/ModifiableSource etc. interfaces and wanted to start a discussion about this topic this week as soon as I get time for it. I hope to get it out of scratchpad either this or next week. > > I have a need for cocoon's XSLTProcessor outside of Cocoon and > thus I will > port that this afternoon. Great! Carsten > Its only component dependencies are > upon the Store > and SourceResolver. Since Store support is optional I will just > leave that > bit unimplemented for now. Is org.apache.avalon.excalibur.xml.xslt a good > package name? > > It also uses org.apache.cocoon.util.ClassUtils, and harm in moving that > pretty much as-is to org.apache.avalon.excalibur.util.ClassUtils? > -pete > > -- > peter royal -> [EMAIL PROTECTED] > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
