[oXygen-user] debugging a java extension?

Kai Hackemesser
Wed May 16 06:22:22 CDT 2007


Hi, Sorin,

I tried so - created a Logger:

    private static Logger log = Logger.getLogger(FlightPlanHelper.class
            .getName());
    static {
        try {
            log.addHandler(new FileHandler());
        } catch (SecurityException e) {
            // TODO Auto-generated catch block
            e.printStackTrace();
        } catch (IOException e) {
            // TODO Auto-generated catch block
            e.printStackTrace();
        }
    }

    public static String getAddressContent(NodeList addressNodes) {
        log.info("called getAddressContent");
.....

But the logger never writes a file - I don't get any error message, 
either. any Idea? Currently using the xalan transformer and the method 
is called in the xsl.

Kai

Sorin Ristache schrieb:
> Hello,
>
> The XSLT Debugger does not step into the Java extensions of the XSLT 
> processor. We have this feature logged as an enhancement request but 
> it was not implemented yet. I recommend generating debug output to a 
> text file from the Java class.
>
>
> Regards,
> Sorin
>
>
> Kai Hackemesser wrote:
>> Hi!
>>
>> I try to debug a stylesheed transformation using Saxon 6.5.5. I wrote 
>> a small java extension class as transformation helper. I now receive 
>> a Nullpointer from within (it's still in development). Is there a 
>> possibility to debug the java class while stepping through the XSLT 
>> Debugger?
>>
>> Kind regards,
>> Kai
>
> _______________________________________________
> oXygen-user mailing list
> 
> http://www.oxygenxml.com/mailman/listinfo/oxygen-user
>
>




More information about the oXygen-user mailing list