XML Editor
Sign up for a WebBoard account Sign Up Keyword Search Search More Options... Options
Chat Rooms Chat Help Help News News Log in to WebBoard Log in Not Logged in
Show tree view Topic
Topic Page 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 Go to previous topicPrev TopicGo to next topicNext Topic
Postnext
Adam ShelleySubject: Using external XSLT processor
Author: Adam Shelley
Date: 08 Oct 2003 12:51 PM
Hello, I am having a problem with the built in Xalan-J parser. I used xalan 2.5.0 (from FOP) and it works fine but within SS it is causing a null pointer exception. I tried configuring it to use an external processor and it gives these settings:

command line c:\javalibs\xalan -IN file:///%1 -XSL %2 -OUT %3

Path c:\javalibs;c:\work

Classpath c:\javalibs\xalan-2.5.0.jar

if outputs the following error message:

External XSLT processing started...
Command line failed:
c:\javalibs\xalan -V -IN file:///"c:\work\TEST31.XML" -XSL "c:\work\STY2F3D.xsl" -OUT "C:\DOCUME~1\08Parts3\LOCALS~1\Temp\RES2F3E.boh" -DIAG
Initial Directory:
(null)

What to do?
Thanks,

-Adam

Postnext
Minollo I.Subject: Re: Using external XSLT processor
Author: Minollo I.
Date: 08 Oct 2003 01:06 PM
Adam,
I guess c:\javalibs\xalan is a batch file? You should change the command
line to reference c:\javalibs\xalan.bat in that case (or whatever the real
extension of the executable is).

Minollo

Postnext
Adam ShelleySubject: Re: Using external XSLT processor
Author: Adam Shelley
Date: 08 Oct 2003 01:12 PM
Hello, thanks for reply. Yes it is the batch file that comes packaged with fop. I tried with or without the batch file extension previously. I think the problem has to do with the "initial directory" being equal to "(null)". I think that if i find the setting that affects this it will work.

On another note: The null pointer reference went away using the built in processor. I ended up modifying the document slightly and then modifying it back to its original state ant it started working. *shrugs*.

Thanks
-Adam

Postnext
Adam ShelleySubject: Re: Using external XSLT processor
Author: Adam Shelley
Date: 08 Oct 2003 01:19 PM
Actually, I found that i modified it slightly differently:

This statement was causing the error:



(note depsite what this looks like while viewing this post: it was done in propper syntax.)

I modified it to this:



And it got rid of the error. This does work with Xalan 2.5.0 that came with FOP but has problems with SS.

Here is the exception stack:

java.lang.RuntimeException: java.lang.NullPointerExceptionTransformerException:

at: file:///c:/work/plds1.xsl 199

; SystemID: file:///c:/work/plds1.xsl; Line#: 199; Column#: 47

javax.xml.transform.TransformerException: java.lang.NullPointerException

at org.apache.xalan.transformer.TransformerImpl.executeChildTemplates(TransformerImpl.java:2329)

at org.apache.xalan.templates.ElemLiteralResult.execute(ElemLiteralResult.java:710)

at org.apache.xalan.transformer.TransformerImpl.executeChildTemplates(TransformerImpl.java:2324)

at org.apache.xalan.templates.ElemLiteralResult.execute(ElemLiteralResult.java:710)

at org.apache.xalan.transformer.TransformerImpl.executeChildTemplates(TransformerImpl.java:2324)

at org.apache.xalan.templates.ElemLiteralResult.execute(ElemLiteralResult.java:710)

at org.apache.xalan.transformer.TransformerImpl.executeChildTemplates(TransformerImpl.java:2324)

at org.apache.xalan.templates.ElemLiteralResult.execute(ElemLiteralResult.java:710)

at org.apache.xalan.templates.ElemForEach.transformSelectedNodes(ElemForEach.java:444)

at org.apache.xalan.templates.ElemForEach.execute(ElemForEach.java:300)

at org.apache.xalan.templates.ElemForEach.transformSelectedNodes(ElemForEach.java:444)

at org.apache.xalan.templates.ElemForEach.execute(ElemForEach.java:300)

at org.apache.xalan.transformer.TransformerImpl.executeChildTemplates(TransformerImpl.java:2324)

at org.apache.xalan.templates.ElemLiteralResult.execute(ElemLiteralResult.java:710)

at org.apache.xalan.templates.ElemApplyTemplates.transformSelectedNodes(ElemApplyTemplates.java:432)

at org.apache.xalan.templates.ElemApplyTemplates.execute(ElemApplyTemplates.java:215)

at org.apache.xalan.transformer.TransformerImpl.executeChildTemplates(TransformerImpl.java:2324)

at org.apache.xalan.transformer.TransformerImpl.applyTemplateToNode(TransformerImpl.java:2147)

at org.apache.xalan.transformer.TransformerImpl.transformNode(TransformerImpl.java:1203)

at org.apache.xalan.transformer.TransformerImpl.transform(TransformerImpl.java:665)

at org.apache.xalan.transformer.TransformerImpl.transform(TransformerImpl.java:1119)

at org.apache.xalan.transformer.TransformerImpl.transform(TransformerImpl.java:1097)

at com.exln.stylus.CXalanDriver.doProcessing(CXalanDriver.java:150)

at com.exln.stylus.CProcessorDriver.process(CProcessorDriver.java:55)

Caused by: java.lang.NullPointerException

at com.exln.stylus.CProcessorDriver.quoteValue(CProcessorDriver.java:1001)

at com.exln.stylus.CProcessorDriver.quoteValue(CProcessorDriver.java:986)

at com.exln.stylus.CXalanDriver.trace(CXalanDriver.java:344)

at org.apache.xalan.trace.TraceManager.fireTraceEvent(TraceManager.java:244)

at org.apache.xalan.trace.TraceManager.fireTraceEvent(TraceManager.java:174)

at org.apache.xalan.templates.ElemVariable.execute(ElemVariable.java:287)

at org.apache.xalan.templates.ElemForEach.transformSelectedNodes(ElemForEach.java:444)

at org.apache.xalan.templates.ElemForEach.execute(ElemForEach.java:300)

at org.apache.xalan.templates.ElemForEach.transformSelectedNodes(ElemForEach.java:444)

at org.apache.xalan.templates.ElemForEach.execute(ElemForEach.java:300)

at org.apache.xalan.transformer.TransformerImpl.executeChildTemplates(TransformerImpl.java:2324)

... 23 more


---------

java.lang.NullPointerException

at com.exln.stylus.CProcessorDriver.quoteValue(CProcessorDriver.java:1001)

at com.exln.stylus.CProcessorDriver.quoteValue(CProcessorDriver.java:986)

at com.exln.stylus.CXalanDriver.trace(CXalanDriver.java:344)

at org.apache.xalan.trace.TraceManager.fireTraceEvent(TraceManager.java:244)

at org.apache.xalan.trace.TraceManager.fireTraceEvent(TraceManager.java:174)

at org.apache.xalan.templates.ElemVariable.execute(ElemVariable.java:287)

at org.apache.xalan.templates.ElemForEach.transformSelectedNodes(ElemForEach.java:444)

at org.apache.xalan.templates.ElemForEach.execute(ElemForEach.java:300)

at org.apache.xalan.templates.ElemForEach.transformSelectedNodes(ElemForEach.java:444)

at org.apache.xalan.templates.ElemForEach.execute(ElemForEach.java:300)

at org.apache.xalan.transformer.TransformerImpl.executeChildTemplates(TransformerImpl.java:2324)

at org.apache.xalan.templates.ElemLiteralResult.execute(ElemLiteralResult.java:710)

at org.apache.xalan.transformer.TransformerImpl.executeChildTemplates(TransformerImpl.java:2324)

at org.apache.xalan.templates.ElemLiteralResult.execute(ElemLiteralResult.java:710)

at org.apache.xalan.transformer.TransformerImpl.executeChildTemplates(TransformerImpl.java:2324)

at org.apache.xalan.templates.ElemLiteralResult.execute(ElemLiteralResult.java:710)

at org.apache.xalan.transformer.TransformerImpl.executeChildTemplates(TransformerImpl.java:2324)

at org.apache.xalan.templates.ElemLiteralResult.execute(ElemLiteralResult.java:710)

at org.apache.xalan.templates.ElemForEach.transformSelectedNodes(ElemForEach.java:444)

at org.apache.xalan.templates.ElemForEach.execute(ElemForEach.java:300)

at org.apache.xalan.templates.ElemForEach.transformSelectedNodes(ElemForEach.java:444)

at org.apache.xalan.templates.ElemForEach.execute(ElemForEach.java:300)

at org.apache.xalan.transformer.TransformerImpl.executeChildTemplates(TransformerImpl.java:2324)

at org.apache.xalan.templates.ElemLiteralResult.execute(ElemLiteralResult.java:710)

at org.apache.xalan.templates.ElemApplyTemplates.transformSelectedNodes(ElemApplyTemplates.java:432)

at org.apache.xalan.templates.ElemApplyTemplates.execute(ElemApplyTemplates.java:215)

at org.apache.xalan.transformer.TransformerImpl.executeChildTemplates(TransformerImpl.java:2324)

at org.apache.xalan.transformer.TransformerImpl.applyTemplateToNode(TransformerImpl.java:2147)

at org.apache.xalan.transformer.TransformerImpl.transformNode(TransformerImpl.java:1203)

at org.apache.xalan.transformer.TransformerImpl.transform(TransformerImpl.java:665)

at org.apache.xalan.transformer.TransformerImpl.transform(TransformerImpl.java:1119)

at org.apache.xalan.transformer.TransformerImpl.transform(TransformerImpl.java:1097)

at com.exln.stylus.CXalanDriver.doProcessing(CXalanDriver.java:150)

at com.exln.stylus.CProcessorDriver.process(CProcessorDriver.java:55)



Postnext
Minollo I.Subject: Re: Using external XSLT processor
Author: Minollo I.
Date: 08 Oct 2003 01:36 PM
This does sound like a bug in Stylus. What Stylus Studio version are you using?

Thanks,
Minollo

Postnext
Adam ShelleySubject: Re: Using external XSLT processor
Author: Adam Shelley
Date: 08 Oct 2003 02:15 PM
5.0 127e evaluation version. Yeah, it does seem like a bug. I'm just glad that it didn't stop me from using the product because it is really saving me alot of time. We have already bought one version of it. Its great.

:)

-Adam

Postnext
Adam ShelleySubject: Re: Using external XSLT processor
Author: Adam Shelley
Date: 08 Oct 2003 04:40 PM
I've been able to reproduce this error in a couple of places so if anyone working on this software would like me to acquire more information about the problem send me an email outlining the all that is required and I'll get it to you.

-Adam

Postnext
Ivan PedruzziSubject: RE: Using external XSLT processor
Author: Ivan Pedruzzi
Date: 08 Oct 2003 04:57 PM

Adam,

We are testing the fix on the internal build, please send us other
testcases if different from the one you described.

Ivan


> -----Original Message-----
> From: stylus-studio-tech Listmanager
> [mailto:listmanager@edn.exln.com]
> Sent: Wednesday, October 08, 2003 5:04 PM
> To: Recipients of 'stylus-studio-tech' suppressed
> Subject: Re: Using external XSLT processor
>
>
> From: "Adam Shelley"
>
> I've been able to reproduce this error in a couple of places
> so if anyone working on this software would like me to
> acquire more information about the problem send me an email
> outlining the all that is required and I'll get it to you.
>
> -Adam
>
>
>
> To reply: mailto:stylus-studio-tech.7065@edn.exln.com
> To start a new topic: mailto:stylus-studio-tech@edn.exln.com
> To login: http://edn.exln.com/~SSDN
>

Posttop
Minollo I.Subject: Re: Using external XSLT processor
Author: Minollo I.
Date: 08 Oct 2003 05:02 PM
We have identified and fixed the error.
We'll make an updated build available as soon as possible.

Thanks,
Minollo

 
Topic Page 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 Go to previous topicPrev TopicGo to next topicNext Topic
Download A Free Trial of Stylus Studio 6 XML Professional Edition Today! Powered by Stylus Studio, the world's leading XML IDE for XML, XSLT, XQuery, XML Schema, DTD, XPath, WSDL, XHTML, SQL/XML, and XML Mapping!  
go

Log In Options

Site Map | Privacy Policy | Terms of Use | Trademarks
Stylus Scoop XML Newsletter:
W3C Member
Stylus Studio® and DataDirect XQuery ™are from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2016 All Rights Reserved.