[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: JAXP Saxon Extensions and Java Objects
Michael Kay wrote: Yes, it looks like this will work nicely. We did a test just setting the objects as jaxp parameters as usual and the picking them up from the Controller object. However, it took be a few minutes to realize that the parameters stored in the controller are wrapped in Saxon classes of thier own. But once I caught on it was smooth sailing. One question, why are there "UserData" and "Parameters" in Saxon? What is "UserData" usually used for?I've got several java objects I'd like to hand to an extension behind the scenes. In theory I could hand them as parameters to the transformer and set them in attributes of my extension element. But a more elegant solution would be to get them somehow into the Context.getController().getUserData(...) hash via some method I'm hoping is available in Saxon for this. Or a method that might exist in JAXP as well? Please, any tips would be great. We're starting on some extension packages for Saxon now, roughly just interfaces for the following libraries: The Servlet API's javax.servlet.http.HttpServletRequest, javax.servlet.http.HttpServletResponse, javax.servlet.http.HttpSession, javax.servlet.ServletContext and JNDI's javax.naming.directory.DirContext (with both read and write capabilities). Why? you might ask. Because we want these capabilities in XSLT without the overhead of other product architectures (Apache Cocoon and the like). This will just be a small set of classes to extend the capabilities of Saxon into the JSP/Servlet Realm. -Mark XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|