Ah, this is for debugging a PDF transform. I think I may be missing a key concept (I've never actually used the XSLT debugger before). I set the XSL file to be the root of my transform in my dev area and the XML file to be the resolved map produced in the temp directory by the Toolkit. In this case, the D4P HTML2 transform, the transform is applied to the map and then does everything. When I try to run it, I get the same issue with resolving the Java extension functions, so clearly the jar is not configured, but I didn't see a place to add that configuration for the debug transform or a way to select a transformation scenario for the debugging. Does this mean I have to copy dost.jar in the Oxygen lib/ dir? I'm trying to avoid that because I am constantly updating the Toolkit under Oxygen so it's easy to forget to copy over the dost.jar file when I put in a new version. Cheers, E. On 11/19/12 8:47 AM, "Oxygen XML Editor Support" <support@oxygenxml.com> wrote:
Hi Eliot,
We'll have it as a topic in the Oxygen User Guide on our web site. Until then, I published the topic to PDF, please see attached.
Regards, Radu
Radu Coravu <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com
On 11/19/2012 4:28 PM, Eliot Kimber wrote:
At the Oxygen User Meetup George presented how to debug Toolkit transforms using the Oxygen debugger. Apparently I wasn't paying close attention because now I can't remember how to do it.
Is George's presentation available somewhere or is the process documented somewhere?
Thanks,
E.
-- Eliot Kimber Senior Solutions Architect, RSI Content Solutions "Bringing Strategy, Content, and Technology Together" Main: 512.554.9368 www.rsicms.com www.rsuitecms.com Book: DITA For Practitioners, from XML Press, http://xmlpress.net/publications/dita/practitioners-1/